I am working with LOGICPD EVM but without LCD . The usb_dev_msc not work well : the PC recognize the device but with errors
-Divice type : Other devices
-Manufacturer : Unknown
-Location : Port_#0008.Hub_#0003 -Device Status : "The drivers for this device are not installed. (Code 28) There is no driver selected for the device"
I think because this axample use/set LCD monitor that I haven't .
Is there someone that has used usb_dev_msc example without LCD monitor ?
Can you send me advise ?
Hi Sergio,
USB library doesn't have any dependency with LCD usage.
You may refer to BeagleBone ‘usb_dev_msc’ example from StarterWare package. This example doesn’t use LCD display.
Please let me know if you still face any issues.
Regards
Sirish
Now I found lcd for my board. Demo application work well, the usb example work as so as the mouse of my PC. With the same comand sequence I load usb_dev_msc example , the application start (initialize lcd with "idle state") but it not work well , I have the same problem. Its true : the problem not depend by lcd. I search BeagleBone in my StarterWare package but I doesn't found it. Have you other advice ? Why the PC not found the USB driver ? My board send to PC the correct information about device ( in Manufactured field I don't see "TI")? The error is :
Can you help me ?
Regards.
Sergio.
I send you an other important information: in Starterware packet , in Binary folder I have 3 type of demo.out : cgt_ccs, gcc, cgt. All types work but only gcc file work well for USB, the other 2 have driver's problem. The 3 type of usb_dev_msc binary application have the same problem and have driver's problem as mentioned before.
Sergio D'Orazio.
BeagleBone example can be found under AM335x StarterWare install path "...\examples\beaglebone\usb_dev_msc". You can download AM335x StarterWare SDK from below link.
http://software-dl.ti.com/dsps/dsps_public_sw/am_bu/starterware/02_00_00_05/index_FDS.html
"... gcc file work well for USB, the other 2 have driver's problem. The 3 type of usb_dev_msc binary application have the same problem ..."
From the above statement, I understand, you were able to execute the mouse example with gcc build only and for usb_dev_msc, you are not able to execute using any of the builds. Please correct me.
Can you please let me know:
1) The host OS being used
2) Were you able to execute the usb_dev_msc pre-built binaries without any change?
Regards Sirish
Thank's Sirish,
1- I am using Windows 7 or Windows XP with same problem
2- I have tested usb_dev_msc pre-build binaries without any change : the 3 type of binary file (gcc,cgt,cgt_ccs) have the same problem on windows 7 and on windows XP, the application start well but host PC has driver problem.
3- I have tested usb_dev_mouse pre-build binaries without any change : the 2 type of binary file (cgt,cgt_ccs) have problem on windows 7 and on windows XP, the application start well but host PC has driver problem; the gcc binary file work well , windows 7 and windows XP know the driver.
We are able to execute the example using GCC build on following the steps documented in the link below using the mini (J6) connector and Windows XP SP2 host PC. Can you please try the same and see if you can proceed?
http://processors.wiki.ti.com/index.php/StarterWare_USB#Example_Application_3
There is a know issue (check the link below) linked with binaries generated using TMS470 tool chain.
http://processors.wiki.ti.com/index.php/StarterWare_01.10.02.02_Release_Notes#Known_Issues_and_Limitations
Hi Sirish,
yesterday I wasn't at work, today I can work on this problem, I am sure that with your help I can solve all problems.
I am following the Example application 3 but I have the same problem. I have seen a different : in my Starterware packet there is USBDCDInit() function and not DCDinit() . Is it correct ?
Second problem: I have only CCSv5 compiler and not GCC compiler . Is this a problem ?
Regards Sergio.
Hello Sergio,
There is a know issue (check the link below) linked with binaries generated using CCS/TMS470 tool chain.
Latest version of TMS470 tool chain will be available at below link. You can give a try.
http://syntaxerror.dal.design.ti.com/alpha/alpha.cgi/TMS470
Since the SDK is tested working for GCC build, you can use this tool chain.
Regards. Sergio.
Can you answer me faster ?
2) and 4):
Below link provides some details on availability of updated TMS470 tool-chain for un-aligned data issue:
http://e2e.ti.com/support/embedded/starterware/f/790/t/171281.aspx#636880
3) "TMS470 isn't OMAPL138 EVM , can I load this executables ?"
From your above question, I understood, you are asking if a .out file generated using TMS470 tool-chain can be used to load over OMAP-L138.
The answer is Yes. 'TMS470 tool-chain' is what is used by CCSv5.
1) I am sorry but, I will have to check this (un-able to execute the pre-built binaries) why! I will try to get back with details soon.
It is re-verified that, the GCC pre-built binaries from the release execute without any issue.
Since the pre-built binaries are not working as expected at your end, I would request you to re-verify if you are executing as documented. If you still see the issue, please try testing the example using a different EVM set-up including a different Mini-B to Std-A connecter (used to connect to the PC).
I had Starterware_1.10.02.02 version and gcc example of this version on my EVM doesn't work.
After a discussion with Texas Italian man, I download a new version (Starterware_1.10.03.03) and gcc example on my EVM work well !!!!
I am waiting a new version of ccs compiler compatible with Starterware application.
In this wait state , I am compiling with gcc-cygwin. At the init I had problems, but now it work well.
If I will have problems , I will ask you.