Here are a list of some things to try if you encounter a USB memory stick or SD card that does not seem to work correctly with Warp. This all applies to PADS release 2.1 or greater.

A) Check to see whether the Warp sees the physical device.
For SD, 'cat /proc/driver/pikasd' If the result is 0 then there is no Sd card recognized. If the result is non-zero then a SD card is seen.
For USB, unfortunately there is no equivalent

B) Check 'dmesg' for any relevant USB or SD messages.

C) Remove and insert the USB or SD and note the messages. Are any messages generated? If not, this could a sign of a problem with the connector.

D) Try the 'mount' command. This will detemrine if the device has been mounted correctly. And if it has been mounted you will see the filesystem being used. Ideally, 'fat' and fat derivatives like vfat and fat32 as well as msdos, ext2 and ext3 are preferred. Also note that USB can take a significant portion of time before mounting.

E) Try the 'fdisk /dev/mmcblk0' or 'fdisk /dev/sda' commands. Option 'p' will list the partition table. Usually you want to ensure that devices have a simple single partition.

F) Try the media in a standard PC to see if it is working there.

G) Try placing a file on the device with a command like 'touch /mnt/sd/test' or 'touch /mnt/usb/test'. If this is not possible check the write access (or lock status) of the device.

H) If autorun specifically is not working then there are two places this can be spawn. First, on boot up the file rc.S will spawn this script. Second, at runtime the autorun script is spawn from udev. This udev scripts are located in '/etc/udev'.

I) If you have a serial cable you can try attaching this to possibly gain more debug inforamtion. For example, in uboot you can try the following commands 'usb info' and 'mmcinfo'.

For any additional problems please post to this thread.