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.

AWR2E44PEVM: Difficulty Running HECR Demo on Radar Toolbox 3.10

Part Number: AWR2E44PEVM
Other Parts Discussed in Thread: AWR2944EVM, UNIFLASH, SYSCONFIG, AWR2944

Tool/software:

Hello,

We are working on a project with the AWR2E44PEVM and are interested in running the HECR demo on it.We have the AWR2944EVM and were able to successfully flash the prebuilt HECR demo binaries. I am following the High End Corner Radar User Guide from the Radar Toolbox 3.10.00.05.
C:/ti/radar_toolbox_3_10_00_05/source/ti/examples/Automotive_ADAS_and_Parking/high_end_corner_radar/docs/High_End_Corner_Radar_users_guide.html

I am confused on how to interpret the instructions to flashing the image to the AWR2E44PEVM. It says that a prebuilt image is provided under <LAB_LOC>/prebuilt_binaries/awr2x44p. This is true. There is a sbl_qspi.release.tiimage file located in this directory.

I flashed the .tiimage file to the board using the uart_uniflash.py but the device does not seem to be outputting data. This was confirmed by using a serial monitor on the data lines.

The user guide say that the mmwavelink does not work in this build and some changes need to be made in the driver code for it to communicate properly. Just so I am understanding correctly, the prebuilt binary provided does not work with the HECR demo?

I have made the specified changes in the soc_rcm.c file. I am unsure how to rebuild the example project.

Further down the guide. It provides instructions for rebuilding the application.
First it says to set the appropriate environment variables in setenv.bat. In the .bat file I made the following changes:
set MMWAVE_SDK_DEVICE=awr2x44P
SET SYSCONFIG_INSTALL_PATH=C:/ti/sysconfig_1.23.1

I then run the setenv.bat command, then using the same command prompt, I navigated to the HECR demo folder for the AWR2E44P located:
C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p

Running "gmake help" only shows the following make targets:

C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p>gmake help
****************************************************************************************
* Makefile Targets for the DEMO 
all             -> Builds the mmw Demo (both MSS, M4 and DSS binaries) and appimage
clean           -> Cleans the mmw Demo (both MSS, M4 and DSS binaries) and appimage
mssDemo         -> Builds the MSS binary for the mmw Demo
mssDemoClean    -> Cleans the MSS binary for mmw Demo 
dssLinkDemo         -> Builds the DSS binary for the mmw Demo
dssLinkDemoClean    -> Cleans the DSS binary for mmw Demo 
bin             -> Builds the appimage for the demo
binClean        -> Cleans the appimage for the demo
mmwLinkDemo         -> Builds the mmw Demo (both MSS and DSS binaries) but not the appimage
mmwDemoClean    -> Builds the mmw Demo (both MSS and DSS binaries)
****************************************************************************************

I do not see an option for an HECR demo.

