Hi Artur,
Sure, I added some content to the discussion a while back but go no further feedback. I was continuing the discussion thru email with Enrique.
I have a couple of concerns:
1. On the 1st rev of the board the LAN IO configuration was set to 3.3V.
The imx6 NVCC_ENET was also set to 3.3V.
But Ethernet did not work. I probed the signals from the imx6 and they were 2.5V. I change the GPIO configuration of the LAN to 2.5V and Ethernet has been working fine since that time.
But with NVCC_ENET at 3.3V I shouldn’t have had to use 2.5V.
I am using the following pins for the Ethernet interface: U20, W20, V21, W21,W22,U21,V20,V23,R2,W23,R4. All of these use NVCC_ENET or NVCC_GPIO (both configured to 3.3V)
Basically it is the exact interface as is in chapter 12, using the RMII interface from the hardware guide. In this document they don’t state if the IO is 3.3 or something else.
On the P2 boards I used the same setup as was in the P1, the LAN VDDIO used VDDHIGH_CAP. Ethernet works fine.
I then had 3 boards fail to boot. In troubleshooting I found that the 2.5V used to power NVCC_LVDS2P5 (required for DRAM) was not at 2.5V, measured between 1 and 2 volts depending on the board.
This 2.5V was sources from the PMIC, not VDDHIGH_CAP.
I reworked a board so that NVCC_LVDS2P5 came from VDDHIGH_CAP and the board boot properly one time. On the 2nd boot if failed and VDDHIGH_CAP no longer measured 2.5V.
So my question would be if the imx6 LAN digital signals to the LAN are at 3.3V levels and the LAN is expecting 2.5V could this pass through and damage both the PMIC 2.5V output and the VDDHIGH_CAP?
Also, for the Ethernet pins I am using can you confirm that 3.3V is correct?
2. I use a super-cap instead of a coin cell to power the LICELL input of the PMIC which in turn power VDD_SNVS_IN of the imx6. I noticed the super-cap charges slow enough that it is not the 1st power rail up as required.
I have reworked to correct this but is it possible this could have cause three boards to fail for the 2.5V as discussed above. On the next rev I am tying VDD_SNVS_IN to VDDHIGH_IN.
Thanks
Steve