IWRL6432BOOST: Regarding the issue that the prebuilt binaries firmware fails to run on the IWRL6432BOOST

Tony Simple

Intellectual 390 points

Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432AOPEVM, IWRL6432

Tool/software:

Hello, expert

The model of the development board I use is IWRL6432and the Boost version is RPOC17 REV.B.

I tested the following several scenarios.

1. The development board is flashed with the firmware "radar_toolbox_3_10_00_05\source\ti\examples\Out_Of_Box_Demo\prebuilt_binaries\out_of_box_L6432.appimage".

After flashing the device, the version number of the firmware can be displayed on the serial port. Then,

I sent the following configuration information to the development board through visualizer and obtained the commands that the firmware does not support (as follows txt).

Fullscreen error2.txt Download

% ****************************************************************
% Configuration Start
% ****************************************************************

sensorStop 0

channelCfg 7 3 0

chirpComnCfg 8 0 0 256 4 28 0

chirpTimingCfg 6 63 0 75 60

frameCfg 2 0 200 64 250 0

guiMonitor 2 1 0 0 0 1 0 0 0 0 0

sigProcChainCfg 32 2 1 0 4 4 0 15 

cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1

aoaFovCfg -60 60 -40 40

rangeSelCfg 0.1 12.0

clutterRemoval 1

compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000

adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/major_motion/adc_data_0001_CtestAdc6Ant.bin

adcLogging 0

lowPowerCfg 1

factoryCalibCfg 1 0 40 0 0x1ff000

mpdBoundaryBox 1 0 1.48 0 1.95 0 3

mpdBoundaryBox 2 0 1.48 1.95 3.9 0 3

mpdBoundaryBox 3 -1.48 0 0 1.95 0 3

mpdBoundaryBox 4 -1.48 0 1.95 3.9 0 3

sensorPosition 0 0 1.44 0 0

minorStateCfg 5 4 40 8 4 30 8 8

majorStateCfg 4 2 30 10 8 80 4 4

clusterCfg 1 0.5 2

baudRate 1250000

sensorStart 0 0 0 0

% ****************************************************************
% Configuration End
% ****************************************************************

% ****************************************************************
% Response from Device
% ****************************************************************

sensorStop 0

Done

mmwDemo:/>channelCfg 7 3 0

Done

mmwDemo:/>chirpComnCfg 8 0 0 256 4 28 0

Done

mmwDemo:/>chirpTimingCfg 6 63 0 75 60

Done

mmwDemo:/>frameCfg 2 0 200 64 250 0

Done

mmwDemo:/>guiMonitor 2 1 0 0 0 1 0 0 0 0 0

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>sigProcChainCfg 32 2 1 0 4 4 0 15 

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1

Done

mmwDemo:/>aoaFovCfg -60 60 -40 40

Done

mmwDemo:/>rangeSelCfg 0.1 12.0

Done

mmwDemo:/>clutterRemoval 1

Done

mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000

Done

mmwDemo:/>adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/major_motion/adc_data_0001_CtestAdc6Ant.bin

Done

mmwDemo:/>adcLogging 0

Done

mmwDemo:/>lowPowerCfg 1

Done

mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000

Done

mmwDemo:/>mpdBoundaryBox 1 0 1.48 0 1.95 0 3

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>mpdBoundaryBox 2 0 1.48 1.95 3.9 0 3

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>mpdBoundaryBox 3 -1.48 0 0 1.95 0 3

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>mpdBoundaryBox 4 -1.48 0 1.95 3.9 0 3

Error: Invalid usage of the CLI command
Error -1
mmwDemo:/>sensorPosition 0 0 1.44 0 0

'sensorPosition' is not recognized as a CLI command
mmwDemo:/>minorStateCfg 5 4 40 8 4 30 8 8

'minorStateCfg' is not recognized as a CLI command
mmwDemo:/>majorStateCfg 4 2 30 10 8 80 4 4

'majorStateCfg' is not recognized as a CLI command
mmwDemo:/>clusterCfg 1 0.5 2

'clusterCfg' is not recognized as a CLI command
mmwDemo:/>

2. I brushed "radar_toolbox_3_10_00_05\source\ti\examples\Industrial_and_Personal_Electronics\mmWave_Demo\prebuilt_binaries\mmw" on the development

board After the firmware "ave_demo_xwrl6432.appimage", when the development version is switched back to "application mode", the DC input power supply is 5V3A,

but no information is obtained from the serial port (similar to the version information in 1).

Based on scenario 1, I analyzed that my development board should not be damaged, but I can't run the program on this fast development board now. Please help me.

Thanks.

3 months ago

