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.
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 Anand Gadiyar:
While you're checking whether this feature is supported and how it works, I've noticed a couple of things that might be of interest.
To try to overcome the problem at point 3. we tried to use an external trigger: So we wait the ack to the rlSensorStart (which is immediate for human beings clocking...) and then we start the transmission. However, also in this case we didin't succed. So somethings is still missing.
Hope you're finding a solution.
In reply to Paolo Falcone:
Please check TI mmWave FAQs before posting a new query
Use your search engine to look for some similar threads as shown below:
"site e2e.ti.com <Your query>"
In reply to Jitendra Gupta:
Thanks for your reply.
I didn't understand what "Si version" actually means and where to retrieve this information.
However, I got this answer from the chip after poweron the device.
RF Version [ 2. 0. 0.15] MSS version [ 1.10. 0.23] mmWaveLink version [ 1. 0. 0. 0]
For the boards I've tested up to now, the content of "Die id" field is: Lot:6000001/Wafer:1/DevX:30/DevY:18.
We have also a second set of boards, whose "Die id" is: Lot:7120004/Wafer:5/DevX:4/DevY:59.
Can you please explain me the difference among them (if any) and clarify whether I need to take some further actions in using the AWR1243 device from an external host? (e.g., dfp version, mss and bss version, etc.)
Thank you in advance,
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.