AWR2944EVM: Failing to set environment (setenv.bat) before building project in CCS.

Mark Passia

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

Tool/software:

Recently I have begun setting up the development environment for the SDK and CCS (12.8.1) working in conjunction with the AWR2944EVM. Importantly the following did work:

Building of the binaries via the cmd line with setenv.bat and gmake clean/all, next flashing via the uniflash python script
Flashing of the binaries onto the AWR2944EVM over JTAG via the CCS's debug mode

My goal is to be able to modify the source code file .c/.h within the CCS, build the modified project and flash it to the EVM directly. However I have encountered here some issues, from what I have diagnosed the problem is that within CCS the environment paths created by the setenv.bat file within the cmd are not accessible and I am unable to make them visible for CCS.

Here is my CCS setup:

Created a C/C++ project in CCS 12.8.1
Imported the demo files from C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\demo\awr294x\mmw
Created a target configuration file for the AWR2944EVM

I tried to resolve the before mentioned issue with the following:

Running the setenv.bat from the terminal within CCS, the idea being that the variables will be in the correct scope then
Moving the setenv.bat, cheenv.bat and setenv.mak to the projects directory
Modifying project properties under C/C++ Build in the Behaviour tab using custom build arguments:
- cmd /C "call C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\scripts\windows\setenv.bat && call C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\scripts\windows\checkenv.bat && gmake all"
Manually adding environment variables under C/C++ Build Environment
- MMWAVE_SDK_INSTALL_PATH=C:/ti/mmwave_mcuplus_sdk_04_07_00_01
- and sever other paths from the setenv.bat file

All of these methods didn't fully resolve the issues. I got the furthest with manually adding the paths but I wasn't able to find all of the necessary paths. After reverting to the default path setting I get this error:

13:04:35 **** Incremental Build of configuration Default for project AWR2944_embeded ****
make all
makefile:13: /ti/common/mmwave_sdk.mak: No such file or directory
make: *** No rule to make target '/ti/common/mmwave_sdk.mak'. Stop.
"make all" terminated with exit code 2. Build might be incomplete.

All help is appreciated

Best regards

Mark

3 months ago

0 Shailesh Joshi 3 months ago

TI__Expert 4090 points

Hi Mark,

Can you add C:\ti\ccs1281\ccs\utils\bin to your windows environment variables and try again?

Regards,
Shailesh

0 Mark Passia 3 months ago in reply to Shailesh Joshi

Intellectual 270 points

Hello,

unfortunately this did not resolve my issue. Please find the screenshot attached showing the added path variable and the error upon a build attempt.

Btw. I don't think that this path is what is/was missing, as CCS does see gmake, the lack of environment variables created by setenv.bat seem to me to be the issue.

Regards,

Mark

0 Shailesh Joshi 3 months ago in reply to Mark Passia

TI__Expert 4090 points

Mark, can you try removing the gmake at C:\ti\xdctools_3_50_08_24_core\ from the path? It is supposed to only use the ccs gmake.

Regards,
Shailesh

0 Mark Passia 3 months ago in reply to Shailesh Joshi

Intellectual 270 points

Hi, I did remove the duplicate gmake path, this did not help.

However when I manually add a path as seen in the screenshot I get a different error, pointing to the fact that the variables initialized by setenv aren't present. Ofc I can add this one path which later on leads to further errors of a similar nature.

0 Shailesh Joshi 3 months ago in reply to Mark Passia

TI__Expert 4090 points

Hi,

Can you try to echo the variable? i.e. echo %MMWAVE_SDK_DEVICE%

Regards,
Shailesh

0 Mark Passia 3 months ago in reply to Shailesh Joshi

Intellectual 270 points

Hi, it yields the following:

C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\demo\awr294x\mmw>echo %MMWAVE_SDK_DEVICE%
%MMWAVE_SDK_DEVICE%

Best regards

Mark

0 Mark Passia 3 months ago in reply to Mark Passia

Intellectual 270 points

I managed to solve this issue, just in case that someone might need this in the future. What you should do in the case described in the first question is the following:

Run the setenv.bat file from the cmd
From the same cmd session launch CCS.exe
Build the project

This solution might not be perfect but it works!

0 Shailesh Joshi 3 months ago in reply to Mark Passia

TI__Expert 4090 points

Thanks a lot Mark for sharing. We had been able to call setenv and gmake from ccs directly and make it work in our setup, so we know it is doable. But glad that you are not blocked by it for now.

Regards,
Shailesh

0 Mark Passia 3 months ago in reply to Shailesh Joshi

Intellectual 270 points

Shailesh Joshi said:
We had been able to call setenv and gmake from ccs directly and make it work in our setup, so we know it is doable.

Well I will be more than happy if you guide me through this!

Sensors

Sensors forum

AWR2944EVM: Failing to set environment (setenv.bat) before building project in CCS.