• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 124 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.

IWRL6432FSPEVM: IWRL6432FSPEVM User's Guide Programming Problem

leo lau
Prodigy 115 points
Part Number: IWRL6432FSPEVM
Other Parts Discussed in Thread: IWRL6432BOOST, IWRL6432AOPEVM, UNIFLASH, IWRL6432

Tool/software:

Hi everyone,

I’m following the user guide for flashing the IWRL6432FSPEVM, but I’ve hit a roadblock at step 3 about programming the firmware. I have tried different method to program a prebuilt firmware to the board but without success.

I have a few observations and questions that might help identify the issue:

  1. The COM port input box doesn’t list the port that appears in Ports(COM) on my system, so I manually entered COM6(I've double checked from device manager). Could this manual input be causing problems, or is this an acceptable workaround?
  2. The user guide references prebuilt_binaries\xwrL64xx, but this path doesn’t exist in my setup. Instead, I selected D:\ti\MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx-evm\motion_and_presence_detection_demo.release.appimage. Is this the correct binary for the IWRL6432FSPEVM?
  3. When I send version\r\n to COM6 via terminal, I get version-related information back. Does this indicate the port is correctly connected, even if flashing isn’t working?

To troubleshoot, I’ve already tried:
  • Powering the development board directly with a 3.3V/1A power supply
  • Running the visualizer as administrator
  • Installing radar_toolbox_3_20_00_04 and MMWAVE_L_SDK_05_05_03_00 in a virtual machine with antivirus disabled

For reference, my system/SDK details are:
  • MMWAVE_L_SDK_05_05_03_00
  • radar_toolbox_3_20_00_04
  • Windows 10 64-bit
  • USB-to-serial device: CP2102N

Any guidance on what might be going wrong with the flashing process would be greatly appreciated! Thank you.
  • 0
    TI__Mastermind 21621 points

    Hello, 

    leo lau said:
    The COM port input box doesn’t list the port that appears in Ports(COM) on my system, so I manually entered COM6(I've double checked from device manager). Could this manual input be causing problems, or is this an acceptable workaround?

    This is expected when using the FSP board with the visualizer (or any device via a 3rd-party USB connector board). The visualizer will only automatically fill the com ports for our EVM boards (e.g. IWRL6432BOOST, IWRL6432AOPEVM). Please continue to enter the com port manually.

    leo lau said:
    The user guide references prebuilt_binaries\xwrL64xx, but this path doesn’t exist in my setup. Instead, I selected D:\ti\MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx-evm\motion_and_presence_detection_demo.release.appimage. Is this the correct binary for the IWRL6432FSPEVM?

    Yes, this is the correct path/binary. 

    leo lau said:
    When I send version\r\n to COM6 via terminal, I get version-related information back. Does this indicate the port is correctly connected, even if flashing isn’t working?

    This indicates your UART connection is correct and also gives us a hint as to why you are unable to flash. The board appears to be in functional mode. You need to connect SOP0 pin to GND and then power-cycle the board to set it into flashing mode.

    Best regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 115 points

    Thank you for your continued support. I have followed the recommended troubleshooting steps, but the issue persists. Here is a summary of what I have tried:

    • Connected the SOP0 pin to GND and power-cycled the board as instructed.
    • Verified with a multimeter that both the SOP0 and SOP1 pins are at 0V.
    • Attempted the entire process on a second computer, which yielded the same result.

    I have been working on this for several days without success. Could you please advise on any further steps I can take? I would appreciate any additional guidance you can provide.

  • 0 in reply to leo lau
    TI__Mastermind 21621 points

    Hello, 

    Thanks for the information. Here are some additional debug steps to try:

    • Double check all connections with the IWRL6432FSPEVM user guide. A common mistake is that uart rx and tx are incorrect, you may want to try swapping those connections incase they are incorrectly made.
    • Attempt to flash using Uniflash instead of the SDK visualizer. It may be possible that there is some bug related to flashing the FSP board with the latest version of the SDK visualizer. Assuming the hardware connections are correct, you should be able to use Uniflash to write the appimage to flash. You can follow the steps outlined in this guide. http://dev.ti.com/tirex/local?id=using_uniflash_with_mmwave&packageId=radar_toolbox For the device selection, choose IWRL6432.

    regards,

    Josh