[Solved] Yet another bricked DockStar

Hi,
I don't know how, but I have bricked my DockStar when trying to update uBoot.
I have tried to unbrick it using JTAG port.

First using my RaspBerry Pi, unsuccessfully, then buying a Bus Pirate.
I've used OpenOCD, and tried to follow several explanations.
I was unable to access nand correctly with given explanations.


I have succeeded doing this :

> soft_reset_halt
(wait about 1/2 sec)
> soft_reset_halt
> nand probe 0
NAND flash device 'NAND 256MiB 3.3V 8-bit (Micron)' found

Then run manually arm mcr and all mww instructions (in place of dockstar_init command).

> arm mcr 15 0 0 1 0 0x00052078
> mww 0xD0001400 0x43000C30
> mww 0xD0001404 0x39543000
(and so on...)

Then, I run several checks :

> nand probe 0
NAND flash device 'NAND 256MiB 3.3V 8-bit (Micron)' found

> nand list
#0: NAND 256MiB 3.3V 8-bit (Micron) pagesize: 2048, buswidth: 8,
        blocksize: 131072, blocks: 2048

> nand check_bad_blocks 0
bad block: 1656
checked NAND flash device for bad blocks, use "nand info" command to list blocks
> nand info 0
(...)
        #1654: 0x0cec0000 (128kB) erase state unknown
        #1655: 0x0cee0000 (128kB) erase state unknown
        #1656: 0x0cf00000 (128kB) erase state unknown (marked bad)
        #1657: 0x0cf20000 (128kB) erase state unknown

I have 1 bad block.

Everything seems OK, so I try to reflash uboot file :

> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 256MiB 3.3V 8-bit'

> nand write 0 uboot.kwb 0 oob_softecc_kw
wrote file uboot.kwb to NAND flash 0 up to offset 0x00080000 in 638.884583s (0.801 KiB/s)

But... I was unable to restart my Dockstar.

So, I have tried the load_image method :

> load_image uboot.kwb 0x800000
524288 bytes written at address 0x00800000
downloaded 524288 bytes in 249.925323s (2.049 KiB/s)

> dump_image uboot_NAND.kwb 0x800000 0x80000
dumped 524288 bytes in 250.210892s (2.046 KiB/s)
--> Compare this image with original one --> OK.

> resume 0x800200

But... nothing happens.

Using a FTDI serial/usb connector, I have nothing.
DockStar LED is permanently off.

Do you think my DocStar is definitively bricked ?
Maybe I'm doing something wrong ?
Do you know a magical trick ?

thanks.



Edited 2 time(s). Last edit at 09/13/2017 02:13AM by BMD_Online.

BMD_Online,

Have you looked at this thread:

HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD
http://forum.doozan.com/read.php?3,21789

If it does not help, then post in that thread so joerg will get notification and help you.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Yes I followed this thread and it doesn't helps.
I will bump his thread.

Hi,

I got it. My DockStar is working now !

First, I had to invert serial connectors :

Dockstar TxD to FTDI RxD
Dockstar RxD to FTDI TxD

I have tried with another DockStar, and it's working like that.

Then, I have tried many, many times to load / write NAND.
I had used both load_image and nand write commands.

I have checked loads

> load_image uboot.kwb 0x800000

then

> verify_image_checksum uboot.kwb 0x800000
> verify_image uboot.kwb 0x800000
> dump_image uboot_NAND.kwb 0x800000 0x80000
$ diff uboot.kwb uboot_NAND.kwb

And checked writes

> nand erase 0 0x0 0xa0000
> nand write 0 uboot.kwb 0 oob_softecc_kw

then

> nand verify 0 uboot.kwb 0 oob_softecc_kw
> nand dump 0 "uboot_NAND.kwb" 0 0x800 oob_only
$ diff uboot.kwb uboot_NAND.kwb

In fact, nand verify tooks 8817.960938s (more than 2 hours),
so I haven't used nand dump check !

In place, I had restarted using

> resume 0x800200

Then, once connected to console, ArchLinux loaded

# nanddump -no -l 0x80000 -f uboot-mtd0-dump /dev/mtd0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
# sha1sum uboot-mtd0-dump
b4bff0fa52030b056b26ff18f7dbf3f59133de2e  uboot-mtd0-dump

By the way, it's working with Bus Pirate and with RaspBerry PI.
Bus Pirate :

> verify_image uboot.kwb 0x800000
verified 524288 bytes in 248.388412s (2.061 KiB/s)

> nand write 0 uboot.kwb 0 oob_softecc_kw
wrote file uboot.kwb to NAND flash 0 up to offset 0x00080000 in 638.884583s (0.801 KiB/s)

Raspberry Pi :

> verify_image uboot.kwb 0x800000
verified 524288 bytes in 2.328349s (219.898 KiB/s)

> nand write 0 uboot.kwb 0 oob_softecc_kw
wrote file uboot.kwb to NAND flash 0 up to offset 0x00080000 in 249.033127s (2.056 KiB/s)

setenv seems also not to be very helpful for all lines of the text file

DockStar> setenv scan_disk 'echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done'
** Too many args (max. 32) **
DockStar>

Work continues ...

This indicates you're not running a recent version of uboot. You may want to look at the https://forum.doozan.com/read.php?3,12381 thread and update to the latest uboot which should solve this issue.

Ray