- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I'm afraid I already know the answer based on a similar CCS5 question. Is there any way to force CCS6 to run a MSP-FET or MSP-FET430UIF in Spy-Bi-Wire mode?
I have inherited a board which was either stupidly or maliciously designed. The designer decided only to hook up the SBW connection, used the wrong value passive, placed it and the 8Mhz crystal far away, routing them side by side for an insane length - in short just about everything you should not do. To make rework nearly impossible this guy used 0402 parts, used no thermal breaks on the power pads so tweezers can't effectively heat enough to remove the wrong parts, placed the components so that a header obscures them so that you really can't rework anything post assembly. Luckily the header was not installed during fab because the assembly house thought it was wrong to place it on top of passives and did not populate them, but the first units we populated with connectors are scrap.
It appears based on web searches that CCS6 automatically picks the JTAG/SBW mode, but, with everything done wrong it always picks wrong. It also picks wrong if I only change the pullup (which is all I can hand rework since luckily the via to 3.3 acts like a bit of a thermal break but the return is just one big plane on the oversized cap.) If I use a MSP430F5529LP's debugger interface and jumpers, CCS6 apparently knows to use SBW and the interface works well enough to load code most of the time.
I don't need diatribes about needing to fix the interface. I don't need warnings about using an intermittent interface and possibly programming wrong. I don't need questions about why the interface was implemented the way it was. The next spin is begun and is actually being done by an actual engineer.
I do need to know if I can force CCS6 to work in SBW mode to maybe get some use out of this batch of hardware.
I looked at a CCS 6.0.1 installation, and by default there is no CCS option to control the JTAG / SBW mode which is used.Michael McCormack said:I do need to know if I can force CCS6 to work in SBW mode to maybe get some use out of this batch of hardware.
By investigation, I found that it is possible to modify the ccsv6\ccs_base\common\targetdb\drivers\msp430_emu.xml file to add a selection of the Interface Type to be used. The modification was to add the following property for the msp430_emu.dvr to the msp430_emu.xml file:
<property Name="Interface Type" desc="Interface Type" Type="choicelist" id="interfaceType" Value="3">
<choice Name="4 Wire JTAG protocol used" value="0"/>
<choice Name="2 Wire (Spy-bi-wire) JTAG protocol used" value="1"/>
<choice Name="2 Wire Devices accessed by 4wire JTAG protocol" value="2"/>
<choice Name="Protocol will be detected automatically" value="3"/>
</property>The modified Windows CCS 6.0.1 msp430_emu.xml is attached
With this XML change the Target Configuration now offers a choice of the Interface Type to be used:
The changes were tested by:
a) Using API Monitor to check that the Interface Type selected on the Target Configuration was passed into the MSP430.dll MSP430_Configure (INTERFACE_TYPE) function for all the four possible interface types.
b) With a MSP-FET430UIF connected to a MSP-5438STK that changing the interface type was having an effect in that the connection worked when "2 Wire Devices accessed by 4wire JTAG protocol" or "Protocol will be detected automatically" were selected, but failed when the other two interface types were selected.
