Re-programing SPI Serial FLASH on CPU Daughtercard (De-bricking)
Posted 04 September 2010 - 08:30 AM
Posted 04 September 2010 - 01:57 PM
Posted 05 September 2010 - 07:46 AM
Posted 05 September 2010 - 09:00 AM
Posted 06 September 2010 - 04:14 AM
The problem is really one step earlier. Why do the firmware authors insist on reflashing the complete bootloader with each firmware upgrade? AFAIK nothing has ever changed in u-boot' date=' but each firmware update erases and then recreates it - creating a window of opportunity for bricking. I don't see any reason for doing it that way.(On a vaguely related note, I put out a call for a sacrifical dead board donation last week to desolder the BGA and see if the JTAG interface goes anywhere on the board. It's a long shot, but it might make debricking slightly less impossible.
Why do they have to make getting a bootloader back on these things so difficult?
Posted 06 September 2010 - 07:27 AM
Posted 06 September 2010 - 07:37 AM
Posted 06 September 2010 - 07:59 AM
Posted 07 September 2010 - 03:44 AM
WonderMedia Technologies, Inc.W-Load Version : 0.17.00.01W-Load loading...U-Boot 1.1.4 (Apr 26 2010 - 20:48:31)WonderMedia Technologies, Inc.WMT U-Boot Version : 0.12.01.00.16U-Boot code: 03F80000 -> 03FB8134 BSS: -> 04006544RAM Configuration:Bank #0: 00000000 128 MBboot from spi flash.flash: Bank1: FF800000 -- FFFFFFFF Bank2: FF000000 -- FF7FFFFFFlash: 16 MB*** Warning - bad CRC, using default environmentIn: serialOut: serialErr: serial### main_loop entered: bootdelay=3### main_loop: bootcmd="cp.b ff200000 01000000 $(rootfs_size); bootm ff000000"Hit any key to stop autoboot: 3 2 1 0 ATSMB Host 390KHz SD Card is not insertedUsage:cp - memory copy## Booting image at ff000000 ...Bad Magic NumberWMT #At this stage I inserted a SDcard with the firmware on, rebooted and off she went . . The M001 reflashed, fixing the config space problems and then booted up to Android.
Posted 07 September 2010 - 04:19 AM
Posted 07 September 2010 - 05:53 AM
Posted 07 September 2010 - 06:20 AM
flashrom -p ft2232_spi:type=2232H,port=A -w spiflash.bin[QUOTE=Stockmann;52506]2) How you compile .bin?[/QUOTE]The bin file is simply the concatenation of w-load and u-boot binaries at their respective offsets. It was generated using :
dd if=/dev/zero of=spiflash.bin ibs=1 count=524288dd if=u-boot.bin of=spiflash.bin ibs=1 conv=notruncdd if=wload.bin of=spiflash.bin obs=1 ibs=1 seek=458752 conv=notrunc
Posted 07 September 2010 - 06:19 PM
Posted 11 September 2010 - 08:45 AM
Posted 12 September 2010 - 07:49 AM
Posted 07 October 2010 - 09:21 AM