winbond SPIFlash.h define for delayMicroseconds(us)

fatal error: util/delay.h: No such file or directory

#include <util/delay.h>

I discover in SPIFlash.h the line where is defined for esp but not for STM32F103C

#if defined (ARDUINO_ARCH_SAM) || defined (ARDUINO_ARCH_SAMD) || defined (ARDUINO_ARCH_ESP8266) || defined (STM ????? )
#define _delay_us(us) delayMicroseconds(us)
#else
#include <util/delay.h>
#endif

So what is the correct defined for STM32F103C because i try many variants?… Thanks for your monumental work , the STM is moore accesible for the entire world!

#if defined(_VARIANT_ARDUINO_STM32_)


#if defined (ARDUINO_ARCH_SAM) || defined (ARDUINO_ARCH_SAMD) || defined (ARDUINO_ARCH_ESP8266) || defined(__STM32F1__)

Now see if my project with load binary from sdcard to winbond BIOS work .On arduino pro mini time to loading was 45minutes…

#if defined (ARDUINO_ARCH_SAM) || defined (ARDUINO_ARCH_SAMD) || defined (ARDUINO_ARCH_ESP8266) || defined(__STM32F1__)

Now see if my project with load binary from sdcard to winbond BIOS work .On arduino pro mini time to loading was 45minutes…

The reason we use __STM32F1__ is because its auto-generated by the Arduino IDE, because of the core is in a folder called STM32F1.

i could add ARDUINO_ARCH_STM32F1 as well I suppose, if this is the new standardised way of defining the architecture name, but I am not sure how that would effect the libraries.
( I think __STM32F1__ will still be defined by the IDE unless they changed something in the IDE recently)

The reason we use __STM32F1__ is because its auto-generated by the Arduino IDE, because of the core is in a folder called STM32F1.

i could add ARDUINO_ARCH_STM32F1 as well I suppose, if this is the new standardised way of defining the architecture name, but I am not sure how that would effect the libraries.
( I think __STM32F1__ will still be defined by the IDE unless they changed something in the IDE recently)

Looks like the ARDUINO_ARCH stuff was there from the start (well, ages ago)

So long ago I don’t remember.

I’d need to double check if __STM32F1__ was originally auto generated, I thought was, but I could be wrong

ARDUINO_ARCH_AVR – Arduino AVR (Uno, nano, etc). ATMega based
ARDUINO_ARCH_SAM – Arduino SAM32 (Due)
ARDUINO_ARCH_SAMD – No idea, picked from previous post.
ARDUINO_ARCH_STM32F1 – STM32 F1 variant (Maple mini, etc)
ARDUINO_ARCH_STM32F3 – STM32 F2 variant (F3Discovery, etc)
ARDUINO_ARCH_STM32F4 – STM32 F4 variant (Netduino2, etc)
ARDUINO_ARCH_ARM – ARM boards
ARDUINO_ARCH_ESP8266 – ESP8266 boards (ESP01, NodeMCU, etc)

Open list in spanish: https://www.foroelectro.net/electronica … -t144.html

I think SAMD is the Arduino Zero

[Naguissa – Fri Mar 17, 2017 7:18 am] –
I was digging about Arduino IDE arches an now I’ve got:

ARDUINO_ARCH_AVR – Arduino AVR (Uno, nano, etc). ATMega based
ARDUINO_ARCH_SAM – Arduino SAM32 (Due)
ARDUINO_ARCH_SAMD – No idea, picked from previous post.
ARDUINO_ARCH_STM32F1 – STM32 F1 variant (Maple mini, etc)
ARDUINO_ARCH_STM32F3 – STM32 F2 variant (F3Discovery, etc)
ARDUINO_ARCH_STM32F4 – STM32 F4 variant (Netduino2, etc)
ARDUINO_ARCH_ARM – ARM boards
ARDUINO_ARCH_ESP8266 – ESP8266 boards (ESP01, NodeMCU, etc)

Open list in spanish: https://www.foroelectro.net/electronica … -t144.html

I want to resurrect this topic to add one extra useful define:

_VARIANT_ARDUINO_STM32_ – STM32 boards, all variants

Also update from Roger:

ARDUINO_ARCH_SAMD – SAMD boards (Arduino Zero and MKR1000)