Thanks Aneesh but the decompiled dts file has no mention of the exact MAC address for eth0, but just to read from the eeprom from what I can gather. Plus an md5sum of the dtb file on the sdimg from Ettus is the same checksum as an e310 that has booted.
On Fri, Nov 27, 2020 at 1:40 PM Philip Balister <[email protected]> wrote: > On 11/27/20 1:34 PM, aneesh patel via USRP-users wrote: > > Hi Andrew, > > The MAC may be in the devicetree blobs in the boot area of the SD image. > > You will need dtcedit to decompile, edit, and recompile as needed. > > I don't think so, since the first time the card boots it does read from > the i2c eeprom. > > I'm guessing u-boot sets the ethaddr env var and saves it in the > environment, but I forget where that might be saved. Need to review the > u-boot configuration for setting about the u-boot env (maybe getting > saved to the sd card). > > Anyone from Ettus paying attention? This is a pretty serious problem for > people copying cards and using them in different units. The correct > behavior is follow the MAC address programmed into the i2c eeprom. > > Philip > > > Amp > > > > Sent from Yahoo Mail on Android > > > > On Fri, Nov 27, 2020 at 1:23 PM, Andrew Payne via USRP-users< > [email protected]> wrote: > _______________________________________________ > > USRP-users mailing list > > [email protected] > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > > > > > _______________________________________________ > > USRP-users mailing list > > [email protected] > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > >
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
