IWR6843AOPEVM: errors encountered during linking

Hi,

Does it work when you make no modifications? What changes do you make that cause it to run out of memory?

Best

Nate

Hello Nathan i did no change to the application. The only this is what i did is configure the device iwr6843AOP. When i do this its adding a other .cmd file  called: xwr6843_C674x.cmd. 

When i build with the device name iwr6843 its building and i can flash but then i dont receive the data as i expect so i think i need to configure the device as IWR6843AOP. 

Best
Marnick

Marnick Bijlsma said:

The only this is what i did is configure the device iwr6843AOP.

What does this mean? Can you show pictures?

Best,

Nate

in the properties i changed the device name from IWR6843 to IWR6843AOP , see below:

Well i tried but when i flash this iam not receiving the data from the sensor as i espect. I receiving the magicword but the versionbytes etc are not valid. 

Can you try flashing the prebuilt binary found in the toolbox to see if it works?

Best,

Nate

Hello Nate,

I tried to flash the binary of the 3D people count from TI toolbox and this is working. Only when i build the mss and dss in CCS iam not receiving the data frames as expected. 

I have 2 more questions. 

In these situations iam using the 3D people count binary from TI toolbox. 
1. When i use the sensing estimator and changing some values for velocity resolution its giving back cfg values ( without error) which i implement in my cfg file. But with these values the sensor is chrashing and not giving back data. i tried a lot of different values and for the most of the time the sensor is crashing. It looks like the sensor cant handle the values. Are you familiar with this problem and what can i do about it? 

2. In the firmware of the 3D people count is an option to enable the self calibration. Is this neccesary to enable self calibration for the best measurements?  

Kind regards,
Marnick

Marnick Bijlsma said:

1. When i use the sensing estimator and changing some values for velocity resolution its giving back cfg values ( without error) which i implement in my cfg file. But with these values the sensor is chrashing and not giving back data. i tried a lot of different values and for the most of the time the sensor is crashing. It looks like the sensor cant handle the values. Are you familiar with this problem and what can i do about it? 

What values are you sending? If you send the Cfg file over a serial tool, like tera term, you can see the error messages typically. 

Marnick Bijlsma said:

2. In the firmware of the 3D people count is an option to enable the self calibration. Is this neccesary to enable self calibration for the best measurements?  

There are a few calibrations that can be enabled/disabled. Can you show the line number you're referring to? Best measurement would typically require calibrations enabled.

Best,

Nate

Hello Nate,

1. What values are you sending? If you send the Cfg file over a serial tool, like tera term, you can see the error messages typically. 

The values i am sending are these: 


i selected the "short range default" without any modification.


Iam already using a serial terminal to see whats happening. the configurations where send succesfully "done" but 
iam not receiving data with this configuration. Other configurations are working so the problem is with the configuration file
and not the software.

See below the terminal sending configurations and the error that magicbyte is empty array. ( no data)

b'Done\n'

Sending config to poort = /dev/ttyUSB0 baudrate = 115200

b'% SDK Parameters\n'

b'Skipped\n'

b"\rmmwDemo:/>% See the SDK user's guide for more information\n"

b'Skipped\n'

b'\rmmwDemo:/>% "C:\\ti\\mmwave_sdk_[VER]\\docs\\mmwave_sdk_user_guide.pdf"\n'

b'Skipped\n'

b'\rmmwDemo:/>resetDevice\n'

b'Resetting Device... \n'

b'\r\n'

b'\r***********************************\n'

b'\rIWR68xx Indoor people counting demo***********************************\n'

b'\rmmwDemo:/>flushCfg\n'

b'Done\n'

b'\rmmwDemo:/>dfeDataOutputMode 1\n'

b'Done\n'

b'\rmmwDemo:/>channelCfg 15 7 0\n'

b'Done\n'

b'\rmmwDemo:/>adcCfg 2 1\n'

b'Done\n'

b'\rmmwDemo:/>adcbufCfg -1 0 1 1 1\n'

b'Done\n'

b'\rmmwDemo:/>lowPower 0 0\n'

b'Done\n'

b'\rmmwDemo:/>\n'

b'mmwDemo:/>% Detection Layer Parameters\n'

b'Skipped\n'

b'\rmmwDemo:/>% See the Detection Layer Tuning Guide for more information\n'

b'Skipped\n'

b'\rmmwDemo:/>% "C:\\ti\\mmwave_industrial_toolbox_[VER]\\labs\\people_counting\\docs\\3D_people_counting_detection_layer_tuning_guide.pdf"\n'

