• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 ... 4 5 [6]
76  General Category / General Discussion / Re: New IT SheevaPlug Customers - Which config did you buy? on: November 30, 2009, 12:15:17 PM

What are you wanting to do with the Sheeva?

How familiar are you with Linux?


I think that getting the basic is a good idea as it seems everything that is done on the higher packages can be done for free, using instructions on here, anyway... Though I'd (a) be a little worried about messing up and (b) like to make an image of the SD card if I got one with that so I could back up in case I do mess up. I assume there is a simple way to image the on-board flash if I buy the basic model however I don't know what that is yet.

I'm hoping to use Sheeva to, initially install Tonido and use their software to easily access my work. Normally at the moment I carry a pen disk to Uni with me but actually work on a machine there and a local machine at home. Keeping things in sync is a pain so being able to always access a "latest" version would be good.

Beyond this, I'd simply like to experiment... There are a few cool things I've seen. I'd like the idea of trying out SSH and also trying to set a Squeezebox server on it (Hopefully getting a Squeezebox for Christmas). The idea of VNC is also something I'd like to try.

I'm not all that familiar with Linux. I've used it in fits and starts, with my latest attempt messing with it on my EEE PC. I actually got pretty reasonable (Obviously no guru) when doing that but once I'd got it set up how I liked it, I never messed with it anymore and then that was that. I did try to run a mail server on a linux server at Uni however that setup was too old and didn't have the packages I wanted, I wasn't allowed to install what I wanted and so that never happened. I guess I could also play with mail servers on the Sheeva too...

I guess what I'm saying is I'd like to use it as a Linux educational tool that also servers a functional purpose, too.

LavaChild -

The preconfigured options are best for those that don't want to be messing around with U-Boot and the installer. At the one extreme, Meteohub is almost a turnkey solution, and this config is aimed at the less technically able Meteohub user.

We suppose that in some cases our customers have the ability, but might not wish to spend the time learning the necessary procedures.

It seems to me that the fact you have signed up here, and are asking this question (and in particular "I'd simply like to experiment..."), suggests to me that you are someone that is prepared to work through the learning process and do it yourself. You'll find help here and on the wiki, and we can offer advice through the New IT forum too. You'll learn a lot, and enjoy it a lot by doing so.

Declaration of interest: I am a New IT employee.
77  General Category / General Discussion / Re: Multi Boot. Question RE: CqCn comment... on: November 29, 2009, 07:42:34 AM
I'm not really sure if this is the best place to post this ... but it is relevant. I'd like to see this option integrated into the installer.

I've tweaked the installer so as to automate preparation of multi-boot systems; the plugs I have prepared in this way seem to have been running OK in all tests over the past week.

Here's my complete uboot-dual-custom.txt (only the ethaddr is obfuscated). It's really just the UBIFS configuration file with boot_mmc and boot_nand variables added, and a real_bootcmd that runs first one and then the other:

Code:
#### Change ONLY in the following few lines

# Following for installation on SD card. If you want to boot from USB stick change it to /dev/sda1
# or /dev/mtdblock1 if you installed rootfs on the NAND inside the plug
bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs

# NAND flash partitions. If using kernel >= 2.6.30 then replace orion_nand with orion_mtd
mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)

# The following is an example MAC address. Change it according the MAC on the back side of the plug
ethaddr 00:50:43:xx:xx:xx

#### DONT change the following.
# Automated process the sets arcNumer to 2097, reset, runs uImage and initrd from USB stick and set bootcmd to 'real_bootcmd' above
# Bootcmd to be used after all installation is done
# removed for multi-boot functionality (see below) : real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000

bootargs_console console=ttyS0,115200
bootcmd run recover1
recover1 setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2 run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3 run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4 usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd

# Added for multi-boot functionality:
bootargs_root_nand ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd_nand setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root_nand); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_root_mmc root=/dev/mmcblk0p2 rootdelay=5
bootcmd_mmc setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
real_bootcmd run bootcmd_mmc; run bootcmd_nand

I've also amended runme.php to allow a new "dual" parameter.

When the plug tries and fails to boot from SD card U-Boot spews:

Code:
Error! cmd : 8, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201

However it gives up the attempt to boot from SD card in about 2 seconds, therefore booting is hardly delayed.

How the installer process works:

(1). Run as usual with "mmc" parameter to prepare SD card.
(2). Remove SD card
(3). Run with "dual" parameter, to install to NAND but with boot parameters that allow for multi-booting, first from SD card, and if this is not available, from NAND.

Once these steps have been completed on one plug (and a person smarter than I may be able to advise a one-step process that accomplishes all of the above), you can then:

(A). Remove SD card; boot from NAND.
(B). Mount USB stick and insert bootable SD card
(C). dd if=/mmcblk0 of=/mnt/my-usb-stick/my-sd-image.img
(D). Wait.
(E). Upon completion, remove SD card and insert a new SD card
(F). dd if=/mnt/my-usb-stick/my-sd-image.img of=/mmcblk0

Thereby cloning the bootable SD card.

