I have some questions about why my MSP430 RF2500 won't consistently connect to the COM Port for the UART connection. I coded the echo received character demo code onto my board (msp430x22x4_uscia_uart_01_9600.c), and at first it worked perfectly, exactly as I expected. I'm using RealTerm, and I changed the settings accordingly to the desired COM Port and baud rate, and the received characters were echoed back without any issues.
However, I then coded the original Wireless Sensor Monitor Demo Access Point Code onto it, and suddenly neither RealTerm nor the WSM GUI are able to connect to the port. The WSM GUI just pops up a little window that says "unable to open com port", and when I make the same changes for Baud Rate and Port# in RealTerm, it pops up a little window that says "BadID, Probably PORT does not exist ie_BadId - Specified comport doesn't exist.". I then tried to put just the abovementioned echo code back onto the board, but had the same issues where it couldn't connect to the COM Port.
I opened up Device Manager to check that the COM Port was connected, and indeed it is listed there, and in the properties, the Device Status window says it is working properly.
Any suggestions/ideas as to why the boards aren't connecting to my PC when they were working perfectly at first? Thanks!
The built in COM-to-USB interface is known to be cheap and buggy. Try rebooting your PC.
Akshay Raghu"BadID, Probably PORT does not exist ie_BadId - Specified comport doesn't exist."
An 'unable to open COM port' often means that the port is in use by a different program. Some mouse drivers or smartphone-syncing apps are know for hijacking every newly appearing COM, lookign for their target device (some do so eternally). Especially when configured in an auto-detect mode.
However, some programs simply have problem with accessing or finding COM ports. There are various reasons. E.g. a hole in the list (COM2 doesn't exist, but COM1, 3, 4 etc. do). Or the port number is above 4/8/16. There are at least three different ways to enumerate COM ports. Relics form DOS age and joining APIs with WinNT.
_____________________________________Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.