• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: GPlugD observations on: April 29, 2011, 05:54:50 PM
I haven't actually tried to boot from other devices.  I pulled the 4 gig card and simply made a 16Gb card with the proper partitions (name them the same as what's in the shipping 4G chip, otherwise they won'y boot).  Their documentation is all over the place.  I've found that naming things like they are on the working device is the path of least resistance.  I didn't really mess around with U-Boot.  They sent me a new kernel that allowed the LAMP stack to work so I could get on with what I'm trying to do.  They aren't very good with documentation or version control.  It's sort of you get what you get and it does what it does.  Good luck.
2  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: April 29, 2011, 05:47:37 PM
Sorry,  I haven't been following the post lately, got other stuff going on.  To answer the earlier thread, I had to get an RMA too.  They took care of shipping.  I just got my dreamplug back yesterday.  Same one as I shipped them.  All they did was re-flash the bootloader so that the unit is now running at 1.2 GHz like they advertise.  Although they could have flashed it with Debian like I asked them to when I sent it back to them,  they just sent it back to me with the same Ubuntu 9.04 like it had before (I sent it back before the Debian image was up on the website).

It's easy to become critical of the way they operate if you don't take into consideration that they are supplying inexpensive hardware to a largely hobbyest market.  There's not a lot of profit in long customer support cycles to people that buy in quantities of one.
3  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: March 29, 2011, 10:57:57 AM
Mystery solved!  Grin

i just spoke with Nancy over at GTI.  She says there were a few units accidentally shipped with Ubuntu 9.04 and some of those units were running at 400 MHz.  New units are shipping with 1.2 GHz and Debian.  I was just one of the lucky people to get a slow beast with a doggy OS.  New one on it's way to me.  Thanks for the help guys!
4  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: March 29, 2011, 08:43:32 AM
I realize that the bogo in bogomips stands for bogus, however, comparing apples to apples one would expect the same processor running at the same speed on essentially the same platform (Guruplug vs Dreamplug) to produce similar numbers.  For instance, if you look at the listing provided by Bw00ster0 on his Dreamplug running Debian his bogomips number is 1192 whereas mine is 396.49.  I have a Guruplug which reports 1192 bogomips, a GplugD which reports 796 and this Dreamplug which reports 396.  Funny how the 1192 is similar to what you might expect of a processor running 1.2 GHz.  The 796 is sort of consistant with the 800 MHz of the GplugD and the 396.49 is consistant with how slowly the text scrolls down the screen when I list a large directory tree.  If I had to guess, I'd say there is something screwed up in a U-Boot setting a bad divide ratio or something.  It really does look like the device is being grossly underclocked.  It doesn't run particularly cool though.  I mean, it's not hot or anything but it'a about as warm as my GplugD.

Really, I'm more concerned with things like it doesn't recognize a cable connected to either ethernet port unless I boot the device with the cable connected.  Once a cable is connected into an ethernet port and ifconfig shows an IP address associated, unplugging the cable will never cause ifconfig show the cable disconnected  regardless of how long you wait.

I'd love to replace U-Boot, the kernel and root_fs to something that works.  I see a couple of people say that they have 1.6.38 and Debian running on their Dreamplug.  I'm not a Linux guy by nature so I need someone to give me a nudge in the right direction.

For instance can someone tell me if I replace the kernel with one from the Sheevaplug repository can I use a root_fs from the Guruplug?  I mean, the Dreamplug really does look just like a repackaged Guruplug +.

As usual, any help is appreciated.

 


5  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: March 27, 2011, 09:29:15 AM
bwooster0 -

Is yours showing the bogomips as 396.49?  I mean this thing looks seriously slow next to both my Guruplug and my GplugD.  Text scrolls down the screen very slowly and I don't have anything running on it.  All I've done is let it boot up.  I've noticed some other weird things too.  It doesn't recognize anything plugged into either ethernet port unless you boot up with the ethernet cable in place, then it gets a valid address from the server but you can only ping other devices on the local network but nothing out on the internet (you cannot apt-get anything).   You know, I have things that I want to do with these plugs but troubleshooting the U-Boot, the Kernel and the root_fs is not on that list.  I wouldn't even mind it if it was just figuring the stuff out once but it's every single device and update I get.  I'd like to put these things in a product I'm working on, but so far,  3 out of every 4 weeks of effort is going into figuring out what GS has done this time.  I can't even count on getting the same device with the same firmware/OS every time I order one.  Once I get a single system working completely correctly, my intent is to get several hundred at a time.  Hopefully, if I order an entire run, most will be the same! or similar.   Smiley

