Recover a BAD CRC in miniboot-Error?

[devnull]

I managed to recover a 6850, where the flash was corrupted, and i needed to upload the images using zModem (will make a blog entry later this week).

But i have another 6850 where i can't enter miniboot, as i has a bad crc.

output is:

Code: Select all

U-Boot 1.1.0(6.1.3.601.R01) (Sep 13 2006 - 14:37:19)

MPC8248 Reset Status: External Soft, External Hard

MPC8248 Clock Configuration
 - Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq  25-75 , Core Freq 100-300
 - dfbrg 0, corecnf 0x1a, busdf 3, cpmdf 1, plldf 0, pllmf 3
 - vco_out  400000000, scc_clk  100000000, brg_clk  100000000
 - cpu_clk  400000000, cpm_clk  200000000, bus_clk  100000000
 - pci_clk   66666666

CPU:   MPC8248 (HiP7 Rev 14, Mask 1.0 1K50M) at 400 MHz
Board: Alcatel OS68xx (Kite II)
I2C:   ready
DRAM:  256 MB
FLASH:  8 MB
In:    serial
Out:   serial
Err:   serial

No ethernet found.
IDE:   Bus 0: OK 
  Device 0: Model: CF 64MB Firm: 06/07/29 Ser#: GHS3ABPCF07061200004
            Type: Removable Hard Disk
            Capacity: 62.5 MB = 0.0 GB (128000 x 512)
USB:   scanning bus for devices... 
      USB device not responding, giving up (status=80000000)
0 USB Devices found
Hit any key to stop autoboot:  0 
## Booting image at ff900000 ...
   Image Name:   miniboot-6.1.3.601.R01
   Image Type:   PowerPC VxWorks Kernel Image (gzip compressed)
   Data Size:    781716 Bytes = 763.4 kB
   Load Address: 00005000
   Entry Point:  00005000
   Verifying Checksum ... Bad Data CRC

I searched the forums, google and the alcatel knowledge base but can't figure out how to recover the miniboot..
I tried to follow http://service.esd.alcatel-lucent.com/p ... umber=6351 to start the backup miniboot, but i can't get into vxWorks, at least in the "thing" i land with the bad CRC i can't edit bootvars with "c" and when issuing "printenv", i can't see anything containing default or backup miniboot

Any hints?

[silvio]

Hi Jan,
I have found the following info for R5. try this pls

[miniBoot]>sysUpdateBootrom
.... Bootrom updated!!!
[miniBoot]> sysUpdateMiniboot (0) (for default)
[miniBoot]> sysUpdateMiniboot (1) (for backup)
bootChange

set flag to 0x0 (for normal boot)

[miniBoot]> sysBoardReset

I think that the miniboot/uboot-files has to be in flash-directory before you can use this commands.
regards
Silvio

[devnull]

Problem is: i am not in miniboot, but something before that, which has pretty strange commands..

issuing run miniboot fails with bad-crc as well..

[silvio]

sorry, i have missed it.
So you has stoped in BootRom with prompt "=>" . I don't know any other tip beside the in the techtip from the knowledgebase. If you have a second switch - you can try to exchange the memory....
regards
Silvio

[devnull]

I don't want to open the switch (warranty?) to exchange memory and in that case i would remove the memory from a working switch moving the problem just to another box. i think i'll check whether this can be RMAed.