ESP32 Wroom32 Bluetooth no longer works

[stefan.erni]

Hi Ben

I used a nice working program and compieled to target.
After this, the computer can not found the BT device anymore.

[stefan.erni]

Hi Ben

After the last update from ESP32, a new project creates only a few files and no folders
That's an advantage and I like it.

But then Bluetooth SPP doesn't work anymore because I can't make a menu config.

And If menue config doesn't work, I can't make any clock settings either to save power set the clock from 240Mhz to 80Mhz

To build a portable device with the ESP32 both settings are important.


I suspect it is a problem from the last update.

b4 the update:

2024-10-10_09-22-28.PNG (39.57 KiB) Viewed 4187 times

after the update:

2024-10-10_09-21-40.PNG (36.65 KiB) Viewed 4187 times

the update:

2024-10-10_08-34-13.PNG (185.58 KiB) Viewed 4187 times

[medelec35]

Hi Stefan.
The new updates have made the ESP32 a lot better and quicker, especially if using the same target device but changing the project name.
When you compile for the very first time with your new target, a folder will be created within the ESP toolchain root directory.

With the new toolchain it will be within FC_ESP
look for a folder with the target name and you should be able to use the menuconfig for all your projects that use the same target, even if you have changed your project name.

For example I used lolin32 lite and the folder that is created for that target:

Esp32 target files.png (12.8 KiB) Viewed 4179 times

[mnfisher]

I haven't encountered this new layout - my attempt at the using new install failed. Might be a good thing though - will this break a lot of things? Adding espressif components such as LVGL / Camera or using modified CMakeLists.txt and partition tables etc?

I just use a 'vanilla' espressif install (now 5.3.1) which seems to work out of the box (everything default) and haven't noticed an issue using the new batch files (yet)?

I looked at the batch files - and not entirely sure I like the idea of having them all in the same place, but should be okay.

I still use command line compilation (idf.py -p COMn -b 921600 flash) which avoids (or avoided) the double export and also highlights errors rather more clearly

Martin

[medelec35]

Hi Martin.
The new layout should work for both existing and new toolchain, so long as its using our lasted batch files.
You might already know this, but I have mentioned it for forum members who don't know that.
The time saving to compile each new project (with the same target device) is amazing e.g less than 30 seconds vs multiple minutes, depending on PC, antivirus etc.

Ben might know more about the breaking side of things.

[stefan.erni]

Hi Martin

For me the new version is more comfortable with one folder for all ESP32s types.
Only configure correctly once and all the project are the same and the projectfolder folder are much smaller.

And:
Bluetooth is working nice again!

At the moment I can run all esp32 s with 240Mhz. But I have to run some at 80Mhz and others at 240Mhz. Later not yet now

I found the folder

2024-10-10_11-17-06.PNG (4.09 KiB) Viewed 4159 times

there is probably the same folder for all of these

2024-10-10_11-08-02.PNG (9.24 KiB) Viewed 4159 times

I will test it later on V5.31
Tested on:

Python 3.7.3
git version 2.21.0.windows.1
IDF Version: v5.0.6

[medelec35]

Hi Stefan,

At the moment I can run all esp32 s with 240Mhz. But I have to run some at 80Mhz and others at 240Mhz. Later not yet

Steve suggested:

having a custom batch file should be enough (one that creates a different folder for the compilation so it doesn’t interfere with the ‘normal’ compilation path.

The batch files (prog and build) would need to modify the following line:
@SET DOS_BUILD_DIR=%BASE_DIR%mtx%CONFIG%

To something like:
@SET DOS_BUILD_DIR=%BASE_DIR%mtx2%CONFIG%

(this is untested though)

I think he is on to something there as you could have:
@SET DOS_BUILD_DIR=%BASE_DIR%mtx80MHz%CONFIG%
&
@SET DOS_BUILD_DIR=%BASE_DIR%mtx240MHz%CONFIG%

Something to think about.