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.

CC430F5137 debugging problem (Fatal error: Could not find device (or device not supported)

Other Parts Discussed in Thread: CC430F5137, MSP-FET

Hello!

I have two boards with CC430F5137. When I try to connect to board by JTAG (MSP430-FET430UIF, v1.4a), I get error ("Fatal error: Could not find device (or device not supported)   Session aborted!" ). This error occure when I use 4-wired JTAG and spi-bi-wire. For programming I use IAR MSP IDE v6.5.0.

  • Hello Oleg,

    Are you using EVMs provided by TI? The error indicates a flawed connection between the MSP-FET430UIF and target device. Make sure all connections are properly made as shown in Figure 2-1 to 2-3 of the Hardware Tools User's Guide (SLAU278).

    Regards,
    Ryan
  • Hello, Ryan!

    No, I use a third-party wireless modules. I used to program the circuit 2-1 and 2-3 from slau278. I use an external power supply, and connect the power to pin VCC_TARGET. The only thing that I have not tried is to program via the bootstrap loader.
  • The external power supply needs to be greater than 3 V but you've done correct by connecting it to VCC_TARGET (JTAG pin 4). Make sure your cables are as short as possible. Do you have any different MSP-FET430UIF devices to test with, or perhaps a newer MSP-FET? Can you measure your TEST, RST, and VCC lines with an oscilloscope?

    Regards,
    Ryan
  • Ryan, just now the board manufacturers reported that JTAG is blocked and into chip write bootloader. Is it possible? And if so, how to unlock JTAG?
  • The CC430 family of devices has similar JTAG features to that of the F5xx/6xx families including the JTAG security lock key which resides in the BSL memory address range. More information is provided in Section 1.4.2 of SLAU320 and Section 1.11.2 of the CC430 User's Guide.

    Regards,
    Ryan
  • Thank you very much, Ryan!

**Attention** This is a public forum