HomeKidd / Homekit-WS2812B-controller

ESP8266 based  Homekit controller for WS2812B lightstrips with WS2812FX support🌈
237 stars 36 forks source link

cant upload #2

Closed kefkevm closed 4 years ago

kefkevm commented 4 years ago

hey,

i want the bin files uploading to my wemos (esp8266). i used nodeflasherMCU. but it won's work. can someone explain me how to get the bin files on my board?

HomeKidd commented 4 years ago

Hi!

All the commands are at the Wiki page. There are tons of videos on the internet about how to install and use esptool.py for flashing ESP8266 boards! 🤓

Esptool is Espressif’s official tool for flashing ESP8266 boards, basically Arduino using it too for that job!

kefkevm commented 4 years ago

i used espressif's official tool but i wont work. i tried another .bin file from another project and this wil work. maybe i need another .bin file because i use a wemos. not a esp???

HomeKidd commented 4 years ago

Could you post an image of the serial what happens when you try to upload it? What command do you entered for flashing the wemos? Wemos is an ESP too so it have to work.

kefkevm commented 4 years ago

2019-11-19

the files are uploaded the program said. but my iphone dont see the wifi network of it.

HomeKidd commented 4 years ago

I’ve never seen this program!😳 Thats NOT the official Esptool by Espressif! Please use the method shown in the Wiki or follow the video i’ve linked in the second comment!

Which Wemos do you have? There are some clone ones and these requires QIO mode for flashing!

kefkevm commented 4 years ago

i downloaded the program here: https://www.espressif.com/en/support/download/other-tools

my wemos is 8266EX based, i have another wemos. 8266MOD. but it gives the same result. no wifi startup or anything.

kefkevm commented 4 years ago

with CMD same problem. cant upload the file. maybe i enter the wrong text in the cmd prompt?

I wrote this in my CMD;

esptool.py -p com4 --baud 115200 write_flash -fs 4MB -fm dio -ff 40m 0x0 rboot.bin 0x1000 blank_config.bin 0x2000 ledstrip.bin

because my wemos is com4 on my pc.

HomeKidd commented 4 years ago

Please upload picture of the command line after flashing is done!

Also the in the command the rboot.bin / blank_config.bin / ledstrip.bin needs to point to the directory where the files are located ( e.g. C:\your\path\to\the\file\ledstrip.bin)

Another thing to check: try it with other Wemos.

I've successfully flashed these bin files to brand new Wemos and its working properly, so it seem to be a hardware issue to me...

HomeKidd commented 4 years ago

Any update?

woainhinhi1314 commented 4 years ago

================================================================= Can connect to WIFI after refreshing but cannot connect to HomeKit,The following is the serial port display return information

HomeKit: Starting server !!! HomeKit: Failed to read flash magic HomeKit: Formatting flash at 0x100000 !!! HomeKit: Failed to erase flash HomeKit: Generated new accessory ID: 50:8D:56:7D:DB:CD !!! HomeKit: Failed to write accessory ID to flash HomeKit: Generated new accessory key !!! HomeKit: Failed to write accessory key to flash HomeKit: Configuring mDNS mDNS announcement: Name=HomeKid-9C361D-508D md=HomeKid NeoPixelpv=1.0id=50:8D:56:7D:DB:CDc#=1s#=1ff=0sf=1ci=5 sh=D+fTpg== Port=5556 TTL=4500 HomeKit: Got new client connection: 4 HomeKit: [Client 4] Pair Setup Step 1/3 HomeKit: [Client 4] Pair Setup Step 2/3 HomeKit: [Client 4] Pair Setup Step 3/3 !!! HomeKit: Failed to compact data: sector data read error !!! HomeKit: Failed to write pairing info to flash: max number of pairings !!! HomeKit: [Client 4] Failed to store pairing (code -2) HomeKit: [Client 4] Closing client connection

Key: 02182017

HomeKidd commented 4 years ago

