[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] Petalogix MMU build

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] Petalogix MMU build
From: Michal Simek <michal.simek@xxxxxxxxxxxxx>
Date: Mon, 30 Mar 2009 11:30:55 +0200
In-reply-to: <49D084B3.30202@xxxxxxxxxx>
References: <49CC9734.9020205@xxxxxxxxxx> <49CC9D2A.5050607@xxxxxxxxxxxxx> <49CCC17F.4070703@xxxxxxxxxx> <49CCCD64.2040202@xxxxxxxxxx> <49D084B3.30202@xxxxxxxxxx>
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20081001)

Hi Finn,


> OK, after some days of frustrating experimenting it seems that the
> reason why the MMU kernel was not starting up properly, was because of
> an early interrupt from a GPIO core that was in the system which has the
> interrupt feature enabled.
> The startup monitor code (pre u-boot) enabled the power supply to the
> display on the board and that apparently triggered an interrupt at a
> very early stage when it's later enabled in the linux driver.
> It's supposed to be sensitive to inputs only - but with xilinx code and
> doc you never know... I'll check the VHDL some day.
> 
> The early interrupt made the kernel panic (without any console output,
> not even with debug enabled AND with a uart_simple port..) - had to see
> that by using xmd and see where the cpu was looping and then looking it
> up in the kernel map file.

This seems to me weird because linux kernel disable irq till intc is ready.
Which MB version do you use?

Thanks,
Michal

