• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3 4 ... 6
16  General Category / General Discussion / Re: Dropbox -> How to upload files from Guruplug? on: December 16, 2010, 08:00:16 AM
There is no ARM version of the Dropbox software
17  Linux Stuff / Kernel / Re: mmc issue with eSATA plugs on: December 07, 2010, 02:49:40 PM
So ... I created a 2.6.36 kernel with the sheeva.with-linux.com config and a patch that eliminated the eSATA differences listed above.

Here's the patch. Apologies if the format is incorrect - I've commented out 4 lines in total - the 4 lines that begin +// in the code below.

Code:
--- arch/arm/mach-kirkwood/sheevaplug-setup.c.original 2010-11-13 14:25:56.000000000 +0000
+++ arch/arm/mach-kirkwood/sheevaplug-setup.c 2010-12-05 14:59:46.000000000 +0000
@@ -52,8 +52,8 @@
 };
 
 static struct mvsdio_platform_data sheeva_esata_mvsdio_data = {
- .gpio_write_protect = 44, /* MPP44 used as SD write protect */
- .gpio_card_detect = 47,   /* MPP47 used as SD card detect */
+// .gpio_write_protect = 44, /* MPP44 used as SD write protect */
+// .gpio_card_detect = 47,   /* MPP47 used as SD card detect */
 };
 
 static struct gpio_led sheevaplug_led_pins[] = {
@@ -86,8 +86,8 @@
 
 static unsigned int sheeva_esata_mpp_config[] __initdata = {
  MPP29_GPIO, /* USB Power Enable */
- MPP44_GPIO, /* SD Write Protect */
- MPP47_GPIO, /* SD Card Detect */
+// MPP44_GPIO, /* SD Write Protect */
+// MPP47_GPIO, /* SD Card Detect */
  MPP49_GPIO, /* LED Green */
  0
 };

This does seem to eliminate the problems I reported in my first post. As to whether this is an appropriate way to fix those problems ...?
18  Linux Stuff / Kernel / mmc issue with eSATA plugs on: November 27, 2010, 04:51:33 AM
I have encountered a problem, which I have traced back to the kernel, when using an SD card on an eSATA plug that boots from NAND.

The problem is that the SD card is not recognised at all, but in some cases it may be recognised if it is inserted in a particular way (ie very quickly), or perhaps the first SD card that is inserted is recognised, but after it is removed, no other SD cards may be recognised.

My investigations tell me:

  • SATA support (using the "sata_mv" module) was first offered in kernel version 2.6.33
  • "Official support" for the eSATA Sheevaplug arrived with 2.6.34
  • On an eSATA plug, with all kernels since 2.6.34, /dev/mmcblk0 is just fine if the plug is booted with arcNumber 2097
  • Conversely, with all kernels since 2.6.34, if an eSATA plug is booted with arcNumber 2678, /dev/mmcblk0 is not recognised
  • In the kernel source, in arch/arm/mach-kirkwood/sheevaplug-setup.c, there is some relevant code


Here are fragments of the code that I have been looking at:

Code:
static struct mvsdio_platform_data sheevaplug_mvsdio_data = {
/* unfortunately the CD signal has not been connected */
};

static struct mvsdio_platform_data sheeva_esata_mvsdio_data = {
.gpio_write_protect = 44, /* MPP44 used as SD write protect */
.gpio_card_detect = 47,   /* MPP47 used as SD card detect */
};

Code:
static unsigned int sheevaplug_mpp_config[] __initdata = {
MPP29_GPIO, /* USB Power Enable */
MPP49_GPIO, /* LED */
0
};

static unsigned int sheeva_esata_mpp_config[] __initdata = {
MPP29_GPIO, /* USB Power Enable */
MPP44_GPIO, /* SD Write Protect */
MPP47_GPIO, /* SD Card Detect */
MPP49_GPIO, /* LED Green */
0
};

And here is where those different settings come into play:

Code:
/* setup gpio pin select */
if (machine_is_sheeva_esata())
kirkwood_mpp_conf(sheeva_esata_mpp_config);
else
kirkwood_mpp_conf(sheevaplug_mpp_config)

Code:
/* enable sd wp and sd cd on plugs with esata */
if (machine_is_sheeva_esata())
kirkwood_sdio_init(&sheeva_esata_mvsdio_data);
else
kirkwood_sdio_init(&sheevaplug_mvsdio_data);

Given the symptoms (that an eSATA plug can cope just fine with SD cards when it boots with arcNumber 2097 - albeit without the ability to use the eSATA port), it seems to me that the problem must lie here.

I don't know why there are different GPIO settings for eSATA and non-eSATA plugs, and by hacking the code I've so far only been able to create a totally non-bootable kernel. I'll try to find time again tomorrow to try again.
19  General Category / Application ideas and development Q/A / Re: Interesting article about Sheevaplug use as webservers at The Register on: November 14, 2010, 01:43:40 PM
The author is member DamonHD
20  Hardware and U-Boot firmware / U-Boot stuff / Re: command requires more arguments on: November 05, 2010, 04:31:05 PM

Code:
sudo strace -f -e trace=bind -o strace.out php -f runme.php mmc
PHP Notice:  Undefined index: OS in /var/forge/workingcopies/esia/src/sheevaplug-installer-v1.0/runme.php on line 7

 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
Cannot parse config file: No such file or directory


I have no idea where to begin with this... any takers?


Starting at the beginning ...

Code:
sudo strace -f -e trace=bind -o strace.out php -f runme.php mmc
PHP Notice:  Undefined index: OS in /var/forge/workingcopies/esia/src/sheevaplug-installer-v1.0/runme.php on line 7

The above may be due to a change in PHP between the time that the script was created, and the version that you have on your host. It's easy to hack the script to replace the OS check with something that is appropriate for your system; the user check creates a similar problem.


Code:
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
Cannot parse config file: No such file or directory

There's a quite specific error message in the final one of these 3 lines. The config file is probably the one detailed in the first line That's where to start.
21  Hardware and U-Boot firmware / Hardware / Re: SheevaPlugs with a - (dash) in the S/N from GLOBALSCALE on: November 05, 2010, 04:24:23 PM
I set my bootargs to this:

bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none


ran this:

Marvell>> run $(bootargs); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000

got this:
Unknown command 'a0000' - try 'help'

The console setting keeps getting mangled to this:

console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)