@woainhinhi1314 Couple minutes ago my friend has the same issue.

When flashing the ESP please change the command according to Wiki page

The problem is HomeKit wants to erase flash sector that not exist when -fs set to 8m (or 1M) like in RavenCore! Change it to -fs 32m OR -fs 4M for 4MB flash size and it will solve the problem! 🤓

--baud 115200 write_flash -fs 32m -fm dio

@kefkevm is it working now?

woainhinhi1314 commented 4 years ago

=============================================================

@woainhinhi1314 Couple minutes ago my friend has the same issue.

When flashing the ESP please change the command according to Wiki page

The problem is HomeKit wants to erase flash sector that not exist when -fs set to 8m (or 1M) like in RavenCore! Change it to -fs 32m OR -fs 4M for 4MB flash size and it will solve the problem!

--baud 115200 write_flash -fs 32m -fm dio

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

========================================================================

When can I join the ws2812 blinking effect gradient?

kefkevm commented 4 years ago

no i dont know how i can point the files to directory location. i have been bussy last week, this is why my reaction is delayed

kefkevm commented 4 years ago

espknipsel1 espknipsel2

so far i am

HomeKidd commented 4 years ago

First things first: the erase command is went well. But the flashing is failed because Python doesnt find the esptool script as shown in the log output.

Second: theres the path to your files: C:\Users\Kevin\Downloads\

Try to run the command from where you first run it with the right path to the files:

C:\Users\Kevin\Downloads\rboot.bin

C:\Users\Kevin\Downloads\blank_config.bin

C:\Users\Kevin\Downloads\ledstrip.bin

B77863CD-ACA0-447F-94E5-06701F1BFF88

When the command runs as it should be you must see the log output as in Arduino (the Current state of flashing in %). Also if you open up Arduino serial monitor (115200 baud) you should see something in serial after succesfull flashing

53835DA6-7C6A-4F58-8369-8D71076A61BA

kefkevm commented 4 years ago

espknipsel3

I have done this, looks right to me but still see nothing in my network list. also arduino IDE dont gives me anything in his monitor.

HomeKidd commented 4 years ago

What flash size do you have? Because first: esptool doesnt print out the Current flash size, second: the flash params set to 0x1000 and 0x2000 but esptool writes it to 0x00001000 and 0x00002000🙄

Run --flash_size to detect it. Its seems to me that the flash size is more than 4Mb (16Mb like in Wemos D1 Pro)🙄 I’ve seen flash writing to 0x00001000 when i’ve used ESP32 with 16Mb flash

Also that i’ve spotted: It takes only 1.2 seconds to flash the ledstrip.bin.... with 115200 baud its takes me to 30-40 seconds so.... maybe - as i’ve mentioned it earlier - its a hardware issue!
You’ve said that it works with other bin files, so its seems to me that the required flash sector for HomeKit is corrupted. Could you try it with a new Wemos? Also change he flash mode from DIO to QIO that maybe works.

I’ve tested the bin files with 2 Wemos, 1 nodeMCU and 1 Custom ESP12F board and it works for me so the code is right and the .bin files are not corrupted.

kefkevm commented 4 years ago

weird, i tried 3 different wemos chips, 1 new wemos and one esp32. but still the same. 0x00001000 always displayed. do i have to change my windows settings maybe?

HomeKidd commented 4 years ago

Also change he flash mode from DIO to QIO that maybe works.

Only thing you can check is changing flash mode from DIO to QIO. But the 1.2 sec flashing is still too fast. Other thing is to download the bin files again! Also: download my BME280 code for checking these are working. Because 170 people made BME280 code work without any issues!

kefkevm commented 4 years ago

i downloaded the bin files again. now it is working!

HomeKidd commented 4 years ago

i downloaded the bin files again. now it is working!

It looks like the downloading doesnt finished properly. I was thinking about this too but i'm not mentioned this option 😄

I'll close the issue finally