Hi Robert, By the way, I'm curious why don't you just use 00:00:00:00:00:00 as a MAC instead? If you patch wl1271-nvs.bin and replace 'deadbeef' with 00:.., TI WLAN driver will attempt to read wl1271-nvs.bin, and if '00:00....' is stored, it will automatically use wl18xx built-in MAC, which is unique for every wireless chip produced by TI. Of course, this will only work for wl18xx chips, but most wireless-capable Beaglebones come with wl18xx.
In other words, if you patch wl1271-nvs.bin and replace 'deadbeef' with '00:00:00..', or completely remove wl1271-nvs.bin, no other patches or scripts will be required, and WLAN MAC will be assigned automatically. On Wednesday, 24 January 2018 20:29:57 UTC+3, RobertCNelson wrote: > > On Wed, Jan 24, 2018 at 11:20 AM, Dan Tian <[email protected] > <javascript:>> wrote: > > Hi, > > I am trying to make identical embedded systems in production with an SD > > card, the SD card image is flashed from a working BBBW board. The issue > I > > have is the newly programmed BBBW would have the same wlan0 mac/ether > > address as the original board, as opposed to their own MAC address one > would > > expect. With all the programmed systems having the same interface mac > > address they will get the same IP from a DHCP server, which is obviously > not > > acceptable. > > > > I am not using /etc/network/interfaces file to configure wlan0, I assume > the > > interface is configured and brought up by connman service. I am thinking > > there might be two ways to resolve this: > > 1) find out how the interface mac address is assigned at startup and > > hopefully there is a way to fix it there. > > 2) manually re-assign the correct wlan0 mac address with a script at > > startup, but not sure what's the best approach here either. > > For the BBBW, by default we grab cpsw0 for wlan0.. > > > https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0#L210 > > > set_wlan_0_mac_from_cpsw_0: > > > https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0#L132 > > > set_wlan_0_mac: > > > https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0#L57 > > > In set_wlan_0_mac, it looks ugly*, as we actually "patch" the firmware > ( /lib/firmware/ti-connectivity/wl1271-nvs.bin ), but then make sure > when updated it's stored in the initramfs. > > TI has a crazier tool that required even more stuff running, then the > 6 dd commands we use.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/44b779a1-0f08-43c9-b537-c91fbba8ed8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
