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 » Mon Sep 13, 2010 12:55 am

I do recall the instructions were slightly off, but I was so excited I got it working that I forgot to fix that particular Wiki entry. (I just went back in and fixed it) I used the compressed rootfs image that I downloaded directly without extracting. That should fix it.
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm

Re: DockStar JTAG

Postby jtagfun » Mon Sep 13, 2010 10:44 am

bzboi wrote:I do recall the instructions were slightly off, but I was so excited I got it working that I forgot to fix that particular Wiki entry. (I just went back in and fixed it) I used the compressed rootfs image that I downloaded directly without extracting. That should fix it.


I noticed you have updated wiki with "ce_ramdisk_v2.0b.img.gz", now the size is correct.

I tried compressed and uncompressed ramdisk v1.2, v2.0a, V2.0b but still got the same error. I did reset env every time and fill in parameters according to wiki.

Kernel loading was fine, something wrong with loading root_fs.
jtagfun
 
Posts: 24
Joined: Sun Aug 29, 2010 11:37 am

Re: DockStar JTAG

Postby bzboi » Mon Sep 13, 2010 12:12 pm

It's been a while since I got it working and I don't have my dockstar this week so I can't verify the steps. Maybe someone else who was successful can jump in. I'm going by memory of how I think the Wiki might have differed compared to what I did.

Did you copy the commands verbatim or did you adjust them for your particular setup like exact file sizes, etc?

Did you erase the nand in mtd2 first?

Which kernel are you using? Did you make sure that the kernel and rootfs match? eg ce_kernel_v2.0.img with ce_ramdisk_v2.0b.img.gz?

Most importantly, are you sure you're using the matching stock uBoot eg ce_uboot_v2.0.bin for the previous two files? These instructions were written assuming stock Dockstar images so if you're using Jeff's uBoot for example, you need to chain-boot through the stock uBoot in mtd2 as per Jeff's script, so it becomes a chicken and egg problem and I'm not sure how that will work. You might also have to set the arcNumber and mainlineLinux settings appropriately. (Not sure since I use the stock uBoot.)

My suggestion is to try using STOCK uBoot/kernel/rootfs. Once you get it working, you can easily make the other changes.

I didn't write that particular Wiki, so I can only guess that the instructions were originally working and got modified to a point that it didn't over time. It suggests that we might need some formal review process for Wiki entries such that at least 2 people must agree before a Wiki entry is made "official".
bzboi
 
Posts: 55
Joined: Sun Jul 11, 2010 5:39 pm

Re: DockStar JTAG

Postby jtagfun » Mon Sep 13, 2010 3:28 pm

bzboi,
Thanks for the suggestions.
I did have original Dockstar Uboot.
There is only one version of kernel for Dockstar from http://Arch Linux ARM.com/os/pogoplug/ce_mirror/
All links to download.pogoplug.com/prod/ have been broken.

Strange thing is:
The very first time when I tried the steps in wiki with decompressed root-fs, it worked.
When I re-tried the steps, they do not work any more. I did try to erase everything except u-boot, but still got the same problem when loading root-fs.

There might be more entries of env need to be added (e.g. some mtd related) after resetenv.
jtagfun
 
Posts: 24
Joined: Sun Aug 29, 2010 11:37 am

Re: DockStar JTAG

Postby jtagfun » Mon Sep 13, 2010 10:27 pm

I compared env from a brand new Dockstar and env after resetenv and found two differences:

(1). "ceserialno" was not set by resetenv.
(2). "ceboardver" was set by resetenv to "REDSTONE 0.1", but it's "REDSTONE 1.0" for the new Dockstar.

After setting "ceserialno" and changing "ceboardver" to "REDSTONE 1.0" I was able to recover kernel and root-fs.
jtagfun
 
Posts: 24
Joined: Sun Aug 29, 2010 11:37 am

Re: DockStar JTAG

Postby ril3y » Tue Oct 05, 2010 2:43 am

Hey guys, I am not sure that I have "bricked" my dockstar. Here is what is happening.. I am attempting to put a new linux image on my dockstar. I have followed various walkthroughs and I always fail at here:

Code: Select all
U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: REDSTONE:0.1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

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.35.4
   Created:      2010-09-25  23:03:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1062884 Bytes =  1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.



It just dies at Uncompressing Linux... I can however follow the instructions here:
http://Arch Linux ARM.com/index.php5?title=Ha ... Reflashing
and restore my dockstar with no problems at all. I am a veteran linux user so I am pretty sure I am not making a simple noob mistake. Anyone have a thought as to what I might be doing wrong? I also have purchased a Wiggler off of ebay to fix via JTAG if needed... (Since the Bus Pirate does not fully support openOCD yet)

Thanks for any suggestions!

ril3y

I can
ril3y
 
Posts: 3
Joined: Tue Oct 05, 2010 2:38 am

Re: DockStar JTAG

Postby peaslaker » Tue Oct 05, 2010 11:31 pm

You're trying to boot a generic new linux image from the cloudengines u-boot. That's not a combination that works.

I am attempting to put a new linux image on my dockstar.


From your description I am not sure how many of the old system components you are seeking to retain. This makes all the difference in the advice that can be given.
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: DockStar JTAG

Postby ril3y » Tue Oct 05, 2010 11:57 pm

So what I need to install the matching uBoot image then? And then it will boot the matching linux kernel?

Thanks for the reply

ril3y
ril3y
 
Posts: 3
Joined: Tue Oct 05, 2010 2:38 am

Re: DockStar JTAG

Postby ril3y » Wed Oct 06, 2010 1:02 pm

Oh and I am not trying to retain ANY of the default firmware features. I want a purely NEW openwrt build. Just a raw clean linux install. I am going to use the board as a linux server.

Ril3y
ril3y
 
Posts: 3
Joined: Tue Oct 05, 2010 2:38 am

Re: DockStar JTAG

Postby peaslaker » Wed Oct 06, 2010 3:01 pm

The main thing is that an ARM linux kernel must contain board specific features (depending on options chosen when the kernel is built). When the kernel is initialised, the bootloader needs to tell the kernel which board it is running on. The alternative is that the kernel is built to just support a single board.

Therefore you can fix this situation either by making sure your kernel is dockstar-specific (which is poorly documented but I think is a valid approach), or by upgrading the u-boot and specifying the appropriate u-boot parameters. The environment parameters that have special meaning are:
Code: Select all
mainlineLinux
arcNumber
bootargs

The old u-boot doesn't include the magic to load the arcNumber into the appropriate register in order to initialise the kernel correctly for the specified board. That is why a new u-boot is required.

The path that most quickly leads to success is that currently documented on the wiki: http://Arch Linux ARM.com/index.php5?title=Pl ... ug_Setboot
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 0 guests