Part Number: IWR1443
Working on a custom board using IWR1443. I can flash IWR1443 successfully with the binary image from SDK_2.1.04:
Commands can be sent with 'Done' acknowledgement on the 'User' UART port. After the 'sensorStart' cli command, only a short burst of data can be observed at the 'Data' UART port at the beginning and then no more data is received. The demo bin supposes to provide a continuous data stream of the detected object coordinates and/or the heatmap data and the data can be used by mmWave Visualizer demo software. All the supply voltages including the internal ones of the chip were checked correct. Any suggestion on why no data is obtained?
Could you please what is the difference between the IWR1443BOOST EVM and custom EVM. If possible share the schematic and layout for the review.
Do you see NERROR signal is being asserted?
Also perform below schematic and layout checklist review (Review the schematic, Layout and Bringup tabs).
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.:
The custom EVM is basically derived from the IWR1443BOOST EVM and so they are very similar. The schematic in Eagle layout tool is attached. The PMIC switching regulator is replaced by a few linear LDOs (not yet updated on the schematic). All the regulators' output voltages are checked correct. The internal generated voltage i.e. bandgap, 1.4V for PLL and synth, vout_pa are all ok.The clock frequency is measured as 40MHz + 20ppm. NERROR signal is always high as measured. So the hardware seems correct. The XDS chip is taken out and the custom EVM is communicated by two UART-USB bridges to a PC by Python code. The Python output log is attached showing the CLI commands used and the acknowledgements from IWR1443. Everything looks ok but there is still no output coming out of the data com port. But with the same python code used to drive the IWR1443BOOST EVM, valid object data can be obtained from the data com port.
Just wonder if we need to compile the source files and flash the generated bin file onto the chip instead of using the pre-built bin file supplied by the SDK.
Thanks a lot,
Henryiwr1443 board Python output log.txtLW-RD77G-AD-V08-TI.schEVM
In reply to Henry Lau:
Just reviewed your checklist and found that pin B1 and D15 on the custom EVM are open. Should they be shorted to ground? Also, B15 is shorted to ground. Should it be open?
Could you please share the pdf file of the schematic? B1, D15 and B15 are used only during the cascading operation, they are not the responsible for this problem.
If the power supply are changed then we need to see power supply stable before the SOP assertion and NRESET release sequencing is adhered to as per datasheet requirements, if it's not done then there is possibility of device entering into wrong boot mode and output may not be coming from the sensor
Also could you please update the schematic representation of what is currently being on the board (PMIC change to LDO etc)?
The schematic as an image file is attached for your preview. The new schematic with the PMIC being replaced by linear LDO's is being prepared and will be sent out once available. The chip should be in the functional mode as it can provide acknowledgment message of 'Done' after CLI commands are sent to the chip (please see the Python output log file as attached). I will check the voltages after power up to make sure they are all ok.5811.iwr1443 board Python output log.txt
Thank you for sharing the schematic, could you please post the pdf file? It's difficult to review with image file.
Here you go. Do you know the function of pin WARM_RESET? I know it can be either input or output. Also, for NERROR_IN, is it active low meaning fault input from an external device?
Thank you, We may need a week to review the schematic and provide you the feedback.
For the Warm reset you could refer to Technical reference manual for more details.
I have added description table from TRM for your reference.
For NERROR_IN your understanding is correct, It is also active low signal to propagate any fault occurring from the other safety sub-system such as PMIC or processor which would be propagated indicating a fault in the system.
CHETHAN KUMAR Y.B.
Reposting the image as table did not come correct in the above post...
Really appreciate for the information. Looking forward to receiving your feedback on the schematic review. The sooner the better.
Another question: there is no output from MCU_CLKOUT pin. Is it supposed to have no output for SDK_2.1.04?
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.