[Solved] BL602/OpenBL602 - How To Change MAC Address with BLDevCube? MAC Conflict Fix

Hi,

I've two BL602 (SM-028_v1.3) Smart Sockets with same MAC Adress, I flashed OpenBK FW 1.17.391 with BL Dev Cube. My Router assigned same IP to Smart Socket. I have to unplug one of Smart socket in order to get it working.
I changed MAC Address within OpenBK Configuration, but it has no affect. The Open BK Configuration do have the updated MAC but I dont think it is saving to flash. Because the router still showing original MAC.
Then I changed IP Adress within OpenBK Configuration, it also has no affect. It still doing DHCP with same IP assigned.

Any one know I can use BL Dev Cube Application to modify MAC Address from BL602 Flash.

Thanks,

I've seen this problem once and I've tried to do a MAC change on the firmware but so far I've failed. I remember that I tried an efuse approach and it somehow bricked my only BL602 dev board, so OpenBeken interface is not able to change MAC on this platform yet.

I don't know yet how to change MAC address correctly on Bl602, but maybe we could investigate this issue a bit more. Was the MAC the same before you flashed? Which flashing tool and settings did you use? Do you have a backup of original firmware?

I've ordered two SMART sockets. This is my 1st BL602 that I received. I've been using bk7231 with openbk. As soon as I opened the Smart Socket, I saw it has BL602. I didn't try the app to pair but researched around how to program BL602 with OpenBK and found Bouffalo Lab Dev Cub utility is able to flash it. I'm not sure if the MAC got changed after OpenBK or not. But I tried the backup flash and didn't figure out how to do it with the utility. So, I just flashed the openbk and I was happy to see it working. Then I flashed the 2nd Smart Socket and that's when I saw both Sockets have the same MAC. The OpenBK Web Link in the flash tab does have a dump of the full 2MB. But it started dumping and then the MCU hangs after. If we can dump the whole flash, maybe we can hexedit and search for the MAC within the flash and flash it back. But I'm not sure how to use the utility to do the dump. If you know, please let me know. I'm getting more SMART sockets and will try to pair them with the app before openbk. So, I can tell you if the MAC gets changed.

I have never done the full flash read and write back procedure for BL602, but as far as I heard, there is option to read if you enable "advanced" tab in BLDevCube.

How your MAC address looks like? Is it something ending with 00 00 00?

I don't know how MAC is handled on BL602, we only support MAC change on BK7231.

Just received another Smart Socket. Just do a normal installation with eWeLink App. After pairing the device to my network.

Bouffalolab_BL602-0941c5 192.168.1.80 AC:D8:29:09:41:C5 <= original FW (3rd Smart Socket)
Bouffalolab_BL602-000000 192.168.1.240 C0:50:43:C9:00:01 <= OpenBK (1st & 2nd Smart Sockets)

1st 3 Octets supposed to be AC:D8:29 but with OpenBK it is C0:50:43
https://maclookup.app/macaddress/ACD829/mac-address-details <= AC:D829 is Bouffalo Lab
Not able to find any MAC info for C0:50:43 ...

I suspected the OpenBK is unable to retrieve the MAC and that is why it got named -00000, it is using the default MAC because it is unable to get the MAC from the device. That is probably why for my 1st and 2nd Smart Sockets, after flashing OpenBK, both have the same exact MAC.

Did you find a solution to change MAC to original or just to something other than OpenBeken default?

I bought two Elivco BSD33 and after flashing, both got C0:50:43:C9:00:01.

I researched the BL602 flashing procedure again, and it seems that the way I flash the BL602 may not be 100% correct. So, I followed a YouTube tutorial using BL-DEV.
Now, all my WiFi sockets have their own MAC addresses

Which youtube tutorial? How did you fix MAC address issue?

>>20920018
This solution resolved my problems both sockets get their own MAC address. Thanks sonnyk88

YouTube tutorial link: https://www.youtube.com/watch?v=bs0ylC6xRs0&t=201s @3:23. Actually, YouTube from elektroda.com :)

I think BL602 firmware does not have a problem with the MAC address. Because of how I've flashed the BL602 originally. I wasn't using all files. Partition table (toml), firmware (bin), boot2 (bin), and dts (dts). Because I saw a YouTube tutorial about the settings (4 items). I filled in all four items. After flashing BL602, the original MAC showed up. :)

This is what I used originally, which caused the MAC issue.


But I still couldn't figure out how to dump the whole flash from BL602 using the advanced option.

So basically whole issue happens if you don't follow our tutorial? Well, no wonder that I have never experienced that!

What do you have under "show advanced options" on your screenshot? Which option exactly breaks MAC?

I didn't change anything in the Advanced tab. Everything is default.

>>20920379
Hi Mad_Maxs, You're welcome. I'm just learning about BL602. I'm glad you and I made the same mistake and that gave others a heads up. I hope the next person didn't make our mistake. And pay attention to the YouTube tutorial that elektoda.com provided in detail, step by step. Not to jump to flashing the BL602 without going through the entire YouTube tutorial.

Good morning. I came across this thread because I experienced the same issue after changing the firmware on my switches with BL602. They all get the same MAC address, which causes network conflicts.

I saw @sonnyk88 response showing the flashing process, but @p.kaczmarek2, my question is... If they are already flashed, is it possible to flash them again in a way that assigns them different MAC addresses?

PD: @p.kaczmarek2 I'm glad to see you again

Added after 7 [hours] 54 [minutes]:

>>21494307 I answer myself. Reflashing with the 'dts' filled solved the problem

Oh, I wasn't paying attention and I got into the same situation. Two sockets originally eWeLink RMC021s BL602L20. Flash and both same MAC address C0:50:43:C9:00:01. Problems with assigning IP address.
I checked the video again and the problem is that I forgot to mark boot2 and dts.
After re-flashing, the socket will get the original MAC address and can set a unique IP.
Thank you very much
Radek