What kind of error?
You cannot do flashing and have UART open at the same time. COM ports can't be shared that way. Only one application can use port com at the time
No, logs can be taken without BLDevCube in an application like RealTerm, choose select COM port and proper baud. On BL602, the same COM port is used for programming and for log output. This is different from BK7231 where there are two UART port, UART1 used for flashing (and TuyaMCU etc etc) and UART2 for log output
What? Impossible, you should get at least a basic log output that happens before OpenBL602 is loaded.
Are you sure? Can you post a screenshot? Maybe your device is all the time in boot mode?
Wait, maybe... just maybe... there is some kind of EN pin on the board that needs to be put to VDD with 10k resistor for module to run? Maybe this module is different from what I experienced in the past...
Please show photo of the setup.
I might have that module somewhere, I haven't yet tried to play around with it, I must look for that, but I have lots of stuff and I don't remember where I've put it.
Now I know what's wrong. Posting screenshots is very helpful.
Firstly, the debug log output of BL602 is at 2000000 baud rate, not the 9600 you have.
Secondly, the debug log output is ASCII text. There is no need to display it as HEX. It's a human-readable format.
I started to use software OpenBL602 but I have the same issue like the ionoleinic - everything was wrote to the conrtoller BL-200 without errors but still I cannot see the hotspot from module - do you have any idea where is the problem?
If there will be needed something copied from the BL-200 I have not used two pieces so I could download something if you give me advices how to proceed that. I check the logs and I think this is the main issue but I do not know how to solve it : ):
Flashed BL602 with whole IoT device backup from your repo: Bl602Lamp-4th.bin.bak - single download option
Boot, paired with Magic Home - mac in IP scan and in boot log:
Code: Text
Log in, to see the code
flashed to OBK with standard BLDC selections. dts file with default macs
Code: Text
Log in, to see the code
AP broadcast name includes original mac (presumably of the dev board as it's always been - 192.168.1.150 I think is always the dev board)
STA mac is the same as seen in GUI and boot logs.
So, in summary, without further fiddling, the mac in the dts file does not seem to have an effect.
thank you for idea with mflasher but it is too late - I uploaded the chip so I have not possibility to come back to the first state. But many thanks for solution wit your backup!
I added also DTS but withouth any good resaults. Also there was not possiblity to wrote the data with partition_cfg_2M - I used 1 M and the software was able to upload the OpenBL_602. But still hostspot is not established. By 2M I had the error 45.
For now I give up to try to do that because it take for me a lot of time : ). I found easier way on ESP and it is more comfortable.
The discussion revolves around the CoRui TUYA WiFi Smart LED Light Bulb 9W E27 RGBCW, which utilizes the BK7231N chip. Users share experiences regarding purchasing, unboxing, and flashing firmware using tuya-cloudcutter. Some users report issues with compatibility, particularly with different modules like BL-200 and BL602, and the challenges faced when attempting to flash firmware or connect to apps. The conversation includes technical details about pin assignments, PWM configurations, and the importance of using the correct baud rate for logging. Users also discuss alternative modules and the cost-effectiveness of purchasing new bulbs versus swapping chips. Summary generated by the language model.