Running "gmake all" leads to an error where a library is not linked properly. Below is the log.
C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p>gmake all
Generating SysConfig files ...
C:/ti/sysconfig_1.23.1/nodejs/node C:/ti/sysconfig_1.23.1/dist/cli.js --product C:/ti/mmwave_mcuplus_sdk_04_07_00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/.metadata/product.json --
script ./dss/dss.syscfg --context c66ss0 --output ./dss/dssgenerated/ --script ./dss_cm4/dss_cm4.syscfg --context m4ss0-1 --output ./dss_cm4/m4generated/ --script ./mss/mss.sys
cfg --context r5fss0-0 --output ./mss/mssgenerated/
Running script...
Validating...
Generating Code (mss.syscfg)...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_dpl_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_dpl_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_drivers_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_drivers_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_drivers_open_close.c...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_drivers_open_close.h...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_pinmux_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_power_clock_config.c...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_board_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_board_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_board_open_close.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_board_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_open_close.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_soc.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_lwipif.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\mss\mssgenerated\ti_enet_lwipif.h...
Generating Code (dss.syscfg)...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_dpl_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_dpl_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_drivers_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_drivers_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_drivers_open_close.c...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_drivers_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_pinmux_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_power_clock_config.c...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_board_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_board_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_board_open_close.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_board_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_open_close.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_soc.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_lwipif.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss\dssgenerated\ti_enet_lwipif.h...
Generating Code (dss_cm4.syscfg)...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_dpl_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_dpl_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_drivers_config.c...        
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_drivers_config.h...        
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_drivers_open_close.c...    
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_drivers_open_close.h...    
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_pinmux_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_power_clock_config.c...    
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_board_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_board_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_board_open_close.c...      
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_board_open_close.h...      
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_config.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_config.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_open_close.c...       
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_open_close.h...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_soc.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_lwipif.c...
Writing C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2x44p\dss_cm4\m4generated\ti_enet_lwipif.h...
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mss_main.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/gtrackAlloc.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ../utils/mmwdemo_flash.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mss_tracker.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/gtrackLog.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./common/mmw_common.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./common/mmw_load_params.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_board_config.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_board_open_close.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_dpl_config.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_drivers_config.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_pinmux_config.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_power_clock_config.c
[R5 Device/Type: awr2x44P/awr2x44P] Building file: ./mss/mssgenerated/ti_drivers_open_close.c
C:/ti/ccs1281/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang -Os -O3 -flto -Wl,--diag_suppress=10063 -Wl,--ram_model -Wl,--reread_libs -Wl,--zero_init=on -Wl,--use_
memset=fast -Wl,--use_memcpy=fast  -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/source/kernel/freertos/lib -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_
00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/source/drivers/lib -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/source/board/lib -Wl,-iC:/ti/ccs1281/ccs
/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/lib  -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_00_01/mmwave_dfp_02_04_17_00/ti/control/mmwavelink/lib -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_0
0_01/mmwave_mcuplus_sdk_04_07_00_01/ti/utils/mathutils/lib -Wl,-iC:/ti/mmwave_mcuplus_sdk_04_07_00_01/mmwave_mcuplus_sdk_04_07_00_01/ti/utils/testlogger/lib -Wl,-iC:/ti/mmwave_
mcuplus_sdk_04_07_00_01/mmwave_mcuplus_sdk_04_07_00_01/ti/utils/hsiheader/lib -Wl,-i../../alg/gtrack/lib/ -Wl,-m=awr2e44p_corner_radar_mss.map \
-o awr2e44p_corner_radar_mss.xer5f obj_awr2x44P/mss_main.oer5f obj_awr2x44P/gtrackAlloc.oer5f obj_awr2x44P/mmwdemo_flash.oer5f obj_awr2x44P/mss_tracker.oer5f obj_awr2x44P/gtrac
kLog.oer5f obj_awr2x44P/gtrackAlloc.oer5f obj_awr2x44P/mmw_common.oer5f obj_awr2x44P/mmw_load_params.oer5f obj_awr2x44P/mssgenerated/ti_board_config.oer5f obj_awr2x44P/mssgener
ated/ti_board_open_close.oer5f obj_awr2x44P/mssgenerated/ti_dpl_config.oer5f obj_awr2x44P/mssgenerated/ti_drivers_config.oer5f obj_awr2x44P/mssgenerated/ti_pinmux_config.oer5f 
obj_awr2x44P/mssgenerated/ti_power_clock_config.oer5f obj_awr2x44P/mssgenerated/ti_drivers_open_close.oer5f -lboard.awr2x44p.r5f.ti-arm-clang.release.lib -lfreertos.awr2x44p.r5
f.ti-arm-clang.release.lib -ldrivers.awr2x44p.r5f.ti-arm-clang.release.lib -llibc.a -llibtestlogger_awr2x44P.aer5f -llibmathutils.aer5f -llibhsiheader_awr2x44P.aer5f -llibgtrac
k3D_awr2x44P.aer5f -lmmwavelink_r5f.lib -llibmathutils.aer5f  \
C:/ti/mmwave_mcuplus_sdk_04_07_00_01/mmwave_mcuplus_sdk_04_07_00_01/ti/platform/awr2x44P/r5f_linker.cmd mss/mmw_mss_linker.cmd
error: cannot find file "libgtrack3D_awr2x44P.aer5f"

 undefined     first referenced
  symbol           in file
 ---------     ----------------
 gtrack_create C:\Users\kyeh\AppData\Local\Temp\lto6
 gtrack_delete C:\Users\kyeh\AppData\Local\Temp\lto6
 gtrack_step   C:\Users\kyeh\AppData\Local\Temp\lto6

error: unresolved symbols remain
error: errors encountered during linking; "awr2e44p_corner_radar_mss.xer5f" not
   built
tiarmclang: error: tiarmlnk command failed with exit code 1 (use -v to see invocation)
gmake: *** [mss/mmw_mss.mak:88: mssDemo] Error 1

In summary,
1) Are the prebuilt binaries for AWR2E44P supposed to work for the HECR demo?
2) What are the steps/documentation to build the binaries for the demo? Where am I going wrong with my procedure to rebuilding the binaries?

