AWRL1432: AWRL1432 raw ADC data Capture with mmw Demo

Hello Ken,

The AWRL1432 can be used in conjuction with DCA1000 for raw ADC data capture. This is explained in the EVM's userguide. 

Hope this helps,

-E. Shareef

Hi Shareef

What I seek are guide to sample ADC raw data while app is running.  so studio cannot be used to collect raw data in this way.

Can you pls suggest which app binary support  real time collection and what  studio_cli cmd should be used?

Thanks 

Ken

Hello,

For binary/additional support I am ccing a colleague of mine here. You should be able to develop a lua script based on stuido API commands to talk to radar device and collect raw adc data.

MATLAB also can control mmWave Studio to collect this data as well. 

Hope this helps,

E. Shareef

Hi Shareef and Cesar

1. A lua script is used to configure RF in studio while in app we do not use lua to configure RF in app.

2. Customer feedback that when they are using adcLogging cmd in CLI , they can only detect clk signals on scope, so both mmw and motion detection demo support real time adcLogging on AWRL1432?

Thanks 

Ken

Ken,

Ken Zhang said:

1. A lua script is used to configure RF in studio while in app we do not use lua to configure RF in app.

Yes, the RDIF is configured in the target code

Ken Zhang said:

2. Customer feedback that when they are using adcLogging cmd in CLI , they can only detect clk signals on scope, so both mmw and motion detection demo support real time adcLogging on AWRL1432?

Yes, both demos support the adcLogging command.

Let me check with SDK team if there is additional documentation

thank you

Cesar

Hi Cesar

Did we ever test adcLogging functionality in mmw demo?

I believe lua and mmw studio are not the correct tools to test it.

Thanks

Ken

Ken Zhang said:

Did we ever test adcLogging functionality in mmw demo?

I am checking with the SDK team. I will let you know as soon as I have an update

Ken Zhang said:

I believe lua and mmw studio are not the correct tools to test it.

You are correct.

thank you

Cesar

Hi,

I have confirmed that "adcLogging" command has been validated by the SDK team.

There is also an example provided here

RadarToolbox\radar_toolbox_1_20_00_11\tools\Adc_Data_Capture_Tool_DCA1000_CLI

This example was developed using the L SDK 5.0 demo.

It can work with L SDK 5.3 demo, however the RDIF configuration in the target code must be modified to only support raw data (no sideband). The demo code must be re-built after the updates.

thank you

Cesar

Hi Cesar

With your guidance, I could successfully record data with AWRL6432 with radar_toolbox_1_20_00_11\tools\Adc_Data_Capture_Tool_DCA1000_CLI\prebuilt_binaries\motion_and_presence_detection_demo.release.appimage and\radar_toolbox_1_20_00_11\tools\Adc_Data_Capture_Tool_DCA1000_CLI\chirp_configs\ xWRL6432_inCabinSensing_5104.cfg  

However, when I try with C:\ti\MMWAVE_L_SDK_05_03_00_02\examples\mmw_demo\motion_and_presence_detection\xwrL64xx-evm\m4fss0-0_freertos\ti-arm-clang\motion_and_presence_detection_demo.debug.appimage and MMWAVE_L_SDK_05_03_00_02\examples\mmw_demo\motion_and_presence_detection\profiles\xwrL64xx-evm\TrackingClassification_MidBw.cfg (already take care of adcLogging/lowPower/baudrate), It failed,  which the log shows as below.

So i think there might be some issue in SDK 5.3.0.2 binary, could you pls help check with team again?

Reset AR Device command : Success

ans =

0

FPGA Configuration command : Success

ans =

0

Configure Record command : Success
Warning: serial will be removed in a future release. Use serialport instead.
sensorStop 0

sensorStop 0

Done
channelCfg 7 3 0

mmwDemo:/>

mmwDemo:/>channelCfg 7 3 0

Done
chirpComnCfg 16 0 0 128 4 28 0

mmwDemo:/>

mmwDemo:/>chirpComnCfg 16 0 0 128 4 28 0

Done
chirpTimingCfg 6 32 0 40 60.5

mmwDemo:/>

mmwDemo:/>chirpTimingCfg 6 32 0 40 60.5

Done
frameCfg 2 0 200 64 100 0

mmwDemo:/>

mmwDemo:/>frameCfg 2 0 200 64 100 0

Done
antGeometryCfg 0 0 1 1 0 2 0 1 1 2 0 3 2.418 2.418

mmwDemo:/>

mmwDemo:/>antGeometryCfg 0 0 1 1 0 2 0 1 1 2 0 3 2.418 2.418

Done
guiMonitor 2 3 0 0 0 1 0 0 1 1 1

mmwDemo:/>

mmwDemo:/>guiMonitor 2 3 0 0 0 1 0 0 1 1 1

Done
sigProcChainCfg 32 2 3 2 8 8 1 0.3

mmwDemo:/>

mmwDemo:/>sigProcChainCfg 32 2 3 2 8 8 1 0.3

Done
cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1

mmwDemo:/>

mmwDemo:/>cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1

Done
aoaFovCfg -70 70 -40 40

mmwDemo:/>

mmwDemo:/>aoaFovCfg -70 70 -40 40

Done
rangeSelCfg 0.1 10.0

mmwDemo:/>

mmwDemo:/>rangeSelCfg 0.1 10.0

Done
clutterRemoval 1

