PaulStoffregen
Well-known member
Looked at the alternate functions on all 12 signals which connect to the ethernet chip. None of them have I2C functionality.
My understanding of the ethernet chip is it's supposed to remain in a low power mode until configured and (probably) can't do much of anything until it hears the 50 MHz clock signal.
But just because I can't imagine any plausible cause doesn't mean it's not a real problem. If further testing on bguthik's shows this really is a case of having the ethernet chip missing causes a failure with Wire2... and if I get the chip, I'll build one of those breakboards and test it here.
My understanding of the ethernet chip is it's supposed to remain in a low power mode until configured and (probably) can't do much of anything until it hears the 50 MHz clock signal.
But just because I can't imagine any plausible cause doesn't mean it's not a real problem. If further testing on bguthik's shows this really is a case of having the ethernet chip missing causes a failure with Wire2... and if I get the chip, I'll build one of those breakboards and test it here.