• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 1119 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

USB-CDC code problem

Murthy r

Hi friends,

I am working in the KEIL uvision3 (Real view) tool.
Right now i am working in the USB-CDC programming for the AT91SAM7SE512 processor.

I have a example source code for AT91SAM7S64 processor in IAR workbench tool.
Downloaded from www.siwawi.arubi.uni-kl.de/.../index_at91.html .This IAR code is working very well.

So, I have coverted the code from IAR to keil tool for AT91SAM7SE512 processor.

The Problem is

1. when i connect the device to the host ( PC ), I am getting the message "USB device is not recognized".

2. can I include any files to this?

Could you please advice on this.

With Regards & Thanks,
Murthy.R

Parents Reply Children
  • 0 in reply to Murthy r

    You have to narrow down the problem more.

    Trace the USB bus traffic on the enumeration.
    You have a successful implementation on SAM7S64.
    Compare the SAM7SE512 traffic with those of SAM7S64.
    Then, you'll know where the enumeration fails in detail.
    - If the enumeration stops on one of Get_Descriptor requests, the descriptor is wrong.
    - If the enumeration sequence differs in one of requests, the firmware response to the request is wrong. Find the request handler on your source code and fix the bug.

    A hardware bus analyzer is better for this purpose, but if you don't have it, download this software sniffer and 'evaluate' it :-)

    Commercial, 1-month eval:
    SourceUSB http://www.sourcequest.com/

    Tsuneo