Flashing went wrong #2
Comments
|
Looks like it either didn't flash properly or maybe to the wrong locations? That check box in the flashing config for donotchgbin can you try it in the opposite. I had a problem flashing myself using that method when I unchecked it worked. Maybe send the log file here too |
|
`*************************** START **************************** START TIME: 202206222156 CONNECT BAUD: 115200
|
|
Hmm yeah that looks right to me. I wonder if trying this flashing utility will work better. https://github.com/esphome/esphome-flasher/releases/tag/1.4.0 Or I wonder if just leaving the values at zero is correct for the offsets. Sounds like esptool uses them to override the binary programmed ones. I usually use platformio w/vscode to flash and monitor&upload if you have those installed can try it that way for now. Can take a look when I'm home tonight in more detail. |
|
And this is the result with the esphome-flasher: `ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) Brownout detector was triggered ets Jun 8 2016 00:22:57 rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) ` |
|
Well from that one it appears that the program is actually written on there and running. I can see some of the things I wrote in the log. But it looks like you have a power problem, there's a brown out detection listed in there and then it reboots. Are you still powered from USB or is this powered from the radio? FYI.. I gave it a try tonight and noticed I had the wrong connect commented out. Please try most recent commit from actions. Tested and it works both ways.. still some glitches sometimes when scanning that required a reboot. |
|
The board was powerd by the pc. `ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
|
Yes that looks correct. I get, Is what you should see when in Central Mode (Master/Bluetooth) You won't be able to see it in the NRF app unless it's in Peripherial mode, it defaults to Central Mode (Master/Bluetooth) until the radio calls for the change. We just got 2.8 working well with edgeTX PR# 2064. Seems to work with this code and the PARA okay. ... Still some issues, can crash the ESP if you switch modes back/forth sometimes. |
|
I don't know if you saw my previous comment but make sure your using the latest push from this repository, https://github.com/dlktdr/BTWifiModule/actions/runs/2546476341 I commented out the wrong line and you can't get a connection with the first one. |
|
yes I tooked the latest |
|
YES it works now, I see the channels from the BLE in my TX! |
|
I've to reconnect after power off - is it right?I've to discover. In model setup the connected field is empty. EDIT: Oops didn't mean to edit this post... but will leave my reply here for future --- ESP boards can be temperamental with their power. Some of those $5 boards have crap on them for power conditioning, I have 2 I got off amazon that are really sensitive to everything :( Won't even run from a PC power supply with extra filtering added after. |
|
Yes that's right in the current state. Have to work on this part still, it's commented out. Was causing a crash in some situations Line 606 in f6c66af |
|
I should also ask, what did you use to flash the software with on the second board. Should I be changing the Wiki, or does that method work for you? Since your the first one who has tried 💯without compiling in vscode .. That I know of.. |
|
I used the ESPHome-Flasher as the only one flasher for the second board. It could be better when you are changing the Wiki, for easy to use and minimize mistakes. |
I use this board:
I flash as ESP32 files from Node32s_Wroom32. Flashing finished, but in serial monitor I see this messages:
Whats wrong?
The text was updated successfully, but these errors were encountered: