AWR6843ISK: how to use captured .bin file on out of box demo

Mani D

Part Number: AWR6843ISK
Other Parts Discussed in Thread: MMWAVE-L-SDK, AWR6843

Tool/software:

Dear sir/madam,

I have captured raw adc data using AWR6843ISK+DCA 1000 card and captured data is stored in .bin file.

I want to Run the out of box demo with this RAW ADC data from .bin file instead of "Front end data coming Via ADC buffer" and run the complete example and visualize the output.

As per my understanding the following step need to be done :

1. .bin file data need to stored and Mapped

2.mmwave_start step code need to be bypassed in the below timing diagram,but this can lead to not generating frame_event and chirp_event trigger causes further code not running.

i have already referred the below thread

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1446873/awr6843isk-how-to-use-captured-bin-file

but i could not get understand logic of " need to simulate a chirp available ISR so that the rest of the signal chain can work as normal".

My question:

1. how to use Captured bin file Raw adc data instead of "Front end data coming Via ADC buffer" and execute entire Example Chain?

2.if any similar design is available with AWR series ,please share details

regards,

Mani

regards,

mani

3 months ago

0 Vignesh Kondapally 3 months ago

TI__Intellectual 2270 points

Hi Mani,

We appreciate you reaching out, please allow us a few days to review your question and respond accordingly.

Best,

Vignesh K.

0 Mani D 3 months ago in reply to Vignesh Kondapally

Intellectual 270 points

hi vignesh,

any update ?

regards,

mani

0 Kristien Everett 3 months ago in reply to Mani D

TI__Genius 13156 points

Hey Mani,

For simple variables that are utilized infrequently during DPC execution, you could print to the debug console using System_printf. For arrays, you could use fwrite to write the data to a binary and then look over the data afterwards. However, there is a chance that adding printouts or writing to a file will violate the timing constraints on the ARM side still.

You could theoretically comment out the DPC_Objdet_Assert on line 645 which would prevent the ARM core from aborting, though this will introduce unexpected behavior and may inject incorrect data into the processing chain.

Regards,

Kristien

0 Mani D 3 months ago in reply to Kristien Everett

Intellectual 270 points

HI kristien,

thanks for your reply.

this question is different from my other question.

My question:

1. how to use Captured bin file Raw adc data instead of "Front end data coming Via ADC buffer" and execute entire Example Chain?

( " need to simulate a chirp available ISR so that the rest of the signal chain can work as normal" - how to do it?)

2.if any similar design is available with AWR series ,please share details

regards,

Mani

0 Kristien Everett 3 months ago in reply to Mani D

TI__Genius 13156 points

Hey Mani,

You can simulate a chirp available through the usage of the EDMA by initiating a transfer (EDMA_startTransfer) to channel ID EDMA_TPCC0_REQ_DFE_CHIRP_AVAIL of channel type EDMA3_CHANNEL_TYPE_DMA. This requires some additional configuration on the EDMA side which can be seen in the range processing test (packages\ti\datapath\dpu\rangeproc\test\hwa_main.c).

Regards,

Kristien

0 Mani D 3 months ago in reply to Kristien Everett

Intellectual 270 points

hi Kristien,

thanks for your reply.

if i want to implement "reading data from bin file and EDMA_startTransfer as suggested by on "TI OUT of BOX "example (C:\ti\radar_toolbox_1_30_01_03\source\ti\examples\Out_Of_Box_Demo\src\xwr6843ISK).

my question :

1. will it work without any issue directly?

2. Do i need to comment any function /API on the existing Code to aviod RF front data transfer/flowing to DPC processing chain?

if i have to comment ,please let me know steps or function to be commented or to follow any reference example available.

Regards,

mani

0 Kristien Everett 3 months ago in reply to Mani D

TI__Genius 13156 points

Hey Mani,

See my comments below.

Mani D said:
1. will it work without any issue directly?

I do not know for certain as that will depend on how you integrate the relevant EDMA code. For example, you could set up a separate adcFileReadTask which is triggered upon receiving sensor start and reads in an ADC data file - similar to what we have in MMWAVE-L-SDK.

Mani D said:
2. Do i need to comment any function /API on the existing Code to aviod RF front data transfer/flowing to DPC processing chain?

You would need to comment out MmwDemo_startSensor within mmw_cli.c since we don't want the sensor starting and populating the ADC data buffer.

Regards,

Kristien

0 Mani D 3 months ago in reply to Kristien Everett

Intellectual 270 points

Hi Kristien,

thanks for your reply.

Kristien said:

2. Do i need to comment any function /API on the existing Code to aviod RF front data transfer/flowing to DPC processing chain?

0 Kristien Everett 3 months ago in reply to Mani D

TI__Genius 13156 points

Hey Mani,

Mani D said:
1.if i comment out MmwDemo_startSensor ,does the remaining processing chain will work, without any issue?

2. else ,what changes do i need to add in the code ,to run the further processing without any issue?

3. if similar approach is done on "MMWAVE-L-SDK",can please share the details on which file /part of which function got implemented?

As described previously, you will still need to simulate a chirp available through the EDMA and should add in a task or function to pull in the captured ADC data. I would highly recommend reviewing the CLI_MMWStart function from the MMWAVE-L-SDK - equivalent to MmwDemo_CLISensorStart from SDK3 - under <MMWAVE_LSDK_INSTALL_DIR>/examples/mmw_demo/mmwave_demo/source/mmw_cli.c and the adcFileReadTask under <MMWAVE_LSDK_INSTALL_DIR>/examples/mmw_demo/mmwave_demo/source/test/ADC_testbuf.c to understand how raw ADC data is fed in on the low power platform. Most of the code should be portable to SDK3, though you may need to find equivalent SDK3 functions or features for some of the LSDK functions.

Note: File opening is only supported when the device is connected to the CCS debugger.

Let me know if you have any other questions.

Regards,

Kristien

0 Mani D 3 months ago in reply to Kristien Everett

Intellectual 270 points

Hi kristien,

Thanks for your reply..

I have gone through your suggestions and reply...

So as per my understanding the following steps need to be done to read adc data from file instead of Rf front end..

1.need to comment execution of mmwave start--which stops the sensor start,but this will lead to not generating any frame event and chirp event by Rf front end..

2.read one chirp of raw adc data from bin file and write into adc buffer memory address..

3. I need to simulate frame event and chrip event by invoking necessary API/command EDMA_startTransfer as you mentioned in your previous reply..

My question:

1.please correct me, my above understanding is correct or any other steps i missed it?

2.please confirm using of "EDMA_startTransfer command generate chirp event or it does transfer of data from ADC buffer to HWA internal memory using EDMA for processing or both ?

3.if EDMA_startTransfer command generate chirp event then do I need use/invoke this command equal to number chirps used in the processing or need to invoke only once itself sufficient?

4.if EDMA_startTransfer command does not do the transfer of Adc buffer data to HwA internal memory...then using which command or routine I can transfer the data for processing?

5.and also confirm, first adc buffer data need to be moved to hwa memory then chrip event need to be generated or first chirp event will be generated them adc buffer data will be moved to hwa memory?

Regards,

Mani

Sensors

Sensors forum

AWR6843ISK: how to use captured .bin file on out of box demo