AWR1843AOP: Code stops running after sending sensor start

Faruk Yurtseven

Part Number: AWR1843AOP

I have a custom board for awr1843aop and lab0014_obstacle_detection_aop works properly with it. When I try to run lab0016_automated_parking demo in debug mode I got a failure. Code stops running after sending aop.cfg (after sending each line it returns Done, I got failure after the sensorStart command).

cd C:\ti\mmwave_automotive_toolbox_3_6_0\labs\lab0016_automated_parking\gui

mmw_demo_parking_xyz.exe xwr18xx 7 5 1 8 ../chirp_profiles/profile_parking_mimo_2d_50m_3d_10m_aop.cfg 1

Thank you,

Faruk.

over 1 year ago

0 Faruk Yurtseven over 1 year ago

Prodigy 50 points

this output little bit different

0 onur emre uygun over 1 year ago in reply to Faruk Yurtseven

Prodigy 110 points

Hello,

I am having to similar problem. I would be grateful if could get back to you on this.

0 Faruk Yurtseven over 1 year ago

Prodigy 50 points

@Cesar

Do you have a solution?

I have exactly the same problem with that :

e2e.ti.com/.../awr1843boost-the-debug-error-in-the-lab0016_automated_parking

0 Cesar over 1 year ago in reply to Faruk Yurtseven

TI__Guru*** 138329 points

Hi,

Are you using the aop binaries?

C:\ti\mmwave_sdk_03_05_00_04\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo_dss.xe674, xwr18xx_mmw_aop_demo_mss.xer4f?

Thank you

Cesar

0 Faruk Yurtseven over 1 year ago in reply to Cesar

Prodigy 50 points

Hi,

First of all, thank you for your reply and I would like to say that I have solved the problem (but I need your idea). I was not able to test the prebuilt binaries due to a difference on my own board. I solved the problem by replacing

% 2D subFrameCfg
subFrameCfg 0 0 0 2 128 50 0 1 1 50
% 3D subFrameCfg
subFrameCfg 1 0 2 3 128 50 0 1 1 50

with

% 2D subFrameCfg
subFrameCfg 0 0 0 2 64 50 0 1 1 50
% 3D subFrameCfg
subFrameCfg 1 0 2 3 64 50 0 1 1 50

in the profile_parking_mimo_2d_50m_3d_10m_aop.cfg file .

0 Cesar over 1 year ago in reply to Faruk Yurtseven

TI__Guru*** 138329 points

Hi,

This is interesting.

Why did you think about making this change?

This parameter is the numLoops, it represents how many times we loop through the unique chirps.

So, in the updated config there are less chirps.

There are probably some other changes in the sw that would explain this behavior

thank you

Cesar

Sensors

Sensors forum

AWR1843AOP: Code stops running after sending sensor start