• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 666 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP 35xx USB Connection

Rizwan Aijaz
Prodigy 20 points

Hi,

 

I am trying to Boot OMAP 3530 from USB. The issue is when I plug the usb cable in, the device appears in Device manager for like 2-3 seconds and then goes away. I have to reset the OMAP to get the device again appear in device manager. I have been able to install usb driver for OMAP (csstusb.sys) in that brief period of appearance but it still doesn't stop OMAP to disconnect after few seconds... I have tried it for Windows 7 64-bit and Windows XP 32-bit....

 

Regards,

 

Rizwan

  • 0
    Intellectual 895 points

    Hi Rizwan,

    Are you running TI's Flash programming application? I am not sure what is your actual problem but this can happen as explained below

    While booting from USB, OMAP sends the ASIC ID through USB to host and waits for boot message. If it doesn't receive any boot message from host on USB, it goes to next boot device in the sequence i.e. UART, NAND or SD/MMC based on the SYS_BOOT pin configurations.

    So when you power ON the device first time and USB cable is connected, host will prompt for driver installation what you are able to do. Then, you need to run TI's Flash programming application and select boot device as USB. Then you need to reset the device when prompted by the application. 

    If you are not running TI's Flash programming application, OMAP will wait for boot message from USB and then move to next boot device in sequence and USB device may not be shown in device manager after that.

    Hope this helps

     

    Vini

  • 0 in reply to Vini
    Prodigy 20 points

    Vini,

    Thanks for the reply. I am using TI flash application and here is what I do. I am able to install the driver when first connecting the OMAP. Then I run the TI Flash application and select the USB as boot device. Then I select "Erase All" or "Download" and press GO. When prompted to reset the device, I do so. The download may even start but it disconnects in the middle....Following is the log that I get in output window...

    ¯     -stdout

    ¯     -omap 3

    ¯     -no_force_package_alignment

    ¯     -t 60

    ¯     -p EVM_MDDR_MICRON_512M

    ¯     -2

    ¯     chip_download NAND1BITBOOT C:\OMAP_FLASHING\Sound_OSDesign\OMAP35xx-nand.raw

    ¯     command branch NAND1BITBOOT 0x0

    ¯ Leaving parameter file:temp_script.txt

    ¯ @temp_script.txt

    ¯ Looking for device (omap usb)

    ¯ Please turn on device

    ¯ Waiting for device (omap usb) // Here I reset the device...

    ¯ Found device (omap usb)

    ¯ Awaiting ASIC id

    ¯ AsicId items 05

    ¯ AsicId id         01 05  01  34 30 07 57 

    ¯ AsicId secure_mode 13 02  01  00 

    ¯ AsicId public_id 12 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

    ¯ AsicId root_key_hash 14 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

    ¯ AsicId checksum   15 09  01  F7 48 8F 28 00 00 00 00 

    ¯ Searching 2nd for: EVM_MDDR_MICRON_512M 343007 57 GP 

    ¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_512m.2nd

    ¯ Entering parameter file:omapflash2nd.txt at line: 11

    ¯     -pheriphalboot_reopen

    ¯ Reading board configuration file Targets\Configurations\configuration_evm35xx_micron_512m.txt

    ¯ Reading definition file .\targets\definitions\definitions_omap3.txt

    ¯     -board_config Targets\Configurations\configuration_evm35xx_micron_512m.txt

    ¯ Leaving parameter file:omapflash2nd.txt

    ¯ Sending size of second file (0x00006804 bytes)

    ¯ Transferring second file to target (0x6804 bytes)

    ¯ Closing boot connection

    ¯ Waiting for device (omap usb)

    ¯ Timeout reopening connection for USB


    - Rizwan

  • 0 in reply to Rizwan Aijaz
    Intellectual 895 points

    Hi Rizwan,

    May be there is no issue with USB. There is a chance that your SDRAM is not assembled properly. To verify this you can try UART boot and if SDRAM is not mounted properly, UART boot should also not work.

    You can verify SDRAM through JTAG also.

    Someone from TI can give you more idea what is happening here based on your log messages but I have faced similar issues with OMAP CBC package and POP memory package where POP memory was not assembled properly in initial set of boards I did and I had to go with re-assembly.

    Anyone there from TI?

     

    Vini