• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 603 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR5969: MSP430FR5969 program and routine run issue on custom board

Jeiner Alvarado Fonseca
Prodigy 30 points
Part Number: MSP430FR5969


Hello,

We have a custom board that use the MSP430FR5969 microcontroller and we are using 2-wire JTAG communication to program the board. We have an issue that the board only can be programmed with the Vcc tool pin in this case 3.3V, but with the Vcc Target of the board is not possible or very hard to upload the program.

After upload the program on the board, the routine only runs with the programmer tool (MSP-FETflash) connected with the Vcc_tool pin configuration. When we use the 3.3V of the board the routine do not run on the microcontroller.

which signals are essential in this case to run the routine?

Why could be produce a error on the upload process use the Vcc_target and works with the Vcc_tool?

Best and regards,

Heiner

  • 0
    TI__Guru 71216 points

    Hello Jeiner,

    VCC_TOOL provides +3.3v from the MSPFET to power your target (if target not self-powered).

    VCC_TARGET is an input to the MSPFET to monitor target voltage VCC  and to power the "target" side of the level translators inside the MSPFET.  This is how the MSPFET can program targets that may have a different VCC than typical 3.3v.

    Is your board self powered?

    Ok, so if your custom board is "self-powered @ +3.3v" during programming, then the only connections you need between the JTAG connector and your target are:

    JTAG TARGET
    TDO/TDI RST/SBWDTIO
    TCK TEST/SBWTCK
    GND GND

    If your target has a VCC other than 3.3 then you need to connect the target's VCC to JTAG-VCC_TARGET pin.

    I have verified on the bench that this configuration works.

    Let me know if this works for you.

**Attention** This is a public forum