Debian on Dockstar on a usb

Hello is there a way to install Debian on Dockstar on a usb key from a pc running Debian without using the Dockstar thank you

You can create this rootfs on your Linux PC:
http://forum.doozan.com/read.php?2,12096

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

thank you but it looks complicated to do: (

This is the instruction to create rootfs (instruction always seems complicated because it is written to spell out all technical details):

Quote

Updated 07 Feb 2014:

Rootfs Debian-3.13.1-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.13.1-kirkwood-tld-2 (and its new features).

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:
- tarball size: 95M
- install size: 276M
- a basic wheezy rootfs
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, and nfs server/client packages.
- see LED controls in /etc/rc.local, and /etc/rc0.d/K07halt (for NSAxxx LEDs control, see pbg4, and buttzy)
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:
Debian-3.13.1-kirkwood-tld-2-rootfs-bodhi.tar.bz2
md5:
7e41aa117a9cea341f007bc6a53ad6a8

Installation:

- format a new ext3 USB drive, and label it rootfs. Note: if your uBoot env for usb_rootfstype is ext2, then use an ext2 USB drive.

- As root user, cd to top level directory and extract it (assuming the USB drive is mounted at /media/sdb1)
cd /media/sdb1
tar -xjf Debian-3.13.1-kirkwood-tld-2-rootfs-bodhi.tar.bz2

- edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype.

sync
- reboot

Ok, too summarize the steps in simple language:

- Download the tarball to your Linux PC.
- Mount a newly formatted Ext3 USB thumb drive.
- Extract the rootfs tarball to the USB drive as root user.
- Sync and umount the USB drive.
- Take it to the Dockstar and cold start.

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

ok thank you;)
I'll try as soon as I fix my Dockstar
because I have a problem to re install the uboot with cable ca-42

CE>> setenv ipaddr 192.168.0.21
CE>> setenv netmask 255.255.255.0
CE>> setenv serverip 192.168.0.1
CE>> saveenv
CE>> nand erase 0x100000 0x400000
CE>> tftp 0x800000 ce_kernel_redstone_v63.img
CE>> nand write.e 0x800000 0x100000 0x1e30f0
CE>> tftp 0x1000000 ce_ramdisk_v2.0b.img.gz
CE>> setenv bootargs $(console) root=/dev/mtdblock2 initrd=0x1000000,0xb39a59
CE>> saveenv
CE>> bootm 0x800000

this is the tutorial that I use except that I'm writing my DockStar not: CE >> but: U-bott >>
I do not if this is what is important
once followed this tutorial my DockStar plant it stops :(


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x51064
331876 bytes read: OK
## Starting application at 0x00C00000 ...


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
u-boot>> nand erase 0x100000 0x400000

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete.
OK
u-boot>> setenv ipaddr 192.168.0.20
u-boot>> setenv serverip 192.168.0.4
u-boot>> saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0xc0000 -- 100% complete.
Writing to Nand... done
u-boot>> nand erase 0x100000 0x400000

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete.
OK
u-boot>> tftp 0x800000 ce_kernel_redstone_v63.img
Using egiga0 device
TFTP from server 192.168.0.4; our IP address is 192.168.0.20
Filename 'ce_kernel_redstone_v63.img'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#####
done
Bytes transferred = 1978608 (1e30f0 hex)
u-boot>> nand write.e 0x800000 0x100000 0x1e30f0

NAND write: device 0 offset 0x100000, size 0x1e30f0
1978608 bytes written: OK
u-boot>> tftp 0x1000000 ce_ramdisk_v2.0b.img.gz
Using egiga0 device
TFTP from server 192.168.0.4; our IP address is 192.168.0.20
Filename 'ce_ramdisk_v2.0b.img.gz'.
Load address: 0x1000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
######################
done
Bytes transferred = 11770457 (b39a59 hex)
u-boot>> setenv bootargs $(console) root=/dev/mtdblock2 initrd=0x1000000,0xb39a59
u-boot>> saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0xc0000 -- 100% complete.
Writing to Nand... done
u-boot>> bootm 0x800000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.22.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1978544 Bytes = 1.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.

and it remains above the block I just do nothing

if you have the solution that would help me a lot
thank you again for your attention



Edited 2 time(s). Last edit at 04/09/2014 07:07AM by DJDavid.

DJDavid,

Your U-Boot is fine! there is nothing wrong. What you are trying to do below, is to load the stock kernel image ce_kernel_redstone_v63.img into mtd2

CE>> setenv ipaddr 192.168.0.21 
CE>> setenv netmask 255.255.255.0 
CE>> setenv serverip 192.168.0.1 
CE>> saveenv 
CE>> nand erase 0x100000 0x400000 
CE>> tftp 0x800000 ce_kernel_redstone_v63.img 
CE>> nand write.e 0x800000 0x100000 0x1e30f0 
CE>> tftp 0x1000000 ce_ramdisk_v2.0b.img.gz 
CE>> setenv bootargs $(console) root=/dev/mtdblock2 initrd=0x1000000,0xb39a59 
CE>> saveenv 
CE>> bootm 0x800000

If you really want to run stock CE kernel, then the above makes sense (Note: I have not looked closely at those addresses, so don't know if they are correct).

However, if you only want to install U-Boot then it is already installed and running OK. So just create a Debian rootfs like I've mentioned in previous post and boot the Dockstar with it. And save the entire boot log so you can see what going on. In case it does not complete booting, post the log here.

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

hello I really need help my docksat's not even light up so I'm this tutorial: http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag /
ca for me was already happen a few years ago
but here is the error message I then all looks good plug

Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.

C:\Users\PC>openocd -f board/dockstar.cfg
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
Error: The specified JTAG interface was not found (buspirate)
The following JTAG interfaces are available:
1: parport
2: ft2232
3: amt_jtagaccel
4: gw16012
5: presto
6: usbprog
7: jlink
8: vsllink
9: rlink
10: arm-jtag-ew
Command handler execution failed

C:\Users\PC>

help me please

Help !!!! please :(

Have you looked at this post?
http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate

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