Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • ... but then if you really need to save power you don't use a dev board, or at least disable the parts you don't need on boot and desolder some leds?
    by nottorp
  • ESP32 never was good for any powersaving applications.
    by SuperMouse
  • As of the recent launch of the ESP32-S31, all the ESP32 product lines have been migrated to RISC-V.

    Unsurprisingly, the old, non-standard, encumbered architecture is not missed.

    by snvzz
  • I did something similar, but less scientific, comparing ESP-IDF and esp-hal (Rust). Unfortunately I learned that the optimizations that are already in ESP-IDF (most of all automatic light sleep between BLE advertisments) are hard to replicate in Rust/esp-hal/embassy and so for battery powered devices you might want to stick to C++/ESP-IDF
    by maufl
  • Hmm, those are some worrying news for Zephyr, but also for Linux. For reasons that escape my full understanding, a lot of embedded hardware needs Linux to work. If Zephyr, which I bet has been carefully crafted for microcontrollers, leaves some unnecessary things on, who knows what even an extremely trimmed down Linux running in, say, the beagle board, gets away with.
    by dsign
  • As an off-topic remark, I've used the qoitech arc power analyzer quite a bit and it's quite nice and easy to use, when your DUT is <5V and low amps. There's also the Nordic PPK2 kit, which is cheaper but I haven't tried it. Both are aiming at the crowd that prefers a simple, handles-most-use-cases, little USB-connected box that runs the client on your computer, rather than a separate bulky thing with screen and whatnot. Trade-offs of course though.
    by retSava

  •     It highlights that an idle loop in Arduino is energetically detrimental.
    That's not particularly uncommon. Many compilers or OSes default to wait loops when there's nothing to do, and they can be pretty power hungry.
    by dlcarrier
  • > execute instructions faster (via -O3)

    One problem with -O3 is that it disregards any effects of the cache (and yes, ESP32s have a bit of cache memory). I recommend using -Os as the default optimization level, as it often has the same or almost the same performance benefits as -O3. Less cache pressure is beneficial, especially for bigger applications, and the smaller code size is of course nice on embedded systems that have limited amounts of flash storage. If you know some specific functions or source files are performance sensitive, you can use pragmas to change optimization for those:

        #pragma GCC optimize("O3")
    See https://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-.... Clang has a similar pragma, see https://clang.llvm.org/docs/LanguageExtensions.html#extensio....
    by gsliepen

Explore Birbla archives

ESP32-C6 Power Consumption: Arduino vs. Zephyr vs. ESP-IDF Comparison · Birbla