[ARMedslack] slackwarearm on seagate dosckstar

Davide louigi600 at yahoo.it
Wed Apr 17 14:53:39 UTC 2013

>> I'ts been a while since I last fiddled with the seagate dockstar ... I
>> puklled it back out wanting to involve it on media streaming via DLNA.
>> I fiddled with a slackwarearm 14 miniroot image on a versatile emulated
>> machine untill I thaught I had all the bits and pieces needed to boot from
>> the dockstar ... but when I put the image on usb stick this is all I'm
>> getting:
>> Loading file "/boot/uImage" from usb device 0:1 (usbda1)
>> 2343448 bytes read
>> Loading file "/boot/uinitrd" from usb device 0:1 (usbda1)
>> 7314743 bytes read
>> USB device 0:1 is bootable
>> ## Booting kernel from Legacy Image at 00800000 ...
>>    Image Name:   Linux-3.8.7-kirkwood
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    2343384 Bytes = 2.2 MiB
>>    Load Address: 00008000
>>    Entry Point:  00008000
>>    Verifying Checksum ... OK
>> ## Loading init Ramdisk from Legacy Image at 01100000 ...
>>    Image Name:   Slackware ARM for kirkwood platf
>>    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
>>    Data Size:    7314679 Bytes = 7 MiB
>>    Load Address: 00000000
>>    Entry Point:  00000000
>>    Verifying Checksum ... OK
>>    Loading Kernel Image ... OK
>> OK
>> Starting kernel ...
>> Uncompressing Linux... done, booting the kernel.
>> And that's it ... nothing more on the serial console and nothing on the
>> network .... actually it does not even appear to mount the root filesystem
>> as the last mount seems to be coherent with the last time I mounted it on my
>> PC
>> Do I need to recompile the kernel (I'm using the kirkwood uImage) or is
>> there something else wrong ?

>Probably. But we need more information. How did you collect the
>information that you've shown us? How is your system (if that term can
>be applied) configured? Including how did you connect its serial

Seial via a modified DKU-5 cable and use minicom to manage that.
The console is connected right and I can use it if I boot into the old image I burned into the internal flash .... but that old system is too crippled to do the streaming stuff !!!!

>I have one here, about all I did was pop off its housing and study the
>internals. My other problems were along the lines of setting the boot
>blocks to boot from an attached USB key.

The custom uboot scripts I'm using can boot ok from a USB stick provided you put the images in the right place so uboot can find them ... and as you can see they are found and loaded.
I even tested that all was ok by booting from a clashNG image on the usb stick too and it boots ok.

>Currently I'm running my activities on a plain black pogoplug. Who has
>an 8Gig key attached, and one of those portable external drives
>attached sized 80 Gig and formatted as FAT32.

>I originally had plans to, do stuff with either via the USB ports but
>not as if either were wearing drives with stuff on them, but doing
>something specific.

>I still want to, ah, target my Dock Star but the difficult part is to
>workout how to attach that serial console and without damaging things.

Buy a DKU-5 compatible cell Phone cable it has the required voltage serial port interface for the dockstar (and may more devices) ... you will just need to tut off the phone plug and wire up an old 2.5" hdu conenctor to the cable so that you can plug it into the dockstar. I think I mention how I did that on the clashNG project 
If you want a readymade woking image for the dockstar have a look at bclash on sourceforge ... it's unmaintained over the last 2 years but it still boots from my onboard flash on the dockstar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20130417/5d4a2fce/attachment-0001.html>

More information about the ARMedslack mailing list