DockStar JTAG

[bzboi]

Hmm, I managed to erase the NAND just fine, but I'm getting an error when trying to perform the write.

Code: Select all

> halt
Halt timed out, wake up GDB.
> sheevaplug_init
> nand probe 0
NAND flash device 'NAND 256MiB 3,3V 8-bit' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 5 on NAND flash device #0 'NAND 256MiB 3,3V 8-bi
> nand write 0 uboot.bin 0 oob_softecc_kw
timed out while waiting for target halted
error executing hosted NAND write
Unable to write data to NAND device
failed writing file uboot.bin to NAND flash 0 at offset 0x00000000
>

It looks like my halt timed out and the target is not truly halted even though I'm able to probe the NAND correctly.

Code: Select all

> nand probe 0
NAND flash device 'NAND 256MiB 3,3V 8-bit' found
> halt
> nand erase 0 0x0 0xa0000
erased blocks 0 to 5 on NAND flash device #0 'NAND 256MiB 3,3V 8-bit'
> nand write 0 uboot.bin 0 oob_softecc_kw
timed out while waiting for target halted
error executing hosted NAND write
Unable to write data to NAND device
failed writing file uboot.bin to NAND flash 0 at offset 0x00000000
> halt
Halt timed out, wake up GDB.
> halt
> sheevaplug_init
> nand write 0 uboot.bin 0 oob_softecc_kw
timed out while waiting for target halted
error executing hosted NAND write
Unable to write data to NAND device
failed writing file uboot.bin to NAND flash 0 at offset 0x00000000
> halt
> nand write 0 uboot.bin 0 oob_softecc_kw
timed out while waiting for target halted
error executing hosted NAND write
Unable to write data to NAND device
failed writing file uboot.bin to NAND flash 0 at offset 0x00000000
>

Well, I guess I'm committed to figuring this out now...

[bzboi]

Try out the steps that Kragorn outlined and hopefully we'll have better instructions written up soon.

I always get missing previlegs for direct i/o ...

I made a seriel cable with the ca 42 nokia data cable...

You need to unzip and run the giveio batch file in the drivers subdirectory

[Rosi]

You need to unzip and run the giveio batch file in the drivers subdirectory

I get an error on copying this on win7, I'll set up a virtuel machine with win xp.

[bzboi]

NAND erase is never a good idea, but hey, at least you can go back now!

WAIT... something isn't quite right yet.

After my NAND erase, I tried Kragorn's procedure to see what I could achieve from within uboot, and I can't get the dockstar to boot. Anyone else in this situation?

[Rosi]

Alright, I tried Kragorns solution with win xp, I installed succesfully the giveio driver and the driver for my ca 42 serial cable, but I get this message when I try to connect:

Code: Select all

Open On-Chip Debugger 0.4.0 (2010-02-22-19:05)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0x378
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : clock speed 500 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.


[Kragorn]

You can't recover with the CA-42 which is a serial cable. If you erased the nand, you'll need a JTAG cable, but there is no garantee that it will work.

I had problem to probe the nand so I used the memory boot option and flashed mtd0 inside Pogoplug. But I guess if you completely erased the nand, you'll have to figure out how to write the kernel and the rootfs so that you can continue after the uboot.

[bzboi]

I had problem to probe the nand so I used the memory boot option and flashed mtd0 inside Pogoplug. But I guess if you completely erased the nand, you'll have to figure out how to write the kernel and the rootfs so that you can continue after the uboot.

Actually, I can't even get uboot to load at the moment. One question I had was what causes the warning

Code: Select all

Warn : use 'feroceon.cpu' as target identifier, not '0'

Thanks.

[bzboi]

As indicated earlier, Kragorn's procedure no longer worked after my NAND was erased. Working on a hunch, I tried the workaround before performing the image load and was finally successful getting uBoot to load. The log below shows the first time I tried the load_image that failed, followed by the halt/reset workaround and the 2nd successful attempt.

Code: Select all

> load_image uboot.bin 0x800000
524288 bytes written at address 0x00800000
downloaded 524288 bytes in 64.262405s (7.967 kb/s)
> resume 0x800200
> nand probe 0
NAND flash access requires halted target
NAND flash access requires halted target
NAND flash access requires halted target
NAND flash access requires halted target
NAND flash access requires halted target
NAND flash access requires halted target
unknown NAND flash device found, manufacturer id: 0x00 device id: 0x00
probing failed for NAND flash device
> halt
Halt timed out, wake up GDB.
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> sheevaplug_init
> load_image uboot.bin 0x800000
524288 bytes written at address 0x00800000
downloaded 524288 bytes in 65.744537s (7.788 kb/s)
> resume 0x800200

PHEW...

I used the memory boot option and flashed mtd0 inside Pogoplug.

From within uboot, I ran

Code: Select all

Marvell>> nand write.e 0x800000 0x0 0x80000

NAND write: device 0 offset 0x0, size 0x80000
 524288 bytes written: OK

I reset the Dockstar and am booting from mtd0 now.

[Kragorn]

I'm not sure what's the problem with nand probe 0. Even when the target is halted I got flash detection problems. But I have always been able to load the uboot image and resume it (be sure that all cpu registers are set to 0 with the "arm reg" cmd).

I think we can say that this thing is now unbrickable.

So now all you have to do is tftp the kernel and rootfs or use JTAG (but I think it might take a long time) and write it to the nand.

[bzboi]

I'm not sure what's the problem with nand probe 0. Even when the target is halted I got flash detection problems. But I have always been able to load the uboot image and resume it (be sure that all cpu registers are set to 0 with the "arm reg" cmd).

I think we can say that this thing is now unbrickable.

So now all you have to do is tftp the kernel and rootfs or use JTAG (but I think it might take a long time) and write it to the nand.

I'm guessing that it's related to whether mtd0 is empty or not. No pressure, but if you're willing to try reproducing my results, I suspect you will encounter the same problem if mtd0 is erased.

I'm just waiting for the 1GB TSOP to show up and then I'll have the world's first 1GB Dockstar! [EVIL LAUGH] (Assuming I don't botch up the rework of course...)