mmwDemo:/>

mmwDemo:/>clutterRemoval 1

Done
compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000

mmwDemo:/>

mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000

Done
adcDataSource 0 adc_data_0001_CtestAdc6Ant.bin

mmwDemo:/>

mmwDemo:/>adcDataSource 0 adc_data_0001_CtestAdc6Ant.bin

Done
adcLogging 1

mmwDemo:/>

mmwDemo:/>adcLogging 1

Done
lowPowerCfg 0

mmwDemo:/>

mmwDemo:/>lowPowerCfg 0

Done
factoryCalibCfg 1 0 40 0 0x1ff000

mmwDemo:/>

mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000

Done
boundaryBox -3.5 3.5 0 9 -0.5 3

mmwDemo:/>

mmwDemo:/>boundaryBox -3.5 3.5 0 9 -0.5 3

Done
sensorPosition 0 0 1.9 0 0

mmwDemo:/>

mmwDemo:/>sensorPosition 0 0 1.9 0 0

Done
staticBoundaryBox -3 3 0.5 7.5 0 3

mmwDemo:/>

mmwDemo:/>staticBoundaryBox -3 3 0.5 7.5 0 3

Done
gatingParam 3 2 2 2 4

mmwDemo:/>

mmwDemo:/>gatingParam 3 2 2 2 4

Done
stateParam 3 3 12 50 5 200

mmwDemo:/>

mmwDemo:/>stateParam 3 3 12 50 5 200

Done
allocationParam 6 10 0.1 4 0.5 20

mmwDemo:/>

mmwDemo:/>allocationParam 6 10 0.1 4 0.5 20

Done
maxAcceleration 0.4 0.4 0.1

mmwDemo:/>

mmwDemo:/>maxAcceleration 0.4 0.4 0.1

Done
trackingCfg 1 2 100 3 61.4 191.8 100

mmwDemo:/>

mmwDemo:/>trackingCfg 1 2 100 3 61.4 191.8 100

Done
presenceBoundaryBox -3 3 0.5 7.5 0 3

mmwDemo:/>

mmwDemo:/>presenceBoundaryBox -3 3 0.5 7.5 0 3

Done
microDopplerCfg 1 0 0.5 0 1 1 12.5 87.5 1

mmwDemo:/>

mmwDemo:/>microDopplerCfg 1 0 0.5 0 1 1 12.5 87.5 1

Done
classifierCfg 1 3 4

mmwDemo:/>

mmwDemo:/>classifierCfg 1 3 4

Done
sensorStart 0 0 0 0

mmwDemo:/>

mmwDemo:/>sensorStart 0 0 0 0

Done

mmwDemo:/>

mmwDemo:/>

mmwDemo:/>

mmwDemo:/>☻☻   2d
Warning: A timeout occurred before the Terminator was reached.
'serial' unable to read all requested data. For more information on possible reasons, see <a href="matlab: helpview(fullfile(docroot,'instrument','instrument.map'), 'serial_somedata')"'>Serial Read Warnings</a>.
 áy1 ?TçxI. 1I&__Y ;Aoù↑ 4TFû↓ FS?úç↑ MTÄÿü N[[emoticon:585a96b39c574b95b19bd00a45086da0]ù- 8OF ?☻ ?Zº Y lU↓Y◄ 8Fr∟±◄ ?G_←?► DF.  ▬ ë O O h  " E ½ ? U & ¶ ? U £ g O ¥ é O x ? 1 ú `  § i ? ∟ ° o  j s ? ⌂ ? ? A ? c ? b ?  w ↑ Q ú ♀ ÿ w ? = ▲ í ù  $ 6 ? } /  û K↨ ?Ü☻ o? yù d? e¬ T\ ?◄ Ä♂ ÿ♂ Ée $r 2$☻ í Ih fY AR ü6 N * j¶ ¿m ÿ▌ »C 3I u9 s# [% U↑ ·? ÷I ?# * 6¶ n ¶2 ª/ k L+ ¥1 ç# GK  H Å← C ½¶

HI, there: 

You can first try to enable less uart data transfer. 

guiMonitor 2 3 0 0 0 1 0 0 1 1 1

Change to

guiMonitor 2 0 0 0 0 1 0 0 0 0 0

Or you can add the uart speedup CLI as 

baudRate 1250000

Best,

Zigang

Hi Zigang 

Tried to modify  guiMonitor, still no LVDS optput. 

But every thing works fine in C:\ti\radar_toolbox_1_20_00_11\tools\Adc_Data_Capture_Tool_DCA1000_CLI.  So I doubt there is some issue in SDK 5302 LVDS functionality.

By the way set baudRate 1250000 would stall DCA1000_cli.

Thanks

Ken

Hi, Ken:

Yes, the capture tool has not built in the support for baud-rate change yet.   Will you be able to work with this example code under Adc_Data_Capture_Tool_DCA1000_CLI then?

Best,

Zigang

Hi Zigang

yes, when using Adc_Data_Capture_Tool_DCA1000_CLI  binary and cfg, everything works fine.

While moving to SDK 5.3.0.2 and taking care of baudrate and adclogging and low power,  still cannot work.

Thanks

Ken

Ken,

We are working to try this feature with SDK 5.3.

We will get back to you in a few days, before end of the week.

thank you
Cesar

Hi Zorah

Thanks for the fix file, it works.

Ken