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 bzboi » Fri Aug 27, 2010 3:28 pm

$this->bbcode_second_pass_quote('Admin', 'N')AND 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?
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm

Re: DockStar JTAG

Postby Rosi » Fri Aug 27, 2010 3:47 pm

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:
$this->bbcode_second_pass_code('', '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.
')
Rosi
 
Posts: 5
Joined: Thu Aug 26, 2010 6:17 pm

Re: DockStar JTAG

Postby Kragorn » Fri Aug 27, 2010 4:22 pm

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.
Kragorn
 
Posts: 11
Joined: Wed Aug 11, 2010 4:35 pm

Re: DockStar JTAG

Postby bzboi » Fri Aug 27, 2010 5:20 pm

$this->bbcode_second_pass_quote('Kragorn', '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
$this->bbcode_second_pass_code('', 'Warn : use 'feroceon.cpu' as target identifier, not '0'')

Thanks.
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm

Re: DockStar JTAG

Postby bzboi » Fri Aug 27, 2010 5:38 pm

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.

$this->bbcode_second_pass_code('', '> 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... :)
$this->bbcode_second_pass_quote('', 'I') used the memory boot option and flashed mtd0 inside Pogoplug.

From within uboot, I ran
$this->bbcode_second_pass_code('', '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.
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm
Top

Re: DockStar JTAG

Postby Kragorn » Fri Aug 27, 2010 7:54 pm

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.
Kragorn
 
Posts: 11
Joined: Wed Aug 11, 2010 4:35 pm

Re: DockStar JTAG

Postby bzboi » Fri Aug 27, 2010 8:03 pm

$this->bbcode_second_pass_quote('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.


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...)
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm
Top

Re: DockStar JTAG

Postby bzboi » Fri Aug 27, 2010 8:22 pm

From within uboot, I used TFTP to transfer the kernel and rootfs to the NAND.
$this->bbcode_second_pass_code('', 'CE>> mw 0x800000 0 0x400000
CE>> tftpboot 0x800000 ce_kernel_redstone_v63.img
Using egiga0 device
TFTP from server 192.168.0.3; our IP address is 192.168.0.4
Filename 'ce_kernel_redstone_v63.img'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##############################################################
done
Bytes transferred = 1978608 (1e30f0 hex)
CE>> nand erase 0x100000 0x400000

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete.
OK
CE>> nand write.e 0x800000 0x100000 0x1e30f0

NAND write: device 0 offset 0x100000, size 0x1e30f0

Writing data at 0x2e3000 -- 100% complete.
1978608 bytes written: OK
CE>> mw 0x800000 0 0x2000000
CE>> tftpboot 0x800000 ce_ramdisk_v2.0b.img
Using egiga0 device
TFTP from server 192.168.0.3; our IP address is 192.168.0.4
Filename 'ce_ramdisk_v2.0b.img'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
############################################
done
Bytes transferred = 14534144 (ddc600 hex)
CE>> nand erase 0x500000 0x2000000

NAND erase: device 0 offset 0x500000, size 0x2000000
Erasing at 0x24e0000 -- 100% complete.
OK
CE>> nand write.e 0x800000 0x500000 0xddc600

NAND write: device 0 offset 0x500000, size 0xddc600

Writing data at 0x12dc000 -- 100% complete.
14534144 bytes written: OK
CE>>')

However, the kernel size seems to be a bit off at 1978544 vs the 1978608 in the binary. Are there any checksums in the binary that could explain the discrepancy? The kernel loads
$this->bbcode_second_pass_code('', '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.22.18
Created: 2009-10-14 20:23:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1978544 Bytes = 1.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.')
and just stops right there for about a minute before rebooting. Can someone post a factory fresh printenv (mask out any sensitive info if you want)? I just want to make sure that I have the boot parameters set up right. I'm particularly suspicious of
$this->bbcode_second_pass_code('', 'bootcmd_original=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000')
the size 0x300000 parameter in bootargs.

Incidentally, I never touched mtd3, so the Arch Linux ARM install uboot is still intact and I can still chainboot through it to USB even if I'm using the original uboot file and not Jeff's updated one. I'm just trying to restore to factory default this time round and am using the uboot/kernel/rootfs binaries from Pogoplug without modification.
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm

Re: DockStar JTAG

Postby z80yyz » Sat Aug 28, 2010 2:27 am

Here is the output before messing with my Dockstar:
$this->bbcode_second_pass_code('', 'Output of Original Dockstar blparam command


baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
ethaddr=<GET:FROM:BOTTOM:OF:YOUR:UNIT>
cesvcid=<GETFROMBOTTOMOFYOURUNIT>
ceserialno=<GETFROMBOTTOMOFYOURUNIT>
ceboardver=REDSTONE:1.0
bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000')
z80yyz
 
Posts: 1
Joined: Sat Aug 28, 2010 2:22 am

Re: DockStar JTAG

Postby candlejack » Sat Aug 28, 2010 4:03 pm

Hi, first great job you've accomplished here.
I hope you could help me unbrick my dockstar.
Today was my first try with a selfmade wiggler using this schematic
http://www.ic-board.de/product_info.php?language=en&info=p14_Wiggler.html&XTCsid=30d201dec3f969ee7ac770bb2907866e
But something doesn't seem right as it only has one reset. I tried both pin2 and pin7 but neither works.
candlejack
 
Posts: 6
Joined: Sat Aug 28, 2010 3:50 pm

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 12 guests