AWR2544LOPEVM: Missing Image File and Errors Building Binaries with make

Joona Kaikkonen

Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544, UNIFLASH

Tool/software:

Hi TI Community,

I'm working with the AWR2544 in the mmWave MCU+ SDK and have encountered an issue regarding missing image files and build errors. Here are the details:

1. Missing Image File: Following the SDK instructions, I'm supposed to flash the SBL QSPI and SBL Multicore App images to the device. However, the specified image file (sbl_multicore_app_system.release.appimage_qspi) referenced in the config file (line 25) under sbl_prebuilt/awr2544-evm/ does not exist in the directory.

C:\ti\mmwave_mcuplus_sdk_04_06_00_01\mcu_plus_sdk_awr2544_09_01_00_05\tools\boot> python uart_uniflash.py -p COM6 --cfg=sbl_prebuilt/awr2544-evm/default_sbl_null.cfg

Parsing config file ... Parsing config file ... ERROR. 1 error(s). [ERROR] Parsing error found on line 25 of sbl_prebuilt/awr2544-evm/default_sbl_null.cfg [ERROR] File not found !!!

2. Attempt to Build Missing Binaries: In the flash tool error messages and solutions page it advises to use command "gmake -s sbl DEVICE=am243x" if you are encountering error message "Parsing config file error" but when i run that command in the directory where the makefile and makefile.awr2544 are located i just get some errors: C:\ti\mmwave_mcuplus_sdk_04_06_01_02\mcu_plus_sdk_awr2544_09_01_00_05> make -s sbl DEVICE=am243x

make[1]: makefile.am243x: No such file or directory make[1]: *** No rule to make target 'makefile.am243x'. Stop. make: *** [makefile:95: sbl] Error 2

I have also tried to run command: "make -s sbl DEVICE=awr2544" but it also leads to some errors.

Could you help with locating the correct image file or troubleshooting the build error? Any insights into resolving these issues would be greatly appreciated.

Thank you!

13 days ago

0 Ajay Narayan 10 days ago

TI__Mastermind 20365 points

Hi Joona,

1) The image files needs to be built before they can be flashed.

2) You can go to "C:\ti\mmwave_mcuplus_sdk_04_06_01_02\mcu_plus_sdk_awr2544_09_01_00_05" path in cmd and run 'gmake help' in cmd, this will give you the list of commands that can be used to build. Find the one corresponding to the one you need.

Regards,

Ajay

0 Joona Kaikkonen 10 days ago in reply to Ajay Narayan

Prodigy 10 points

Hi, thanks for the response. How do i know what is the correct file that i need to build? If i try to run some make commands example 'make makefile.awr2544 all' it gives me some error that i think is caused by cygwin. Any idea whats that about?

0 Joona Kaikkonen 10 days ago in reply to Ajay Narayan

Prodigy 10 points

This is part what i get when i run 'make help'. Im not sure how should i read this

0 Ajay Narayan 9 days ago in reply to Joona Kaikkonen

TI__Mastermind 20365 points

Hi Joona,

Can you please use the gmake.exe provided within the CCS. Its in path "C:\ti\ccs1271\ccs\utils\bin".

Also, you can use the help by coping the command shown in help and executing the same, as follows:

gmake -s -C examples/drivers/boot/sbl_multicore_app/awr294x-evm/system_nortos all

Please go the through the reamefirst document to know the exact steps.

Regards,

Ajay

0 Joona Kaikkonen 8 days ago in reply to Ajay Narayan

Prodigy 10 points

Hi, thanks for the reply. Currently i have followed the instructions provided by the readme file in mcu_plus_sdk_awr2544_09_01_00_05 :

Step 1: Download, install SDK and related tools, see Download, Install and Setup SDK and Tools [NEEDS TO BE DONE ONCE when SDK is installed]
Step 2: Download, install and setup CCS for development, see Download, Install and Setup CCS [NEEDS TO BE DONE ONCE when SDK is installed]
Step 3: Setup EVM for program execution, see EVM Setup
Step 4: Build a "hello world" example for the EVM, see Build a Hello World example
Step 5: Load and run the "hello world" example on the EVM, see CCS Launch, Load and Run
Step 6: Flash the "hello world" example on the EVM and boot without CCS, see Flash a Hello World example [OPTIONAL and is typically needed after all development via CCS is done]

About step 2: setting up CCS

There are instructions to create a target configuration

the instructions said:

In "Board or Device" type "AWR2544" and select "evmAM273x"

but when i type "awr2544" i only get "awr2544" ??

Then i get stuck at the step 3: EVM Setup. This is what i have done:

- i set the mode to UART bootmode

- i get c printed in the terminal

- i close the terminal

Next the instruction tells me to :

Open a command prompt and run the below command to flash the SOC initialization binary to the EVM.

cd ${SDK_INSTALL_PATH}/tools/boot
python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr2544-evm/default_sbl_null.cfg

I run that command with the correct COM in dir cd ${SDK_INSTALL_PATH}/tools/boot.
But this is where i get the error from the line 25 in file default_sbl.cfg.

The line 25 from that file is: --file=../../examples/drivers/boot/sbl_multicore_app/awr2544-evm/system_nortos/sbl_multicore_app_system.release.appimage_qspi --operation=flash --flash-offset=0xA0000
That file in the line 25 doesnt exist in my directories, so i should somehow build it?

In your response you provided this: gmake -s -C examples/drivers/boot/sbl_multicore_app/awr294x-evm/system_nortos all.
When i type that in the dir: mcu_plus_sdk_awr2544_09_01_00_05, it gives error "No such file or directory"
When i run the command "gmake help" in the dir: "mcu_plus_sdk_awr294x_09_00_00_15", it doesnt even provide me anything from: "/examples/drivers/boot/sbl_multicore_app/"

Question: why in some instruction the device name is "awr294x-evm" and not "awr2544-evm". Which one should i use?
I also tried to run the command with "awr2544-evm": "gmake -s -C examples/drivers/boot/sbl_multicore_app/awr2544-evm/system_nortos all", but i get same error "No such file or directory".

In the sdk: "mcu_plus_sdk_awr294x_09_00_00_15", the files needed for the steps above exist without building anything. But they are for the different board?

PS. im using the "XDS110 debugger" usb port for these stuff, should i be using the other port "FTDI USB connector"?

Some photos of the steps and errors etc: