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.

How to change mode for MSP-FET430UIF to Spy-bi-wire in CCS 5.2.1?

Other Parts Discussed in Thread: MSP430F5342

 

I'm using the MSP430F5342. I have successfully connected to the part and executed code via 4-wire JTAG.

Now I have reconfigured my board to use the 2 wire SBW interface. I have verified that the board is wired according to Figure 2-3 in the Hardware Tools manual (SLAU278K).

When I try to launch debug, I get "Error connecting to the target: Unknown device"

 

Where is the setting in Code Composer 5.2.1 to tell the FET to work in SBW mode??

 

 

 

  • Hi Chris,

    a few things here.  CCS actually automatically selects.  Basically it checks for a JTAG connection and switches to SBW if it does not find it.   So there is no setting you need.   A few things when debugging.   Sometimes things can be quite capacitance sensitive and in fact there are two different values and schematics shown in the documentation.   Did you make a change to the capacitor?   There is a free flash programming tool I find useful also in order to help debug these connection issues at times.  I would see if you can connect using the free flash programmer from Elprotronic. ( www.elprotronic.com).   In this tool you specifically selelct SBW or JTAG.   What changes did you make to try swtiching modes?

    Best Regards,
    LIsa

  • I cut and jumpered a few tracks to match fig2-3. 

    I also changed the R-C pair to 47k and 2.2nF. I now changed cap to 220pF, but it still doesn't work.

    I'll try the Elprotronic tool next

     

  • Hi Chris,

    hmmm jumpering etc does not sound good for a debug connection.   However, give the elprotronic tool a try and keep us informed.  Also double check  you connections are as good and as short in trace length etc as possible. 

    Best Regards,
    Lisa

  •  

    The Elpro tool is reporting that "Verify Security Fuse" is failing.

    Next, I'm going to check waveforms on an O-scope to verify they look good.

  •  

    The Elpro tool had the wrong port selected. When I switched it from automatic to the proper COM port, it now works.

    I was able to do a blank check (which failed because there was code loaded), then a chip erase, then another blank check which passed.

     

    Then I relaunched CCS and tried to debug and everything seems to work now.

    Not sure what changed, but I'm happy! :-)

    Thanks for your help!

     

     

     

  • Hi Chris,

    very happy to hear.   All the best with development.

    Best Regards,

    Lisa