IWR6843: IWR6843AoPCB: Running Vitals Sign Demo on IWR6843AoPCB custom board doesn't capture data

Dear Arun:

We are going to need a couple of days to get started resolving your issue.

Best regards,

Connor Desmond

Hi Arun,

Please confirm the  Silicon revision of IWR6843AOP device.

The current offering Tirex for Vital signs only supports ES1.0  and in order yo use in on ES2.0 revision you would have to recompile and adapt to new revision.

Please check the migration to IWR7843AOP ES2.0 in the following guide  Migrating to xWR68xx and xWR18xx Millimeter Wave (Rev. B)

Thank you,

Vaibhav

Hi Vaibhav,

This is not Antenna On Package(AoP) EVM. As I mentioned above it is Antenna on PCB (IWR6843AoPCB) ES2.0 revision device (https://www.mistralsolutions.com/product-engineering-services/products/som-modules/60ghz-industrial-mmwave-radar-module/)

Thanks

Arun

Dear Connor,

Thank you for your reply!

Providing some debugging screen shots, this may help you to identify the issue.

One thing I observed that the MMWave_config() is happening before issuing the profile configuration commands. I hard coded the commands by modifying the cli.c file in MMwave SDK-03.03.00.03.

I put break point at line #557 in mss_main.c,

Then it hits in second break point in MMWave_configLink() under mmwave_link.c.

 So above we can see that it is checking for the configurations and try to configure MMWave. At the same time no commands are issued, see the serial terminal at bottom right corner.

Error has happened and threw exception at line #635.

Please help me to solve this issue.

Regards

Arun

Arun

Before we debug further.

Is this issue the same as posted here :   https://e2e.ti.com/support/sensors/f/1023/t/899308

If yes then we would want to close out the other one and continue the debug here. 

Please let us know.

Thank you,

Vaibhav

Dear Vaibhav,

Yes it i same as http://e2e.ti.com/support/sensors/f/1023/t/899308.

Regards

Arun

Hi Vaibhav,

It is found that passing the MMWDEMO_CLI_SENDORSTART_EVT in MmwDemo_mssCtrlPathTask() function even if the event MMWDEMO_CLI_SENDORSTART_EVT not posted from CLI.

Can you please suggest why this event is updating even this not posted anywhere?

Thanks

Arun

Dear Arun:

I am going to request that you make a new thread. I am going to close this thread.

Best regards,

Connor Desmond

Dear Connor,

I wonder that why you close this issue without any suggestion. This issue not yet resolve also I had opened two threads regarding the same issue and closed after some requests.

You can refer those threads,

1. https://e2e.ti.com/support/sensors/f/1023/t/895479

2. https://e2e.ti.com/support/sensors/f/1023/t/895479

There are other members also facing this issue. So kindly help us to resolve this issue.

Regards

Arun

Hi Arun,

I thought we resolved the original issue here:

https://e2e.ti.com/support/sensors/f/1023/t/899308

If this issue is not resolved let's take it there. 

The last post on this thread is different issue. 

"It is found that passing the MMWDEMO_CLI_SENDORSTART_EVT in MmwDemo_mssCtrlPathTask() function even if the event MMWDEMO_CLI_SENDORSTART_EVT not posted from CLI."

Asking to create separate thread for this.

Thanks

Yogesh

Dear Yogesh,

Thank you for the reply!

The following thread is having the same issues. I'm also debugging this issue, and adding observations on these threads to cut down this issue.

You can refer the following threads to get the idea.

1. https://e2e.ti.com/support/sensors/f/1023/t/899308

2. https://e2e.ti.com/support/sensors/f/1023/t/895479

3. https://e2e.ti.com/support/sensors/f/1023/t/895479

The last post was my observation on this issue while debugging using XDS110-JTAG connection in our custom board.

I have opened another thread for the previous post, refer https://e2e.ti.com/p/addpost?rt=906754

For a clarification, whether I need to open one-to-one thread for each of my observation to solve this issue?

Regards

Arun

Hi Arun,

If the original issue is not resolved then there is no need to create new thread. 

The vital sign pre-build binaries have been verified on IWR6843 ISK and there should not be any issue running the same on custom board as long as there are no changes to pin-mux setting. Please verify the pin-mux setting in mss_main.c. But I do not think this should be issue.

I feel there is mis-match b'n DFP firmware on the device and the one needed by vital sign. 

Please flash the pre-build vital sign vital_signs_demo_68xx.bin meta-image from Industrial tool box 4.3.2. This should work as-is if there is no changes required for your custom board. Also this will flash required firmware for the vital signs since it is not loaded through CCS. 

Also if you have to modify the existing vital sign meta image, please make sure you use SDK 3.3 for compilation.

For verification if you are using the right firmware, you should not see any error with issuing below config since calibration was not included in SDK 3.3 :

calibDcRangeSig -1 0 0 0 0

Please follow the same and let me know the result.

Thanks

Yogesh