Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 46968

bad crc and ro serial console unbrick?

$
0
0
I tried to restore uboot to facotry and ended up with bad checksum. I messed up the pad by the rx pin so i cant write from serial console. here is what happens on boot:
U-Boot 1.1.4  Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00691750

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD (GUESSED): DISCOVERY:0.1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Created:      2011-02-17   8:10:10 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes =  3.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
CE>>

Is there any way to unbrick?

Viewing all articles
Browse latest Browse all 46968

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>