Doesn't matter how many times i set it, it goes back to the same setting. Has anyone had this issue?



The corrupted environment variable with value a0000 is a bug in one or more versions of U-Boot. Newer versions don't have the bug.
22  Hardware and U-Boot firmware / Hardware / Re: Dead plug - Please help me with steps to recover it on: November 04, 2010, 01:28:25 AM
Try to ssh in to it. There's one version of U-Boot that produces no output on the console, so without ssh'ing in you are omitting a potentially useful test.
23  General Category / Success stories / Re: Slackware-current (~13.1) on SheevaPlug on: November 02, 2010, 11:55:13 AM
These instructions worked fine for me:

http://mirrors.vbi.vt.edu/mirrors/linux/armedslack/armedslack-current/INSTALL_KIRKWOOD.TXT

I installed to SD card (the full installation occupies 4.8G in /, and 22M in /boot ). I used an eSATA plug, but don't have the eSATA drive recognised at the moment. First time I've used Slackware, so now that I've installed it, I'm not completely sure what to do with it. But those instructions are excellent, and like tylernt, I had success first time.
24  Hardware and U-Boot firmware / Hardware / Re: Meteohub on GuruPlug Standard? on: October 25, 2010, 04:27:10 PM
http://wiki.meteohub.de/Images
25  Linux Stuff / Linux distributions / Re: Debian: Wvdial : command not found on: October 06, 2010, 11:24:54 AM
As far as wvdial is concerned, it's not available:

http://plugcomputer.org/plugforum/index.php?topic=2332.0
26  Linux Stuff / Linux distributions / Re: GuruPlug update on: October 06, 2010, 11:20:54 AM
What do you think are the "debian upgrade issues" that the Sheevaplug has? (The ex-factory Sheevaplug comes with Ubuntu 9.05).

The Guruplug comes with Debian. If the fact that the Sheevaplug comes with an end-of-life Ubuntu is the issue that you are referring to, then no, it does not apply to the Guruplug.
27  Linux Stuff / General Linux questions / Re: MAC address the same for each plug? on: October 06, 2010, 11:17:19 AM
Does each plug have a the same MAC address? I've used the command ifconfig -a and I get the same mac address.


There is a sticker on the underside of every Sheevaplug & Guruplug. The MAC address(es) of the plug should in all cases match the MAC address shown by ifconfig.


However ... in all the plugs I have seen, I think I have twice seen a difference between the outside of the plug and the actual MAC address. The process by which the MAC addresses are set (or, I suppose, the stickers are attached) is manual, so errors seemingly can occur.

You can change the MAC address on a Sheevaplug by entering at the U-Boot prompt:

Code:
setenv ethaddr F0:AD:4E:00:xx:xx
saveenv
reset

Of course you MUST use a valid and appropriate MAC address; the one I've given above is not valid but shows the format of the command. Use the actual MAC address from the sticker on your plug.
28  Hardware and U-Boot firmware / U-Boot stuff / Re: mtdparts to reference "entire" NAND read-only on: September 26, 2010, 09:53:52 AM
I don't know about referencing the NAND as one device, but these are the notes I have made (copied from an earlier thread here, most likely)

JFFS2:
Code:
mkdir/mnt/block2
mount -t jffs2 /dev/mtdblock2 /mnt/block2 -o ro

UBIFS:

cat /proc/mtd

dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"

ubiattach /dev/ubi_ctrl -m 2 -d 0
mount -t ubifs ubi0_0 /mnt/nand

OR
mount -t ubifs ubi0:rootfs /mnt/nand

umount ubi0_0
OR
umount ubi0:rootfs

(I'm not quite sure why I have the umount options listed, like I say, it was probably copied from somewhere else).
29  General Category / General Discussion / Re: Recommendable SD(HC) cards/USB sticks for the Sheevaplug on: September 24, 2010, 01:18:52 PM
The Ubuntu rootfs is the one from the original installer package; the Debian rootfs's are generated using debootstrap.

There are SD card images here
30  General Category / General Discussion / Re: Virtual Machine for GuruPlug development on: September 14, 2010, 09:17:38 AM
As promised, the files may be downloaded from the New IT website:

http://www.newit.co.uk/files-guruplug/big_ignoramus-virtual_host2010-06/

# GuruPlug_host_June_2010.zip.001
# GuruPlug_host_June_2010.zip.002
# GuruPlug_host_June_2010.zip.003
# GuruPlug_host_June_2010.zip.004
# checksum.txt

And I have created an additional file to briefly explain the files, and link back to here:

# plugcomputer_forum_link.txt
Pages: 1 [2] 3 4 ... 6