Hello,
We have a custom carrier using a LAN9221 and a USB device connected to the DM3730 Torpedo. We
were noticing occasional failures on the LAN9221 and tracked it down to the board type/machine
type being assigned as per console logs. Most of the time, the board is set as DM37xx Torpedo,
but in about 15% of boot-ups, the board is set as DM37xx SOM LV. I believe this is dynamically
set from omap3logic.c, and is supposed to change if there is a pull-down on HSUSB0_DATA5. Are
any of the pins on the connector going to impact the results of that omap3logic pin check?
Additionally, has anyone seen a situation where a SOM incorrectly self-identifies?
Thank you,
Stephen