AWR6843AOP: Software getting stuck after mmwave_execute, unable to send anymore commands.

Jahiz Ahmed

Part Number: AWR6843AOP
Other Parts Discussed in Thread: AWR1843

Tool/software:

Hi im running into a problem where my device stops responding to CLI commands,

we have a system with both MSS (DPM) and DSS (DPC), however currently after the sensorStart command the software seems to get stuck.

i have not been able to find out where the software seems to get stuck. however i have been able to confirm the following things:

processors are able to synchronize.

CLI is started

MMWave_start is called successfully

and mmw_sensor execute are called .

The last function that seems to be called is mmw_execute.

The DPM on the MSS is started, however
The DPC on the DSS is never started,

Is there anything i can look at between DPM start and DPC start as believe the problem should be there?

Unfortunately i cannot share my radar configuration as it is under development however we do have an NDA with TI if we can share over email.

Thanks,

Jahiz

7 months ago

0 zigang Yang 7 months ago

TI__Mastermind 40495 points

Hi, Jahiz:

I assume that you are developed your own demo, not a TI demo, is that correct? Is your demo working in any chirp configuration? Let us say you increase the frame duration to 500ms. What is your radar Cube size? Is it possible that the memory is overflow?

Best,

Zigang

0 Jahiz Ahmed 7 months ago in reply to zigang Yang

Prodigy 10 points

Hi Zigang,

We did start with a TI demo, specifically this one:

However we then modified it and now we're porting it back to the 6843.

The modification was adding CLI functions and a new DPU.

I have not tried changing the frame duration, however I believe that is not the issue as we are not seeing any output from the radar on a spectrum analyzer.

I was able to get this memory output from my debug messages which leads me to believe its not a memory allocation problem:

The radar cube size is 393,216 bytes.

0 zigang Yang 7 months ago in reply to Jahiz Ahmed

TI__Mastermind 40495 points

I am re-assigning your ticket to a ADAS expert.

Best,

Zigang

0 Jahiz Ahmed 7 months ago in reply to zigang Yang

Prodigy 10 points

As an update: I was able to get the DPC started however i am not getting this frame start event.

0 Jahiz Ahmed 7 months ago

Prodigy 10 points

Has this been re-assigned?

0 Cesar 7 months ago in reply to Jahiz Ahmed

TI__Guru*** 149044 points

Hi,

Usually we recommend using the mmwave SDK demo and not the Parking demo. The performance is similar.

If you would like to debug this issue further you would need to coonect CCS and step through the code. I think that the changes made to the code have produced this behavior.

Thank you

Cesar

0 Jahiz Ahmed 7 months ago in reply to Cesar

Prodigy 10 points

Hi Cesar,

The software in question is working on an AWR1843, the only things i've done for the port so far are changing the libraries, SOC macros and stuff.

could you tell me what the differences would need to be to run on an 6843?

I have been connecting CCS and stepping through the code however its a little harder since its running on dual core.

Is there something specific i should look for?

The software seems to be stuck in the mmwave_execute function, which seems to have many blocking calls.

It would be alot of work to switch to another example so I would like to avoid that if possible as implementing the software again.

0 Jahiz Ahmed 7 months ago in reply to Jahiz Ahmed

Prodigy 10 points

Any updates on this?

0 Cesar 7 months ago in reply to Jahiz Ahmed

TI__Guru*** 149044 points

Hi,

The automated parking demo for 1843 is based on the src code from the mmwave sdk 3.6 oob demo. ( you have noticed there is no source code in radar toolbox folder)

And the 6843 and 1843 oob demos are identical.

So you should definitely switch to the 6843 oob demo and further debug

Thank you

Cesar

0 Jahiz Ahmed 7 months ago in reply to Cesar

Prodigy 10 points

Hey Cesar,

sorry I dont really understand what you mean,

we started with the demo however we have added a lot of software ontop of it.

The software is currently working on the 1843 and our task is to port this to the 6843.

We are no longer running just demo firmware.

I need to understand why this software is not working after changing the target hardware.

Can you tell me what would cause the radar to not transmit??

0 Cesar 7 months ago in reply to Jahiz Ahmed

TI__Guru*** 149044 points

Please see this thread.

It gives an example of a demo that was running on both 18xx and 68xx

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/914788/iwr6843-how-could-i-migrate-the-3d_people_counting-example-code-from-iwr6843-to-iwr1843

Of course first you need to make sure that you create specific profile.cfg for 68xx

Thank you

Cesar

+1 Jahiz Ahmed 6 months ago in reply to Cesar

Prodigy 10 points

This didnt solve the issue, but somewhere along the way something did. Unfortunately because i was trying so many things i dont know what did it. Maybe your advice will help someone with an example that is not already in code composer. However i did manage to resolve my issue.

Sensors

Sensors forum

AWR6843AOP: Software getting stuck after mmwave_execute, unable to send anymore commands.