AWR1843: AWR1843_MRR demo: Hardcoded Config to CLI commands

Rehman

Part Number: AWR1843
Other Parts Discussed in Thread: AWR1642,

Tool/software:

Hi.......is there any ways by which we can convert the hardcoded config in MRR demo to CLI commands. We have understood all the configs of the MRR demo , the problem is that how to convert them to CLI commands.

over 1 year ago

0 Gabriel Gigliotti over 1 year ago

TI__Expert 3150 points

Helo,

In the mss_mrr_cli,c file there is a function called MRR_MSS_CLIInit. You can see that is where the hardcoded configuration takes place and the option to initialize the CLI is defined out. You can define out the advancedcfg and sensor start and redefine the CLI initialization portion. See SDK 3.6 for further examples to then incorporate the CLI functions.

Thanks,

Gigliotti

0 Rehman over 1 year ago in reply to Gabriel Gigliotti

Intellectual 265 points

Hai...., The point is how to convert the given hardcoded config to CLI command in the MRR demo.....Can I convert MRR demo such that i can use a similar custom gui of ours like MMWAVE_DEMO Visualiser in which I can send the configs from PC.

+1 Gabriel Gigliotti over 1 year ago in reply to Rehman

TI__Expert 3150 points

Hello,

Yes, you have to use the mmwave example from SDK 2.1 for the AWR1642 and apply it to the AWR1843. A good start is looking at the cli.c file in the mss folder to see their implementation for the AWR1642. I would start in the mss_mrr_cli.c file for the AWR1843 MRR demo. Warning, it is quite an involved process.

Thanks,

Gigliotti

0 Rehman over 1 year ago in reply to Gabriel Gigliotti

Intellectual 265 points

Ya,,got it. will look into this. For now I found this info helpful.....

0 Rehman over 1 year ago in reply to Gabriel Gigliotti

Intellectual 265 points

Ya,,got it. will look into this. For now I found this info helpful.....

0 Rehman over 1 year ago in reply to Gabriel Gigliotti

Intellectual 265 points

Hai.....instead of doing this I came up with an idea.....i.e i will convert the MRR and SRR chirp configs in the MRR demo to CLI Commands and then pass to the out_of_box demo so that I will get the same functionality of MRR demo with CLI commands.

What is your opinion about this....?

+1 Kaushik Gowda over 1 year ago in reply to Rehman

TI__Mastermind 20605 points

Hey Rehamn,

This won't be the case as the MRR application has additional processing when compared to the OOB demo and therefore, a direct migration of the CLI params would not be possible.

Regards,

Kaushik

0 Rehman over 1 year ago in reply to Kaushik Gowda

Intellectual 265 points

OK....Thanks....If further doubt comes will reach back.

0 Rehman over 1 year ago in reply to Gabriel Gigliotti

Intellectual 265 points

Instead of looking into SDK 2.1 for AWR1642 it will be good to look at the OOB demo for AWR1843 right...?, The only change will be needed to make in the MSS part right..?

0 Rehman over 1 year ago in reply to Kaushik Gowda

Intellectual 265 points

OKK....Is there any software from u guys to convert to CLI commands....OR we should read the SDK and convert it one by one to CLI commands.

+1 Kaushik Gowda over 1 year ago in reply to Rehman

TI__Mastermind 20605 points

Hi Rehman,

Thank you for your patience! We do not have any SW to convert the header-based config into a CLI config.

This conversion would have to be done by the user as each user would have their own SW architecture.

Rehman said:
The only change will be needed to make in the MSS part right..?

Regards,

Kaushik

0 Rehman over 1 year ago in reply to Kaushik Gowda

Intellectual 265 points

Thank you.....

Sensors

Sensors forum

AWR1843: AWR1843_MRR demo: Hardcoded Config to CLI commands