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.
Part Number: AWR1243BOOST
I already have ported the mmwave library to an external processor and run the application examples with success.
Now, I want to use the SPI to gather ADC data.
To this purpose, I have set the intfSel field in rlDevDataPathCfg_t struct to 2 and I expect to receive ADC data through multiple async events with iD RL_DEV_AE_MSS_ADC_DATA_SB.
After having configured the AWR1243 and started the sensor (everything seems to were went well, since all the ACKs have been collected), I receive the first async event with iD RL_DEV_AE_MSS_ADC_DATA_SB. It correctly contains 220bytes od ADC data. But after that, no more async events are received and I'm not able to gather the whole data packet.
I was wondering whether the sensor expects some communication protocol after having send the first data packet. According to the ICD, my expectation is that I should receive all the async events in sequence without the need of replying the sensor.
Thank you in advance for any suggestion.
In reply to Jitendra Gupta:
About Silicon version, it is ES2.0 in both cases.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Paolo Falcone:
I have tried mmWave_example of DFP 184.108.40.206 on AWR1243 ES2.0 where I ran pre-built .exe but the change in mmwaveconfig.txt
intfSel=2; /* For ADC over SPI */
chirpEndIdxFCF=2; /* reduce no. of chirp to total 3 in a frame */
frameCount=1; /* single frame */
And I see multiple Async event for ADC data over SPI (in trace.txt, subID 0x500A, search for '[RD]0x500A' text in this file)
Could you please try above setting change (mmwaveconfig.txt: single frame setting) with existing exe application at your end.
Note- Based on single frame you can find out how much time device takes (time difference in trace.txt from first Async event to last one) to send all async event and give that much frame duration for muli-frame setting.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.