• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 509 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430FR59941: Using DSLite in UniFlash to force MSP430 into 4-wire JTAG mode with sequence on TEST/nRST pins (SYSJTAGPIN=1)

Newman
Expert 5685 points
Part Number: MSP430FR59941
Other Parts Discussed in Thread: UNIFLASH, , MSP-FET, MSP430WARE, MSP-TS430PN80B, MSP430FR5994

Hi Team MSP,

How can I use DSLite scripter in UniFlash to force MSP430 into 4Wire JTAG mode w/ TEST/nRST? 

Where is the best documentation WRT DSLite in UniFlash.. Is this the only/best ( http://software-dl.ti.com/ccs/esd/uniflash/docs/v5_0/quick_start_guide/uniflash_quick_start_guide.html ) ?

Anything in http://devi.ti.com/tirex etc.. or a specific app note?

Thanks, Merril

Ref.. The required sequence on TEST/nRST to enable 4Wire JTAG is described here.. (https://www.ti.com/lit/ug/slau320aj/slau320aj.pdf )..

  • 0
    TI__Mastermind 49692 points

    Hi Merril,

    Newman said:
    How can I use DSLite scripter in UniFlash to force MSP430 into 4Wire JTAG mode w/ TEST/nRST? 

    DSLite uses settings found in the device-specific .ccxml file. You used to be able to specify the JTAG mode in the target configuration settings in Code Composer Studio (CCS), which would update the target configuration (.ccxml) file accordingly (assuming CCS project properties > CCS General > Project > "Manage the project's target-configuration automatically" option was deselected), but not anymore.

    Now, the JTAG mode is configured automatically and by default, it can't be selected manually in CCS. However, I was able to use @Chester Gillon's helpful thread Forcing SBW mode to modify the 'msp430_emu.xml' file used by CCS and switch between SBW and 4-wire JTAG on a target board. This functionality depends on whether or not the JTAG circuitry matches what's recommended in the MSP430 Hardware Tools user's guide.

    <?xml version="1.0"?>

<drivers id="MSP430">
                <isa Type="MSP430" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <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>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="1">
                                                  <choice Name="Fast" value="0"/>
                                                  <choice Name="Medium" value="1"/>
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>

    Newman said:
    Where is the best documentation WRT DSLite in UniFlash.. Is this the only/best ( http://software-dl.ti.com/ccs/esd/uniflash/docs/v5_0/quick_start_guide/uniflash_quick_start_guide.html ) ?

    Yes.

  • 0 in reply to James Evans
    TI__Expert 5685 points

    Hi James, 

    Thanks.. some more clarifiers..

    1. Do MSP430's that support both 2Wire (SBW) and 4Wire JTAG.. always default to 2Wire (SBW)?

    2. If an MSP430 that supports both 2Wire (SBW) and 4Wire JTAG is only connected to the debugger w/ 4Wire JTAG (and no nRST/TEST connections).. can the debugger communicate w/ the MSP430? 

    3. Or are the nRST/TEST signals still required to switch the device from 2Wire (SBW) to 4Wire JTAG?

    Thanks, Merril

  • 0 in reply to Newman
    TI__Expert 5685 points

    Hi James,

    Thx!  As mentioned.. the real device in use is the (MSP430FR59941).  In addition to the q's above WRT 2Wire/4Wire defaults/etc on MSP.. Here is some more info on the issue.. 

    The overall goal is to get the tools CCS/DSLite/etc to be able to program the MSP430FR w/ SYSJTAGPIN=1.

    Add'l customer info below..

    Thanks, Merril

    It turns out that the older, gray MSP-FET also mostly don’t work with SYSJTAGPIN =1 using UniFlash, DSLite, or MSPFlasher; we get the same flash failures.

     Confirmed what does work

    Steps to reproduce success with UniFlash (using 3rd party tool)

    1. Have MSP-FET and unit set up
    2. Confirm UniFlash fails (cannot flash the device)
    3. Quit Uniflash
    4. Run a command with FET-Pro-430-Lite (blank device, erase,  or flash, any command seems to work) – this succeeds
    5. Quit FET-Pro-430-Lite
    6. Launch Uniflash and flash the device – this now succeeds

     So it seems the FET-Pro-430-Lite is performing some sequence to allow access to flash the device.  Perhaps it is also setting SYSJTAGPIN to 0?

     Is there a way to have Uniflash, DSLite, or MSFlasher do the same and set SYSJTAGPIN to 0 before flashing?

  • 0 in reply to Newman
    TI__Mastermind 49692 points

    Hi Merril,

    Newman said:
    1. Do MSP430's that support both 2Wire (SBW) and 4Wire JTAG.. always default to 2Wire (SBW)?

    I would assume so for most devices with shared JTAG pins, since the goal is to increase the IO count while allowing 4-wire JTAG to be used if necessary. However, the proper circuit must be used for whichever interface is used.

    Newman said:
    2. If an MSP430 that supports both 2Wire (SBW) and 4Wire JTAG is only connected to the debugger w/ 4Wire JTAG (and no nRST/TEST connections).. can the debugger communicate w/ the MSP430? 

    No. Footnote D in Figure 2-1 Signal Connections for 4-wire JTAG Communication in the MSP430 Hardware Tools User's Guide says the following:

    "The connection to the JTAG connector RST pin is required when programming or debugging a device that supports 2-wire JTAG communication, even when using 4-wire JTAG communication mode on these devices."

    Newman said:
    3. Or are the nRST/TEST signals still required to switch the device from 2Wire (SBW) to 4Wire JTAG?

    Yes. See my comment above. The reason is given in the Configuring JTAG Pins section of the MSP430FR58xx, MSP430FR59xx, and MSP430FR6xx Family User's Guide.

    "With SYSJTAGPIN cleared, the pins with JTAG functionality are configured as general-purpose I/O. In this case only a special sequences on the TEST and RST/NMI pins enables the JTAG functionality."

    More details about this sequence is provided in the Enable JTAG Access section of the MSP430 Programming With the JTAG Interface app note, under the MSP430 devices with Spy-Bi-Wire (SBW) access bullet. Note that the RST/NMI pin mentioned above corresponds to the SBWTDIO pin mentioned below. Also, the TEST pin mentioned above corresponds to the TEST/SBWTCK pin mentioned below.

    "Devices with SBW also support the standard 4-wire interface. The 4-wire JTAG interface access is enabled by pulling the SBWTDIO line low and then applying a clock on SBWTCK. Exit the 4-wire JTAG mode by holding the TEST/SBWTCK low for more than 100 µs."

    I hope this summary clears things up. Make sure to carefully implement the 4-wire JTAG circuit in Figure 2-1 Signal Connections for 4-wire JTAG Communication in the MSP430 Hardware Tools User's Guide if that's the interface you want to use.

  • 0 in reply to Newman
    TI__Mastermind 49692 points
    Newman said:
    As mentioned.. the real device in use is the (MSP430FR59941).

    Thanks. It's always good to know which device is actually being used. I updated the thread title accordingly.

    Newman said:
    The overall goal is to get the tools CCS/DSLite/etc to be able to program the MSP430FR w/ SYSJTAGPIN=1.

    Let me talk through this approach. By default, a new unprogrammed device will not have SYSJTAGPIN = 1. They would need to program the device with code that enables this register, using the SBW interface (assuming they don't use the JTAG entry sequence) or JTAG interface (assuming the JTAG entry sequence is sent).

    It sounds like the entry sequence is working with IAR and FET-Pro-430-Lite but not with UniFlash, DSLite or MSPFlasher. Can they program the device using CCS? I'm assuming they are using the correct JTAG circuit.

    In the meantime, I'll try to find a target board for the FR5994 to check if I can program the device via 4-wire JTAG, MSP-FET and UniFlash. I may need to order some devices, so I'll let you know tomorrow what I find.

  • 0 in reply to James Evans
    TI__Mastermind 49692 points

    Hi Merril,

    Quick update. I found a target board with a MSP430FR5994 device. Using CCS v10.3, black MSP-FET, MSP-TS430PN80B target board with JP3 to JP8 set to JTAG mode, I programmed the blink LED code example from MSP430Ware. This code does not set SYSJTAGPIN = 1. CCS programmed the board successfully, so the entry sequence must have been sent correctly.

    /* --COPYRIGHT--,BSD_EX
 * Copyright (c) 2015, Texas Instruments Incorporated
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * *  Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * *  Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *
 * *  Neither the name of Texas Instruments Incorporated nor the names of
 *    its contributors may be used to endorse or promote products derived
 *    from this software without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
 * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
 * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 *******************************************************************************
 * 
 *                       MSP430 CODE EXAMPLE DISCLAIMER
 *
 * MSP430 code examples are self-contained low-level programs that typically
 * demonstrate a single peripheral function or device feature in a highly
 * concise manner. For this the code may rely on the device's power-on default
 * register values and settings such as the clock configuration and care must
 * be taken when combining code from several examples to avoid potential side
 * effects. Also see www.ti.com/grace for a GUI- and www.ti.com/msp430ware
 * for an API functional library-approach to peripheral configuration.
 *
 * --/COPYRIGHT--*/
//******************************************************************************
//  MSP430FR5x9x Demo - Toggle P1.0 using software
//
//  Description: Toggle P1.0 using software.
//  ACLK = n/a, MCLK = SMCLK = default DCO
//
//           MSP430FR5994
//         ---------------
//     /|\|               |
//      | |               |
//      --|RST            |
//        |               |
//        |           P1.0|-->LED
//
//   William Goh
//   Texas Instruments Inc.
//   October 2015
//   Built with IAR Embedded Workbench V6.30 & Code Composer Studio V6.1
//******************************************************************************
#include <msp430.h>

int main(void)
{
    WDTCTL = WDTPW | WDTHOLD;               // Stop WDT

    // Configure GPIO
    P1OUT &= ~BIT0;                         // Clear P1.0 output latch for a defined power-on state
    P1DIR |= BIT0;                          // Set P1.0 to output direction

    PM5CTL0 &= ~LOCKLPM5;                   // Disable the GPIO power-on default high-impedance mode
                                            // to activate previously configured port settings

    while(1)
    {
        P1OUT ^= BIT0;                      // Toggle LED
        __delay_cycles(100000);
    }
}

    Then, I generated a TI-TXT file from the same code example in CCS, copied it to a known location on my PC, opened UniFlash v6.2, browsed to the location of the TI-TXT file and successfully programmed the device using the 4-wire JTAG interface. This indicates that UniFlash also must have sent the entry sequence correctly to switch from SBW to JTAG.

    Thus, this sounds like a hardware issue rather than a tools issue.

  • 0 in reply to James Evans
    TI__Mastermind 49692 points

    Hi Merril,

    I was able to duplicate the behavior you described above. As a prerequisite, the MSP430 device must be programmed with code that enables the SYSJTAGPIN = 1 before trying to program it with UniFlash or DSLite. It is not a hardware issue, but a software issue related to UniFlash, and I've filed a bug to resolve it in a future release.

    When trying to program the device using UniFlash and DSLite, I encountered an error on the initial try, but after trying again, the device would get programmed successfully. I realized that the first failed attempt was erasing the device, which changed SYSJTAGPIN back to 0, the default value. That is why the second attempt worked for me.

    In the meantime, here is a workaround that will allow them to use DSLite to program the MSP430FR5994, even if it was already programmed with code setting SYSJTAGPIN = 1.

    Prerequisite

    • Modify 'msp430_emu.xml' file used by CCS to select a specific JTAG interface
    • In CCS, select the "2 Wire Devices accessed by 4wire JTAG protocol" option under View > Target Configurations > Advanced and save the changes to the .ccxml file
    • Copy that file to a known location and rename it to distinguish it from the default .ccxml file

    Changes for DSLite

    • Modify 'msp430_emu.xml' file used by UniFlash/DSLite to support the JTAG interface defined by the .ccxml file
      • File is located here: C:\ti\uniflash_<version number>\deskdb\content\TICloudAgent\win\ccs_base\common\targetdb\drivers\msp430_emu.xml
      • Add what you added to CCS's file, but place it under the FR59xx device section. See example below: 
        msp430_emu.xml 
        <?xml version="1.0"?>

<drivers id="MSP430">
                <isa Type="MSP430" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <property Type="hiddenfield" Value="MSP430" id="interface" />
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="1">
                                                  <choice Name="Fast" value="0"/>
                                                  <choice Name="Medium" value="1"/>
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
                <isa Type="MSP430L092" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <property Type="hiddenfield" Value="MSP430" id="interface" />
                                                <property Name="Emulation Type" desc="Emulation Types" Type="choicelist" id="emuType" Value="0">
                                                                <choice value="Normal"/>
                                                                <choice value="ROM"/>
                                                </property>
                                                <property Type="hiddenfield" id="NormalActivationCode" Value="0xA55AA55A"></property>
                                                <property Type="hiddenfield" id="ROMActivationCode" Value="0x5AA55AA5"></property>
                                                <property Type="hiddenfield" id="supportExtMemDL" Value="true"></property>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="0">
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
                <isa Type="MSP430C09x" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <property Type="hiddenfield" Value="MSP430" id="interface" />
                                                <property Type="stringfield" id="password" Name="Password: (HEX format)"></property>
                                                <property Type="hiddenfield" id="passwordMinLength" Value="8"></property>
                                                <property Type="hiddenfield" id="passwordMaxLength" Value="8"></property>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="0">
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
                <isa Type="MSP430FR57xx" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
												<property Type="hiddenfield" id="supportLPMx5" Value="true"></property>
                                                <property Type="stringfield" id="password" Name="Password: (HEX format)"></property>
                                                <property Type="hiddenfield" id="passwordMinLength" Value="0"></property>
                                                <property Type="hiddenfield" id="passwordMaxLength" Value="120"></property>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="1">
                                                  <choice Name="Fast" value="0"/>
                                                  <choice Name="Medium" value="1"/>
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
				<isa Type="MSP430FR59xx" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
												<property Type="hiddenfield" id="supportLPMx5" Value="true"></property>
                                                <property Type="stringfield" id="password" Name="Password: (HEX format)"></property>
                                                <property Type="hiddenfield" id="passwordMinLength" Value="0"></property>
                                                <property Type="hiddenfield" id="passwordMaxLength" Value="120"></property>
												<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>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="1">
                                                  <choice Name="Fast" value="0"/>
                                                  <choice Name="Medium" value="1"/>
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
                <isa Type="MSP430F1xx_SLOW" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <property Type="hiddenfield" Value="MSP430" id="interface" />
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="0">
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>
                <isa Type="RF430FRL15X" ProcID="0x6b800000">
                                <driver file="../../DebugServer/drivers/msp430_emu.dvr">
                                                <connectionType Type="MSP430"/>
                                                <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
                                                <property Type="hiddenfield" Value="MSP430" id="interface" />
                                                <property Name="Emulation Type" desc="Emulation Types" Type="choicelist" id="emuType" Value="0">
                                                                <choice value="Normal"/>
                                                                <choice value="ROM"/>
                                                </property>
                                                <property Type="hiddenfield" id="NormalActivationCode" Value="0xA55AA55A"></property>
                                                <property Type="hiddenfield" id="ROMActivationCode" Value="0x5AA55AA5"></property>
                                                <property Type="hiddenfield" id="supportExtMemDL" Value="true"></property>
                                                <property Name="JTAG/SBW Speed" desc="JTAG/SBW Speed" Type="choicelist" id="interfaceSpeed" Value="0">
                                                  <choice Name="Slow" value="2"/>
                                                </property>
                                </driver>
                </isa>

		<isa Type="CORTEX_M4_432" ProcID="0x75803800">
		        <driver file="../../DebugServer/drivers/msp430_emu.dvr">
		            <connectionType Type="MSP430"/>
		            <property Type="hiddenfield" Value="msp430.dll" id="dllName" />
		            <property Type="hiddenfield" Value="MSP430" id="interface" />
		            <property Type="hiddenfield" Value="true" id="haltOnConnectByDefault" />
		            <property Type="hiddenfield" Value="true" id="supportsNonIntrusiveConnect" />
		            <property Type="hiddenfield" Value="true" id="disableInternalFlashManager" />
		            <property Type="hiddenfield" Value="true" id="disableArmAdvancedFeatures" />
		            <property Type="hiddenfield" Value="true" id="disableSoftwareBreakpoint" />
		            <property Type="hiddenfield" Value="true" id="disableSoftLaunch" />
		            <property Type="hiddenfield" Value="true" id="msp432fet" />
		            <property Name="JTAG/SWD (Auto-detect)" desc="JTAG/SWD (Auto-detect)" Type="choicelist" id="interfaceSpeed" Value="1">
		                <choice Name="Fast" value="0"/>
		                <choice Name="Medium" value="1"/>
		                <choice Name="Slow" value="2"/>
		            </property>
		            <property Type="hiddenfield" Value="true" id="Make Device Secure" />
		        </driver>
	    </isa>
	    <isa Type="CS_DAP" ProcID="0x38000405">
        	<driver file="NONE">
	            <connectionType Type="MSP430"/>
        	</driver>
	    </isa>

</drivers>

      • Save the changes
    • Open command prompt and navigate to DSLite.bat location: C:\ti\uniflash_<version number>
    • Run this command after connecting MSP-FET to the device and after tweaking arguments for your configuration, and be sure to use the .ccxml file from earlier

    dslite --config=2_MSP430FR5994_2x4.ccxml --verbose --flash --verify msp430fr599x_1_sysjtagpin_1.c.txt

    The device should be programmed successfully. Here's the output from my test:

    C:\ti\uniflash_6.2.0>dslite --config=2_MSP430FR5994_2x4.ccxml --verbose --flash --verify msp430fr599x_1_sysjtagpin_1.c.txt
Executing the following command:
> "C:\ti\uniflash_6.2.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\bin\DSLite" flash --config=2_MSP430FR5994_2x4.ccxml --log=ds_new.log --verbose --flash --verify msp430fr599x_1_sysjtagpin_1.c.txt

For more details and examples, please refer to the UniFlash Quick Start guide.

DSLite version 10.2.0.2249
Configuring Debugger (may take a few minutes on first launch)...
        Initializing Register Database...
        Initializing: MSP430
        Executing Startup Scripts: MSP430
Connecting...
Loading Program: msp430fr599x_1_sysjtagpin_1.c.txt
        Preparing ...
        0 of 28 at 0x4000
        0 of 16 at 0xff80: 16%
        0 of 130 at 0xffb4: 25%
        Finished: 25%
        Setting PC to entry point.: 25%
info: MSP430:  There were 174 bytes written.
Verifying Program: msp430fr599x_1_sysjtagpin_1.c.txt
        Preparing ...
        0 of 28 at 0x4000
        0 of 16 at 0xff80: 16%
        0 of 130 at 0xffb4: 25%
        Finished: 25%
info: MSP430: Program verification successful for msp430fr599x_1_sysjtagpin_1.c.txt
Success

C:\ti\uniflash_6.2.0>

    I hope this helps. Please let me know if you have any questions.

  • 0 in reply to Newman
    Guru 34033 points

    BTW, I don't get it what is the customer target? Is there any advance of using JTAG over SBW on FRAM devices?

  • 0 in reply to zrno soli
    TI__Mastermind 49692 points

    The customer was experiencing unwanted entries into BSL mode using the SBW interface and setting SYSJTAG=1 to switch to JTAG was a temporary fix to prevent those BSL entries. It quickly became obvious that this was a corner case that our tools didn't handle correctly whereas the Elprotronic and IAR tools did. I believe the customer has resolved whatever was causing the unwanted BSL entries, but I wanted to share the workaround in case they or other customers needed a solution before it was fixed in an upcoming release.

**Attention** This is a public forum