AWR6843AOP: After the Bypass CLI, the RF module cannot work

Hi Cherry

I'll need more information in order to assist you.

There are two examples of hard coded config in the Resource Explorer.

• Hard Coded Config for mmWave SDK Demo
• Multi-Gesture Recognition

The Multi-Gesture Recognition lab implements the hard-coded CLI the way the documentation describes it.

Regards,

AG

Hi AG,

Thanks for your reply!

The customer takes the following approach:

The cli module source code in utils is extracted and hard-coded by multiplexing the original engineering cli-related functions, but debug mode does not work. The same modification work well in 1642evm and in the area scan of 6843aop, but the overhead_mount_occupancy does not work.

The customer is using a different approach than the official hard code. The official hard code changes the source code too much and may cause bugs during the modification process.

Expecting the updates!

Thanks!

Best Regards,

Cherry Zhou

Hi AG,

Thanks for your reply!

The code is not hanging and the console output is normal.

The customer now suspects that BSS cannot start, causing both MSS and DSS to be in IDLE state without receiving an event from BSS, and UART has no result output.

The use case also does not work properly in debug state, and is the same as the customer-modified engineering. But this direct burn bin file is fine.

The customer also implements hard coded startup in the same way on other demo projects, but this overhead_mount_occupancy fails. The customer‘s project aims to build on this demo for secondary development.

Could you help to check this? Thanks a lot!

Best Regards,

Cherry

Hi AG,

Sorry to bother you, may I now is there any updates about the latest info?

Thanks again!

Best Regards,

Cherry

Hi Cherry

I'll need more information from customer.

There should be some information in the CCS Debug Console. Please follow up with customer and then we can proceed.

Regards,

AG

Hi AG,

Sorry for the delay.

The customer has updated the below info:

Akash Gondalia said:

There should be some information in the CCS Debug Console.

The info in the CCS Debug Console is as same as when it's not bypass, except it dose not start up.

Thanks and Best Regards,

Cherry

Hi Cherry

Please have customer look at this Out of Box Demo with Hard Coded Config Lab. From the information you've given me, it is clear customer is not implementing it this way.

In the demo the CLI Task is replaced with a task that sets the chirp config parameters structurally (hard-coded config). They might even be able to replace the existing CLI Task in their code with the new CLI Task in the Hard Coded Config Lab.

Regards,

AG