[Avila] Oops, flashed redboot

[Burns, Darrell]

Joel,

Try downloading your kernel and ramdisk using serial xmodem or ymodem,
rather than network.  It does appear that something in redboot was built
incorrectly, but I am not an expert on that.  Early on, I always had to
use the serial downloads, rather than TFTP, because my redboot wasn't
correctly accessing the network ports.  Hope this helps out.

Darrell Burns=20

-----Original Message-----
From: Joel Lindsay [mailto:joel at waveteq.com]=20
Sent: Wednesday, December 20, 2006 12:22 AM
To: 'Avila'
Subject: [Avila] Oops, flashed redboot
Subject: [Avila] Hi,

Please note I am using the 2347 Rev C 1 port board.

I tried to flash redboot as I wanted to use netflash to update my
firmware
from a cgi form.  It was all working great except I was getting CRC
errors
when checking the FIS partitions.

Reading the mailing list archives I learned that this was because I
needed
to turn off the CRC checking in redboot.

I had the Redboot source on my Avila dev CD, so I untarred it and
changed as
specified in aforementioned article:

"and here's the details regarding disabling the FIS check that redboot
v2.02
does by default when loading an image from flash:

packages/redboot/current/cdl/redboot.cdl line 791 change 'default_value
1'
to
'default_value 0' to disable FIS checksum checks"

I then recompiled (had to download tcl etc) which went fine.  I wanted
to
use netflash instead of having to jtag, so I used the non-byte swapped
reboot.bin and flashed to mtd0 with netflash -bkdlu /dev/mtd0
redboot.bin.

Everything seemed to work OK, except when reboot started, it didn't find
NPEB, but instead found NPEC

"Trying NPE-B...no PHY found
Trying NPE-C...[error] ixEthMiiPhyScan : unexpected Mii PHY1 ID 20005c90
success. Using NPE-C with PHY 1.
Ethernet eth1: MAC address 00:d0:12:12:50:32
IP: 192.168.1.66/255.255.255.0, Gateway: 192.168.1.2
Default server: 192.168.1.50"

It booted up fine, but now it getting kernel panics, sometimes on boot
and
sometimes after its been up for 10-30 seconds.

Now my zImage is not working and I can't change it from redboot prompt
as it
says cant find my server.

"RedBoot> exec 0x01600000
Can't execute Linux - invalid entry address
RedBoot> fis delete zImage
Delete image 'zImage' - continue (y/n)? y
... Erase from 0x50080000-0x50180000: ........
... Unlock from 0x507e0000-0x50800000: .
... Erase from 0x507e0000-0x50800000: .
... Program from 0x01fe0000-0x02000000 at 0x507e0000: .
... Lock from 0x507e0000-0x50800000: .
RedBoot> load -r -v -b 0x01600000 zImage
Using default protocol (TFTP)
__udp_sendto: Can't find address of server
Can't load 'zImage': some sort of network error"

Nothing is wrong with my TFTP server, everything is exactly the same as
before.

Did I need to do something more to the redboot source because of the
board I
am using or is something else going on?

Has someoneseen problems similar to these?  Can I reload redboot from
the
redboot prompt as I can't access linux anymore, or do I have to jtag it.
If
so, then what to fix problem.

Any help is appreciated.

Joel Lindsay

---------------------------------------------------------------------
To unsubscribe, e-mail: avila-unsubscribe at lists.unixstudios.net
For additional commands, e-mail: avila-help at lists.unixstudios.net