IWR6843AOP: Compilation error

Divya:

Before for we get into the debug process could you please let me know if you have made any modifications to the area scanner demo, or if you are trying to run the lab from what is provided in the industrial toolbox. This be important to know before proceeding.

Best regards,

Connor Desmond

I'm trying to run the lab from Industrial toolbox. 

Regards,

Divya 

Divya:

The first thing that I want you to do is make sure that you go through the labs user's guide very carefully. Specifically remember that for the IWR6843AOP there is a MSS and DSS both of which need to be flashed with their respective binaries. Also make sure that you have the correct SW + HW requirements which are specifed in the top of the lab's user guide. From what I can initially gather from the error that you are getting the DSS firmware is not building, so I would pay extra attention to the instructions in that part of the guide.

Also could you also confirm if you have successfully ran the Out of Box Demo on your HW. This is the best way to verify that the HW that you have is working correctly. If you haven't then please do so.

Best regards,

Connor Desmond

Hi Connor,

I have a problem in building the project. I could successfully build the project for the area scanner demo but not for the long range demo. I'm getting the error for the area scanner and not long range. If you can see the screenshot I have the .bin file for long range and not area scanner.

So what is the reason for the error in the area scanner demo to build?

Regards,

Divya 

Divya:

1. I would suggest downloading the industrial toolbox directly into your machine e.g. C:\ti and import the CCS projects instead of using the resource explorer.

2. What version of CCS are using?

3. In the project explorer notice in the DSS project notice that you have [Active - ods]. You are using IWR6843AOP, this is not correct. Please read the user guide. It specifically calls this out.

Best regards,

Connor Desmond

Hi Connor,

There is some miscommunication here. I’m trying to build the project in CCS for that a sensor is not needed to be connected to the system. I build the demo project and it should give me binary files of ODS atleast. I did the same for long range. I didn’t connect the ISK to build the project. For debugging yes I would do that but my project isn’t even building so I can’t go to the debugging.

I’m using version 10.1.1 code composer studio

I already have an industrial toolbox installed on my PC. I tried that.

Regards,

Divya Teja Settimali

Hi Connor,

Is this the reason for area scanner to give a compilation error and long range not?

Regards,

Divya Teja Settimali

Hi Connor,

Thanks for the reply. I have downloaded the exact version you mentioned and built the project and it is the same error again. Please check the screenshot below.

I need some further assistance on this.

Regards,

Divya Teja Settimali

Divya:

Are you using a TI provided EVM or are you using a custom EVM that you have designed?

Best,

Connor

Divya,

What version of the mmWave SDK are you using? I just built this project in the ODS configuration using Industrial Toolbox 4.7.0 with no issue.

Best Regards,
Alec

Hi Connor,

It is the Ti provided EVM.

Regards,

Divya Teja Settimali

Hi Alec,

I'm using mmWave SDK 03.05.00.04 version and Industrial Toolbox 4.7.0. Even I didn't have a problem earlier and also no problem with Long range. It is happening with area scanner.

Regards,

Divya Teja Settimali

Hi,

I would try it out for the area scanner and let you know but I could build the project for the long range demo as mentioned earlier and I'm having trouble with the debugging. As soon as you launch the debug mode why is it the pointer is always not starting at main(). That is definetly one question I have here. Because it is so random each time I launch the target configuration and also when the pointer starts with main() I'm having trouble with adding breakpoints for debugging. I need guidance with that as well. I would be glad to hear it from you supporting some documentation abou the debugging and breakpoints. I'm trying to view the data that is sent to Matlab from the sensor which is in turn through UART displayed on GUI. Thanks in Advance.

Regards,

Divya Teja Settimali

Divya,

Do you have the CCSDebug image flashed onto the device already via uniflash? 

Best Regards,
Alec

Yes I already did flash the CCSDebug image flashed onto the device.

Regards,

Divya Teja Settimali

Divya,

Are you doing a reset between each load in CCS? 

Best Regards,
Alec

Hi,

Yes, also tried connecting multiple times after reset. What is the difference between following this debug procedure in mentioned in this link Using CCS Debug for Development (ti.com) and then loading debug mode directly on clicking the debug option in the CCS? Because loading the debug mode directly in the CCS works or starts at main() most of the time.

Regards,

Divya Teja Settimali

Divya,

I haven't encountered issues following the steps in the guide you posted, and am not sure if there are any issues with the debug button, so if it works for you then I would say carry on. Were you able to resolve your build issue for this project?

Best Regards,
Alec

Hi Alec,

I have many doubts about the debug mode

1. What is the difference between a ccsdebug bin file and normal bin file. I could connect ISK sensor with a .bin demo file flashed on it and connect it to EVM and set the hardware breakpoints and why do I need to do the following procedure with ccsdebug bin file ?

2. Can I make changes in the libraries or the common files that are available? 

For example I want to make changes in the trackerproc_3D.c 

I wanted to remove the comments in the lines 481 and 482 and add tilt but despite of removing the comments and compiling it didn't work.

3. I wanted a break point to view the result variable and I put a hardware breakpoint.

but debug never goes into that function at all and to check the flow of the code I need multiple hardware breakpoints and multiple hardware breakpoints are not supported. I was following the below flow diagram.

I hope I'm clear with the questions and would wait to hear from you. Could you let me know if I'm missing something or didn't follow something right.

Regards,

Divya Teja Settimali

Hi Alec,

We are trying to interface 2 IWR6843 ISKs and 2 IWR6843 AOPs with a Rasberry-Pi. So there is a power consumption issue. We want to reduce the power consumption and Low power command on cfg file is not applied for the device as mentioned in the User guide. The total power supply to all the USB ports in aggregrate is 1200 mA. Could you please guide me with a solution to reduce the power consumption by each device so that we wouldn't have these issues?

Regards,

Divya Teja Settimali

Divya,

The question has derailed here quite a bit from the original question, can you make a new post and mark this one as resolved to keep things clear for other users?

Best Regards,
Alec

Hi Alec,

Thank you for the reply. So I have raised another post with the question as suggested. Here when I'm trying to rebuild the libraries locally it gives an error from the screenshot. Could you let me know how to get rid of it?

Regards,

Divya Teja Settimali

Hi Divya,

I just built this on my end with no issue, have you modified anything in your copy of the mmWave SDK or the Industrial Toolbox that could cause this to occur? Additionally, if you click on the project and go to properties->Build->ARM Linker->File Search Path, do you see "libtrackerproc_xwr68xx.aer4f" listed in the top box and "${LRPD_PARENT_DIR}/common/src/dpu/trackerproc_overhead/lib" listed in the bottom box?

Hi Alec,

I did make a change in the library and so deleted the lib that I wanted to rebuild and added the include path according to your previous post.

• Remove the libs that you want to rebuild from the project linker settings. 
  
  • project properties->ARM Linker->File Search Path and then remove whatever libraries that you want to rebuild from the top field "Include library file or command file as input"
• Add the source files that you want to rebuild to your project
  • This can make your #includes a bit challenging as the paths may change, so I recommend making the file path in your project match that of the file's normal location 
  • Example: if you see "#include common/src/dpu/trackerproc_overhead/trackerproc.h" then I would create the folder common in your top level of your CCS project, then the sub folders for src, dpu, and trackerproc_overhead, and then store the .h file in this folder so that you do not need to update all the include paths.

After this I see the error and I do not know what to do further. 

Regards,

Divya Teja Settimali