> 
> So the GPIO irq has been removed for now....
> I have actually managed to hit the 16-plb slave device limit of the
> plb_v20 core, so there's no room for a watch-dog until I generate
> another PLB port on the MPMC controller (which I should anyway).
> 
> Regards,
> 
> Finn
> 
> 
> Finn Stadel Nielsen skrev:
>> OK I've been doing some experimenting:
>>
>> It seems that if the linux image (linux.bin) is downloaded via xmd, it
>> boots ok. But if loading image.ub and running it with bootm or loading
>> linux.bin and using go, then things go wrong.
>> That indicates to me that something is not reset in the linux startup
>> sequence. It is working in non-MMU configs, so what has changed.. ??
>> I'll see if I can figure it out..
>>
>> Regards,
>>
>> Finn
>>
>> Finn Stadel Nielsen skrev:
>>> Hi Michal,
>>>
>>> I did turn it on:
>>>
>>> ---
>>> # Serial drivers
>>> #
>>> CONFIG_SERIAL_8250=y
>>> CONFIG_SERIAL_8250_CONSOLE=y
>>> CONFIG_SERIAL_8250_NR_UARTS=1
>>> CONFIG_SERIAL_8250_RUNTIME_UARTS=1
>>> # CONFIG_SERIAL_8250_EXTENDED is not set
>>>
>>> #
>>> # Non-8250 serial port support
>>> #
>>> # CONFIG_SERIAL_UARTLITE is not set
>>> CONFIG_SERIAL_CORE=y
>>> CONFIG_SERIAL_CORE_CONSOLE=y
>>> CONFIG_UNIX98_PTYS=y
>>> CONFIG_LEGACY_PTYS=y
>>> CONFIG_LEGACY_PTY_COUNT=256
>>> ---
>>>
>>> also:
>>>
>>> -- 
>>> CONFIG_XILINX_UART16550_0_INSTANCE="RS232"
>>> CONFIG_XILINX_UART16550_0_BASEADDR=0xFFFE8000
>>> CONFIG_XILINX_UART16550_0_HIGHADDR=0xFFFE9FFF
>>> CONFIG_XILINX_UART16550_0_IS_A_16550=1
>>> CONFIG_XILINX_UART16550_0_HAS_EXTERNAL_XIN=0
>>> CONFIG_XILINX_UART16550_0_HAS_EXTERNAL_RCLK=0
>>> CONFIG_XILINX_UART16550_0_SPLB_AWIDTH=32
>>> CONFIG_XILINX_UART16550_0_SPLB_DWIDTH=64
>>> CONFIG_XILINX_UART16550_0_SPLB_P2P=0
>>> CONFIG_XILINX_UART16550_0_SPLB_MID_WIDTH=2
>>> CONFIG_XILINX_UART16550_0_SPLB_NUM_MASTERS=3
>>> CONFIG_XILINX_UART16550_0_SPLB_NATIVE_DWIDTH=32
>>> CONFIG_XILINX_UART16550_0_SPLB_SUPPORT_BURSTS=0
>>> CONFIG_XILINX_UART16550_0_FAMILY="spartan3e"
>>> CONFIG_XILINX_UART16550_0_HW_VER="2.00.b"
>>> CONFIG_XILINX_UART16550_0_IRQ=5
>>> CONFIG_XILINX_UART16550_0_CLOCK_HZ=75000000
>>> -- 
>>> CONFIG_UART16550=1
>>> CONFIG_STDINOUT_BASEADDR=0xFFFE8000
>>> CONFIG_XILINX_ERAM_START=0x80000000
>>> CONFIG_XILINX_ERAM_SIZE=0x04000000
>>> CONFIG_XILINX_FLASH_START=0xf0000000
>>> CONFIG_XILINX_FLASH_SIZE=0x08000000
>>> CONFIG_XILINX_FLASH_WIDTH=16
>>> CONFIG_XILINX_FLASH_DATAWIDTH_MATCHING=1
>>> CONFIG_XILINX_LMB_START=0x00000000
>>> CONFIG_XILINX_LMB_SIZE=0x00004000
>>> CONFIG_XILINX_CPU_CLOCK_FREQ=75000000
>>> -- 
>>>
>>>
>>> Is there any requirement on the location of the peripheral base
>>> addresses  ? - I also noticed that the MMU examples have the base
>>> address below system memory. For example:
>>>
>>> CONFIG_STDINOUT_BASEADDR=0x84000000
>>> CONFIG_XILINX_ERAM_START=0x8c000000
>>> CONFIG_XILINX_ERAM_SIZE=0x02000000
>>> CONFIG_XILINX_FLASH_START=0x90000000
>>> CONFIG_XILINX_FLASH_SIZE=0x01000000
>>>
>>> It's strange that there is absolutely no output at all..
>>> U-boot works fine by the way.
>>>
>>> Regards,
>>>
>>> Finn
>>>
>>> Michal Simek skrev:
>>>> Hi Finn,
>>>>
>>>>  
>>>>> Hello all,
>>>>>
>>>>> Is the 16550 UART supported in a MMU configuration ?
>>>>> I noticed that all the MMU refecrence platforms use the uartlite as
>>>>> console and when running a MMU linux on my platform, there's no output
>>>>> to the console of any kind...
>>>>>     
>>>>
>>>> Yes it is. Just turn on uart16550 in linux menuconfig and disable
>>>> uartlite.
>>>> There is only missing early_printk features.
>>>>
>>>> CONFIG_SERIAL_8250=y
>>>> CONFIG_SERIAL_8250_CONSOLE=y
>>>>
>>>>
>>>> Thanks,
>>>> Michal
>>>>
>>>>  
>>>>> Finn
>>>>> ___________________________
>>>>> microblaze-uclinux mailing list
>>>>> microblaze-uclinux@xxxxxxxxxxxxxx
>>>>> Project Home Page :
>>>>> http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>>>>> Mailing List Archive :
>>>>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>>>>
>>>>>
>>>>>     
>>>>
>>>>  
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database:
>>>> 270.11.30/2026 - Release Date: 03/27/09 07:13:00
>>>>
>>>>   
>>>
>> ___________________________
>> microblaze-uclinux mailing list
>> microblaze-uclinux@xxxxxxxxxxxxxx
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database:
>> 270.11.30/2026 - Release Date: 03/27/09 07:13:00
>>
>>   
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> 
> 

-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

References:
- [microblaze-uclinux] Petalogix MMU build
  - From: Finn Stadel Nielsen
- Re: [microblaze-uclinux] Petalogix MMU build
  - From: Michal Simek
- Re: [microblaze-uclinux] Petalogix MMU build
  - From: Finn Stadel Nielsen
- Re: [microblaze-uclinux] Petalogix MMU build
  - From: Finn Stadel Nielsen
- Re: [microblaze-uclinux] Petalogix MMU build
  - From: Finn Stadel Nielsen

Prev by Date: Re: [microblaze-uclinux] ETHERNET LITE not recognized
Next by Date: Re: [microblaze-uclinux] ETHERNET LITE not recognized
Previous by thread: Re: [microblaze-uclinux] Petalogix MMU build
Next by thread: [microblaze-uclinux] Unknown opcode error
Index(es):
- Date
- Thread