Binary differences for ESP32 on this site.

All ESP32 boards running MicroPython.
Target audience: MicroPython users with an ESP32 board.
Post Reply
outsidewall
Posts: 7
Joined: Mon Apr 20, 2020 9:27 pm

Binary differences for ESP32 on this site.

Post by outsidewall » Sat Apr 24, 2021 7:40 pm

Hello,

What is the differences between the binary distributions for the ESP32 on this site?
I have read that the SPIRAM is an ESP32 with external ram, however I'm at loss what the differences are with the others.

Regards John

marcidy
Posts: 133
Joined: Sat Dec 12, 2020 11:07 pm

Re: Binary differences for ESP32 on this site.

Post by marcidy » Sun Apr 25, 2021 5:51 pm

Code: Select all

GENERIC : esp32-20210425-unstable-v1.15-13-g530c76f6c.bin
GENERIC : esp32-20210423-unstable-v1.15-4-g5669a6095.bin
GENERIC : esp32-20210423-unstable-v1.15-3-g00d6a79b3.bin
GENERIC : esp32-20210421-unstable-v1.15-2-g6e0f9b926.bin
GENERIC : esp32-20210420-unstable-v1.15.bin
GENERIC : esp32-20210419-unstable-v1.15.bin
GENERIC : esp32-20210418-v1.15.bin 
The filename parses as:

Code: Select all

<architecture>-<date compiled>-[stability]-<micropython release version>-[micropython minor version]-g[git commit].bin
So if you want to use (as opposed to test) micropython, use one that is not unstable and a release version, ie GENERIC : esp32-20210418-v1.15.bin
If you want to test upcoming release candidates, check unstable ones.

outsidewall
Posts: 7
Joined: Mon Apr 20, 2020 9:27 pm

Re: Binary differences for ESP32 on this site.

Post by outsidewall » Mon Apr 26, 2021 8:40 pm

Hello,

Thank you or your reply, I was also interested in the differences between

esp32-idf4 (builds)

and

esp32-20210418-v1.15.bin (builds)

Reason being it seems the non idf4 (builds) do not seem to have the umqtt module

Regards John

marcidy
Posts: 133
Joined: Sat Dec 12, 2020 11:07 pm

Re: Binary differences for ESP32 on this site.

Post by marcidy » Mon Apr 26, 2021 9:39 pm

idf4 is the version of the esp-idf that the firmware uses. previously 4 wasn't supported, and now it is, so I assume that is to mark the epoch for esp-idf 4 in 1.14 versions where the transition from 3.3 to 4 occurred. 1.15 uses esp-idf 4+ only, so no need to identify esp-idf versions in 1.15 micropython builds.

I don't use the mqtt module so not sure, i don't track it's movements.

If you aren't using a release version, there's likely to be changes while migrations occur. IF you need stability, stick to full releases (e.g. v1.14, v1.15, etc).

Post Reply