AWR1843BOOST: HardConfig for AWR1843BOOST in OOB demo

Rehman

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

Tool/software:

Hai,

In the AWR1843 OOB demo i needed to hardconfig the CFG file. Actually I followed the Documentation of hard_coded_config_68xx.

I updated the CLI.c file as followed and for building the flash i followed "Building Flash Binary with HCC Implentation" ( Method A.2 (Editing an Existing CCS Project for HCC)) .

But it's not working for me.

When i am uploading CFG files from Mmwavedemo visualiser it is working fine.

But the HARD CONFIG part is not working.

I would also like to know whether the X,Y,Z and doppler values of OOB demo are in Q format and little endian format as in MRR demo.

In my CCS software the OOB demo is of "isk" configuartion. Is this creating an issue?

Thanks and regards

Rehman.

7 months ago

0 shruti gupta 7 months ago

TI__Genius 11220 points

Hi Rehman,

In one of the toolbox example, for 1642 device, it has been implemented. You can take that as reference.

You can access the example from here - radar_toolbox_2_30_00_12\source\ti\examples\Fundamentals\CAN_Data_Output\1642_object_data_over_can

Regards,

Shruti

0 Rehman 6 months ago in reply to shruti gupta

Intellectual 265 points

Hi Shruti,

This example which you gave me doesn't explain nothing related to how to HardCode chirp config in OOB demo and about decoding the X,Y and Z values of OOB demo.

Regards,

Rehman

0 Rehman 6 months ago in reply to shruti gupta

Intellectual 265 points

Hai ,

It would be great if TI can guide me.

The OOB demo i am using is from mmwaveSDK 3.6.0.0-LTS for my AWR1843BOOST board.

I have followed "Building Flash Binary with HCC Implentation" ( Method A.2 (Editing an Existing CCS Project for HCC)) .

I have also added CLI.c and CLI_mmwave.c file from mmwaveSDK 3.6.0.0-LTS packages as mentioned in the document " Hard Coded Config User Guide ".

I followed ( Method A.2 (Editing an Existing CCS Project for HCC)) for flashing binary.

I also tried "Method B" by running command prompt, but it was giving errors "gmake is not recoginsed as an internal or external command".

Regards,

Rehman

0 shruti gupta 6 months ago in reply to Rehman

TI__Genius 11220 points

Hi Rehman,

Can you share the error snippets that you are getting?

Regards,

Shruti

0 Rehman 6 months ago in reply to shruti gupta

Intellectual 265 points

Hai Shruti,

Ya will share.

Is it the issue of the SDK? .

Regards,

Rehman

+1 Rehman 6 months ago in reply to shruti gupta

Intellectual 265 points

Hai Shruti,

The HCC thing is been solved.

The issue was in the HardConfigCommands which i was sending.

Regards,

Rehman

Sensors

Sensors forum

AWR1843BOOST: HardConfig for AWR1843BOOST in OOB demo