Hello > Interesting. I thought I was imagining things because after running saveenv > and rebooting, the MAC address seemed to revert back to 02:44:01:02:00:00. I > thought I must have forgotten to run saveenv, but now I wonder if I had run > saveenv but that at least some of the i2c stuff happened to work for that > boot and so the old MAC address reappeared. Does that sound plausible?
I believe the derived mac address only ever gets used if nothing else is available. If that is the case, then what what you saw would be consistent with a forgotten saveenv. You can check the routine doing this in uboot in board/kat/roach2/roach2.c, should be on github > Is there anything I could/should look for when trying to fix the i2c problem? > If I wanted to try reading the i2c eeprom from u-boot, which i2c address (and > bus?) would I use? Is there an i2c address map anywhere? uboot has a i2c detection routine which should list visible i2c devices. regards marc