Do you have any idea what version of U-Boot, kernel and file system is up on the Plugcomputer downloads page?  Since it's dated Mar 4, 2011, I'm assuming it's not the same as my March 11 build.

Also, I see where one of the NewIT guys says he's got the Dreamplug booting from the external SD slot.  I'd be ok with that too.  Right now, my GplugD does that, although, there is an issue where it will not reboot correctly unless I remove the SD card with the power off.  That's a major pain in the butt too.  GS and Marvell are looking into that right now.  They think I have a defective device.  They issued me an RMA and we'll wait and see.

As far as the competition, the single driving factor for me is the physical dimension.  Even the Dreamplug form factor is starting to push the limits.  I plan to use these devices in a form of telemetry application that needs to fit in a small diameter pipe.  The GplugD fits ok into a 4" pipe and the Dreamplug can fit into a 6" pipe.  All the other devices I'm aware of are larger and wouldn't work for me (Except perhaps a Gumstix and they're too expensive and a little slow, last time I looked).

As they say, you get what you pay for.
6  Hardware and U-Boot firmware / Hardware / I just received a new Dreamplug today on: March 26, 2011, 01:52:38 PM
I just received a new Dreamplug today and it doesn't match the DreamPlug user guide.

root@ubuntu:/proc# cat cpuinfo
Processor       : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS        : 396.49
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

root@ubuntu:/proc# uname -a
Linux ubuntu 2.6.33.6 #1 PREEMPT Tue Feb 8 03:18:41 EST 2011 armv5tel GNU/Linux

root@ubuntu:/proc# cat version
Linux version 2.6.33.6 (root@localhost.localdomain) (gcc version 4.2.1) #1 PREEMPT Tue Feb 8 03:18:41 EST 2011


root@ubuntu:/etc# cat debian_version
5.0


U-Boot 2011.06-02334-g8f495d9-dirty (Mar 01 2011 - 06:57:05)
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
Marvell>> ?
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
date    - get/set/reset date & time
dhcp    - boot image via network using DHCP/TFTP protocol
echo    - echo args to console
editenv - edit environment variable
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
go      - start application at address 'addr'
help    - print command description/usage
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mtest   - simple RAM read/write test
mw      - memory write (fill)
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
sf      - SPI flash sub-system
sleep   - delay execution for some time
source  - run script from memory
tftpboot- boot image via network using TFTP protocol
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor version


Marvell>> printenv
bootcmd=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootc;
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
eth1addr=XX:XX:XX:XX:XX:XX
ethaddr=XX:XX:XX:XX:XX:XX
stdin=serial
stdout=serial
stderr=serial

Environment size: 524/4092 bytes

Well, there you have it.

If someone wants me to print out anything more, I'd be happy to.

One other observation and that is that this system feels really doggy.  Like the 396 BogoMips is a realistic number.  My GplugD shows 796 BogoMips and feels slower than my GuruPlug that shows 1196 BogoMips.  If anyone has any ideas about what it all means I'd love to hear about it.

I'd also like to get this over on Debian so if anyone has any experience doing that perhaps you could point me in the right direction.  Every other Plug I have came with Debian.

Ubuntu 9.04 is not what I want to be running.

Thanks!

7  Hardware and U-Boot firmware / Hardware / GPlugD observations on: February 16, 2011, 12:07:49 PM
I've been playing the the GPlugD for a few days now and here are some additional observations.  In my previous post I made mention of the constant stream of block errors on the SD card.  Marvell contacted me regarding my post and explained that the new version 2 kernel solves that problem.  Sure enough, wiping the SD card and replacing the Kernel and the root_fs does, in fact, solve those issues and renders the GplugD much more stable.  Globalscale should consider putting the later buids on the plugs up front or at least post a message about this as it took a couple of days before I replaced the SD images. 

There is a mp4 file titled "The American" on the GUI.  For me, clicking this file causes a browser to open and start playing the file.  About 1-2 seconds into the file playing the screen tears, goes black and then the system crashes.  I'm not sure what's going on there but the Marvell folks tell me that their system doesn't do that so... I have no explanation or actually any interest is solving this as it is not really germain to what I am doing with the plug.

MySQL 5.0.51a will not install on the device. PERIOD!.  3 days of messing with it failed.  During configuration apt-get and aptitude both report that there are unresolved dependencies that preclude configuring or running mysqld.  It aborts immediately after starting and before writing a error log.  It's just gone!  Appache2 runs fine.

I have decided to see if I can get Squeeze to run on the device and that's what I am currently doing.  So far the only messages I have received from the upgrade is that the UImage does not support dependency booting.  We shall see if the system boots when it gets done.  More to follow...
 
8  Hardware and U-Boot firmware / Hardware / Re: I just got my new GPlug-Display on: February 13, 2011, 02:12:20 PM
Ok, so here's an update.  I took the sd card out of the GPlug-D and put it into a Ubuntu system.  The Ubuntu system showed the kernel partition but not the fs partition.  So I told Ubuntu to remove the drive safely and it did.  When I plugged the card back into the Ubuntu system after the safe removal, both partitions showed up.  I shut the card down a second time and placed it back into the GPlug-D.  the GPlug-D booted up perfectly normally after that.  BTW - the names of the partitions do not match the docs as per building a bootable SD card. 

So, now that it's working again.  Here are some first impressions.  It's not a speed demon by any stretch.  It takes about 50 seconds or so to boot up into X11.  There is almost no apps of any kind on the GUI (not even a method of changing screen resolution).  Iceweasle is the browser and it works, but it takes about 5 seconds from the time you click the mouse until anything actually happens.  Scrolling the screen is relatively fast but changing to another web page sends you back to the 5 second wait. 

There is a MP4 file on the device called "The American".  Attempting to play it causes a media player to open and the video starts but the whole screen garbles and then the whole system crashes and you have to reboot to get the system back up.  Doing an apt-get install of anything produces a pretty much continuous stream of IO error messages saying that the ext3 fs has encountered another bad block. 

With Internet, HDMI and the console running I'd say the temperature of the device is about the same as what I see on my GuruPlug Server Standard.
9  Hardware and U-Boot firmware / Hardware / I just got my new GPlug-Display on: February 13, 2011, 09:13:07 AM
I just got my new GPlug-Display and am a bit confused!!! 

When I received it on Friday afternoon I lit it off from the console and it ran just fine.  I changed the password and took a quick look around the file system.  Since I didn't have a HDMI cable I only ran it from the console.  Saturday night I picked up a HDMI cable and plugged it into the unit and a monitor.  The plug failed to boot and terminated in the following lines of code (these are only the lines from where it diverged from a normal boot).:

 mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 USD   3.75 GiB
 mmcblk0: p1 p2
mmc1: new high speed SDHC card at address 0001
mmcblk1: mmc1:0001 00000 7.60 GiB
 mmcblk1: p1
usb 1-1: new high speed USB device using pxau2h-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected     // This is the last normal line!!!
pxa-sdh pxa-sdh.0: DATA Line Error(status: 0x0010)!
mmcblk0: retrying using single block read
pxa-sdh pxa-sdh.0: DATA Line Error(status: 0x0010)!
mmcblk0: error -5 transferring data, sector 2046218, nr 24, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2046234
Buffer I/O error on device mmcblk0p2, logical block 229623
lost page write due to I/O error on mmcblk0p2
JBD: recovery failed
EXT3-fs: error loading journal.
EXT2-fs: mmcblk0p2: couldn't mount because of unsupported optional features (4).
List of all partitions:
b300         3941376 mmcblk0 driver: mmcblk
  b301          104594 mmcblk0p1
  b302         3836250 mmcblk0p2
b308         7974912 mmcblk1 driver: mmcblk
  b309         7970816 mmcblk1p1
No filesystem could mount root, tried:  ext3 ext2 cramfs vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

The big question I have is, is this a failure of the plug or simply a corruption of the fs on the sd card?  Also, does anyone know what the procedure is to send the unit back for warranty?

Thanks in advance!

Glen
Pages: [1]