Arduino for STM32

Sorry for posting this a few months later, but I just wanted to note that I have deprecated the use of the AHT10 in the STM32 GPSDO project and I now recommend the use of the AHT20 instead of the AHT10, basically because it costs essentially the same and is slightly more accurate. The AHT10 and ...

Hello,

You can see here our GPSDO from SYRLINKS.
They use STM32

https://time-frequency.syrlinks.com/gnss-timing-modules/

Cyril BOISSY
Syrlinks


Hello Cyril,
Very nice GPSDOs and the low power consumption is quite unique. Thank you for mentioning your products, and that they use STM32 MCUs. I ...

Unfortunately I didn't read this topic before ordering 5 x LM35DZ from a vendor on AliExpress. Of course I got a bunch of fake ones... :x
As far as I can tell they are just NPN transistors.
I opened a dispute and was promptly refunded.
And yes I am amazed that scammers will go as far as re-marking ...

Efficiency is a measure of processing performance divided by average power consumption and so is rather irrelevant for peak power consumption. As for disabling cores, this raises more questions than it answers, imo.

Again, the RPi Zero 2 W specs all look good/acceptable considering its tiny size ...

Unfortunately for any SBC you have to size your power supply for peak (not average) power consumption. So having a tiny SBC with a relatively large peak power requirement of 5V@2.5A kind of defeats the whole purpose of the small size.

Indeed when one reads the specs for the Raspberry Pi Zero 2 W, everything looks dandy, until one gets to the power requirements: 5V @ 2.5A! :o

Uhhh, What? Yes: 5V @ 2.5A . And that's a pity, because with a lower power consumption this RPi Zero 2 W could have found a home in a much larger number of ...

The AHT10 humidity sensor has the problem that only one device of it can be connected with an I2C bus.
This is remarked in the datasheet.
...


STrange:
1. I have been using an AHT10 with other I2C devices on the same I2C bus for months now.
2. I cannot find any mention of "the problem that only ...

...
I do not have any constraint of the analogRead() delay from timer interrupt to aquisition,
...


Unfortunately I have that exact constraint: I must read the ADC within a narrow time window of 2µS +/-500ns after the interrupt. So that really determines three things:
1. Reading the ADC channel ...

It is a bad idea to use analogRead in an ISR.
As it configures, calibrate, process, wait for result and deinit. Too long for an isr and no interrupt is not disabled .
In that case you need to implement manually using ll for example.
You can refers to F4 example:
https://github.com ...

...
I need to read an analog value from inside an Interrupt Service Routine ...


NO YOU DO NOT ...

Simply set a bool flag (global) and read the analog value in your main (loop{} ) or any called function.

...


As I wrote, I have the constraint that I must read the ADC within a narrow time ...