b'Skipped\n'

b'\rmmwDemo:/>profileCfg 0 60 7 5.7 48.8 0 0 70.92 1 249 5914 0 0 30\n'

b'Done\n'

b'\rmmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1\n'

b'Done\n'

b'\rmmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2\n'

b'Done\n'

b'\rmmwDemo:/>chirpCfg 2 2 0 0 0 0 0 4\n'

b'Done\n'

b'\rmmwDemo:/>frameCfg 0 2 27 0 100 1 0\n'

b'Done\n'

b'\rmmwDemo:/>dynamicRACfarCfg -1 4 4 2 2 8 12 4 12 5.00 8.00 0.40 1 1\n'

b'Done\n'

b'\rmmwDemo:/>staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0\n'

b'Done\n'

b'\rmmwDemo:/>dynamicRangeAngleCfg -1 0.75 0.0010 1 0\n'

b'Done\n'

b'\rmmwDemo:/>dynamic2DAngleCfg -1 3.0 0.0300 1 0 1 0.30 0.85 8.00\n'

b'Done\n'

b'\rmmwDemo:/>staticRangeAngleCfg -1 0 8 8\n'

b'Done\n'

b'\rmmwDemo:/>antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0\n'

b'Done\n'

b'\rmmwDemo:/>antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2\n'

b'Done\n'

b'\rmmwDemo:/>antPhaseRot 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1\n'

b'Done\n'

b'\rmmwDemo:/>fovCfg -1 70.0 70.0\n'

b'Done\n'

b'\rmmwDemo:/>compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0\n'

b'Done\n'

b'\rmmwDemo:/>\n'

b'mmwDemo:/>'

b'% Tracker Layer Parameters\n'

b'Skipped\n'

b'\rmmwDemo:/>% See the Tracking Layer Tuning Guide for more information\n'

b'Skipped\n'

b'\rmmwDemo:/>% "C:\\ti\\mmwave_industrial_toolbox_[VER]\\labs\\people_counting\\docs\\3D_people_counting_tracker_layer_tuning_guide.pdf" \n'

b'Skipped\n'

b'\rmmwDemo:/>staticBoundaryBox -3.0 3.0 0.5 7.5 0.0 3.0\n'

b'Done\n'

b'\rmmwDemo:/>boundaryBox -4.0 4.0 0.0 8.0 0.0 3.0\n'

b'Done\n'

b'\rmmwDemo:/>sensorPosition 2.3 0 15\n'

b'Done\n'

b'\rmmwDemo:/>gatingParam 3 2 2 3 4\n'

b'Done\n'

b'\rmmwDemo:/>stateParam 3 3 12 500 5 6000\n'

b'Done\n'

b'\rmmwDemo:/>allocationParam 20 100 0.1 20 0.5 20\n'

b'Done\n'

b'\rmmwDemo:/>maxAcceleration 0.1 0.1 0.1\n'

b'Done\n'

b'\rmmwDemo:/>trackingCfg 1 2 800 30 46 96 55\n'

b'Done\n'

b'\rmmwDemo:/>presenceBoundaryBox -3 3 0.5 7.5 0 3\n'

b'Done\n'

b'\rmmwDemo:/>sensorStart\n'

b'Debug: Init Calibration Status = 0xffe\n'

TypeError: 'bool' object is not subscriptable
magicByte is empty array
'bool' object is not subscriptable
Traceback (most recent call last):
  File "/home/pi/ltt-rhythm-fall-detection-demo/src/model/uart/data.py", line 57, in data_thread
    if raw["error"] != 0:

2. There are a few calibrations that can be enabled/disabled. Can you show the line number you're referring to? Best measurement would typically require calibrations enabled.

Which calibrations do you recommend. Iam using the mmWave for detecting people, tracking in short range. 
The lines i was reffering to are these. 

Kind regards,
Marnick
 

Hi,

I think the problem is in the profileCfg line. I don't see the exact error, but I would recommend modifying the values sequentially to see which one is causing the failure. I suspect it may be caused by the non-power-of-2 value for the number of samples (249), or the suspiciously small values for ADC start time or chirp idle time,

Best,

Nate

Hello Nate,

Thankyou for replying, 

I dont have an answer on the following question:

2. There are a few calibrations that can be enabled/disabled. Can you show the line number you're referring to? Best measurement would typically require calibrations enabled.

Which calibrations do you recommend. Iam using the mmWave for detecting people, tracking in short range. 
The lines i was reffering to are these. 

Best,

Marnick

For best measurement you should enabled calibration.

Best,

Nate