The current hardware is a custom carrier board based for colibri interfaces plugged with a Colibri iMX6ULL 512MB Wi-Fi / Bluetooth V1.1A.
Our application just use a several GPIOs that were marked as “default colibri function” but in the SoM seems to be reused -internally- o mixed with some ENET2 pins and exposed to the pinout on the module, so we can’t use some GPIOs on i.MX6ULL carrier boards because the assign signal is not clearly specified in the General Colibri Design Guide and the datasheet for the colibri SoM itselt just explicity the signal as “non standard funcion”, related with ENET2 … but it seems that it is related with ENET2 and ENET1.
The main issue resides on 184 pin, GPIO1_IO07, this pin boot in ALT5 state: GPIO1.IO07. Disabling the ENET2 interface (fully, we don’t use any part or pin of those) force the ENET1 interface to go down, because the 184pin is shared with the external ETH2 pinout, hence, you can’t use this pin without disabling both ethernet interfaces. Or … just don’t use at all because you only can use if you planned to put an ethernet 2nd interface.
The main issue is that somehow, ENET1 and ENET2 shared some lines with a few pins, makeing them unsable for generic uses.
I just want a confirmation about this issue, and if it is true, move to another GPIOs mappings… “problematic” with “shared” signals.