We have an OMAP35xEVM with the OMAP3530 ES2.1. When we power-up this EVM with EMU0 pulled low, the processor comes out of reset in a halted state. Through JTAG we are able to see that the processor is waiting at the start of boot code for a go comand from the JTAG emulator.
We also have a custom platform which uses the OMAP3503 ES3.1. When we power-up this board with EMU0 pulled low, the processor does not come out of reset in a halted state. The boot code appears to be running until halted by the JTAG emulator.
Our SYS_BOOT pins are configured the same as the EVM. Is it possible that there is another input to the processor that controls this behaviour?
Is there a difference in the processors or the silicon revisions that would account for the different behaviour?