Hello Champs,
HW: AWR1642BOOST
SW: mmwave_automotive_toolbox_3_0_0
Customer changed ADC_SAMPLE_VAL from 256 to 300, but there is nothing shown on the UI. Is there something he missed?
Thanks
Regards,
Shine
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Shine,
I would like you to confirm the following:
Error: mmWave Config failed [Error code: -3108 Subsystem: 41]
If so, you will have to make changes either to the sampling rate or the ramp end time to accommodate the 300 samples for the same chirp.
Additionally, I would kindly request the customer to migrate to the latest version of the automotive toolbox if possible.
Regards,
Kaushik
Hi Kaushik,
Thank you very much.
Was the application running fine before the modifications?
Before the modifications, the application and the GUI are both running fine.
Is the reload configuration box is checked in the GUI? This needs to be applied before starting the GUI.
As for the GUI configuration, what other parameters need to be modified except for the chirp number?
When you made the changes, were the changes applied to both the mss and dss project cfg header file?
Yes, the modification is made in srr_config_chirp_design_SRR80.h.
- Can you confirm this is the same error you see in CCS when you try running the code with the changes?
Error: mmWave Config failed [Error code: -3108 Subsystem: 41]
After modifying the parameters and running the code, there is no error message as below snapshot shown. But the GUI can't detect the object. (Please be noted that SAMPLERATE_VAL is set to 6,000, frequency slope is set to 5.8, when SAMPLERATE_VAL is set to 5000, it prompted the error. )
Regards,
Shine
Hi Shine,
Thanks for your input. I would also like to confirm the state of your application. Can you make sure the whether the application is running or has gone to idle by setting breakpoints?
Regards,
Kaushik
Hi,
Thanks for your input. It looks like the pipeline is running as expected from your screenshot. Can you confirm if there is data coming out on the UART data port?
Regards,
Kaushik
Hi Nicky,
You can try to run the srr_ti_design_visualization.m with breakpoints and observe whether the right data has been received from the board (Check data once it has been read and parsed based on TLVs). This can confirm that the application on the board is not at fault and there could be something to do with the GUI.
Regards,
Kaushik
Hi Nicky,
Can you set a breakpoint in the code (run it for a single frame first) and verify that the datapath is working fine? Affirm the reception and processing of new chirps and obtaining point cloud accordingly. Also, with increase in number of ADC samples, can you make sure that the L3 memory section is not overflowing?
Regards,
Kaushik
Basically, I want you to backtrack the flow of the code. For a given frame we would need to check where the datapath has gone for a toss, if at all. The UART data is not given out but has DSS generated the object data as intended? Has the same been passed out to MSS? Has the MmwDemo_interFrameProcessing() completed without any issues? Best way to check this would be to run the demo for a single frame and step through the flow of the code within the SRR_DSS_mmWaveTask.
Regards,
Kaushik
Hi Nicky,
Can you let me know what steps you are taking to debug the same?
As mentioned earlier, it would be simple to run the code for a single frame (refer frameCfg) and step through the code by placing breakpoints.
Regards,
Kaushik