RE: [microblaze-uclinux] Petalinux Unofficial Bug Report

["Leonid" <Leonid@xxxxxxxxx>]

Hi, Michal:

Sorry for not answering your very interesting message right away, I was
drugged out by other project for a while.

On Monday, January 08, 2007 12:38 PM Michal Simek wrote:

> U-boot has implementation only for Suzaku board (for Microblaze). but 
> this port has many problem.
[Leonid] I'm using u-boot port from petalogix site - they have posted
complete uClinux distro only recently. They have ports for some Xilinx
boards, including Spartan-3e Starter Kit which close to my proprietary
board based on Spartan-2e. I didn't have serious problems running
u-boot/uClinux on the reference board except the fact that Ethernet
loosed packets frequiently (must be u-boot problem since under uClinux
it doesn't happen). Also flash writing is extremely slow - takes about
6-7 minutes just to save u-boot environment.

While working with my own HW, I have problems with flash and Ethernet.
U-boot cannot recognize the flash. This is what printed out if DEBUG is
defined:

FLASH: flash detect cfi
fwc addr 21000000 cmd 0 0 8bit x 8 bit
fwc addr 21000055 cmd 98 98 8bit x 8 bit
is= cmd 51(Q) addr 21000010 is= ff 51
fwc addr 21000000 cmd 0 0000 16bit x 8 bit
fwc addr 210000aa cmd 98 9898 16bit x 8 bit
is= cmd 51(Q) addr 21000020 is= ffff 5151
fwc addr 21000000 cmd 0 0000 16bit x 16 bit
fwc addr 210000aa cmd 98 0098 16bit x 16 bit
is= cmd 51(Q) addr 21000020 is= ffff 0051
fwc addr 21000000 cmd 0 00000000 32bit x 8 bit
fwc addr 21000154 cmd 98 98989898 32bit x 8 bit
is= cmd 51(Q) addr 21000040 is= ffffffff 51515151
fwc addr 21000000 cmd 0 00000000 32bit x 16 bit
fwc addr 21000154 cmd 98 00980098 32bit x 16 bit
is= cmd 51(Q) addr 21000040 is= ffffffff 00510051
fwc addr 21000000 cmd 0 00000000 32bit x 32 bit
fwc addr 21000154 cmd 98 00000098 32bit x 32 bit
is= cmd 51(Q) addr 21000040 is= ffffffff 00000051
fwrite addr 21000000 cmd 0 0000000000000000 64 bit x 8 bit
fwrite addr 210002a8 cmd 98 ffffffffffffffffffff98 64 bit x 8 bit
is= cmd 51(Q) addr 21000080 is= ffffffffffffffffffff5151515151515151
5151515151515151
fwrite addr 21000000 cmd 0 0000000000000000 64 bit x 16 bit
fwrite addr 210002a8 cmd 98 00ff00ff00ff00ffffff98 64 bit x 16 bit
is= cmd 51(Q) addr 21000080 is= ffffffffffffffffffff0051005100510051
0051005100510051
fwrite addr 21000000 cmd 0 0000000000000000 64 bit x 32 bit
fwrite addr 210002a8 cmd 98 000000ff000000ffffff98 64 bit x 32 bit
is= cmd 51(Q) addr 21000080 is= ffffffffffffffffffff0000005100000051
0000005100000051
fwrite addr 21000000 cmd 0 0000000000000000 64 bit x 64 bit
fwrite addr 210002a8 cmd 98 00000000000000ffffff98 64 bit x 64 bit
is= cmd 51(Q) addr 21000080 is= ffffffffffffffffffff0000000000000051
0000000000000051
not found
## Unknown FLASH on Bank 0 - Size = 0x00000000 = 0 MB

It's worth to mention that in EDK project I'm using the same IP core the
reference board is using.

With Ethernet situation is not good as well: after configuring IP
address and netmask, cannot ping:

U-Boot> ping 192.168.0.1
Error while sending frame
Error while sending frame
ping failed; host 192.168.0.1 is not alive

When uClinux boots up (I have downloaded it using XMD) it doesn't see
eth0 interface (I'm using the same configuration I had for Spartan-3e
Starter Kit).

All these problems most likely happen because drivers' code doesn't
match actual HW, but since this is my first experience with EDK based
project I have difficulties to find them. I'll appreciate any hints
where to look.

> 2. My patch isn't in u-boot tree because I had problem with submit my 
> patch (Problems about indentation, etc., I clear it, but Wolfgang
doesn't 
> send me any reply till now.)

[Leonid] Did you look up your patch in 1.1.5 tree? This is where I have
found my own fix submitted back in October (and I didn't receive any
official confirmation either).

> My changes are on my site www.monstr.eu
[Leonid] Somehow I didn't find any code on your site, can you help
please? 

> * Added support emac for Microblaze
[Leonid] Do you mean that there is no Ethernet support in u-boot now? It
works for Spartan-3e at least... May be this is petalogix port. Yours
may be better actually.

> If you are solving any problem about U-BOOT on Microblaze, please
contact 
> me.

[Leonid] It's very kind of you. I would like to ask several other
EDK/Microblaze related questions if you don't mind.

1) I could use XMD to set breakpoints, but I failed to have source-level
debug (I mean code running from RAM, like u-boot, not BRAM-based
applications which are parts of EDK).

2) You have u-boot as OS in your EDK project. Can you supply TCL file
for this OS?

3) I understood you have some first stage bootloader in your project -
are its sources available? 

4) Where your u-boot runs from? It can probably be in BRAMs, but not in
my case - biggest application I can run from there is 16K while u-boot
binary >100K. 

5) Have you ever run EDK or some of its components under Linux? I'm
forced to used Windows version (I'm using EDK 8.1 now). So, to have
compilation results available for uClinux/u-boot build, I keep my EDK
project on Linux machine (Fedora Core 4) and mount its disk via Samba.

6) I noticed that u-boot is using standard cfi_flash.c for my flash, do
you think it's correct choice?

Best regards
Leonid.

___________________________
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/