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.
Many of the inductive sensing EVMs can utilize the same debugging process to solve an issue where the EVM won't connect to the GUI. This post will talk about the different possibilities and how to resolve them.
This guide applies to inductive sensing EVMs that use the MSP4305528 in their EVM. Generally, these EVMs use the Sensing Solutions GUI. This includes but is not limited to: LDC1000EVM, LDC1314EVM, LDC1614EVM
In the case that an inductive sensing EVM isn't communicating with a PC, it is usually one of three main causes, a failed firmware update, a failed driver install, damage to the board. In the case that the board is physically damaged, there isn't much that can be done but there are steps that can be taken to solve the first two issues.
In the case of a failed driver install, the proper EVM driver is included with the Sensing Solutions GUI. You can manually update the EVM's USB driver through the device manager with the driver file being located at C:\ti\Sensing Solutions EVM GUI-1.10.0\EVM Driver if the GUI was installed in the default location. The files name is evm.inf. Note that '1.10.0' is the sensing solutions GUI version so it may change depending on which version you installed.
In the case for a failed firmware update, the best option is to reflash the EVM by putting it into BSL mode and using a separate tool to flash the MSP on the board. Here are the steps to do that:
At this point, the EVM should be recognized by the Sensing Solutions GUI and connect properly.
If you have any questions, feel free to ask a new question.
Best Regards,
Justin Beigel