• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 80 subscribers
  • Views 527 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.

Programming a 'G2231 'out of the board' using the Launchpad

Manuel Perales
Prodigy 30 points


Hello,

I am developing a MSP-based board to measure temperatures. I should need to re-program the microcontroller on the final board, thru the Launchpad board, using the spy-by wire interface, i suppose. 

 

How can i do this? What signals are needed, and how i have to configure CCS4 to use the launchpad as an external programmer/debugger. 

Is it possible or not?

Thanks in advance.

  • 0
    Guru 227245 points

    The LaunchPad has 5 jumpers between teh FET part and teh target part. You need the signals labeled TEST and RST, as well as GND. Route them to your target. That's all. You might want to route VCC too if your target is not self-powered during programming.
    However, if the target is self-powered, the voltage should mathch the LaunchPad voltage. Or, if you power the target by the LaunchPad, the target's surrounding circuitry should be content with the Launchpad voltage.

  • 0 in reply to Jens-Michael Gross
    Prodigy 30 points

    Thanks for your answer.

     

    I've done that, connecting the RST, TEST, gnd, vcc, and even tx-rx sometimes. But every time Code composer says me  "Error connecting to the target: Could not find device (or device not supported).

    Should i change something in Code Composer configuration, or what should it be?

     

    Thanks again

    ManoloP

  • 0 in reply to Manuel Perales
    Expert 1620 points

    Ti will tell you that CCS will do that  "automatically" and you do not have to do anything to make it happen. They are correct most of the time.  That is, it works most of the time. The problem is, sometime for some reason, it "automatically" does not work and there is nothing you can do.

     

  • 0 in reply to OCY
    Prodigy 30 points

    It's true.

     

    In fact, for some reason that I can't understand, now it's working. 

     

    The only thing I've changed is the length of the cables that connect the launchpad with the target board.

     

    But, if it's working, it's working. It seems a little bit odd to me, but it's working ;-)

     

    Thanks to everybody!

    ManoloP 

  • 0 in reply to Manuel Perales
    Guru 227245 points

    Manuel Perales said:
    The only thing I've changed is the length of the cables that connect the launchpad with the target board.

    SBW is a serialized JTAG protocol. Where on one clock data is sent, on the next data is received on the same line (so input becomes output and input again with each clock tick tick).
    It is possible that due to line length, line capacitances, whatever, the timing is so much disturbed that the connection doesn't work anymore.

  • 0 in reply to Manuel Perales
    Expert 1610 points

    Hi,

    Manuel Perales said:
    The only thing I've changed is the length of the cables that connect the launchpad with the target board.

    from my beginning with mcu programming with homemade programmers I can tell you, that this will be the solution most of the time. A simple cable like these 4 wires can give you much pain - keep them as short as possible, use shielded cables each signal to minimize crosstalk and let every wire be the same length.

    External programming with the LaunchPad works like a charm - I'm using it on courses. But as a hint I do not use the small connector on the right of the jumpers but the jumper connectors. I just made a cable fitting on the connector out of a short piece of shielded cat7 patch cable (laying around) with two connectors on each side to easy connect the launchpad to a home build board.

    Cheers,

    Jan

     

**Attention** This is a public forum