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: IWR1443
In order to check our custom produced IWR1443 boards we measured the clk on clkm, clkp and OSC_CLKOUT pin. The clkp and clkm signal look good to us, but we can not receive any signal from the OSC_CLKOUT pin (A14). Do we need to enable this port by software or is it not functional at all? We use Silicon 3.0.
Typically, OSC_CLKOUT is used for the Cascading configuration in AWR1243, where in master device would provide the clock to slave device on the OSC_CLKOUT pin. Were you able to get the radar operational? i.e. Running out of box demo on the custom hardware?
Specifically, if you want to look at the clock then, In this case you may want to enable MCU_CLKOUT by issuing below API.
Thanks and regards,
CHETHAN KUMAR Y.B.
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 CHETHAN KUMAR Y.B.:
In reply to Marcel Friesch:
Thanks for the confirmation, and glad to hear custom board is working well.
40MHz Clock is available on the OSC_CLKOUT pin, To get this we need to issue Multi-chip master API shown below from the Radar Interface control document.
From application point of view this is used in cascade configuration.
Thank you for advising on how to enable the clk output.
I am uncertain though, whether it is possible to bring an IWR1443 device into Multichip Master mode, since from the screenshots you posted is says clearly that only xx1243 devices can do so?
Would be nice to get a confirmation on this.
We also need the Sync in and Sync out features to trigger frames externally, does this work with IWr1443? And can you give us some Code examples for this?
Thank you very much.
Multi-chip master API is supported on 1243 device family only.
Sync_in signal is used for hardware triggering.
Please refer below documentation from Radar interface control document:
Frame trigger API need to select hardware trigger option instead of software trigger option.
On the SYNC_IN pin you need to follow below timing diagram requirement as specified in the datasheet shown below .
With is option Radar frame trigger would be based on the timings of Sync_in signal. This is supported in IWR1443 device family.
For the Sync_out signal it's used typically in Cascaded application scenario in AWR1243 device families.
For that you need to issue muti-master API then master device sends out Sync_out signal to Slave at frame boundary.
This may not be applicable for IWR1443 device as cascade feature is not supported.
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.