0 Nathan Block 3 months ago

TI__Mastermind 37805 points

Hi,

Try this one?

C:\ti\MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx-aop\motion_and_presence_detection_demo_aop.release.appimage

Let me know if it works? If not, please send pictures and screenshots confirming the steps you're taking.

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I tried the firmware you mentioned, but this one also has no log output.

The following are the operation steps

step1 Adjust the board to the flash mode, And select the board type

step2 Select the serial port and firmware and the flashing is successful

step3 Select the board to the application mode, restart and observe the log

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Please send a photo of your switch settings and a screenshot of your serial monitor settings. Be sure the switch settings are set to functional mode.

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate ,

I have set the flashing mode to off.

I have set the functional mode to on.

Thanks.

0 jack cao 3 months ago

Prodigy 10 points

Thanks, I am looking into it.

0 Nathan Block 3 months ago in reply to jack cao

TI__Mastermind 37805 points

In functional mode, please set 1.6 OFF to enable I2C.

Best

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

Thank you for your reply. I will return to the company next week and test this item.

Thanks.

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I tried to turn off s1.6, but still couldn't see the version log output.

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Hi Tony,

See this video

https://www.ti.com/video/6349200931112

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I followed the instructions in the video to open the visualizer. When I clicked "send configuration to device", the following error appeared.

I still think there might be an issue with the part where the device fails to send the version log upon startup.

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

When you open a serial terminal for the device at 115200 baud do you see any output? If not it sounds like your EVM may not be working properly. Do you have another one you can test with? Or a different computer to test on?

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

Since I don't have the second IWRL6432BOOST, I used IWRL6432AOPEVM for the test.

When I plugged in the IWRL6432AOPEVM development board, the flashing process(C:\ti\MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx-aop\motion_and_presence_detection_demo_aop.release.appimage), the use of the serial port assistant to view the version log, and the debugging through visualizer all went smoothly.

I replaced another computer and used a baud rate of 115200 to check if IWRL6432BOOST had any version log output. The result was negative.

Here I have another question. The firmware "motion_and_presence_detection_demo_aop.release.appimage" is located in the AOP directory. Its name also contains the word "aop". Can this firmware be run on boards like IWRL6432BOOST which are not of the AOP type? If this answer is definite, then it seems that there is something wrong with my development board.

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Tony Simple said:
Here I have another question. The firmware "motion_and_presence_detection_demo_aop.release.appimage" is located in the AOP directory. Its name also contains the word "aop". Can this firmware be run on boards like IWRL6432BOOST which are not of the AOP type?

The AOP appimage CANNOT be run on the BOOST board. Use the BOOST appimage on the BOOST board. Does that work?

Best,
Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

Nathan Block said:
Try this one?

C:\ti\MMWAVE_L_SDK_05_05_03_00\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx-aop\motion_and_presence_detection_demo_aop.release.appimage

I don't have a firmware that can run on the IWRL6432BOOST. I tried following this instruction.

Could you recommend a firmware path that can run on the IWRL6432BOOST?

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Hi Tony,

For the IWRL6432BOOST, use the following :

C:\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

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I tried what you said about this file. After the functional mode was activated, the serial port still did not output anything (just like in the other tests we conducted above).

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Hi Tony,

Is it possible there is something wrong with your computer? Can you test on a different computer? Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I repeated the above steps using another computer, but still couldn't see the log output.

1. Set to flashing mode

2 flash operation successful

3 Set to functional mode

4 No log output was seen.

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Can you try using tera term? This is the CLI tool I use.

Please also try switching S5 to the OFF position for both switches.

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

This is what Tera Term saw.(switching S5 to the OFF)

Thanks.

0 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

Hi Tony,

S5 is here, please switch it OFF.

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

Sorry, I mistook it for S1.5. Even after turning off S5, there was still no log output.

Thanks

+1 Nathan Block 3 months ago in reply to Tony Simple

TI__Mastermind 37805 points

HI Tony,

When did you order this board? Is it possible it's ES1 silicon? Does the first line on the IC read XL6432, or IWRL6432? If it's ES1 silicon, you need to run an older SDK. Try https://www.ti.com/tool/download/MMWAVE-L-SDK/05.01.00.03

Best,

Nate

0 Tony Simple 3 months ago in reply to Nathan Block

Intellectual 390 points

Hi Nate,

I have been purchasing it for over a year now.,On the chip is "XL6432", and I guess it is for the ES1 silicon. This old version can be run.

Thanks

Sensors

Sensors forum

IWRL6432BOOST: Regarding the issue that the prebuilt binaries firmware fails to run on the IWRL6432BOOST