Have you experienced this with several SD cards? USB DOK/HDD?

Hi,

Regarding the USB Audio, I have my plug serving as a music jukebox @home, look @ the wiki http://plugcomputer.org/plugwiki/index.php/USB_Audio
There are some posts on the forum related to this topic that might help you, just search.

Regarding the installer on win32, are you using XP?

If you want the plug to use your custom kernel you might need to clean up the kernel modules that were installed in /lib. I suggest you use the config used in http://sheeva.with-linux.com/sheeva/ as base and add/remove from it drivers.

If you need a clean rootfs, take the Ubuntu rootfs.tar.gz from the installer http://plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=53

Look @ http://plugcomputer.org/plugforum/index.php?topic=717.0, you can also fine valuable information in the plug forum

Any special reason you did not try the installer to recover the file system on the NAND flash?

Please pay attention to the fact that the kernel running on the plug you got from GlobalScale includes Marvell LSP based Kernel (2.6.22.18+LSP) and the one you are using with installer is based on mainline (>2.6.30).

It could be that there is some bug in the mainline...

Basically after the flash burn procedure finished, you should disconnect the mini USB and connect it again (do not remove the SD card during the installation procedure).
This action is needed since windows does not release the USB device until the USB cable is removed from the PC. I tried several openocd actions but none helped.

So if windows does not release the FTDI driver (in case you do not remove the USB cable), you will not be able to see to console since windows does not allow both ports to be active (FTDI JTAG and Console) unlike Linux that does support opening ports for both devices.

The problem is this, disconnecting the USB cable might cause a HW reset which might interfer with the installation procedure, this is why you should do the disconnect of the mini USB right after the burn finished or wait several minutes for the intallation to finish, without opening the serial, it is hard to know when it finishes, a HW reset should indicate the process end (all LEDs light up).

You should have the following files on the DOK root directory:
1) initrd
2) modules.tar.gz
3) rootfs.tar.gz
4) uImage

transmission supports both torrent file upload from your PC and URL

I have my Plug running transmission-daemon, this torrent client is fast and has a slick web GUI, try it out.

Hi SuperRoach,

Running ./runme.php mmc will create two partitions on the SD card and will modify the uboot env to boot from the SD.
The USB DOK is used to trore the file system, kernel modules and uImage that is copied to the SD during the process of the installer (done by initrd loaded by uboot)

What do you mean by that?
when you run the runme.php and the console prints the openocd stuff the plug resets?

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 )

Hi klauterbach,

The cruzer is U3 based, could it be that the U3 is preventing uboot to recognize the DOK? can you try another DOK?

Regarding the Bad Magic number, since uboot could not find the DOK it continued the boot procedure by trying to load from 00800000 but since nothing was burned there but this sector was erased the uImage Magic number could not be found, thus uboot did not find a valid uImage.

Hi Reedy,


When plugging your mini USB you should see two new devices in the /dev/ttyUSB*, here is my dmesg for the mini USB plug action:

The first one is used by the openocd as JTAG and the second one is the console.
Do you see these two devices?

If you want to burn the new uboot then you can run the installer without any USB DOK connected to the plug, so basically you are running the openocd to burn the uboot and uboot env.

If this is the case I recommend you change the /uboot-env/uboot-mmc-custom.txt file.