Closed joncutting closed 2 years ago
Wich core are you using? Roger Clark or ST core?
Thanks!
It’s the ST core 2.2
On Tue, Jan 4, 2022 at 2:46 PM Naguissa @.***> wrote:
Wich core are you using? Roger Clark or ST core?
Thanks!
— Reply to this email directly, view it on GitHub https://github.com/Naguissa/uTimerLib/issues/16#issuecomment-1005193977, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFSOLD3ALDWMXO3HZC7BMV3UUNTC3ANCNFSM5LINB7SQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
--
Jonathan Cutting @.***
Solved on new 1.7.0 release, https://github.com/Naguissa/uTimerLib/releases/tag/1.7.0
Cheers!
uTimerLib.h line 150 references
_VARIANT_ARDUINO_STM32_
and this is for some reason not defined when I use Nucleo32 / NucleoG031K8, so the library compile borks because it doesn't know anything about Timer3.As a workaround I created a platform.local.txt file with a single line
compiler.extra_flags=-mcpu={build.mcu} {build.flags.fp} -DUSE_FULL_LL_DRIVER -D_VARIANT_ARDUINO_STM32_ -mthumb "@{build.opt.path}"
To clean this up I would suggest to use
ARDUINO_ARCH_STM32
instead of_VARIANT_ARDUINO_STM32_
.