[Bug]: ESP32 goes into error after uploading VS CODE about firmware HOT 18 CLOSED

Yes there is a regression on the original ESP32 that is not present on the S3 based devices which are working fine on the new framework. We will hunt down a resolution before a new release, but as of now, master is not working for these devices.

from firmware.

I don't have problem with ESP32 and that firmware. Tested build and upload via VSCode on old Heltec V2 and newer Heltec V3.

Could you try to upload firmware.factory.bin via esptool?

from firmware.

Is there anymore info you can give us?

• Can you describe the process you've been using to build / flash the firmware?
• Do you know which variant you're compiling for?
• Have you customized the code in any way?
• What hardware are you using? How is it wired?

The more info, the better. Never know what will be helpful.

from firmware.

I downloaded from git fw to the VS Code folder.
I choose "default_envs = meshtastic-diy-v1" or "default_envs = nano-g1-explorer" both have ESP32 and without any change I compile and upload to ESP32. (ESP+OLED+RA-01SH) via the web it works, I just have to change the code because of the RA-01SH)

I tried uploading through esptool and also the same error.

from firmware.

Just checking: have you seen this page before? https://meshtastic.org/docs/development/firmware/build/
Sorry if I'm repeating info you've already seen. Just want to make sure!

from firmware.

If you use DIY, how do you specify the ESP32 variant?

from firmware.

Yes, the problem may be that it sets me as a bad ESP32, but I don't know where to set a type?
And what exactly to set?

from firmware.

Yes, the problem may be that it sets me as a bad ESP32, but I don't know where to set a type?
And what exactly to set?

If you follow the official instructions, it tells you how to set a type, or how to make a diy type.

from firmware.

Ok, I'll try to make a new board. But on the website it was enough to use DIY v1. I also found out that there is no esp32dev.json file created for ESP32 dev in the boards, so I will try to create it and set the parameters in it.

from firmware.

But on the website it was enough to use DIY v1

Oh, I didn't read this part close enough, sorry.

If you use "DIY V1" with https://flasher.meshtastic.org, then it works? Is that correct?

Can we try this fresh, from the very start with no changes? First want to check that it's possible to use DIY V1 with VS Code

Instead of setting default_env, maybe it's easier to select like this:

Then you can click this button to build the firmware and upload it to your device:

Is this the same technique you have already tried?
I think it's good to try a simple test like this first, without any code changes for RA-01SH.

from firmware.

I tried again on the website and the device started up. Then I tried the same bin file with esptool and it also worked.
I then downloaded firmware-master again and selected "meshtastic-diy-v1" again and the same ESP32 error still reboots with the same error. I tried uploading the same generated file "firmware.factory.bin" via esptool and also the same error.

from firmware.

I tried to open another ESP32 project and upload it normally and it works through VS Code.

from firmware.

Is it okay to see fullscreen screenshots instead? Especially when you are using VS Code, there might be some other clue available there.

I see that when you use the web flasher, you select 2.3.6. I think right now you are probably building the newest version, instead of 2.3.6? Maybe it's good to test if it's possible to build 2.3.6 with VS Code. This might show whether the difference is because of different firmware versions, or whether it's different when you use VS Code.

You can select v2.3.6 in VS Code like this:

from firmware.

So version 2.3.6.7 works even through VS Code!!!

from firmware.

Interesting! Does 2.3.10 work? If yes, then we know the issue is quite new, and maybe know where to look.

from firmware.

A suggestion just now from @caveman99: can you please try change the VS Code version from 2.3.6 back to "master", then use "Erase Flash", and then upload?

from firmware.

Hi,

While working on adding keypad support for the Chatter, I think I encountered a problem related to this issue (#2896)
I was building and flashing with VSCode, and everything was working properly but when I tried to pull the latest master (from a12b992 to 2233507) in order to submit a merge request, the same code makes the Chatter (it's esp32 based) bootloop.

I reverted all my changes and the current master doesn't works for me on the Chatter
I tried erasing the flash and flashing again to no avail

I'm suspecting something happened with this commit 0c9da9a

from firmware.

fixed in 2.3.11 firmware release

from firmware.