• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 1030 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 Flash Segments MSP430F2013 using SPW

Frank Thornemann Hansen
Prodigy 10 points
Other Parts Discussed in Thread: MSP430F2013, BEEPROG2

Hello

I wish to program a segment of the information flash in the MSP430F2013 using the beeprog2 programmer from ELNEC without changing the content of the remainder of the flash.

When setting the programmer to use standard JTAG it has an option to program information memory without touching the DCO constants and the program flash however when changing to spy-by-wire this option is removed.

The programming should be used during production for writing calibration constants to the information flash and should use spy-by-wire due to reduction in wiring, which will enable the use of existing tools.

If i have understood correctly there should be no difference between the spy-by-wire and the full JTAG interface except for the speed. This does however not seem to be the case when using the beeprog2 programmer and software. Is this because they have not implementet the feature or is there a limitation in the spy-by-wire interface.

 

Frank Hansen

  • 0
    Guru 58965 points

    I do not know anything about beeprog2. But I think what you observed is because they have not implemented the feature. I use KickStart with SBW. I always tell it to erase main-flash and preserve info-flash. Never had any problem.

  • 0
    Guru 227245 points

    Frank Thornemann Hansen said:
    is there a limitation in the spy-by-wire interface.

    The SBW interface is jsut a serialization of the parallel JTAG protocol. It takes three clock cycles instead of one, and during the three cycles it will serially perform the input and output operation that normally appear parallel on the JTAG. So SBW is, in terms of functionality, 100% transparent.It's just the factor 3 decrese in speed and the decrease in required external signal lines. Internally, the SBW interface directly interacts with the normal JTAG logic.

    So if something is not working with SBW that works with normal JTAG, then someone has forgotten to implement this functionality for the SBW mode.

**Attention** This is a public forum