Appreciate the help.

  • Hello Kevin,

    The soc_rcm.c file needs to be rebuilt in the SDK sbl_qspi application. Do you have the SDK?
    Also I am confused, you have mentioned you want to run the AWR2E44P EVM, but you only have AWR2944EVM? Could you clarify?
    Also how are you exactly flashing the AWR2E44P application? Which tool you are using for flashing and which files exactly?

    Regards,
    Saswat Kumar

  • To clarify, in addition to the AWR2E44PEVM we also have a AWR2944EVM. So we have both devices. Using Radar Toolbox version 3.0, we had managed to get the HECR demo for the AWR2944EVM flashed and working. I wish to get the updated version of the HECR demo on Radar Toolbox 3.1 working on both boards. I wish to start by getting the HECR demo working on the AWR2E44PEVM. However, I am running into a few stumbling blocks.

    The AWR2E44PEVM does not appear to be supported with the UniFlash tool. It recognizes the device but does not continue to the next page when pressing "Start".

    When manually trying to search for the device, it does not appear in the device list.


    Following the documentation from the AWR2x44P MCU+ SDK 10.00.00, it seems like flashing binaries is done with the uart_uniflash.py tool. I make a custom cfg file based on the "default_sbl_qspi.cfg" file located at:
    C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mcu_plus_sdk_awr2x44p_10_00_00_07\tools\boot\sbl_prebuilt\awr2x44p-evm

    However, I noticed that an appimage of the HECR for the AWR2X44P does not exist in Radar_Toolbox 3.1. The modified cfg file is listed below:

    #-----------------------------------------------------------------------------#
    #                                                                             #
    #      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
    #                                                                             #
    #-----------------------------------------------------------------------------#
    #
    # By default this config file,
    # - points to pre-built flash writer, bootloader for this EVM
    # - The application image points to relative path of the sbl_multicore_app_system application image for this EVM
    #   - Make sure this application is built before running this script
    # - You can customized this config file to point to your own bootloader and/or application images
    # - You can use --operation=flashverify if you just want to verify the flash contents and not flash the file.
    #
    
    # First point to sbl_uart_uniflash binary, which functions as a server to flash one or more files
    --flash-writer=sbl_prebuilt/awr2x44p-evm/sbl_uart_uniflash.release.tiimage
    
    # Now send one or more files to flash or flashverify as needed. The order of sending files does not matter
    
    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    #--file=sbl_prebuilt/awr2x44p-evm/sbl_qspi.release.tiimage --operation=flash --flash-offset=0x0
    --file="C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\prebuilt_binaries\awr2x44p\SBL_BSS_DSS_MAILBOX\sbl_qspi.release.tiimage" --operation=flash --flash-offset=0x0
    
    # send the application image to flash. Flash it at 0xA0000 as the SBL expects it at this location
    # To connect to C66x core and load the program using CCS we should provide a valid appimage with while loop.
    #--file=../../examples/drivers/boot/sbl_multicore_app/awr2x44p-evm/system_nortos/sbl_multicore_app_system.release.appimage_qspi --operation=flash --flash-offset=0xA0000
    
    # UNSURE WHAT APPIMAGE TO POINT TO HERE

    The High End Corner Radar user guide says that there should be an prebuilt appimage file to load. But I do not see the appimage file in the prebuilt_binaries directories.


    I hope this clarifies things. There was some confusion on my part documenting this.

    In summary:
    - HECR demo from Radar Toolbox 3.0 flashed and tested successfully with AWR2944EVM
    - Can not successfully flash HECR demo with Radar Toolbox 3.1 on to AWR2E44PEVM. There appears to be missing appimage files in the prebuilt_binaries directory?
    - This led me to try to rebuild the binaries for the project which led to my initial post above.

  • Hello Kevin,

    Can you reinstall the Radar toolbox and show me what are the contents you are seeing for the prebuilt binaries for the AWr2x44P? 
    If it is not present then I have to report it as a bug as well, so can you please let me know.

    Regards,
    Saswat Kumar

  • Hello Saswat,

    I did a fresh install of Radar Toolbox 3.1. The tree for the prebuilt directory is shown below. This is a fresh install of Radar Toolbox 3.1. An appimage file exists for the AWR2944 but not for the AWR2E44P.

    PS C:\Users\kyeh\Downloads\radar_toolbox_3_10_00_05\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\prebuilt_binaries> tree /f /a
    Folder PATH listing
    Volume serial number is 2003-ABD7
    C:.
    +---awr2944
    |       awr2944_corner_radar.appimage
    |
    \---awr2x44p
        \---SBL_BSS_DSS_MAILBOX
                sbl_qspi.release.tiimage

  • As a sanity check I attempted to flash the AWR2E44PEVM appimage with the following modified .cfg file.

    #-----------------------------------------------------------------------------#
    #                                                                             #
    #      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
    #                                                                             #
    #-----------------------------------------------------------------------------#
    #
    # By default this config file,
    # - points to pre-built flash writer, bootloader for this EVM
    # - The application image points to relative path of the sbl_multicore_app_system application image for this EVM
    #   - Make sure this application is built before running this script
    # - You can customized this config file to point to your own bootloader and/or application images
    # - You can use --operation=flashverify if you just want to verify the flash contents and not flash the file.
    #
    
    # First point to sbl_uart_uniflash binary, which functions as a server to flash one or more files
    --flash-writer=sbl_prebuilt/awr2x44p-evm/sbl_uart_uniflash.release.tiimage
    
    # Now send one or more files to flash or flashverify as needed. The order of sending files does not matter
    
    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    #--file=sbl_prebuilt/awr2x44p-evm/sbl_qspi.release.tiimage --operation=flash --flash-offset=0x0
    --file="C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\prebuilt_binaries\awr2x44p\SBL_BSS_DSS_MAILBOX\sbl_qspi.release.tiimage" --operation=flash --flash-offset=0x0
    
    # send the application image to flash. Flash it at 0xA0000 as the SBL expects it at this location
    # To connect to C66x core and load the program using CCS we should provide a valid appimage with while loop.
    #--file=../../examples/drivers/boot/sbl_multicore_app/awr2x44p-evm/system_nortos/sbl_multicore_app_system.release.appimage_qspi --operation=flash --flash-offset=0xA0000
    --file="C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\prebuilt_binaries\awr2944\awr2944_corner_radar.appimage" --operation=flash --flash-offset=0xA0000

    When connected to the serial User Port. The following would display:

    Starting QSPI Bootloader ... 
    INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 400000000 Hz !!!
    [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
    [BOOTLOADER_PROFILE] Boot Media Clock : 80.000 MHz 
    [BOOTLOADER_PROFILE] Boot Image Size  : 188 KB 
    [BOOTLOADER_PROFILE] Cores present    : 
    unknown
    m4ss0-1
    r5f0-0
    [BOOTLOADER PROFILE] System_init                      :        346us 
    [BOOTLOADER PROFILE] Drivers_open                     :         23us 
    [BOOTLOADER PROFILE] LoadHsmRtFw                      :          3us 
    [BOOTLOADER PROFILE] Board_driversOpen                :       2726us 
    [BOOTLOADER PROFILE] CPU load                         :      22104us 
    [BOOTLOADER_PROFILE] SBL Total Time Taken             :      25204us 
    
    Image loading done, switching to application ...
    INFO: Bootloader_socCpuResetRelease:264: PBIST memory tests exeucted by RBL, RINFOL : 0x20 and RINFOU : 0x0
    INFO: Bootloader_runCpu:155: CPU r4 is initialized to 200000000 Hz !!!
    INFO: Bootloader_runCpu:155: CPU m40-1 is initialized to 200000000 Hz !!!
    
    

    The COM ports appear to be frozen. When running the Automotive Visualizer gui_main.py. The following is printed out:

    Python is  64  bit
    Python version:  sys.version_info(major=3, minor=13, micro=3, releaselevel='final', serial=0)
            Data COM Port found: COM27
            CLI COM Port found: COM28
    Sensor position changed to
    Height:  3.0
    Azimutal tilt:  0.0
    Elevation tilt: 0.0
    Demo Changed to: High end Corner Radar
    HECR Demo loaded
    Parser type:  High end Corner Radar
    Connected
    Connected to AWR2944 with UART Port at COM28 and Data Port at COM27
    ERROR: No data detected on COM Port, read timed out
            Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out
            Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    b''
    sensorStart
     issued
    
    ERROR: No data detected on COM Port, read timed out
            Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out
            Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out
            Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out

  • Hello Kevin,

    That is happening because you are using the SBL of AWR2x44P with the AWR2944 device which will not function.
    Please use the files intended for each device.

    Regards,
    Saswat Kumar

  • Apologies that was a typo on my end. In the previous post I was flashing that configuration to the AWR2E44PEVM.

    The problem is that the prebuilt appimage for the AWR2E44PEVM is still not in the Radar Toolbox files. Thus, I cannot use the intended file for the AWR2E44PEVM.

  • Hello Kevin,

    Can you send me a screenshot of the directory contents, like I mentioned if it is missing then it needs to be provided for next update.

    Regards,
    Saswat Kumar

  • Below is the file tree for the prebuilt_binaries directory.

    PS C:\Users\kyeh\Downloads\radar_toolbox_3_10_00_05\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\prebuilt_binaries> tree /f /a
    Folder PATH listing
    Volume serial number is 2003-ABD7
    C:.
    +---awr2944
    |       awr2944_corner_radar.appimage
    |
    \---awr2x44p
        \---SBL_BSS_DSS_MAILBOX
                sbl_qspi.release.tiimage




  • Hi Kevin,

    Thank you for bringing this topic on the E2E forums. Few of the new files and changes of HECR demo were missed in this Radar Toolbox release. Please use the attached folder for latest AWR2x44P HECR demo.

    high_end_corner_radar.zip

    Regards,

    Samhitha