• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 214 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Custom Firmware Upload Issue – COM Port Not Detected in Functional Mode

JAEHOON KIM
Intellectual 405 points
Part Number: IWRL1432BOOST
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Dear [TI Support Team],

I am encountering an issue where the COM port is not detected in the Device Manager after switching from Flashing Mode to Functional Mode when using a custom-built firmware file. Below is a detailed description of the issue and the steps I followed.

Steps Taken with TI-Provided Firmware (No Issues)

  1. Followed the "High Accuracy Low Power Sensors User Guide":
  2. Flashed TI-provided firmware (high_accuracy_xwrl14xx_demo.appimage) using UniFlash (Version: 9.0.0.5086).
    • File Path: 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
  3. Switched from Flashing Mode to Functional Mode.
  4. Opened Industrial_Visualizer.exe and successfully connected.
    • File Path: C:\ti\radar_toolbox_2_30_00_12\tools\visualizers\Applications_Visualizer\Industrial_Visualizer\Industrial_Visualizer.exe
  5. Loaded both configuration files successfully:
    • C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\Level_Sensing\high_accuracy_low_power_sensors\chirp_configs\high_accuracy_demo_fast_update_xwrl14xx.cfg
    • C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\Level_Sensing\high_accuracy_low_power_sensors\chirp_configs\high_accuracy_demo_xwrl14xx.cfg

There were no issues when using the TI-provided firmware.

Issue with Custom-Built Firmware(The code has not been modified.)

After following the "Build the Firmware from Source Code" process, I successfully built the firmware, generating: (Perform build without changing anything after import)

  • C:\Users\MSI\workspace_v12\high_accuracy_xwrl14xx\Debug\high_accuracy_xwrl14xx_demo.Debug.appimage
  • C:\Users\MSI\workspace_v12\high_accuracy_xwrl14xx\Debug\high_accuracy_xwrl14xx_demo_auth.Debug.appimage

File Path:
C:\Users\MSI\workspace_v12\high_accuracy_xwrl14xx\Debug\high_accuracy_xwrl14xx_demo.Debug.appimage

Steps Taken with Custom Firmware

  1. Switched to Flashing Mode and flashed high_accuracy_xwrl14xx_demo.Debug.appimage using UniFlash.
  2. Switched to Functional Mode and powered on the board.
  3. Issue: The COM port was not detected in Device Manager.
    • (When using TI’s firmware, the COM port appears correctly.)
  4. Switched back to Flashing Mode, and the COM port was detected.
  5. While in Flashing Mode, switched to Functional Mode, then pressed the S2 Reset Switch, and reattempted steps 4 & 5.
    • Result: It worked fine.

Issue Summary

  • When flashing the custom-built firmware, switching to Functional Mode results in the COM port not being detected.
  • However, when using TI-provided firmware, the COM port is detected without any issues.
  • Resetting the board while in Flashing Mode, then switching to Functional Mode, allows normal operation.

Question

Does this indicate a potential issue with the custom-built firmware?
Are there any additional debugging steps or configurations I should check?

Thank you for your support.

Best regards,

  • +1
    TI__Expert 4180 points

    Hello,

    Did you power cycle the device after flashing? If so, this could happen if switch S5 is on. Could you check your switch settings to see if S5 is on? 

    If it is on, can you modify the switch and try again?

    And as there no code changes, there shouldn't be any problem with your custom firmware.

    Regards,

    Sharan

  • 0 in reply to Sharan S S
    Intellectual 405 points

    I turned off the two S5 switches that were previously ON, and now the system is operating normally. The issue has been resolved. I sincerely appreciate your helpful response.