When using the OMAP3503DCBB
We first boot an OMAP in UART boot mode, the OMAP transmits a few ascii characters to tell the loader software on the terminal end when it is ready. We usually see something like a 40W or a 40T depending on the version of the processor.
I have a few on my desk that are putting out the hex codes 04 01 FD which do not translate to any meaningful ascii character.
On the boards that work, the characters 40W are the first printable ascii characters transmitted, but they are not the first data transmitted. Both designs start with the same three characters 04 01 05. The boards that do not work, hang after the 05, the boards that works continues to transmit more data, some of which is the 40W characters. Do you know what would cause the OMAP to stop transmitting any serial data after only three characters? Power is still there, clock is still present.
I can boot from SD Card on both boards.
Any ideas on the cause for this?
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. 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 respect to these materials. 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.