@vincent3 I don't know how to solve this problem, but if you are willing to take the risk, you can try enabling "Erase all" in the flashing settings, which is False by default. Then tell me if it helped, otherwise we can try to think about something else.
My BL602 dev board from aliexpress has currently a broken WiFi (even after full erase, probably efuse error, I don't know) and I am waiting for new one to arrive.
I have did some more progress on BL602 because I also have a bulb and a led strip (but they are not connected by wires to flasher, they use OTA) and recently I enabled SSDP and DDP drivers.
Hello, I bought a light bulb that came with BL602 managed to flash with latest firmware (.517) however after flashing, disconnecting boot and repowering the chip, there is no access point, so i opened the UART, and it seems to be in a loop of some sort, also reflashed useing the erase flash TRUE option and same thing.
My chip is the BL-M5 V1.2
Please post full log and try the firmware 1.15.511.
I am currently on 1.15.511 and it seems to work fine:
Also, if you have a BL602 bulb, please consider posting a teardown in separate topic. Adding BL602 device teardowns is very helpful, we don't have much of them.
https://openbekeniot.github.io/webapp/devicesList.html
Added after 5 [minutes]:
EDIT: I just got a suggestion from @Zain00 , are you powering it from a reliable power supply? maybe it boot loops because you try to power it from USB to ttl adapter that can't provide enough current.
So it works now? Great.
Well, to be honest, I think we've been repeating that on our Youtube channel several times already. Use good power supply, preferably external LDO 3.3V and power it from good 5V, so it gives a stable 3.3V for WiFi module. Something like AMS1117 3.3 will do great, although we are using TC1264-3.3.
Today I got a switch with DT-BL02, I was not successful at flashing this module.
With BLDevCube version: 1.4.8, I get {"ErrorCode": "003D","ErrorMsg":"BFLB FLASH MATCH TYPE FAIL"}
With version: 1.8.3 I can flash the chip but then no AP appears and no RX/TX reading from the BLDevCube.
You are 100% right. It is all about stable 3.3V. My BL602 (socket in my case) doesn't boot on USB2TTL 5Vto3,3V stabilizer (boot loop) but works great powered by an internal 230V AC-DC power supply.
BLISP (Bouffalo Labs ISP tool & library)
This is an open source tool and library for flashing Bouffalo RISC-V MCUs.
NOTE: Library API and blisp tool cli arguments are not stable yet.
Supported MCUs
bl60x - BL602 / BL604 / TG7100C / LF686 / LF688
bl70x - BL702 / BL704 / BL706
bl70xl - BL702L / BL704L
bl606p - BL606P
bl61x - BL616 / BL618
bl808 - BL808
Supported OS
Windows
Linux
MacOS
FreeBSD
How to update Pinecil V2
Check out the wiki page.
Building from code
Clone repository
If you have not cloned this repository locally; clone the git repository locally by running
git clone --recursive https://github.com/pine64/blisp.git
cd blisp
git submodule update --init --recursive
Build the library and command line utility
For building blisp command line tool, use following commands:
mkdir build && cd build
cmake -DBLISP_BUILD_CLI=ON ..
cmake --build .
Need more build details? See here.
Usage
For BL70X, BL61X, BL808 and BL606P, connected via USB, you can use following command, which will auto-detect serial port:
.\blisp.exe write --chip=bl70x --reset .\name_of_firmware.bin
or
.\blisp.exe write -c bl70x --reset .\name_of_firmware.bin
For BL60X, you need to specify also the serial port path:
blisp write --chip bl60x --reset -p /dev/ttyUSB0 name_of_firmware.bin
It suggests that LF686 may be a version of BL602, have you tried programming that?
I'm a little bit confused about post #252, can't decipher if that user flashed the LF686 with the BL602 firmware or not. but later i can give it a try and see if i can flash it!
Wow that is a very good news, can you submit a device teardown as a separate article so we can include this in our online templates list?
Submit the IoT device teardown/review/guide/article and get a free SD card What do you need for domoticz? It has been discussed few times already but I am not sure if it's fully there. Domoticz has this strange MQTT format.
Would you be able to tell me exactly what the relay should publish on change and what should listen to so it works with Domoticz? With examples? But I am not asking for a link to docs with a 50 options, just a basic, most minimal, possible MQTT format that would help you to get it running with domoticz. The most basic version.
Sorry for the late reply, I don't know if this helps but here's the log from the console of a tasmota (ESP) RGB controller output from the commandos ON/OFF (issued from domoticz):
OFF domoticz
10:48:43 MQT: stat/Leds_Desktop/RESULT = {"POWER":"OFF"}
I also received such errors, it helped - I unpacked the packed program from git into a file with a short name, e.g. D:\1\ - and then, after properly preparing the links for the batch, it worked without any problems. version 1.4.8 works. Originally, I unpacked the program: D:\BL602 IoT SDK and the DT-BL10 WiFi and BLE RISC-V development board\OpenBL602-master\ here there was a program with subdirectories. Maybe it will help you. 73 Best regards
@p.kaczmarek2 I think there is a problem with the latest BL602 OTA update. After updating the device, it stopped working and I had to reflash it with USB.
I had one device pricked, and I get this error when I try to flash it
{"ErrorCode": "0003","ErrorMsg":"BFLB LOAD HELP BIN FAIL"}
{"ErrorCode": "0050","ErrorMsg":"BFLB IMG LOAD SHAKEHAND FAIL"}
Hmm I just had a report on Github also saying that OTA breaks after 609:
The user says that he can easily recover device via UART.
I can't see any bad changes in code around 609, problem might be related to flash binary size.
So far I have disabled few unused drivers in BL602 and reduced flash memory usage by 5KB, we'll check soon if it works. I am unable to do so yet due to the continuous lack of dev board (my one was bricked by MAC change attempt about a week or two ago).
Are you sure that UART flashing is not working for you? Have you done boot pull trick?
@Zain00 , the reported OTA issue has been solved. Tests have shown that the binary size was too big for BL602 OTA system.
I will be reducing binary size further soon.
I've just received two devices with LF686. I've uploaded software for BL602 according to instruction (twice, first download attempt failed). It seems that everything works fine on first device. I mean MQTT reports changes, led dimms as expected. The only strange thing was IP in AP mode it was 192.168.169.1 ... maybe I did something wrong. Fortunately IP was reported on serial port.
Edit :
Second device went even easier. After connecting to network browser opened page http://www.msftconnecttest.com/ with device so could easy configure my wifi. So far both devices works well.
BTW . My version looks exactly the same , PCB is perfectly the same as BL version , only processor is different.
Hello,
it would seem that new Magic Homes from china are coming with BL602 relabeled as LF686 (LF686C20).
You can google documentation about this processor version under "BF2 Data sheet (LF688/LF686)" .
I've been able to successfully flash it with OpenBeken without any problems.
@p.kaczmarek2 Thank you for this great work to get rid of the ewelink cloud stuff. They almost went to the trashcan.
I just stepped over the videos on youtube and with the help of the forum I was able to flash all of my fake-sonoff SWITCH-WF.
The only thing I experienced was that the resistor (3,3V-LOG pad) used to get it into boot mode. It worked only on the first device, all other did not enter boot mode. Measuring the voltage at the pin showed that it was in an undefined logical area when using 10k and had to be smaller, 1k did the job. The configuration for this device 1-LED, 5-BTN, 22-REL.
Works like a charm!!
Hello, my name is Paco, I'm from Spain and this is my first message in this forum
This project and this topic is very interesting for me.
I bought a RGB LED strip with IR remote control and WiFi like this in AliExpress ( Link )
I expected it to be compatible with Magic Home, to be able to integrate it into Home Assistant, but the suggested app to handle it was TechLife Pro, which cannot be integrated into Home Assistant
II thought about flashing Tasmota for it, but it's not compatible either
I disassembled the controller and found that it has BL602C20 chip
I finally found this thread, which has the instructions to get it able to flash and integrate it into Home Assistant locally
I have read the whole thread, but I haven't quite found the specific instructions to be able to flash the device, but on the OpenBK7231T_App github page there is a lot of information to get started
My first step was to follow the instructions in the Russian guide BL602 RGB (Link)
My device is not exactly the same, but it is very similar, and I followed the proposed steps:
1.- Solder wires to the exposed pins (VCC I08 RX TX GND) There is another pin labeled RES, which must be to RESET the board. I have not used it. I have assumed that the I08 pin corresponds to the Boot PIN, since I have read that the GPI08 must be activated to put the chip in flashing mode
2.- Connect the device to a USB-TTL adapter with a resistor to activate the flashing mode. I have followed this scheme:
3.- I downloaded the components suggested in that guide (BL602.zip, which includes the flashing program BLDevCube.exe) and the firmware OpenBL602_1.15-406.bin
4.- Connect the TTL to my Windows PC and run the BLDevCube.exe utility, replacing the files with those corresponding to the locations on my hard drive and select the COM6 port that appeared to connect the USB-TTL
5.- When clicking Create and Download, the following error message appears ERROR : {"ErrorCode":"0069","ErrorMsg":"BFLB FLASH ID NOS SUPPORT"}
I tried again with the last firmware OpenBL602_1.17.29.bin with the same result
[input_path]
pt_bin_input = "C:\\...\\partition\\partition_cfg_2M.toml"
boot2_bin_input = "C:\\...\builtin_imgs\\blsp_boot2.bin"
cfg2_bin_input = "C:\\...\\OpenBL602_1.17.29.bin"
meida_bin_input = ""
romfs_dir_input = ""
mfg_bin_input = ""
img_bin_input = ""
[20:39:14.957] - ========= Interface is Uart =========
[20:39:14.969] - eflash loader bin is eflash_loader_40m.bin
[20:39:14.972] - ========= chip flash id: ef4015 =========
[20:39:14.974] - flash_id:ef4015 do not support
[20:39:14.976] - ========= chip flash id: ef4015 =========
[20:39:14.977] - flash_id:ef4015 do not support
[20:39:14.978] - Please check your partition table file
I think the problem could be that the chip is BL602C20, and that it is not exactly the same as the BL602L20 chips in other devices. The partition table file
I have also studied Youtube tutorials "Magic Home BL602 RGB LED Strip programming with OpenBeken - new Tasmota/Esphome port style firmware" and "How to flash new Sonoff BL602 bulb B05-BL-A60 - 100% free from cloud guide and BP5758 configuration" , but I have not found a solution or that I have done something wrong
Does anyone have any clue what could happen?
If I manage to solve it, I will document it and write a teardown. Thanks in advance
Hello, I haven't checked myself, but I've seen comments in this thread saying that it can be flashed with a newer version of BLDevCube.exe . I am not sure yet. Maybe someone like @Zain00 can know more about it.
Btw you can also do a firmware read (backup) first with BLDevCube.exe as well. Just in case that something goes wrong.
I have tried flashing the chip with this new version and the same files as suggested in the Russian guide, except OpenBL602_1.17.29.bin and it seems to have worked, no errors
Hey guys!
Just hooked up 3 of my Magic Home LED controllers with OpenBeken and it works flawlessly for a little bit using MQTT. However, after around 50-55 minutes, all three of my controllers become unresponsive at the same time (if powered up at the same time...), and are inaccessible with MQTT and IP. The LEDs stay on, so I'm assuming something with my WiFi / MQTT configuration might be off. The only logs with ALL selected only show this repeating until crash:
Can somebody share working connection diagram for flashing Magic Home LED Controller based on BL602 chip? I tried to use Arduino UNO without Atmega IC of course as flashing tool.
Connection:
Arduino site ---> LED controller site
5V ---> main VCC of LED controller (simply power up device)
GND ---> GND
TX ---> TX (this is not an error because it works while flashing esp8266)
RX ---> RX (this is not an error because it works while flashing esp8266)
The discussion revolves around the development and integration of firmware for devices based on the BL602 chip, particularly focusing on flashing procedures, MQTT connectivity, and Home Assistant integration. Users share their experiences with various models, including Magic Home LED controllers and Sonoff devices, detailing successful flashing processes, issues with WiFi connectivity, and the need for stable power supplies. The conversation also touches on the implementation of features like OTA updates, Alexa integration, and the challenges faced with different firmware versions. Users report on the behavior of their devices post-flashing, including boot loops and MAC address duplication issues, while seeking solutions and sharing troubleshooting tips. Summary generated by the language model.
