I think the issue here is that GPIO12 has a very high pull-up (100K) plus what I assume is a fairly large parasitic capacitance from whatever is connected to the connector GPIO12 leads up to (plus the connector and traces themselves, obviously). The monitor doesn't do anything with GPIOs, all it doe...

Chegewara is right. Additionally, code run within a critical section more-or-less has the same restrictions as code running in an IRQ, that is, it should not (directly or indirectly) call any blocking functions.

What power supply are you using?

Well, it's not a package, it's a component. I'm far from an expert on CMake, but from what I understand you would add it like this: as described here

What is your current code now? I kind-of lost track during the thread... In general, the idea of a semaphore is to only trigger the semaphore during the IRQ (as you're not allowed to do much more, as blocking functions like printf() won't work in an interrupt context) and then have a task waiting on...

Nothing much to explain... It's a small chip that makes sure the ESP32 is reset properly even if the power supply voltage is too wonky for the internal reset logic to properly do it. There's more information on the Internets, if you need it.

You mean the standard in general? The only legal source I know of is the MIPI Alliance, who will happily give you a standard as soon as you become a member. Yes, I know it's not the most convenient or cheap way to get the standard, but as far as I know it's the only *legal* way to do so, and as an a...

What you have is a flavour of the (non-S2) ESP32. All ESP32 chips have a designation (like U4WHD) after their 'ESP32' identifier; the meaning is in chapter 7 (Part number and ordering information) of the datasheet . indicating packaging, binning and configuration of the silicon. In your case, your c...

PeterR wrote: ↑

Thu Jul 09, 2020 5:34 pm

It is interesting that the EVB uses GPIO0 for all the problems this can cause.
I use GPIO0 so I cannot tell you!

A possible reason is that GPIO17 is used by PSRAM on modules/boards that have it.

@PeterR: Nothing wrong with the general concept of starting multiple tasks for multiple sensors, even if they're on the same I2C bus, even with only two cores. While it probably does not make much sense from a performance PoV, if that's the way you like to write your code and it fits the performance...