Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Can you provide a reference schematic to your baseboard?

Do you have a USB memory stick connected to one of the two ports?

-Mike

Hi,

USB stick is not connected. It is a USB cable only.
The configuration is like this :

UART to USB via FT232R : This works..able to login as root.
USB1 pins 23,25 pinhead to USB : This connection does not get recognized when connected to PC.
Should this be USB0 instead ?

Could you please let me know on what pins which USB is supported ?
For example :
Pin numbers x,y : USB/1.1
Pin numbers a,b : USB/2.0
..and how to get them detected.

Any help getting this working is appreciated.
Thanks
TN.

USB support for the OMAP-L138 is fully described in the User Guides provided by the TI on it's OMAP-L138 Processor web page.

USB1 (pins 23,25) is a HOST only USB 1.1 compliant port. You cannot hook it directly to a PC as that port is intended to be a USB controller/hub (e.g., so you can plug in a keyboard or mouse or USB stick, etc.).

USB0 (pins 29,31) is an OTG capable USB 2.0 compliant port. By default, I believe that it may be configured as a HOST port, but you can reconfigure the kernel (and rebuild it) to make it a CLIENT or peripheral port to plug into your PC. You will need to consider how the port should present itself to the PC (e.g., as a mass storage device, a serial port, a camera, etc.) and locate/find the appropriate host/PC side drivers to complete the interface.

I would recommend posting these questions on the TI E2E site, as these are specific to the OMAP-L138 (and not our module) and you'll likely get a lot more help than we can provide.

-Mike

Thank you very much for the information. After using USB 1.1 port as host port, connecting a USB flash drive, I have problem as described here : http://support.criticallink.com/redmine/boards/10/topics/666
lsmod shows empty list and the modules under kernel do not have module for usb.
Now, I am stuck in a loop. How can I transfer anything ?
Thanks for your patience.

You will need to rebuild the kernel (and install it on your system) such that it supports USB mass storage devices and ensure that the FAT filesystem is enabled.

You can download a new kernel image (painful, I understand) to run out of memory or burn into the NOR FLASH via uBoot using the serial "loadb" command and sending the file via the kermit protocol. Then you can boot the new kernel image and your device should be seen and a mount point created by udev.

-Mike

1. Read for binary (kermit) download to 0xc0700000 at 115200 bps...
   Then I sent the uImage via kermit (binary, same baud, 1byte checksum )
   After file transfer, the iminfo 0xc0700000 shows
   Checking image at c0700000
   Legacy image found
   Bad Header Checksum.

Would you please guide how to fix this ? Thank you.

What program are you using for terminal access?

I just tested with Tera Term Professional Version 4.57, using the default Kermit settings, and the Kermit transfer seems to have worked fine:

U-Boot > loadb
## Ready for binary (kermit) download to 0xC0700000 at 115200 bps...
## Total Size      = 0x001e2e64 = 1977956 Bytes
## Start Addr      = 0xC0700000
U-Boot > iminfo

## Checking Image at c0700000 ...
   Legacy image found
   Image Name:   Linux-2.6.34-rc1-00103-gb9bfedc-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1977892 Bytes =  1.9 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK

\Greg

Thank you. I downloaded Tera Term and it worked !
sorry to bother you - one last question. I noticed that after kernel installation using the uImage I built, the modules are missing. How can I make sure the drivers (.ko) files get into the uImage ?

What modules are missing exactly? In the kernel menuconfig you can elect to "Enable loadable module support" and then include certain drivers as modules (select M instead of Y in the menuconfig). Perhaps you changed this when rebuilding the kernel? Or are you referring to the kernel objects provided by Critical Link in the MDK release (dsplinkk.ko, fpga_ctrl.ko, fpga_uart.ko, etc.)?

\Greg