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.

IWRL1432BOOST: XDS110 Port Not Detected in Functional Mode After Flashing Custom-Built Appimage

Part Number: IWRL1432BOOST
Other Parts Discussed in Thread: IWRL1432, UNIFLASH,

Tool/software:

Hello,

I am experiencing an issue where the XDS110 port is not detected when I switch the SOP to Functional Mode.

When I flash the appimage file provided by TI, the XDS110 port remains detectable even after switching to Functional Mode:
File:
C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\Level_Sensing\high_accuracy_low_power_sensors\prebuilt_binaries\high_accuracy_xwrl14xx_demo.appimage

However, when I build the project in Code Composer Studio 12.7.0 using mmWave low-power SDK 05.05.00.02 by following the steps:
"High Accuracy Low Power Sensors => High Accuracy xWRL14xx AppSS => Import to CCS IDE",
and flash the generated appimage file:
File:
high_accuracy_xwrl14xx => Debug => high_accuracy_xwrl14xx_demo.Debug.appimage,
the XDS110 port is no longer detected after switching to Functional Mode.

Additionally, the file sizes are different:

My built file: high_accuracy_xwrl14xx_demo.Debug.appimage (188KB)
TI provided file: high_accuracy_xwrl14xx_demo.appimage (144KB)
Why is the XDS110 port not detected in Functional Mode when using my built appimage?

Additional (The section where the hard fault occurs is shown in the image below.)

Thank you.

  • Additionally, I used CCS for debugging by referring to the following URL:

    URL: https://dev.ti.com/tirex/explore/content/radar_toolbox_2_30_00_12/software_docs/using_ccs_debug.html

    After completing the steps up to "3.2 Connect to EVM using Target Configuration File and Load Binaries", the program enters the HwiP_hardFault_handler() function defined in Hwip_armv7m_handlers_freertos.c:

    void HWI_SECTION HwiP_hardFault_handler()

    {

    volatile uint32_t loop = 1;

    while(loop)

    ;

    }

    In the Console window, the following error occurs:

    Cortex_M4_0: Can't Run Target CPU: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g., lower TCLK). (Emulation package 12.7.0.00105)

  • Hi

    There is no relation between XDS110 detection with the CCS project being built. In the prebuilt image, release configuration is provided which is the reason for difference in the size of the appimage that you are seeing.

    What do you mean by XDS110 is not detected? Are you referring to the COM ports in the device manager? If you are able to connect the JTAG as shown in the picture above, it means XDS110 is active and detected correctly

    Before you connect the JTAG and load the CCS project generated .out, have you flashed empty.release.appimage from <MMWAVE_SDK5_INSTALL_DIR>\examples\empty\xwrL14xx-evm\m4fss0-0_freertos\ti-arm-clang

    After you have flashed  empty.release.appimage, you need to configure the IWRL1432 EVM in functional mode and reconnect the EVM. Are these steps followed before connecting to JTAG?

    After connecting CM4 through JTAG, you need to perform Run->Reset->CPU Reset before loading the .out

    Let me know if it works correctly after following these steps

    Regards

  • What do you mean by XDS110 is not detected? Are you referring to the COM ports in the device manager?
    => Yes, that's correct. I followed the process outlined in the "Build the Firmware from Source Code" section from the URL below and generated the high_accuracy_xwrl14xx_demo.Debug.appimage file.

    I then used UniFlash to "Load Image" with this file.
    After the upload was completed, I confirmed the console message:
    [2025. 2. 7. PM 4:46:29] [SUCCESS] Program Load completed successfully.

    Next, I powered off the device and switched from Flashing Mode to Functional Mode.
    However, when I powered the device back on via USB, the XDS110 was not detected in the Device Manager (COM ports were not found).

    If I switch back to Flashing Mode and power on the device, the COM ports reappear in the Device Manager.
    I have two IWRL1432BOOST boards, and both exhibit the same behavior.

    URL: dev.ti.com/.../node
    ------------------------------------------------------------------------------------------------------------------------------------------
    If you are able to connect the JTAG as shown in the picture above, it means XDS110 is active and detected correctly
    => When I flashed "C:\ti\MMWAVE_L_SDK_05_05_00_02\examples\empty\xwrL14xx-evm\m4fss0-0_freertos\ti-arm-clang\empty.release.appimage" using UniFlash, the XDS110 was correctly detected in the Device Manager.

    Before you connect the JTAG and load the CCS project generated .out, have you flashed empty.release.appimage from <MMWAVE_SDK5_INSTALL_DIR>\examples\empty\xwrL14xx-evm\m4fss0-0_freertos\ti-arm-clang
    => I have followed the entire process outlined in the URL below, and this corresponds to the "1. Flash the CCS Debug Firmware using UniFlash" step.

    After you have flashed empty.release.appimage, you need to configure the IWRL1432 EVM in functional mode and reconnect the EVM. Are these steps followed before connecting to JTAG?
    => I have followed the entire process outlined in the URL below, and this corresponds to the "2. Setup the EVM for Functional Mode" step.
    I was able to connect JTAG after performing the sequence of actions described in the URL.
    URL: CCS Debug Mode Guide
    ------------------------------------------------------------------------------------------------------------------------------------------
    After connecting CM4 through JTAG, you need to perform Run->Reset->CPU Reset before loading the .out
    => I had not performed that sequence initially, but after doing so, I confirmed that it operates correctly.
    ------------------------------------------------------------------------------------------------------------------------------------------
    Let me know if it works correctly after following these steps
    => I ran the "Industrial_Visualizer.exe" program and confirmed that it is functioning correctly (level sensing is working properly).
    ------------------------------------------------------------------------------------------------------------------------------------------
    However, even after flashing "C:\Users\MSI\workspace_v12\high_accuracy_xwrl14xx\Debug\high_accuracy_xwrl14xx_demo.Debug.appimage" using UniFlash and switching to Functional Mode, the XDS110 port is not detected in the Device Manager.

    I believe that the detection of the XDS110 port in the Device Manager depends on the appimage file being flashed.

  • Hi

    If you see that COM ports are not detected, then place the EVM in flashing mode and plug the USB. Now, you will see the COM port detected, at this point, change the SOP to functional mode and assert NRESET switch on the EVM without unplugging the USB. 

    Regards

  • When the NRESET switch is asserted, the system operates normally. However, is there a way to resolve the issue where the COM port is not detected?

    If the board is assembled into the enclosure, it will no longer be possible to assert the switch.

  • We have noted the problem but do not have a solution yet. For now, you will have to work with asserting NRESET

    Regards

  • Is this issue occurring on all IWRL1432BOOST boards, or only on the two boards that I have?

  • This issue occurs on some of the boards. We are trying to find a workaround for it

    Regards