logo elektroda
logo elektroda
X
logo elektroda

Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

p.kaczmarek2 119487 485
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #151 20200356
    p.kaczmarek2
    Moderator Smart Home
    Very good spotting, @bxwen19 ! Still, I wouldn't worry about that. There are some 3.3V LDO regulators that have different pinout than AMS1117.

    If you're unsure about the 3.3V and 5V roles and think that information on the silkscreen is incorrect, then disconnect the programmer from the device and power it from mains and then carefully check if "5V" is really a 5V pin and "3.3V" is really 3.3V pin. Just to be sure.

    Then, disconnect mains (always disconnect mains before doing any programming, never connect mains while doing programming) and use 5V pin as stated before - it's an input of the LDO (AMS1117 or any other LDO).
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #152 20201507
    bxwen19
    Level 5  
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    I'll do the main experiment once I have time. I took everything apart and took more pictures.

    Added after 23 [minutes]:

    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Found the footprint of the LDO. pin2 is input. pin3 is output. I'll use a 5V supply.
  • #153 20202209
    p.kaczmarek2
    Moderator Smart Home
    Thanks for photos. This is very informative.
    bxwen19 wrote:
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Would you be able to tell which BL602 pins are routed to the pads of the "S40 WiFi module", for the future reference?

    Also looking at 6211A datasheet... I can see how it can be confusing.
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
    Helpful post? Buy me a coffee.
  • #154 20203591
    Maniac2002
    Level 6  
    Maniac2002 wrote:
    Hello,
    so here comes the information.
    It is a Switch-WF.
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working! Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    It has a Bl602L20.

    Please can you give me a step by step manual

    I have a USB to UART Dongle and i have already soldered teh cables to the PCB (RX,TX, GND and 3.3V)
    Ma Questionss are:

    Which flashing Tool do i nedd?
    Which firmwarefiles do i need.
    What do i need to do to flasch the "tasmota replacement firmware" to the device?

    Thanks in advance and best regards
    Maniac2002


    Hello,

    I was wrong. Ich boot pin is not the switch on the device. Can you provide me some Informationen hiw to find the Boot pin for a bl602e20 Chip.

    Tanks in advanve and best regard
    Maniac2002
  • #155 20203690
    p.kaczmarek2
    Moderator Smart Home
    Hello @Maniac2002 . I will try to help you here. You need to find BOOT pin, which is, unless I'm much mistaken, the GPIO8.
    Please refer to this schematic: (this is another board)
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
    I have composed an image for you. The dot marks the first pin. See where GPIO8 is:
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
    Now, my question is, where does the via goes with GPIO8? Can you look at the other side of the board? Where is this PCB track connected? I can't clearly see it on your photos...

    Maybe you can check with multimeter where does GPIO8 goes?
    Helpful post? Buy me a coffee.
  • #156 20204384
    Wolle62
    Level 2  
    Hello everyone,
    iv got the same Magic Home Controller as in Thread1 described.
    And use an USB UART Adapter with 3,3V Logiclevel with a PL2303 Chip until 115200 bd.
    This: https://www.conrad.com/p/usb-rb-ttl-cable-for-raspberry-pi-409202 Is it the wrong one?
    But i cant program the Bl602. The Flashtool always says, that there is no communication with the serial Port. "Listening Failure..."
    I clickt on "Refresh", the right Serial Port (11) will displayed, but no connection. I measured the 3,3V, it stays stable, Boot Pin ist with 1K Resistor to 3,3V connected.
    On the PCB the Boot Pin has a pulldown Resistor of 10K. Thats why I took a 1k Pullup.
    Any suggestions? Any Changes of the Programming Procedure or Software?
    I tryd the Flasher downloaded from this Thread.
    On "Firmware Bin" I set the .bin File from the Github Repo? Is it right so?
    Thank You!
  • ADVERTISEMENT
  • #157 20204825
    bxwen19
    Level 5  
    Where to get the flash tool? the dldevcube.exe I got is 1.8.0. It doesn't look like the 1.4.8 in the first post. I don't know what to do
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
    Added after 22 [minutes]:


    Would you be able to tell which BL602 pins are routed to the pads of the "S40 WiFi module", for the future reference?
    Close-up of S40 WiFi module circuit board showing labeled pins GND, 21, 22, and 5V, visible traces, and board markings.


    Middle pin is connected to pi 20 (GPIO11)

    button->GPIO0
    LED2-> GPIO1
    relay = LED1 ->GPIO11
  • #158 20205072
    p.kaczmarek2
    Moderator Smart Home
    Wolle62 wrote:

    And use an USB UART Adapter with 3,3V Logiclevel with a PL2303 Chip until 115200 bd.
    This: https://www.conrad.com/p/usb-rb-ttl-cable-for-raspberry-pi-409202 Is it the wrong one?

    I haven't tried this flash tool yet. I am using CH340G.
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
    Wolle62 wrote:

    On "Firmware Bin" I set the .bin File from the Github Repo? Is it right so?
    Thank You!

    The configuration shown on screenshots in first post is correct.

    bxwen19 wrote:
    Where to get the flash tool? the dldevcube.exe I got is 1.8.0. It doesn't look like the 1.4.8 in the first post.

    I think it was attached somewhere in this thread, but you can also get it in my SDK fork:
    https://github.com/openshwprojects/OpenBL602
    open tools->flash tool

    Have you tried probing the middle pin with multimeter?
    Helpful post? Buy me a coffee.
  • #159 20205839
    bxwen19
    Level 5  
    OK, manage to flash using Rx0 and Tx0 instead.

    Cell phone can see a wifi access point openbl602_...., if click, it says sign into network,showed tasmota interface, but then disconnect
    Teraterm shown random symbols. There is no baud rate 2000000 to choose


    Finally, wifi is connected. Is it time to remove the wires and solder everything back? Is the OTA working? How to toggle the relay and how to read the power?

    The middle pin doesn't seem to go anywhere.
  • #160 20206994
    Wolle62
    Level 2  
    i will try it like in the Screenshot
    But i cant find the Firmware bin File like in the second Picture in Thread1.
    "W:\Test\customer_app\bl602_sharedApp\build_out\bl602_sharedApp.bin"

    In my downloaded Folder there ist no Folder "build_out" and no File "bl602_sharedApp.bin in "Costumer_app\bl602_sharedApp"?
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    The Link https://github.com/openshwprojects/OpenBK7231T_App/tree/main/bl602_release
    there ist Error404

    EDIT: Found it here:
    https://github.com/openshwprojects/OpenBK7231T_App/releases
    Thank You, now i Will try again flashing
    It workt now.
    The Problem was, the actual Driver from Profilic for the PL2303 Adapter does not work. I must use an older Driver from Windows 7.
    Than the Flashing works without Problems.
    Now i configure my "new" Controller to controll a RGB Stripe.

    Done, works great!
    Is there a Way to connect the Device via MQTT2 to FHEM?
  • #161 20208252
    Wolle62
    Level 2  
    After one Day of succesfull work, i disconnected the working Controller from Power.
    Until now, the Controller works fine.
    After disconnecting from Power an reconnecting, the Controller was not reachable.
    I flashed it again, no Accespoint, I flashed the 1.12.59 but nothing happens again. Than flashed 1.12.61 again, nothing...
    What could I do, to bring the Controller back to live?
    What am i doing wrong? Its still flashable. but no Accesspoint after flashing.

    EDIT: I disconnected the Device 6 Times like Tasmota Devices and he is online again.
    Now i go on with MQTT Configuration.
  • #162 20211551
    p.kaczmarek2
    Moderator Smart Home
    bxwen19 wrote:
    Is the OTA working?

    Unfortunatelly, there was no easy and ready to use OTA example in original SDK (I used the SDK from before the breaking change of flash format mady by Buffalo Labs) so OTA for BL602 is not present yet.

    bxwen19 wrote:
    How to toggle the relay and how to read the power?

    The "Generate Home Assistant Cfg" option should give you a fair idea of how the MQTT topics for receive and set relay state are named.

    Wolle62 wrote:

    What could I do, to bring the Controller back to live?

    The first most important step would be to look at the UART logs and determine what is crashing or why the device is not connecting to your WiFi
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #163 20215293
    Wolle62
    Level 2  
    I have a Problem with the Home Assistant Template
    The Code, generated with the Web GUI works, but i got 3 Sliders for each Color one.

    The Code posted in this Thread to fix this, dont work for me.
    Home Assistant starts after in Safe Mode. I putted the Code in the configuration.yaml as described, but no Success.

    Can someone explain me what to do?

    Iv got 2 Tasmota Devices within the System. That collides with this Yaml Configuration i think.

    EDIT: I have it: There is a new Format in Configuration.yaml since my used Version.
    This is how it works now: i Must more RTFM!
    
    mqtt:
      light:
      - unique_id: "OpenBL602_05CA43EB"
        name: "DVES_BL602"
        rgb_command_template: "{{ '#%02x%02x%02x0000' | format(red, green, blue)}}"
        rgb_state_topic: "cmnd/DVES_BL602/led_basecolor_rgb"
        rgb_command_topic: "cmnd/DVES_BL602/led_basecolor_rgb"
        command_topic: "cmnd/DVES_BL602/led_enableAll"
        availability_topic: "DVES_BL602/connected"
        payload_on: 1
        payload_off: 0
        brightness_command_topic: "cmnd/DVES_BL602/led_dimmer"
        brightness_scale: 100
        brightness_value_template: "{{ value_json.Dimmer }}"
        brightness_state_topic: "cmnd/DVES_BL602/led_dimmer_get"
  • ADVERTISEMENT
  • #164 20217017
    bxwen19
    Level 5  
    I finally got some time to figure out most of the pins of sonoff S40 . The LEDs and relay are verified to be working as expected. I am not sure how to set the power monitoring device though. GPIO pin 14 is connected to cse7759b tx pin. It is supposed to receive readout from the chip. Which one should I choose?

    @p.kaczmarek2, is cse7759b supported yet? The datasheet is readily available. The cse7759b periodically sends data to bl602. If it is not supported yet, do you have a plan to make it work? I am not sure if I am up to the task to write code for it.

    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Pinout diagram of the BL602C/E QFN32 chip with labeled pins and connections to external components (button, LED, Pad 1, Pad 2, Pad 3).
  • #165 20228945
    bxwen19
    Level 5  
    @p. kaczmarek2 it seems that CSE7759B used by sonoff S40 is compatible with CSE7766. drv_cse7766.c is in the driver folder. What item from the dropdown list should I choose to enable it? Thanks.

    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!
  • #166 20235908
    bryanmandville
    Level 4  
    @p. kaczmarek2 thanks so much for all your hard work, this firmware is awesome! I was able to get a Smart Life door/window sensor (BL602) working in Home Assistant. It's great. However, the one issue I have, with this being a battery powered sensor, is that it seems to drain the battery very fast. The sensor when used with Tuya lasted for months and now I only get about 48hrs...

    Any tips on configurations changes to help improve battery life?

    Right now I just have the configuration set up as a binary sensor with a DigitalInput_NoPullUp on pin 8.

    Will definitely be supporting this awesome project moving forward!!

    Thanks
  • #167 20235972
    p.kaczmarek2
    Moderator Smart Home
    @bxwen19 CSE7759B driver is almost finished but I have not tested it myself as I don't have any devices with CSE7759B chip. Are you able to help with checking if it works correctly? Futhermore, I think that an UART wrapper must be needed for BL602 first, as the CSE7759B was developed for BK (I was implementing it without having device at hand for a certain user)
    @bryanmandville I don't know about this issue yet. You might need to look into the power saving mode of BL602. I haven't encountered BL602-based battery devices so far. What kind of sensor you have? Can you provide some photos or maybe do a short teardown article (gallery of photos + names of chips + info where to buy/box photos) and post here: https://www.elektroda.com/rtvforum/forum507.html
    Is your device by any chance a TuyaMCU? Or just BL602? It's the first time I hear about BL602-based door/window sensors.
    Helpful post? Buy me a coffee.
  • #168 20236011
    bryanmandville
    Level 4  
    p.kaczmarek2 wrote:

    @bryanmandville I don't know about this issue yet. You might need to look into the power saving mode of BL602. I haven't encountered BL602-based battery devices so far. What kind of sensor you have? Can you provide some photos or maybe do a short teardown article (gallery of photos + names of chips + info where to buy/box photos) and post here: https://www.elektroda.com/rtvforum/forum507.html
    Is your device by any chance a TuyaMCU? Or just BL602? It's the first time I hear about BL602-based door/window sensors.


    Apologies p.kaczmarek2... I've been flashing everything in my home and I mixed this up. The door sensor is actually a CB3S Chip which upon closer look does seem to be a a TuyaMCU

    "CB3S is built in with a 32-bit MCU whose running speed can be up to 120 MHz, a 2-MB flash memory, and a 256-KB RAM, to support the Tuya cloud connection."

    https://developer.tuya.com/en/docs/iot/cb3s?id=Kai94mec0s076

    I will post a tear down article this weekend.

    Thanks again!
  • #169 20236048
    p.kaczmarek2
    Moderator Smart Home
    @bryanmandville thanks! I will wait to see teardown, I will later add a link to our online database.
    Regarding the power issue.... did you modify the circuit to keep the CB3S always on and running?
    Helpful post? Buy me a coffee.
  • #170 20236080
    bxwen19
    Level 5  
    p.kaczmarek2 wrote:
    @bxwen19 CSE7759B driver is almost finished but I have not tested it myself as I don't have any devices with CSE7759B chip. Are you able to help with checking if it works correctly? Futhermore, I think that an UART wrapper must be needed for BL602 first, as the CSE7759B was developed for BK (I was implementing it without having device at hand for a certain user)

    @p.kaczmarek2 Yes I can check if you send me the binary. Also if you give me some instruction I can write some code for it also. Thank you for all the work.
  • #171 20236089
    bryanmandville
    Level 4  
    p.kaczmarek2 wrote:
    @bryanmandville thanks! I will wait to see teardown, I will later add a link to our online database.
    Regarding the power issue.... did you modify the circuit to keep the CB3S always on and running?


    @p.kaczmarek2 I never made any changes to the circuit at all. I really didn't do very much configuration tbh as I just want to use it as a binary sensor. I flashed the firmware, set up wifi and MQTT, determined which pin went hi/lo when contact was made/lost, set that pin to "DigitalInput_NoPullUp" and like I said, even with no MCU drivers or anything set up, it worked perfectly in Home Assistant, just not for very long because the battery. I will dig into the tuyaMCU configuration a bit more this weekend.

    Thanks!
  • #172 20240183
    omelchuk890
    Level 11  
    @p.kaczmarek2
    Thanks for the dev cube 1.4.8 file!!!
    Flashed, configured WiFi, enabled the necessary pins, configured flags, 7 and 10 (Flags (Current value=1152)), connection to the broker.
    MQTT does not work...
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Version 1.5.8 working
    Tasmota replacement for BL602, programming, pairing with Home Assistant, now with OTA working!

    Version 1.14.18 working !!!

    P.S. Figured it out. If you leave the mqtt login and password fields empty, we get an error. You need to insert something, even if authorization is not required.
    For BK7231, this was irrelevant.
  • #173 20251234
    GabrielGrabowski
    Level 6  
    Witam. Zrobiłem wrzut DevCube 1.4.8.
    Co jest nie tak? Próbowałem różne wersje programu, drugi moduł, różne wsady i nic... Wcześniej udało mi się wrzucić i otrzymać poprawne odpowiedzi w terminalu, lecz moduł nie utworzył AP.

    Terminal:
    Spoiler:

    # 4 湓
    Spectrum. 0佧
    ,4 & 4 粼7 noise fibula $ swollen ( 4
    foot
    # 4 $心 ;
    /0你+ )  # yan 7 哭phewan) 坭
    Beat up
    ! 6 renders
    Phosphorus flea & slaughter(

    4! Review; &4 Nao Piao

    , Mi Zhushi$swollen (4
    Zupu 7 蜿phee&zai( 4 beat ! 6 獼
    Nao.0揲匏. bristle/ Nao,
    Yin 7 + 4
    /0 ! Shuttle; Nian Zhu
    6
    /0Qin Hui Mi 幹幹幹幹循媪圪幹循娸
    $ Noise# broken list
    tomb
    $ Noise# spike list
    Qiansuo
    $ fleas! spike list
    Kuaisui
    $

    $ fleas! spike list
    Ge
    sparkling
    $ fleas#broken list
    Ge
    favorite
    $ fleas#broken list
    tomb
    Good luck.3
    ) # ), /樗+ # 1
    6# ! ## ) Total 6+ Zou 4$Pian$ #) PI
    3
    ` Xuzou/4Miansuo+ 4) + PI, ) 6
    +! take ;) Score #+ # + Suo// Yuyou, 6杳+ 4 烨筵 3
    溆7 6 Noise Fe$zai(4
    Feet+/0 # 4 4 淠
    #


    Program DevCube:
    Spoiler:

    [18:38:25.944] - ========= Interface is Uart =========
    [18:38:25.958] - eflash loader bin is eflash_loader_40m.bin
    [18:38:25.958] - ========= chip flash id: ef4015 =========
    [18:38:25.958] - Update flash cfg finished
    [18:38:25.974] - create partition.bin, pt_new is True
    [18:38:25.974] - bl60x_fw_boot_head_gen xtal: 40M
    [18:38:25.974] - Create bootheader using C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\efuse_bootheader/efuse_bootheader_cfg.ini
    [18:38:25.974] - Updating data according to
    [18:38:25.989] - Created file len:176
    [18:38:25.989] - Create efuse using C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\efuse_bootheader/efuse_bootheader_cfg.ini
    [18:38:25.989] - Updating data according to
    [18:38:25.989] - Created file len:128
    [18:38:26.005] - ========= sp image create =========
    [18:38:26.005] - Image hash is b'c5e2ce515a5783ac80efdd4910238a466572f882b53b3284e63c763e1da9847f'
    [18:38:26.005] - Header crc: b'52b188af'
    [18:38:26.005] - Write flash img
    [18:38:26.021] - bl60x_fw_boot_head_gen xtal: 40M
    [18:38:26.021] - Create bootheader using C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\efuse_bootheader/efuse_bootheader_cfg.ini
    [18:38:26.021] - Updating data according to
    [18:38:26.036] - Created file len:176
    [18:38:26.036] - Create efuse using C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\efuse_bootheader/efuse_bootheader_cfg.ini
    [18:38:26.036] - Updating data according to
    [18:38:26.036] - Created file len:128
    [18:38:26.052] - ========= sp image create =========
    [18:38:26.058] - Image hash is b'f2e01bef7a48325f0cb39fd0b2c61ffd95aa8daded602ca2dc95638834cd1952'
    [18:38:26.058] - Header crc: b'16729adb'
    [18:38:26.058] - Write flash img
    [18:38:26.074] - FW Header is 176, 3920 still needed
    [18:38:26.074] - FW OTA bin header is Done. Len is 4096
    [18:38:26.275] - FW OTA bin is Done. Len is 732224
    [18:38:26.938] - FW OTA xz is Done
    [18:38:26.938] - ========= eflash loader config =========
    [18:38:27.013] - =========C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\device_tree/bl_factory_params_IoTKitA_40M.dts ——> bl602/device_tree/ro_params.dtb=========
    [18:38:27.219] - Version: bflb_eflash_loader_v2.0.0
    [18:38:27.219] - Program Start
    [18:38:27.219] - ========= eflash loader cmd arguments =========
    chipname : None
    chipid : False
    usage : False
    flash : True
    efuse : False
    write : True
    erase : False
    read : False
    none : False
    port : COM3
    baudrate : None
    config : None
    interface : None
    xtal : None
    start : None
    end : None
    addr : None
    mac : None
    file : None
    data : None
    mass : None
    loadstr : None
    loadfile : None
    userarea : None
    csvfile : None
    csvaddr : None
    para : None
    aeskey : None
    aesiv : None
    key : None
    ecdh : False
    echo : False
    auto : False
    version : False
    [18:38:27.257] - Config file: C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\eflash_loader/eflash_loader_cfg.ini
    [18:38:27.257] - serial port is COM3
    [18:38:27.257] - chiptype: bl602
    [18:38:27.257] - ========= Interface is Uart =========
    [18:38:27.257] - com speed: 2000000
    [18:38:27.257] - Eflash load helper file: C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\eflash_loader/eflash_loader_40m.bin
    [18:38:27.257] - Eflash load helper file: C:\msys64\home\48533\bl_iot_sdk-master\tools\stary_flash_tool\bl602\eflash_loader/eflash_loader_40m.bin
    [18:38:27.257] - ========= load eflash_loader.bin =========
    [18:38:27.257] - Load eflash_loader.bin via uart
    [18:38:27.257] - ========= image load =========
    [18:38:27.736] - tx rx and power off, press the machine!
    [18:38:27.736] - cutoff time is 0.1
    [18:38:27.852] - power on tx and rx
    [18:38:28.677] - reset cnt: 0, reset hold: 0.005, shake hand delay: 0.1
    [18:38:28.677] - clean buf
    [18:38:28.913] - send sync
    [18:38:29.126] - ack is b'4f4b'
    [18:38:29.211] - shake hand success
    [18:38:29.226] - get_boot_info
    [18:38:29.226] - data read is b'010000000000000003000000d3f2d605b9181800'
    [18:38:29.226] - sign is 0 encrypt is 0
    [18:38:29.226] - segcnt is 1
    [18:38:29.226] - segdata_len is 30192
    [18:38:29.327] - 4080/30192
    [18:38:29.416] - 8160/30192
    [18:38:29.512] - 12240/30192
    [18:38:29.613] - 16320/30192
    [18:38:29.697] - 20400/30192
    [18:38:29.798] - 24480/30192
    [18:38:29.882] - 28560/30192
    [18:38:29.929] - 30192/30192
    [18:38:29.929] - Run img
    [18:38:30.040] - Load helper bin time cost(ms): 2783.65673828125
    [18:38:30.146] - ========= flash read jedec ID =========
    [18:38:30.146] - Flash load shake hand
    [18:38:30.199] - clean buf
    [18:38:30.420] - send sync
    [18:38:30.632] - ack is b'4f4b'
    [18:38:30.717] - Read flash jedec ID
    [18:38:30.717] - readdata:
    [18:38:30.717] - b'ef401500'
    [18:38:30.717] - Finished
    [18:38:30.717] - Program operation
    [18:38:30.717] - Dealing Index 0
    [18:38:30.717] - ========= programming bl602/img_create/whole_img_boot2.bin to 0x00000000
    [18:38:30.717] - ========= flash load =========
    [18:38:30.717] - ========= flash erase =========
    [18:38:30.717] - Erase flash from 0x0 to 0xb98f
    [18:38:31.040] - Erase time cost(ms): 323.72900390625
    [18:38:31.118] - decompress flash load 22164
    [18:38:31.133] - Load 2048/22164 {"progress":9}
    [18:38:31.149] - Load 4096/22164 {"progress":18}
    [18:38:31.165] - Load 6144/22164 {"progress":27}
    [18:38:31.171] - Load 8192/22164 {"progress":36}
    [18:38:31.186] - Load 10240/22164 {"progress":46}
    [18:38:31.202] - Load 12288/22164 {"progress":55}
    [18:38:31.218] - Load 14336/22164 {"progress":64}
    [18:38:31.233] - Load 16384/22164 {"progress":73}
    [18:38:31.233] - Load 18432/22164 {"progress":83}
    [18:38:31.249] - Load 20480/22164 {"progress":92}
    [18:38:31.271] - Load 22164/22164 {"progress":100}
    [18:38:31.271] - Load 22164/22164 {"progress":100}
    [18:38:31.271] - Write check
    [18:38:31.303] - Flash load time cost(ms): 200.289794921875
    [18:38:31.303] - Finished
    [18:38:31.303] - Sha caled by host: 194e180166ca945012e261580c23e9a181fb3d34a9e1a50c54d0dd649754a400
    [18:38:31.303] - xip mode Verify
    [18:38:31.318] - Read Sha256/47504
    [18:38:31.318] - Flash xip readsha time cost(ms): 15.3681640625
    [18:38:31.318] - Finished
    [18:38:31.318] - Sha caled by dev: 194e180166ca945012e261580c23e9a181fb3d34a9e1a50c54d0dd649754a400
    [18:38:31.318] - Verify success
    [18:38:31.318] - Dealing Index 1
    [18:38:31.318] - ========= programming bl602/partition/partition.bin to 0xe000
    [18:38:31.318] - ========= flash load =========
    [18:38:31.318] - ========= flash erase =========
    [18:38:31.318] - Erase flash from 0xe000 to 0xe10f
    [18:38:31.422] - Erase time cost(ms): 104.41796875
    [18:38:31.487] - Load 272/272 {"progress":100}
    [18:38:31.487] - Load 272/272 {"progress":100}
    [18:38:31.487] - Write check
    [18:38:31.487] - Flash load time cost(ms): 0.0
    [18:38:31.487] - Finished
    [18:38:31.487] - Sha caled by host: da4d2fe7d42a71246b0e84d64665b70ad701435f89716c48e6f23ef55340eaa0
    [18:38:31.487] - xip mode Verify
    [18:38:31.487] - Read Sha256/272
    [18:38:31.487] - Flash xip readsha time cost(ms): 0.0
    [18:38:31.487] - Finished
    [18:38:31.487] - Sha caled by dev: da4d2fe7d42a71246b0e84d64665b70ad701435f89716c48e6f23ef55340eaa0
    [18:38:31.487] - Verify success
    [18:38:31.487] - Dealing Index 2
    [18:38:31.487] - ========= programming bl602/partition/partition.bin to 0xf000
    [18:38:31.487] - ========= flash load =========
    [18:38:31.487] - ========= flash erase =========
    [18:38:31.487] - Erase flash from 0xf000 to 0xf10f
    [18:38:31.588] - Erase time cost(ms): 100.16748046875
    [18:38:31.666] - Load 272/272 {"progress":100}
    [18:38:31.666] - Load 272/272 {"progress":100}
    [18:38:31.666] - Write check
    [18:38:31.666] - Flash load time cost(ms): 0.0
    [18:38:31.666] - Finished
    [18:38:31.672] - Sha caled by host: da4d2fe7d42a71246b0e84d64665b70ad701435f89716c48e6f23ef55340eaa0
    [18:38:31.672] - xip mode Verify
    [18:38:31.672] - Read Sha256/272
    [18:38:31.672] - Flash xip readsha time cost(ms): 0.0
    [18:38:31.672] - Finished
    [18:38:31.672] - Sha caled by dev: da4d2fe7d42a71246b0e84d64665b70ad701435f89716c48e6f23ef55340eaa0
    [18:38:31.672] - Verify success
    [18:38:31.672] - Dealing Index 3
    [18:38:31.672] - ========= programming bl602/img_create/whole_img.bin to 0x10000
    [18:38:31.672] - ========= flash load =========
    [18:38:31.672] - ========= flash erase =========
    [18:38:31.672] - Erase flash from 0x10000 to 0xc2c3f
    [18:38:33.927] - Erase time cost(ms): 2254.998291015625
    [18:38:34.374] - decompress flash load 393092
    [18:38:34.384] - Load 2048/393092 {"progress":0}
    [18:38:34.404] - Load 4096/393092 {"progress":1}
    [18:38:34.414] - Load 6144/393092 {"progress":1}
    [18:38:34.430] - Load 8192/393092 {"progress":2}
    [18:38:34.446] - Load 10240/393092 {"progress":2}
    [18:38:34.461] - Load 12288/393092 {"progress":3}
    [18:38:34.461] - Load 14336/393092 {"progress":3}
    [18:38:34.477] - Load 16384/393092 {"progress":4}
    [18:38:34.492] - Load 18432/393092 {"progress":4}
    [18:38:34.515] - Load 20480/393092 {"progress":5}
    [18:38:34.530] - Load 22528/393092 {"progress":5}
    [18:38:34.546] - Load 24576/393092 {"progress":6}
    [18:38:34.562] - Load 26624/393092 {"progress":6}
    [18:38:34.577] - Load 28672/393092 {"progress":7}
    [18:38:34.577] - Load 30720/393092 {"progress":7}
    [18:38:34.593] - Load 32768/393092 {"progress":8}
    [18:38:34.615] - Load 34816/393092 {"progress":8}
    [18:38:34.631] - Load 36864/393092 {"progress":9}
    [18:38:34.646] - Load 38912/393092 {"progress":9}
    [18:38:34.662] - Load 40960/393092 {"progress":10}
    [18:38:34.678] - Load 43008/393092 {"progress":10}
    [18:38:34.693] - Load 45056/393092 {"progress":11}
    [18:38:34.715] - Load 47104/393092 {"progress":11}
    [18:38:34.715] - Load 49152/393092 {"progress":12}
    [18:38:34.731] - Load 51200/393092 {"progress":13}
    [18:38:34.746] - Load 53248/393092 {"progress":13}
    [18:38:34.762] - Load 55296/393092 {"progress":14}
    [18:38:34.788] - Load 57344/393092 {"progress":14}
    [18:38:34.803] - Load 59392/393092 {"progress":15}
    [18:38:34.815] - Load 61440/393092 {"progress":15}
    [18:38:34.831] - Load 63488/393092 {"progress":16}
    [18:38:34.847] - Load 65536/393092 {"progress":16}
    [18:38:34.847] - Load 67584/393092 {"progress":17}
    [18:38:34.863] - Load 69632/393092 {"progress":17}
    [18:38:34.889] - Load 71680/393092 {"progress":18}
    [18:38:34.905] - Load 73728/393092 {"progress":18}
    [18:38:34.915] - Load 75776/393092 {"progress":19}
    [18:38:34.931] - Load 77824/393092 {"progress":19}
    [18:38:34.947] - Load 79872/393092 {"progress":20}
    [18:38:34.963] - Load 81920/393092 {"progress":20}
    [18:38:34.963] - Load 83968/393092 {"progress":21}
    [18:38:34.988] - Load 86016/393092 {"progress":21}
    [18:38:35.004] - Load 88064/393092 {"progress":22}
    [18:38:35.015] - Load 90112/393092 {"progress":22}
    [18:38:35.031] - Load 92160/393092 {"progress":23}
    [18:38:35.047] - Load 94208/393092 {"progress":23}
    [18:38:35.063] - Load 96256/393092 {"progress":24}
    [18:38:35.078] - Load 98304/393092 {"progress":25}
    [18:38:35.094] - Load 100352/393092 {"progress":25}
    [18:38:35.109] - Load 102400/393092 {"progress":26}
    [18:38:35.115] - Load 104448/393092 {"progress":26}
    [18:38:35.131] - Load 106496/393092 {"progress":27}
    [18:38:35.147] - Load 108544/393092 {"progress":27}
    [18:38:35.163] - Load 110592/393092 {"progress":28}
    [18:38:35.178] - Load 112640/393092 {"progress":28}
    [18:38:35.194] - Load 114688/393092 {"progress":29}
    [18:38:35.194] - Load 116736/393092 {"progress":29}
    [18:38:35.216] - Load 118784/393092 {"progress":30}
    [18:38:35.231] - Load 120832/393092 {"progress":30}
    [18:38:35.247] - Load 122880/393092 {"progress":31}
    [18:38:35.263] - Load 124928/393092 {"progress":31}
    [18:38:35.278] - Load 126976/393092 {"progress":32}
    [18:38:35.294] - Load 129024/393092 {"progress":32}
    [18:38:35.310] - Load 131072/393092 {"progress":33}
    [18:38:35.316] - Load 133120/393092 {"progress":33}
    [18:38:35.332] - Load 135168/393092 {"progress":34}
    [18:38:35.347] - Load 137216/393092 {"progress":34}
    [18:38:35.363] - Load 139264/393092 {"progress":35}
    [18:38:35.389] - Load 141312/393092 {"progress":35}
    [18:38:35.405] - Load 143360/393092 {"progress":36}
    [18:38:35.416] - Load 145408/393092 {"progress":36}
    [18:38:35.432] - Load 147456/393092 {"progress":37}
    [18:38:35.448] - Load 149504/393092 {"progress":38}
    [18:38:35.463] - Load 151552/393092 {"progress":38}
    [18:38:35.479] - Load 153600/393092 {"progress":39}
    [18:38:35.489] - Load 155648/393092 {"progress":39}
    [18:38:35.510] - Load 157696/393092 {"progress":40}
    [18:38:35.516] - Load 159744/393092 {"progress":40}
    [18:38:35.532] - Load 161792/393092 {"progress":41}
    [18:38:35.547] - Load 163840/393092 {"progress":41}
    [18:38:35.563] - Load 165888/393092 {"progress":42}
    [18:38:35.579] - Load 167936/393092 {"progress":42}
    [18:38:35.594] - Load 169984/393092 {"progress":43}
    [18:38:35.610] - Load 172032/393092 {"progress":43}
    [18:38:35.616] - Load 174080/393092 {"progress":44}
    [18:38:35.632] - Load 176128/393092 {"progress":44}
    [18:38:35.648] - Load 178176/393092 {"progress":45}
    [18:38:35.663] - Load 180224/393092 {"progress":45}
    [18:38:35.679] - Load 182272/393092 {"progress":46}
    [18:38:35.695] - Load 184320/393092 {"progress":46}
    [18:38:35.710] - Load 186368/393092 {"progress":47}
    [18:38:35.716] - Load 188416/393092 {"progress":47}
    [18:38:35.732] - Load 190464/393092 {"progress":48}
    [18:38:35.748] - Load 192512/393092 {"progress":48}
    [18:38:35.763] - Load 194560/393092 {"progress":49}
    [18:38:35.779] - Load 196608/393092 {"progress":50}
    [18:38:35.795] - Load 198656/393092 {"progress":50}
    [18:38:35.817] - Load 200704/393092 {"progress":51}
    [18:38:35.817] - Load 202752/393092 {"progress":51}
    [18:38:35.832] - Load 204800/393092 {"progress":52}
    [18:38:35.848] - Load 206848/393092 {"progress":52}
    [18:38:35.864] - Load 208896/393092 {"progress":53}
    [18:38:35.879] - Load 210944/393092 {"progress":53}
    [18:38:35.895] - Load 212992/393092 {"progress":54}
    [18:38:35.917] - Load 215040/393092 {"progress":54}
    [18:38:35.933] - Load 217088/393092 {"progress":55}
    [18:38:35.949] - Load 219136/393092 {"progress":55}
    [18:38:35.964] - Load 221184/393092 {"progress":56}
    [18:38:35.980] - Load 223232/393092 {"progress":56}
    [18:38:35.996] - Load 225280/393092 {"progress":57}
    [18:38:36.011] - Load 227328/393092 {"progress":57}
    [18:38:36.017] - Load 229376/393092 {"progress":58}
    [18:38:36.033] - Load 231424/393092 {"progress":58}
    [18:38:36.049] - Load 233472/393092 {"progress":59}
    [18:38:36.064] - Load 235520/393092 {"progress":59}
    [18:38:36.080] - Load 237568/393092 {"progress":60}
    [18:38:36.095] - Load 239616/393092 {"progress":60}
    [18:38:36.095] - Load 241664/393092 {"progress":61}
    [18:38:36.117] - Load 243712/393092 {"progress":61}
    [18:38:36.133] - Load 245760/393092 {"progress":62}
    [18:38:36.149] - Load 247808/393092 {"progress":63}
    [18:38:36.165] - Load 249856/393092 {"progress":63}
    [18:38:36.180] - Load 251904/393092 {"progress":64}
    [18:38:36.196] - Load 253952/393092 {"progress":64}
    [18:38:36.212] - Load 256000/393092 {"progress":65}
    [18:38:36.218] - Load 258048/393092 {"progress":65}
    [18:38:36.233] - Load 260096/393092 {"progress":66}
    [18:38:36.249] - Load 262144/393092 {"progress":66}
    [18:38:36.265] - Load 264192/393092 {"progress":67}
    [18:38:36.280] - Load 266240/393092 {"progress":67}
    [18:38:36.296] - Load 268288/393092 {"progress":68}
    [18:38:36.312] - Load 270336/393092 {"progress":68}
    [18:38:36.318] - Load 272384/393092 {"progress":69}
    [18:38:36.333] - Load 274432/393092 {"progress":69}
    [18:38:36.349] - Load 276480/393092 {"progress":70}
    [18:38:36.365] - Load 278528/393092 {"progress":70}
    [18:38:36.380] - Load 280576/393092 {"progress":71}
    [18:38:36.391] - Load 282624/393092 {"progress":71}
    [18:38:36.406] - Load 284672/393092 {"progress":72}
    [18:38:36.418] - Load 286720/393092 {"progress":72}
    [18:38:36.433] - Load 288768/393092 {"progress":73}
    [18:38:36.449] - Load 290816/393092 {"progress":73}
    [18:38:36.465] - Load 292864/393092 {"progress":74}
    [18:38:36.480] - Load 294912/393092 {"progress":75}
    [18:38:36.496] - Load 296960/393092 {"progress":75}
    [18:38:36.512] - Load 299008/393092 {"progress":76}
    [18:38:36.518] - Load 301056/393092 {"progress":76}
    [18:38:36.533] - Load 303104/393092 {"progress":77}
    [18:38:36.549] - Load 305152/393092 {"progress":77}
    [18:38:36.565] - Load 307200/393092 {"progress":78}
    [18:38:36.580] - Load 309248/393092 {"progress":78}
    [18:38:36.596] - Load 311296/393092 {"progress":79}
    [18:38:36.611] - Load 313344/393092 {"progress":79}
    [18:38:36.618] - Load 315392/393092 {"progress":80}
    [18:38:36.634] - Load 317440/393092 {"progress":80}
    [18:38:36.649] - Load 319488/393092 {"progress":81}
    [18:38:36.681] - Load 321536/393092 {"progress":81}
    [18:38:36.696] - Load 323584/393092 {"progress":82}
    [18:38:36.712] - Load 325632/393092 {"progress":82}
    [18:38:36.718] - Load 327680/393092 {"progress":83}
    [18:38:36.734] - Load 329728/393092 {"progress":83}
    [18:38:36.749] - Load 331776/393092 {"progress":84}
    [18:38:36.765] - Load 333824/393092 {"progress":84}
    [18:38:36.781] - Load 335872/393092 {"progress":85}
    [18:38:36.807] - Load 337920/393092 {"progress":85}
    [18:38:36.818] - Load 339968/393092 {"progress":86}
    [18:38:36.834] - Load 342016/393092 {"progress":87}
    [18:38:36.850] - Load 344064/393092 {"progress":87}
    [18:38:36.865] - Load 346112/393092 {"progress":88}
    [18:38:36.881] - Load 348160/393092 {"progress":88}
    [18:38:36.907] - Load 350208/393092 {"progress":89}
    [18:38:36.918] - Load 352256/393092 {"progress":89}
    [18:38:36.934] - Load 354304/393092 {"progress":90}
    [18:38:36.966] - Load 356352/393092 {"progress":90}
    [18:38:36.992] - Load 358400/393092 {"progress":91}
    [18:38:37.008] - Load 360448/393092 {"progress":91}
    [18:38:37.019] - Load 362496/393092 {"progress":92}
    [18:38:37.034] - Load 364544/393092 {"progress":92}
    [18:38:37.050] - Load 366592/393092 {"progress":93}
    [18:38:37.097] - Load 368640/393092 {"progress":93}
    [18:38:37.113] - Load 370688/393092 {"progress":94}
    [18:38:37.119] - Load 372736/393092 {"progress":94}
    [18:38:37.150] - Load 374784/393092 {"progress":95}
    [18:38:37.166] - Load 376832/393092 {"progress":95}
    [18:38:37.181] - Load 378880/393092 {"progress":96}
    [18:38:37.213] - Load 380928/393092 {"progress":96}
    [18:38:37.219] - Load 382976/393092 {"progress":97}
    [18:38:37.250] - Load 385024/393092 {"progress":97}
    [18:38:37.266] - Load 387072/393092 {"progress":98}
    [18:38:37.281] - Load 389120/393092 {"progress":98}
    [18:38:37.313] - Load 391168/393092 {"progress":99}
    [18:38:37.334] - Load 393092/393092 {"progress":100}
    [18:38:37.334] - Load 393092/393092 {"progress":100}
    [18:38:37.334] - Write check
    [18:38:37.350] - Flash load time cost(ms): 3354.038330078125
    [18:38:37.350] - Finished
    [18:38:37.366] - Sha caled by host: 2afa3a8cf784e7a6a7c004df027c420236e596c804e11f3151581a8ad45eba61
    [18:38:37.366] - xip mode Verify
    [18:38:37.435] - Read Sha256/732224
    [18:38:37.435] - Flash xip readsha time cost(ms): 69.48974609375
    [18:38:37.435] - Finished
    [18:38:37.435] - Sha caled by dev: 2afa3a8cf784e7a6a7c004df027c420236e596c804e11f3151581a8ad45eba61
    [18:38:37.435] - Verify success
    [18:38:37.450] - Dealing Index 4
    [18:38:37.450] - ========= programming bl602/device_tree/ro_params.dtb to 0x1f8000
    [18:38:37.450] - ========= flash load =========
    [18:38:37.450] - ========= flash erase =========
    [18:38:37.450] - Erase flash from 0x1f8000 to 0x1f9729
    [18:38:37.567] - Erase time cost(ms): 116.047119140625
    [18:38:37.636] - decompress flash load 1640
    [18:38:37.651] - Load 1640/1640 {"progress":100}
    [18:38:37.651] - Load 1640/1640 {"progress":100}
    [18:38:37.651] - Write check
    [18:38:37.667] - Flash load time cost(ms): 30.9765625
    [18:38:37.667] - Finished
    [18:38:37.667] - Sha caled by host: 4fd42b104897efb92f6a396b4e15193b842fd35a4463dacd20f2ea64ff354634
    [18:38:37.667] - xip mode Verify
    [18:38:37.667] - Read Sha256/5930
    [18:38:37.667] - Flash xip readsha time cost(ms): 0.0
    [18:38:37.667] - Finished
    [18:38:37.667] - Sha caled by dev: 4fd42b104897efb92f6a396b4e15193b842fd35a4463dacd20f2ea64ff354634
    [18:38:37.667] - Verify success
    [18:38:37.667] - Program Finished
    [18:38:37.667] - All time cost(ms): 10447.595947265625
    [18:38:37.798] - [All Success]
  • #174 20252710
    yipe
    Level 8  
    I managed to flash it with pain. Question. How to make the device connect to a hidden network?
  • #175 20252742
    p.kaczmarek2
    Moderator Smart Home
    @omelchuk890 there was indeed a difference in the library from MQTT with LWIP, I moved the fix from BK7231 to BL602 and it should be ok. Corrected.

    @GabrielGrabowski do you set the same baud as in my article? These signs indicate incorrect baud setting. Does the GPIO mini-demo from SDK BL602 posted earlier in this topic also give you such strange signals on UART? Show a screenshot of the UART program, are you using RealTerm?

    @yipe in Options you have Configure WiFi and there is a field to enter the SSID and password. Then after reboot it should join.
    Helpful post? Buy me a coffee.
  • #176 20252824
    yipe
    Level 8  
    It`s not running right now. After saving, he shouts that he doesn`t see the network. I suspect he needs to see it before he connects it. By default it is in esphome, but there you can fix it with the quickconnect option
  • #177 20252857
    p.kaczmarek2
    Moderator Smart Home
    Just to be sure, because BL602 has few users and is sometimes not tested - does it work with regular WiFi that is visible?
    Helpful post? Buy me a coffee.
  • #178 20253141
    yipe
    Level 8  
    That`s how it works. I turn off the SSID broadcast on the AP and the bl602 cannot connect. I turn on the broadcast and there is a connection.
  • #179 20255413
    GabrielGrabowski
    Level 6  
    p.kaczmarek2 wrote:

    @GabrielGrabowski do you set the same baud as in my article? These signs indicate incorrect baud setting. Does the GPIO mini-demo from SDK BL602 posted earlier in this topic also give you such strange signals on UART? Show a screenshot of the UART program, are you using RealTerm?


    You were right. I set the baud to one less 0. I managed to read the terminal, but now I have another problem, the same as the colleagues above.
    BL602 restarts forever. I power it from 1117, the GPIO demo program works correctly, but when uploading a batch from WIFI the chip goes crazy. What could be the reason for this? I uploaded various versions of firmware, bootloaders and partitions.

    Spoiler:

    Booting BL602 Chip...
    ██████╗ ██╗ ██████╗ ██████╗ ██████╗
    ██╔══██╗██║ ██╔════╝ ██╔═████╗╚════██╗
    ██████╔╝██║ ███████╗ ██║██╔██║ █████╔╝
    ██╔══██╗██║ ██╔═══██╗████╔╝██║██╔═══╝
    ██████╔╝███████╗╚██████╔╝╚██████╔╝███████ ╗
    ╚═════╝ ╚══════╝ ╚═════╝ ╚═════╝ ╚══════╝


    -------------------------------------------------- ----------
    RISC-V Core Feature:RV32-ACFIMX
    Build Version: release_bl_iot_sdk_1.6.22-22-g1d4ff804-dirty
    Std Driver Version: 541807d
    PHY Version: a0_final-73-g62481a0
    RF Version: 79cc6b9
    Build Date: Oct 25 2022
    Build Time: 10:01:02
    Boot Reason: BL_RST_SOFTWARE_WATCHDOG
    -------------------------------------------------- ----------
    Heap 131504@0x42021e50, 5888@0x4204a900
    Boot2 consumed 11ms

    blog init set power on level 2, 2, 2.
    [IRQ] Clearing and Disable all the pending IRQ...
    ------------------TRNG TEST------------------------------ ---
    **********TRNG TEST rand[4fde8545]**************
    **********TRNG TEST rand[23df6817]**************
    -------------------------------------------------- ----------
    [ 0][INFO : hal_boot2.c: 285] [HAL] [BOOT2] Active Partition[0] consumed 596 Bytes
    [ 0][INFO : hal_boot2.c: 82] ======= PtTable_Config @0x4200e754=======
    [ 0][INFO : hal_boot2.c: 83] magicCode 0x54504642; version 0x0000; entryCnt 7; age 0; crc32 0x12DF9A26
    [ 0][INFO : hal_boot2.c: 89] idx type device activeIndex name Address[0] Address[1] Length[0] Length[1] age
    [ 0][INFO : hal_boot2.c: 91] [00] 00 0 0 FW 0x00010000 0x000e8000 0x000d8000 0x00088000 0
    [ 0][INFO : hal_boot2.c: 91] [01] 02 0 0 mfg 0x00170000 0x00000000 0x00032000 0x00000000 0
    [ 0][INFO : hal_boot2.c: 91] [02] 03 0 0 media 0x001a2000 0x00000000 0x00047000 0x00000000 0
    [ 0][INFO : hal_boot2.c: 91] [03] 04 0 0 PSM 0x001e9000 0x00000000 0x00008000 0x00000000 0
    [ 0][INFO : hal_boot2.c: 91] [04] 05 0 0 KEY 0x001f1000 0x00000000 0x00002000 0x00000000 0
    [ 0][INFO : hal_boot2.c: 91] [05] 06 0 0 DATA 0x001f3000 0x00000000 0x00005000 0x00000000 0
    [ 0][INFO : hal_boot2.c: 91] [06] 07 0 0 factory 0x001f8000 0x00000000 0x00007000 0x00000000 0
    [ 0][INFO : bl_flash.c: 96] ======= FlashCfg magiccode @0x42049c18, code 0x47464346 =======
    [ 0][INFO : bl_flash.c: 97] mid 0xEF
    [ 0][INFO : bl_flash.c: 98] clkDelay 0x1
    [ 0][INFO : bl_flash.c: 99] clkInvert 0x1
    [ 0][INFO : bl_flash.c: 100] sector size 4KBytes
    [ 0][INFO : bl_flash.c: 101] page size 256Bytes
    [ 0][INFO : bl_flash.c: 102] ---------------------------------------------------------------
    [ 0][INFO : hal_board.c:1249] [MAIN] [BOARD] [FLASH] addr from partition is 001f8000, ret is 0
    [ 0][INFO : hal_board.c:1257] [MAIN] [BOARD] [XIP] addr from partition is 231e7000, ret is 0
    [ 0][ERROR : hal_board.c: 942] wifi NULL.
    [ 0][ERROR : hal_board.c:1075] bt NULL.
    sizeof(StackType_t)=4
    [OS] Starting aos_loop_proc task...
    [OS] Starting TCP/IP Stack...
    --▒▒Starting bl602 now....
    Booting BL602 Chip...

  • #180 20259298
    yipe
    Level 8  
    @GabrielGrabowski Are you uploading 1.4.8 or another version? I had a similar experience when I uploaded 1.8.0

Topic summary

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.
ADVERTISEMENT