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.

MSP432E401Y: Evaluation Board of MSP432E401YTPDTR

Part Number: MSP432E401Y
Other Parts Discussed in Thread: UNIFLASH, MSP-GANG, MSP-FET

Hello Team,
I was referring to the user guide SLAU748B for one of our designs with MSP432E401YTPDTR controller.
Ideally the shield of the crystal must me connected to the GND for better noise performance.
Please correct me if I am wrong.

Why these pins are not connected to GND?



Also, is there any problems if we connect the shield pins of the RJ45 connector and USB connectors together and connecting them to chassis GND?.


Looking for your reply.

  • Hi,

    Why these pins are not connected to GND?

      You can connect to GND but NC is also ok per vendor's recommendation. See below. 

    Also, is there any problems if we connect the shield pins of the RJ45 connector and USB connectors together and connecting them to chassis GND?.

    Please follow MSP432E System Design Guideline for chassis ground connection. https://www.ti.com/lit/pdf/slaa770

  • Hello Team,
    Can I edit/flash the boot loader of the MSP432 with the XDS110 debugger?.
    Or do I need BSL rocket to do the same?.

  • The bootloader is small piece of program that is to be loaded through JTAG just like any other programs (.e.g. hello, blinky and etc). You can load the bootloader to the flash using XDS110 debug probe or other probes like XDS200 or Jlink.

  • Hello Charles,
    Thank you for your quick reply.
    If we can flash boot loader via XDS110, why we need BSL rocket connector in the Ethernet MSP432E401Y Microcontroller
    LaunchPad?.
    So if I understand you correctly, I don't need to use the BSL rocket to flash the boot loader but just the XDS110 debugger is enough to flash the boot loader in my PCB with MSP432.
    Please correct me if I am wrong.

  • Hi,

      You use the JTAG debug probe to load the 'bootloader'. Once the bootloader is running, it will configure your specified comms port (.e.g. UART) and is going download the firmware from that specified comms interface, not JTAG. For example, the bootloader is configured to download the firmware from a UART port. You need the BSL rocket connector so that the firmware download can happen through the UART interface or other interfaces like SPI and I2C. The XDS110 is only a JTAG debug probe that allows you to download firmware through the JTAG interface, not UART, SPI, I2C and others.  

      I hope this diagram will clarify. https://www.ti.com/lit/pdf/slau746

      

  • Hello,

      You use the JTAG debug probe to load the 'bootloader'. Once the bootloader is running, it will configure your specified comms port (.e.g. UART) and is going download the firmware from that specified comms interface, not JTAG.

    In our PCB we have MSP432E401Y and TM4C(XDS110) connected like in evaluation boards. So can we use UNIFLASH with "XDS Application UART" to load the bootloader?(even in bare microcontroller)

    Can JTAG in XDS110 load the bootloader code in the MSP432E401Y? if yes please tell how that can be done?

  • Hi,

    To buy BSL-Rocket, is the below product link correct?

    https://www.mouser.in/ProductDetail/Olimex-Ltd/MSP430-BSL?qs=J7x7253A5u5ktaUHQ83VeQ%3D%3D

    If not, can you please provide the correct link?

  • Hi Monica,

      You can find additional information about BSL on the product page. https://www.ti.com/tool/MSPBSL

      Olimex-Ltd is our partner who builds BSL Rocket. You can purchase from them directly if you want from https://www.olimex.com/Products/MSP430/BSL/MSP430-BSL/. If you want to purchase from other vendors it is fine too. 

      As you can see on the product there are other options as well like MSP-FET and MSP-GANG but BSL Rocket is the lowest cost option. 

  • Hello Charles,
    Thank you for your reply.
    We have a TC2050-IDC-NL-FP connector.


    This is a 10 pin connector.
    What is the purpose of this connector.
    We cannot locate any mating connector in the XDS110.

    Looking for your reply

  • Hi,

      This is a JTAG connector to the XDS110 MCU. It is on the backside of the board at the upper right corner. This connector is for accessing the XDS110 MCU through JTAG interface.  In general, there is no reason for you to use it. 

  • Hello Charles,
    Thank you for your quick reply.
    So, if we understand you correctly, this JTAG interface will be used to flash the TM4C controller in the EVK.
    Please correct me if I am wrong.
    Can we flash the TM4C in the EVK with this JTAG interface if we use the debugger TMDSEMU110-U?.
    We have this on board debugger using the TM4C MCU in our custom board with MSP432 as main controller.
    So, we may need to flash the TM4C MCU initially in order to make it work as the debugger.
    The binary file for the TM4C is already available.

    Is it possible to flash the bootloader and firmware for TM4C mentioned in the below link?

    software-dl.ti.com/.../emu_xds110.html

    Or we need this JTAG interface to flash?

  • So, if we understand you correctly, this JTAG interface will be used to flash the TM4C controller in the EVK.
    Please correct me if I am wrong.

    Yes.

    Can we flash the TM4C in the EVK with this JTAG interface if we use the debugger TMDSEMU110-U?.

    Yes.

    So, we may need to flash the TM4C MCU initially in order to make it work as the debugger.
    The binary file for the TM4C is already available.

    Is it possible to flash the bootloader and firmware for TM4C mentioned in the below link?

    software-dl.ti.com/.../emu_xds110.html

    You will need to open a new post so the CCS and the toolchain experts can assist you. I'm not familiar enough on how to burn the XDS110 firmware onto the JTAG. If you follow the link, it is not using JTAG to update the firmware but rather through USB in DFU mode. 

    Manual update

    If manual updating or diagnostics is required, using a Windows host is highly recommended. Close any instances of CCS that are running in your system. Open a Windows Command Prompt and issue the following commands:

    Note:

    The steps below are for an installation of CCSv10.4 in the default directory. Please update the path and firmware file name when using different CCS and firmware versions.

    Note:

    For UniFlash, the path to the XDS110 folder is: [UNIFLASH INSTALL DIR]\deskdb\content\TICloudAgent\win\ccs_base\common\uscif\xds110.

    1. Go to the directory where the utility is installed:

    C:\>cd C:\ti\ccs1040\ccs\base\common\uscif\xds110

    2. Run the configuration just to make sure a XDS110-class debugger is connected (or to list how many are connected) and what is the firmware revision installed on it:

    C:\ti\ccs1040\ccs\base\common\uscif\xds110>xdsdfu -e

    3. Put the XDS110 in DFU mode:

    C:\ti\ccs1040\ccs\base\common\uscif\xds110>xdsdfu -m

    4. Run the updater, passing the firmware file and resetting the debug probe afterwards:

    C:\ti\ccs1040\ccs\base\common\uscif\xds110>xdsdfu -f firmware_3.0.0.16.bin -r

    In case of a bricked pod

    In certain scenarios there is a chance your Pod or Launchpad becomes bricked by the firmware update. Check the Troubleshooting section below for additional details.

    Finding and updating the serial number

    When using multiple debug probes in the same host, in general it is necessary to properly differentiate each debug probe by serial number.

    To find out what is the serial number of all connected debug probes, follow steps 1 and 2 above

    If you want to set the serial number to a specific value:

    1. Unplug all other debug probes from the host

    2. Follow steps 1 through 3 above

    3. Set the serial number suffix (RECOMMENDED):

    C:\ti\ccs1040\ccs\ccs_base\common\uscif\xds110>xdsdfu -n 4567 -r

    Or we need this JTAG interface to flash?

    JTAG is not a must. As described, you can use DFU to update the firmware although JTAG could be another option to reload the bootloader and the firmware. Follow the instructions in the link under the Troubleshooting section.