This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR6843AOP: Unable to run people counting demo on 6843AOP

Part Number: AWR6843AOP
Other Parts Discussed in Thread: SYSBIOS

Hello TI Team,

We are running 68xx_people_counting demo project from tool box mmwave_industrial_toolbox_4_1_0. We are specifically interested in this project, as we are looking for a example with 6843_AOP+DSM. In other examples, hardware accelerator is used. We need a example where DSM is used for range, heatmap calculation.

We are able to compile the MSS and DSS code. After executing the codes, we are able to get to a point where CLI gets operational but after that the code crashes. We are getting below log. We can confirm that DSS is still in running stage and mss goes in to suspended state.

Can you please let us know if there is any obvious reason for this failure. We have not made any change to the lab code and we have not sent the configuration file yet. The crash happens before that.

[Cortex_R4_0] **********************************************
Debug: Launching the Millimeter Wave Demo
**********************************************
Debug: MMWDemoMSS Launched the Initialization Task
Debug: System Heap (TCM): Size: 98304, Used = 4912, Free = 93392 bytes
Debug: MMWDemoMSS mmWave Control Initialization was successful
[C674X_0] Debug: Logging UART Instance @00817a60 has been opened successfully
Debug: DSS Mailbox Handle @0080eac0
Debug: MMWDemoDSS create event handle succeeded
Debug: MMWDemoDSS mmWave Control Initialization succeeded
Debug: MMWDemoDSS ADCBUF Instance(0) @00817a48 has been opened successfully
Debug: MMWDemoDSS Data Path init succeeded
Debug: MMWDemoDSS initTask exit
[Cortex_R4_0] Debug: CLI is operational
Exception occurred in ThreadType_Task.
Task handle: 0x8006430.
Task stack base: 0x8006490.
Task stack size: 0x1000.
R0 = 0x0801cfd0 R8 = 0xffffffff
R1 = 0x08007198 R9 = 0xffffffff
R2 = 0x0000006a R10 = 0xffffffff
R3 = 0xc8000130 R11 = 0xffffffff
R4 = 0xffffffff R12 = 0x17650300
R5 = 0xffffffff SP(R13) = 0x08007190
R6 = 0xffffffff LR(R14) = 0x00014d5d
R7 = 0x080072a0 PC(R15) = 0xc8000130
PSR = 0x600c019f
DFSR = 0x00000000 IFSR = 0x0000000d
DFAR = 0x00000000 IFAR = 0xc8000130
ti.sysbios.family.arm.exc.Exception: line 201: E_prefetchAbort: pc = 0xc8000130, lr = 0x00014d5d.
xdc.runtime.Error.raise: terminating execution

Thanks,

Rohan

  • Hello Rohan,

    Have you tried using a more recent version of the toolbox? ITB_4_1_0 is very old. Please also confirm if you are using the TI AOP EVM and if you are able to flash and run the prebuilt binary?

    Did you make any modifications to the code? Also what do you mean by DSM?

    Regards,

    Jackson

  • Hello Jackson,

    Thanks for reply. I have mis-spelled DSS to DSM. We need a AOP example, for object/people detection, where DSS is used for data processing. In the latest version of ITB, all the example of people detection or area scanner are based on MSS and Hardware Accelerator. Thus I decided to work with ITB_4_1_0.

    The people counting demo in ITB_4_1_0 is based on SDK_3.3.0.2. As this sdk does not have support for 6843AOP, we have migrated the lab to SDK_3.5.0.4. After migration we are able to building the code. The DSS is initialising without any error, but the MSS is crashing during initialisation. 

    We are unable to run the prebuild binary, as those binaries are with sdk_3.3.0.2. As we are running the lab on 6843_AOP, the prebuild binaries are not suitable. Thus we are building new binary with sdk_3.5.0.4.

    Thanks,

    Rohan

  • We need a AOP example, for object/people detection, where DSS is used for data processing.

    Can you be more specific about what you need the DSS to perform with processing? The OOB demo for AOP does only use the MSS, you are correct. But the people counting demo (compatible with AOP) performs most of the pointcloud processing on the DSS side. Only the range profile is calculated in the HWA, the rest of the processing is done with the DSP. Is there something else you are looking for?

    Regards,

    Jackson