Arduino for STM32

my 2 cents:
1. nothing can be of no delay.
2. arrays need to be referenced.
3. may want to code the numbers (20 or 2) as macros or part of a struct so the users can reconfigure the library easily for his/her applications.
4. may want to remove the uart print out of the library.

It is impossible and unnecessary to have your original ask ("changing pin states on different ports at the same time").

It is possible and depending on the spec, to change the pin state on different ports sufficiently fast.

Understanding the timing on the software is key

It isn't always worth it to have a genuine chip.

this is less of an issue on the actual code but the approach to coding. I would suggest that you think about the key building blocks of what you are trying to do, and then figure out how to integrate the code. I would divide the code into 1) read the probe; 2) convert that probe reading into a duty ...

Here's my sketch, maybe I'm missing something? maybe you want to change the way you write your code. I would do something like this. //update the display if (millis() - timer_display > PR_DISPLAY) { timer_display += PR_DISPLAY; //advance to the next update point //update the display update_display(...

as others have mentioned, you need to help others to help you - a difficult spot to be in. short of that, two observations: 1. whether that particular loop works depends on many factors, including the initial value of "timer" and its type. 2. unstable control loop is often due to too much ...

it is fun to rig up anything. microchip has a good an on crystal oscillators: https://ww1.microchip.com/downloads/en/AppNotes/00826a.pdf you may also check out the si part I mentioned earlier - si5351. it is widely available with ready-made pcbs. you will also find arduino libraries made for it. a g...

with that said, modern HSIs are fairly accurate / very accurate. I am running UARTs off HSI at 115K2bps all day long. I think between accurate HSI, factory calibration, and user-trimming, HSIs can cover most of the use cases. HSEs still hold an advantage in terms of timing stability, however. so if ...

if you want to use HSE, a few options. 1. find a chip that supports HSE. F0 or PY32 for example. 2. if space is a constraint, use an external oscillator (crystal or mems - less accurate), or small foot-print clock generator. 3. if space isn't a constraint, something like HC4060, or even a STM32F103 ...

what about 3n502?

I have used a part that's similar to cdce937 but with only 2 pll outputs. fairly easy to program (i2c).