LDC1614EVM: LDC1614 shows up as LDC1314

Edgar Ortega

Part Number: LDC1614EVM
Other Parts Discussed in Thread: LDC1614, LDC1314

Hi,

I have revamped the LDC1614 to fit into our application, I finally have the hardware up and running.

I noticed that when I flash it, my board version and the OneUI application show connected, but it thinks it is connected to : SSP EVM connected - LDC1314.

I've verified that the LDC1614 is populated on the board.

Also if I try to update firmware via USB-BSL, the USB connection drops immediately and never upgrades to the package I need, the pcb starts a loop of reconnecting and dropping but it does this at different times during the update. (FET is disconnected while doing this) and the red led on the board is on, I do hear the USB connecting to system and see it in the EVM in windows device manager.

Any ideas/suggestions?

Thanks.

over 7 years ago

0 Luke LaPointe over 7 years ago

TI__Genius 13335 points

Hello,

It sounds like initially it was flashed with the LDC1314 firmware instead of the LDC1614. Some questions to consider to help your debug.

When you put the EVM into BSL mode, how does it show up in the device manager? If it is not in BSL mode it will show up as EVM under the COM ports. Ensure that the board is indeed in BSL mode before trying to reflash the firmware.
How are you updating the firmware when it is in BSL mode? We recommend to use the MSP430 Python Firmware Upgrader. I've posted instructions for this in a different thread: https://e2e.ti.com/support/sensor/inductive-sensing/f/938/p/664915/2445916?tisearch=e2e-sitesearch&keymatch=ldc*%20bsl#2445916
Try a different USB port or PC. Sometimes we've seen that due to the version of windows or settings it may cause connecting/disconnecting issues on the USB port.

Let us know if this solves your issue.

Cheers,

Luke

0 Edgar Ortega over 7 years ago in reply to Luke LaPointe

Intellectual 270 points

Thanks so much,
It did not work, but had a closer look at my hardware and pull up resistors between processor and sensor on SDA and SCL were missing, installed them and it worked.

I tested it by flashing the processor with the CCS7, ( Had to install MSP430v4.1.1 compiler), and the board went back to EVM1314.

Also had to upgrade to Sensing Solutions GUI 1.9.4, (was using 1.9.2).

Do you have any idea how to modify the code snoc072 to report as EVM1614?

Thanks.

0 Edgar Ortega over 7 years ago in reply to Edgar Ortega

Intellectual 270 points

Found the #defined, host_interface.h, near the top, uncomment HOST_DEVICE_LDC1614, comment out HOST_DEVICE_LDC1314.

Sensors

Sensors forum

LDC1614EVM: LDC1614 shows up as LDC1314