[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Problem with 2nd stage bootloader (u-boot)
Hi John!
John Williams wrote:
> If you read from the address (using u-boot's memory read
> command or xmd) do you get 0xffffffff at flash addresses (ie
> blank flash data)?
This is what I get:
U-Boot> md 0x28000000
28000000: ffff0008 aa99ffff 2000ffff 3000ffff ........ ...0...
28000010: 0000ffff 2000ffff 2000ffff 3001ffff .... ... ...0...
28000020: 0004ffff 3001ffff 0167ffff 3000ffff ....0....g..0...
28000030: 0000ffff 2000ffff 3000ffff 0000ffff .... ...0.......
28000040: 3000ffff 0000ffff 2000ffff 2000ffff 0....... ... ...
28000050: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
28000060: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
28000070: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
28000080: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
28000090: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000a0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000b0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000c0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000d0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000e0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
280000f0: 2000ffff 2000ffff 2000ffff 2000ffff ... ... ... ...
The patterns of the upper 16 bits are familiar to me, thats
exactly what I read every time when I tried to write my own
bootloader. The lower 16 bits were always correct (half words of
the data I wrote to flash before).
I think one of the chips is broken or something like that.
> Perhaps you can modify the ML401 design to use only 16-bit wide
> flash, and change the UCF file to point the lower 16 bits of
> the flash data to either chip.
Hm, sounds like a good idea. Half of the flash should be enough.
I'm trying that now but I takes a while till XPS finishes. I'll
tell you if that worked.
> > I think (and hope) Impulse C will create code which is using
> > the FSL driver automatically because they say in that in
> > their book.
> You should be able to use the generic FSL fifo driver to talk
> to impulse perhperals. Remember FSL fifo driver is just raw IO
> - if there's any data-level protocol (such as packet start/stop
> commands) required by the Impulse coprocessors, it's your
> applications responsibiiliy to generate them.
I'll keep that in mind!
> There is an LCD driver for PPC linux that works on the ML403
> board - it should work OK on the ML401 with MicroBlaze but I've
> never tried it.
Ok, then I'll try. If it should not work, do you maybe have an
other idea what I could do? I want to do the following as some
kind of investigation:
1. Do something with the hardware using software running on
uCLinux (in eg text on the LCD, blinking leds, etc.)
2. Do the same thing but this time in hardware (custom IP)
I want to generate both applications using Impulse C and split it
to two processes. One is generating sending data and the other
one receives it and does something with the hardware according to
the data it received. In the second case one of the process is a
hardware process.
The "doing something in hardware" part of if should be as simple
as possible so if it is possible to avoid writing an own device
driver it would save me some time.
> I'll try to dig it out and send it, but you'll haev some
> hacking to do to get it going.
Thanks nice. I will take a look at it in any case, maybe I can do
something with it (I'll send the results back to you if I have
any useful ones).
> It's on the list for inclusion in the next petalinux release,
> but there's still work to be done there.
Sounds good. I already like the current version of petalinux :)
Best regards and thanks
Jarno Radde
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message.
Thank you for your co-operation.
___________________________
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/