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.
within my (bare metal) application it happens from time to time the Ethernet PHY can't be initialised. This can be fixed by toggling the power, on next boot everything works fine. This happens rarely so that I haven't been able to track down this problem until now.
So I tried to workaround this by a reboot via watchdog - but this leads to an endles loop, the PHY comes back in same unusable state as before.
So it seems rebooting via watchdog is "not cold enough" to solve this issue.
So my question: are there any other possibilities to have a more hard/cold restart of AM3358 CPU?
Can you give information what is the PHY part number and what is your hardware connection of the PHY reset signal?
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 Biser Gatchev-XID:
it is a BeagleBone Black which comes with an LAN8710A, reset is connected to NRESET_INOUT of AM3358
In reply to qxc:
This is a known issue. The problem is that the AM335X nRESET_INOUT (or warm reset) is released at approximately the moment that the PHY latches internally it's bootstrap resistors. Once in a while this happens too soon and the PHY doesn't come out of reset correctly. This can be avoided if the PHY reset is tied to a processor GPIO (it's important that the GPIO stays in low state during reset and at reset release time).
Biser Gatchev-XIDThis can be avoided if the PHY reset is tied to a processor GPIO (it's important that the GPIO stays in low state during reset and at reset release time).
That's no option for me since the layout and connections of BeagleBone Black are fixed and I do not have any influence to them. So...are there any software workarounds? Something that is similar to a manual power cycle?
You can consider using the PMIC_POWER_EN signal to turn off the PMIC. See Table 20-62 in the AM335X TRM Rev. J for details.
OK, but how is it turned back on without the need to let the user cycle the power? It should re-power automatically, elsewhere it would be the same like cold reboot done by user.
There is no solution for this on the BB Black you are using.
Part Number: BEAGLEBK
I've come up with a software only workaround that can make sure a BBB will always come up with a working Ethernet port - although it can take a few minutes and require several automatic internal power cycles.
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.