In other words, if one prefers to boot from SD card, this configuration now allows for that SD card to be cloned / backed-up by the same plug, simply by not booting from the SD card. Furthermore, many different SD cards may be created, if you have prepared suitable rootfs's. I've created debian lenny, debian squeeze, and the original Ubuntu flavours so far.

Hope this is clear.
78  Hardware and U-Boot firmware / U-Boot stuff / Re: How to configure uboot without serial line? on: November 26, 2009, 06:25:08 AM
fw_setenv and fw_printenv don't work correctly on the SheevaPlug. It's been discussed here:

http://plugcomputer.org/plugforum/index.php?topic=117.0
79  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: November 26, 2009, 05:07:33 AM
I downloaded the prebuilt squeeze rootfs and used the installer (to install to SD card): worked fine.

I then modified DebianSheeva1-03.sh to refer to lenny instead of squeeze and executed the script on my SD-booting squeeze plug. The rootfs was fine except for /dev/ttyS0, which wasn't created (and I didn't notice until I tried to log in). Double-checked the script, yes, the chroot ./debian/ mknod -m 660 /dev/ttyS0 c 4 64 line is there. Manually executed chroot ./debian/ mknod -m 660 /dev/ttyS0 c 4 64 and tar czf ../rootfs.tar.gz * and this time it worked fine.

Tried a second time, by renaming the original debian directory and this time I noticed mknod: `/dev/ttyS0': File exists (and I double checked, it did seem to exist). Tested the new rootfs usiung the installer; same result (can't login using serial):

Code:
INIT: Id "T0" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

ssh'ed in and mknod -m 660 /dev/ttyS0 c 4 64; now I can log in via serial port.

Third attempt. Go back to previous filesystem; manually executed

Code:
chroot ./debian/ mknod -m 660 /dev/ttyS0 c 4 64
cd ./debian
tar czf ../rootfs.tar.gz *

Re-run installer, serial login fine now.

Does that make sense? Line 152 in the script chroot ./debian/ mknod -m 660 /dev/ttyS0 c 4 64 isn't behaving the way we want it to ... for me, at least.
80  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: November 23, 2009, 04:57:16 PM
Just seen your post about rebuilding the rootfs.tar.gz. Despite which, I am here to report a success using the downloaded rootfs.tar.gz and the installer 1.0 (ie I didn't test the script, but the procedure certainly works on my hardware).
81  Hardware and U-Boot firmware / U-Boot stuff / Re: U-boot 3.4.23 - mmcinit has odd output on: November 16, 2009, 01:42:06 AM
No joy. 

4. Linux refuses to display output or boot (two incantation recipes tried, including one that displayed output when used with a previous u-boot/kernel).


I can confirm this major problem; the plug gave off a death-like appearance. I wasn't patient enough to wait to see if the final stages of the installer worked, but re-running with an older version of U-Boot confirmed that resuscitation was possible. A version of U-Boot that kills console output is a dangerous beast. (I believe that I am responding to the correct thread in terms of where I downloaded this version, and I believe that 3.4.25 is that version).
82  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: October 16, 2009, 10:04:17 AM
Hi Reedy,

Well it looks like your Linux does see the two ttyUSB ports and there is no permission issue.
I occasionally get the same error from openocd, to recover I try the following:
* press the reset button with the paper clip
* unplug/plug the mini USB
* power cycle the plug
* rmmod and modprobe the device driver

One of the above gets the job done for me, now if it does not work for you then try:
* replacing the mini USB cable, users have complained that the mini USB socket can be loosy
* try the installer on a Linux machine
* try the installer on a XP machine (my last resort Wink)

I had one plug that was quite resistant to opencd's connection attempts. I got fed up of seeing these errors:

Code:
Error: timed out while waiting for target halted
Runtime error, file "openocd/config/board/sheevaplug.cfg", line 21:
     **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

Every time opencd tried to do its thing, it would *immediately* trigger a reboot of the plug - which I could see in the console, and by the ethernet connection alerts on my desktop.

Of course I tried disconnecting / reconnecting, rebooting the host, power cycling the plug, all sorts.

Eventually I had success by using a paperclip on the reset button and *immediately* after releasing the button, running runme.php. (Well, let's say 2 or 3 seconds later - it wasn't quite simultaneous).
83  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: October 11, 2009, 01:23:36 PM
I'm on XP, and I've been having the same issues as reedy. Specifically, this part:

Code:
reedy@reedy-laptop:/media/disk/sheevaplug-installer-v1.0$ sudo php runme.php nand

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: JTAG communication failure: check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Error: unexpected Feroceon EICE version signature
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted


Thanks!

Any ideas would be appreciated.

I was having what looked like exactly the same problem. I finally fixed it after getting a hint from this thread.

In uboot/openocd/config/interface/sheevaplug.cfg I stepped "jtag_khz 2000" first down to jtag_khz 1000 - still no go, then jtag_khz 500 and it worked. My uboot/openocd/config/interface/sheevaplug.cfg reads:

Code:
interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x9e88 0x9e8f
ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
jtag_khz 500

Pages: 1 ... 4 5 [6]