-
Notifications
You must be signed in to change notification settings - Fork 409
Description
Hello,
I am experiencing an issue with the OpenBeken firmware for Mini Smart Switch WiFi T1-2S-NL (the BK7238 chip). After changing the MAC address via the web interface, the device fails to create its Wi-Fi access point on the next boot.
Steps to Reproduce:
- Flash a clean OpenBK7238_QIO_1.18.172.bin (or other version) onto a BK7238-based device (e.g., a relay).
- The device boots successfully and creates its Wi-Fi AP. Connection and web interface work correctly.
- Navigate to the Network or System settings in the web interface.
- Change the MAC address to a new, locally administered unicast address (e.g., CA:47:8C:42:88:01).
- Save the settings. The device reboots.
- After reboot, the Wi-Fi access point does not appear. The device becomes unreachable over Wi-Fi.
Expected behavior: The device should reboot with the new MAC address and create its Wi-Fi access point as usual.
Actual behavior: The Wi-Fi interface fails to initialize.The device is bricked from a network perspective until it is reflashed. Through UART, I can see the bootloader looping, attempting to boot unsuccessfully (go os_addr(0x10000)..........), indicating a problem occurring very early in the firmware initialization, likely related to Wi-Fi/RF calibration or MAC validation.
Workaround: The only way to recover the device is to perform a full chip erase and reflash the original firmware image.Changing the MAC address via the web interface is not a viable option.
Additional context:
· The original MAC address that works is C8:47:8C:42:88:48.
· The new MAC address I tried (which causes the failure) is CA:47:8C:42:88:01.
· I have confirmed that the new MAC address is a valid locally administered unicast address.
· The issue is reproducible 100% of the time.
· This prevents setting up multiple devices on the same network without MAC conflicts.
Thank you for your work on this project. I hope this issue can be resolved.