Yes, my explanation in the other forum post is correct. Thanks for reminding me about the other post. I had forgotten about the RSTTIME2 counter being stalled until the external reset source is released. However, there still may be cases where using the WARMRSTn terminal as an input and output can cause problems. The most likely case is when a simple push-button switch is being used as an external reset source. There could be an issue if someone held the push-button long enough for the RSTTIME1 timer to expire and the push-button contacts bounced on release such that the WARMRSTn signal went low enough to generate a short invalid reset pulse to the peripheral devices but not low enough to re-trigger the AM335x reset circuit. In this case, the peripheral device may receive this short invalid reset pulse and enter an unknown state while the AM335x device begins executing code that is not able to communicate with this peripheral device since it is in an unknown state. This may not be a problem if the external source doesn’t generate invalid short reset pulses.
Regards,
Paul
