Print

[NewITMalcolm]

Hi Ralph,

Using dd to load GuiPlug 2.6, the sizes were OK, but partition 1 was created as type 83 (Linux) instead of 06 (fat16) and again fsck was unhappy, of course.

Are you using the correct image? The Sheevaplug image has partition 1 as ext2 and the Dreamplug image has a Fat16 partition 1.

Both images are very similar but the Dreamplug version has Wifi and bluetooth enabled.

http://downloadsnewit.co.uk/SD-images/Dreamplug/GuiPlug/
http://downloadsnewit.co.uk/SD-images/Sheevaplug/GuiPlug/

NewITJames

[Ralph Houston]

Using dd to load GuiPlug 2.6, the sizes were OK, but partition 1 was created as type 83 (Linux) instead of 06 (fat16) and again fsck was unhappy, of course.

Are you using the correct image? The Sheevaplug image has partition 1 as ext2 and the Dreamplug image has a Fat16 partition 1.
Both images are very similar but the Dreamplug version has Wifi and bluetooth enabled.

Having spent some time on this, using dd creates partitions labelled as two type 83. Inside partition 1 is a fat16 uImage file which boots OK. This is just a matter of untidiness, so you can't fsck the kernel image or back it up for example without correcting the partition label to fat16 (06).

dd is probably not the best tool for this as the destination must be defect-free for it to work.

An interesting note is that the Bluetooth and wireless LEDs are not activated by this code.

[Classe]

I think it would be really nice to have a basic version of Debian with say, just SSH, that an efficient, lean server could be built on.

Headless versions of Debian Squeeze, Wheezy and Ubuntu are in the pipeline and will be offered on SD card and for free download.

And it seems from my observations that the reported flakiness of the wireless is down to Network-Manager

Wireless should be 100% stable on the GuiPlug v2.6.

NewITJames

Hi James,

Great work with GuiPlug 2.6, stable and a smooth boot    When can we expect to find headless version of Debian Squeeze?

Only one issue where I concur with Ralph, fs on vfat is reported as 83...


BR

[NewITMalcolm]

Hi Classe,

When can we expect to find headless version of Debian Squeeze?

I am working on them now (Squeeze and Wheezy) and they should be ready end of this week.

The Globalscale Debian image is ready for download if you want to try that.

http://downloadsnewit.co.uk/SD-images/Dreamplug/ex-factory-2011-08-26-debian-lenny/

Only one issue where I concur with Ralph, fs on vfat is reported as 83...

I used mkdosfs to create the partition that was misreported so I will try mfks.vfat and see it that fixes it on the new images. I think it may be a bug in Ubuntu on the machine I created the images on.

#mkdosfs -n gui-kern-fat /dev/sdb1
mkfs.vfat -n dp-kern /dev/sdb1

NewITJames

Update - The fix is actually to use fdisk then < t 6 w > on the 1st partition to set it's type to FAT16. (Thanks to Confusticated/Ralph).

 

[Gabrielx]

Hi guys, I Have a Sandisk 8 gb micro sd card that i put guiplug 2.6 on. Works fine when i use it on the external sd slot with an adapter but when i try to put it inside the dreamplug it wont boot.  Help Plz

[NewITMalcolm]

Hi Gabrielx,

Could you post the bootlog to show where it fails and your uboot environment variables(printenv) please.

NewITJames

[Gabrielx]

Hi Gabrielx,

Could you post the bootlog to show where it fails and your uboot environment variables(printenv) please.

NewITJames

Im kind of a newbie do i need the jtag to get the bootlog and uboot environment??

[Gabrielx]

Hi Gabrielx,

Could you post the bootlog to show where it fails and your uboot environment variables(printenv) please.

NewITJames

Im kind of a newbie do i need the jtag to get the bootlog and uboot environment??

/quote]

Here You Go.


U-Boot 2011.06-02334-g8f495d9-dirty (Mar 28 2011 - 05:21:06)
Marvell-DreamPlug

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
SF: Detected MX25L1606 with page size 256, total 1 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0
Unknown command 'el_in_mem' - try 'help'
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 02 3A 00
2 Storage Device(s) found
Device NOT ready
   Request Sense returned 02 3A 00
** Can't read from device 1 **

