[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] uclinux port to Multimedia board
Hi,
the value of the variable ticks in linux-2.4.x/init/main.c is allways
the same (0), i think that the problem comes from the timer, but i can't
find it. I checked the xparameters.h file and everything seems right.
The CPU_CLK_FREQ is set with the correct value.
with the bogomips computation loop commented, i was abble to boot
further, and the system hangs after : Freeing init memory. Maybe those
problems are connected.
Thanks,
Didier
Christopher John Comis wrote:
> Hi John, Didier and Mark,
>
> Sorry about my delayed response.
>
> John, I made the corrections you indicated. The system still hangs as it
> did before. However, now I get 2048 pages, whereas before I only had 256 :)
>
> On node 0 totalpages: 2048
> zone(0): 2048 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
>
> Didier and Mark, Mark is correct in that I have 32 bits. However, only 19
> of them are mapped to the ZBT pins. I am using the zbtio peripheral, which
> was created by someone in my lab. I am not too familiar with the
> opb_zbt_controller, although I am thinking, as a next step, to try this
> peripheral instead of my zbtio core. Have either of you managed to get
> uClinux running with this peripheral?
>
> As a side note, I hacked into the OS a bit deeper. The time_init function
> (and all subsequent timer initialization) functions are executing correctly.
> After these, I can use the get_irq_list(char *) function, and get the
> following output:
> CPU0
> 0: 0 XINTC timer
> ERR: 0
>
> This function doesn't say a whole lot, other than the interrupt is there.
>
> I can see the timer is working and the interrupt controller is generating an
> interrupt to the processor. However, neither of the functions
> handle_IRQ_event or handle_irq are called.
>
> Like Didier and Mark both alluded to, I'm going to look into the memory a
> bit further. If that is certainly not the problem, I'll likely look into
> the interrupt routines in entry.S, and see if those are being accessed.
>
> Any further advice would be greatly appreciated.
>
> Thanks!
> Chris
>
>
>
>>-----Original Message-----
>>From: owner-microblaze-uclinux@itee.uq.edu.au [mailto:owner-microblaze-
>>uclinux@itee.uq.edu.au] On Behalf Of John Williams
>>Sent: October 24, 2004 10:53 PM
>>To: microblaze-uclinux@itee.uq.edu.au
>>Subject: Re: [microblaze-uclinux] uclinux port to Multimedia board
>>
>>Hi Christopher,
>>
>>Christopher John Comis wrote:
>>
>>
>>>I am wondering if any of you could please help me out. I am trying to
>>
>>port
>>
>>>to the Xilinx Multimedia board. I made several modifications to
>>
>>accommodate
>>
>>>the mbvanilla platform to my board:
>>
>>>- I set 1MB of my ZBT RAM to base address 0xFE000000-0xFEFFFFFF
>>>- I set 8MB of my ZBT RAM to base address 0xFF000000-0xFF7FFFFF (note
>>
>>that
>>
>>>this memory is actually divided across 4x2MB banks)
>>
>>I see you posted a correction to this address map. So, the physical
>>address map is
>>
>>1MB at 0xffe00000 - 0xffefffff
>>8MB at 0xff000000 - 0xff7fffff
>>
>>Is this correct?
>>
>>[snip]
>>
>>
>>>I made the following modifications to the uclinux platform:
>>>- I adjusted mbvanilla.h as follows:
>>>#define ERAM_ADDR 0xFFE00000
>>>#define ERAM_SIZE 0x00100000
>>>- I adjusted the address space of mbvanilla.ld as follows:
>>>OPB : ORIGIN = 0xFFE00000, LENGTH = 0x00100000
>>
>>This will squish the entire Linux system (kernel + user space memory +
>>file system) into a 1MB block based at 0xffe00000. The 8MB block from
>>0xff000000 will be completely invisible to the kernel.
>>
>>Is that your intention?
>>
>>Putting the entire kernel + filesystem + user space into 1MB when you
>>have 8MB available doesn't make a lot of sense to me, but perhaps you
>>have something else in mind for the 8MB block at 0xff000000?
>>
>>This may or may not be causing the errors you are seeing, but you should
>>confirm what you are trying to do.
>>
>>To simplify things at first, I recommend you change ERAM_START and
>>ERAM_SIZE to 0xff000000 and 0x00800000 respectively, and similarly in
>>the link script.
>>
>>One other thing, after you make changes in the link script, you should
>>manually delete the file linux-2.4.x/linux.ld - I'm not certain that the
>>auto-dependencies are correct, so you might end up linking with an old
>>version.
>>
>>Cheers,
>>
>>John
>>___________________________
>>microblaze-uclinux mailing list
>>microblaze-uclinux@itee.uq.edu.au
>>Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>>Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-
>>uclinux/
>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/