DockStar JTAG

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Re: DockStar JTAG

Postby ecc » Thu Apr 21, 2011 6:44 pm

The dockstar.cfg referenced in the wiki disables DCC downloads, resulting in much slower image loading.

It turns out they work fine on the DockStar -- the problem was the work area address was left unmodified from the Sheevaplug and was set to 256M, but the DockStar only has 128M.

The following changes enable significantly faster downloads:

$this->bbcode_second_pass_code('', '
$_TARGETNAME configure -work-area-phys 0x6000000 -work-area-size 65536

arm7_9 dcc_downloads enable
arm7_9 fast_memory_access enable
')
ecc
 
Posts: 5
Joined: Mon Sep 06, 2010 4:46 pm

Re: DockStar JTAG

Postby jasonldf » Sun May 22, 2011 1:01 pm

$this->bbcode_second_pass_quote('jasonldf', '')$this->bbcode_second_pass_quote('N3x', '
')If you're interested, you wan read the mains steps here: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate
N3x

Thanks for this, I'll be trying this out to resurrect my dockstar with Bus Pirate JTAG soon.


Thanks, I finally had the chance to try the steps and managed to recover and write uboot to nand. My dockstar is alive again
jasonldf
 
Posts: 8
Joined: Sun Dec 12, 2010 3:47 am

Re: DockStar JTAG

Postby displacedtexan » Sun Jul 24, 2011 8:09 pm

$this->bbcode_second_pass_quote('N3x', '
')After I bricked my Dockstar, (with some kind of hazardous nand scrubing) I ordered a BusPirate from Sparkfun and after an evening of trials (and a lot of failed attempts) I managed to recover my Dockstar with my BusPirate and and FTDI USB-Serial Adapter under Linux (Archlinux in my case).
If you're interested, you can read the mains steps here: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate
(There might be some language mistakes, I apologize. (and if someone wan't to correct, I'll edit the article) I'm a French student so I know It's perfectible, but iI wrote it in English to make it accessible to most people. Common steps are not really detailed, if you think it's necessary I can edit the article.

Thanks to everyone for the work previously done on JTAG with the Dockstar.

N3x

N3x,

Thanks for you post, it allowed me to get quite a way toward a working dockstar!

I am able to load the bootloader into RAM and seem able to write to the NAND. Unfortunately there are bad blocks that I think are causing me problems.

$this->bbcode_second_pass_quote('', 's')topping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: read_nand_cached: error reading nand off 0xe20000 size 8192 bytes done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
## Starting application at 0x00800200 ...


U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
Marvell>> nand erase

NAND erase: device 0 whole chip
Skipping bad block at 0x00320000
Skipping bad block at 0x00e20000
Skipping bad block at 0x064c0000
Erasing at 0xffe0000 -- 100% complete.
OK
Marvell>> nand write.e 0x800000 0x0 0x80000

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


When I reboot, nothing happens (no serial output, no LED activity)

I am assuming that the bootloader is getting written to bad blocks preventing my dockstar from booting. How do I overcome?

I am way over my head, but am having fun tinkering!

Thanks for any help...
displacedtexan
 
Posts: 3
Joined: Sun Jul 24, 2011 7:58 pm
Top

Re: DockStar JTAG

Postby N3x » Sun Jul 24, 2011 8:43 pm

I don't have any real solution but:

Which file are you trying to load (that causes the inodes errors) ? You may try to use the one I host on my server (which was known to work correctly)... Yours may be corrupted.. who knows ?

If the nand is really faulty, I'm not sure if you'd be able to recover your dockstar (until you change the chip by removing it and soldering a new one in place...). And until you are able to use at least uboot, I don't know how to check for failures (uboot provides tools for checking the nand if I remember well...)

I'm not really an expert with the Dockstar (or any other ARM based card...)... Someone else may have a better idea :P
N3x
 
Posts: 3
Joined: Sun Feb 06, 2011 1:21 am

Re: DockStar JTAG

Postby displacedtexan » Mon Jul 25, 2011 9:01 pm

$this->bbcode_second_pass_quote('N3x', 'I') don't have any real solution but:

Which file are you trying to load (that causes the inodes errors) ? You may try to use the one I host on my server (which was known to work correctly)... Yours may be corrupted.. who knows ?

If the nand is really faulty, I'm not sure if you'd be able to recover your dockstar (until you change the chip by removing it and soldering a new one in place...). And until you are able to use at least uboot, I don't know how to check for failures (uboot provides tools for checking the nand if I remember well...)

I'm not really an expert with the Dockstar (or any other ARM based card...)... Someone else may have a better idea :P


I tried both yours and the one available at http://jeff.doozan.com/debian/uboot/files/uboot/uboot.mtd0.dockstar.jeff-2010-10-23.kwb.

I'll have to try it again using yours and post the serial output.

Thanks!
displacedtexan
 
Posts: 3
Joined: Sun Jul 24, 2011 7:58 pm
Top

Re: DockStar JTAG

Postby displacedtexan » Tue Jul 26, 2011 8:22 pm

Finally got it to work.

I did two thing differently. First after running the "resume 0x800200" command, I IMMEDIATELY switched to the terminal screen and hit a key to keep the dockstar from rebooting. Previously I would let it reboot a few times and then stop it.

After flashing the nand, I quit openocd, disconnected the buspirate and then rebooted. Worked fine. Previously I had left the JTAG adapter connected.

Thanks for the help!
displacedtexan
 
Posts: 3
Joined: Sun Jul 24, 2011 7:58 pm

Re: DockStar JTAG

Postby N3x » Tue Jul 26, 2011 8:25 pm

:) Nice to see you finally manage to recover your device, and to read the steps you used. It may be usefull to someone else one day (yeah, maybe to me ^^ We never know...)
N3x
 
Posts: 3
Joined: Sun Feb 06, 2011 1:21 am

Re: DockStar JTAG

Postby jzero » Tue Jul 10, 2012 8:12 am

Hi.
Well, I have some problems. I bricked my Dockstar while trying to reflash...
Anyway I've got a JTAGKey-Tiny and Conncted it to my Dockstar. But I'm unable to halt it in a kind of way...
Here is my OpenOCD output:

TELNET:
$this->bbcode_second_pass_code('', 'Open On-Chip Debugger
> init
> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: enabled, D-Cache: disabled, I-Cache: enabled
> sheevaplug_init
unexpected Feroceon EICE version signature
Halt timed out, wake up GDB.
timed out while waiting for target halted
Command handler execution failed
in procedure 'sheevaplug_init' called at file "command.c", line 650
in procedure 'wait_halt' called at file "dockstar3.cfg", line 36
called at file "command.c", line 361
> 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
> poll
background polling: on
TAP: feroceon.cpu (enabled)
target state: running
> halt
Halt timed out, wake up GDB.
timed out while waiting for target halted
Command handler execution failed
in procedure 'halt' called at file "command.c", line 650
called at file "command.c", line 361
>
')
OPENOCD
$this->bbcode_second_pass_code('', 'Open On-Chip Debugger 0.4.0 (2012-07-09-15:44)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
2000 kHz
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 15
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Error: unexpected Feroceon EICE version signature
Info : accepting 'telnet' connection from 0
...
')

You see, first time: "target halted in ARM state due to debug-request, current mode: Supervisor", this is what I get with "press reset workaround". But after that, "nand probe 0" and anything else fails with "target not haltet".

Any suggestions?

j-zero

PS: Sorry for my english ;)
jzero
 
Posts: 1
Joined: Tue Jul 10, 2012 8:04 am

Previous

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 13 guests