Ti usb serial

Control your cookie preferences You can control your preferences for how we use cookies to collect and use information while you're on TI websites by adjusting the status of these categories. These cookies help identify who you are and store your activity and account information in order to deliver enhanced functionality, including a more personalized and relevant experience on our sites. If you do not allow these cookies, some or all site features and services may not function properly.

If you do not allow these cookies, some or all of the site features and services may not function properly. Accept all. These cookies, including cookies from Google Analytics, allow us to recognize and count the number of visitors on TI sites and see how visitors navigate our sites.

This helps us improve the way TI sites work for example, by making it easier for you to find information on the site. These cookies enable interest-based advertising on TI sites and third-party websites using information you make available to us when you interact with our sites.

Interest-based ads are displayed to you based on cookies linked to your online activities, such as viewing products on our sites. Then, PC's Device Manager is shown as below figure. I executed Btool. Then, BTool is shown as below figure. What is the problem? Up 0 Down Cancel. Try COM13 instead. Dear TI. COM 12 is only shown in the BTool. So, I can not try to connect COM I solved this problem.

This problem was PC enviornment error. Thank you for your quick response. Like a USB to serial convertor.

For connecting from the Windows 10, weather we need to have different driver files? Already some driver files are available in the folder. The controller is used as USB device mode?

In this case, the VBUS connection to the controller is necessary? Yes, that's essentially right. Suggest reviewing the comments at the top of the main. I'm not certain if they work on Win10 by default. If not, see the E2E below for a potential fix. Recommend reading section When the example code executed, the code stuck SysCtrlInit while! I think it should work with the internal oscillator if you want to try that. You've confirmed the example SW does not get stuck anywhere while running and debugging the code?

The 'device descriptor request failed' error might be an issue on the windows PC side. Searching online it seems there's a number of things you can try. You may need to try re-installing the drivers following the method from the E2E post below:. I have confirmed that the example code is working correctly. I have tried different methods in the forum posts as suggested, but no use.

Always shows that "The best driver for your device is already installed". I have tried both the examples and inf files.

Could you please clarify what you meant by " respective driver. Is this the correct step for driver update. Any other method I need to follow? I am seeing something different than you. The example works fine after all these steps too.

Maybe it's still a hardware issue. Can you provide a picture of your HW set-up? You can find the files in the directory below:. I could able to solve the issue by modifying the clock configuration.

Actually we are using 10Mhz external crystal.