** Unable to use usb 1:1 for fatload **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
## Error: "botcmd_sda" not defined
Marvell>> printenv
bootdelay=3
baudrate=115200
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd_usb=usb start
x_bootcmd_kernel=fatload usb 0 0x6400000 uImage
x_bootargs=console=ttyS0,115200
x_bootargs_root=root=/dev/sda2 rootdelay=10
ethact=egiga0
ethaddr=F0:AD:4E:00:7C:AD
eth1addr=F0:AD:4E:00:7C:AE
clear_kerho=Purging kernel in memory
bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;
boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000;
bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}
clear_kerin_mem=echo Purging kernel in emory; mw 0x6400000 0x0 0x300000
bootcmd=el_in_mem; run bootcmd_sdb; run botcmd_sda
stdin=serial
stdout=serial
stderr=serial
bootargs=console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait

Environment size: 944/4092 bytes

[NewITMalcolm]

clear_kerho=Purging kernel in memory
bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;
boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000;
bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}
clear_kerin_mem=echo Purging kernel in emory; mw 0x6400000 0x0 0x300000
bootcmd=el_in_mem; run bootcmd_sdb; run botcmd_sda

You have lots of missing characters in there. it should match below

Code: [Select]

clear_kernel_in_mem=echo Purging kernel in memory; mw 0x6400000 0x0 0x300000
bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;
boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000;
bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}
bootcmd=run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda
Here are the commands to get it working.

Code: [Select]

setenv bootcmd_sdb 'setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;'
setenv boot_sdb 'fatload usb 1 0x6400000 uImage; bootm 0x6400000;'
setenv bootcmd_sda '${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;'
setenv bootcmd_eth 'setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}'
setenv clear_kernel_in_mem 'echo Purging kernel in memory; mw 0x6400000 0x0 0x300000'
setenv bootcmd 'run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda'
saveenv
then to tidy up the extra variables you have

Code: [Select]

setenv clear_kerho
setenv clear_kerin_mem


[Gabrielx]

clear_kerho=Purging kernel in memory
bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;
boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000;
bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}
clear_kerin_mem=echo Purging kernel in emory; mw 0x6400000 0x0 0x300000
bootcmd=el_in_mem; run bootcmd_sdb; run botcmd_sda

You have lots of missing characters in there. it should match below

Code: [Select]

clear_kernel_in_mem=echo Purging kernel in memory; mw 0x6400000 0x0 0x300000
bootcmd_sdb=setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;
boot_sdb=fatload usb 1 0x6400000 uImage; bootm 0x6400000;
bootcmd_sda=${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootcmd_eth=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}
bootcmd=run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda
Here are the commands to get it working.

Code: [Select]

setenv bootcmd_sdb 'setenv bootargs console=ttyS0,115200 root=/dev/sdb2 panic=10 rootwait; usb start; run boot_sdb;'
setenv boot_sdb 'fatload usb 1 0x6400000 uImage; bootm 0x6400000;'
setenv bootcmd_sda '${bootcmd_eth}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;'
setenv bootcmd_eth 'setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}'
setenv clear_kernel_in_mem 'echo Purging kernel in memory; mw 0x6400000 0x0 0x300000'
setenv bootcmd 'run clear_kernel_in_mem; run bootcmd_sdb; run bootcmd_sda'
saveenv
then to tidy up the extra variables you have

Code: [Select]

setenv clear_kerho
setenv clear_kerin_mem


Just wanted to say Thanks for the help James.

Its helped alot.

Im a pretty busy guy so thats why the thanks comes a little bit late .

[LJK]

Hi guys,

What am I doing wrong...

I received a brand new Dreamplug with 16GB SD containg GUIPlug and Mimo 720s monitor from NewIT at end of last week, 29th October.

Without SD card plugged in, the Dreamplug boots and  I can ssh onto it and log in. I can also get the placeholder web page up in my browser.

With SD card and Mimo monitor plugged in, only the power LED lights, I see no network activity and Mimo stays blank.

I looked at the contents of the SD on my Ubuntu desktop and it looks like bootable Linux.

I also tried with Mimo on a powered hub with no change. If I plug the Mimo into my desktop, I see a green screen, but it stays black on the Dreamplug.

Any ideas?