Hi,
I found the root cause.
In the constructor I had and old debug print statement to Serial1.
For completeness, I have options
- USB support : None
- U(S)ART : Enabled (generic Serial)
Small sketch to reproduce the issue
#include "Arduino.h"
#include "srcWrapper.h"
class CommandHandler ...
Search found 6 matches
- Fri Nov 27, 2020 1:36 pm
- Forum: General discussion
- Topic: Use of global/static objects
- Replies: 7
- Views: 4908
- Wed Nov 25, 2020 3:04 pm
- Forum: General discussion
- Topic: Use of global/static objects
- Replies: 7
- Views: 4908
Re: Use of global/static objects
Yes, I can share but overall it is a complex one with combined esp/stm support.
Let me first try to make a minimal version of it by stripping and shortcutting.
Let me first try to make a minimal version of it by stripping and shortcutting.
- Wed Nov 25, 2020 2:38 pm
- Forum: General discussion
- Topic: Use of global/static objects
- Replies: 7
- Views: 4908
Re: Use of global/static objects
Try to define global the CommandHandler* commandHandler;
then do the new in the setup().
Initializing it that way is working OK.
The library is my own, I am using it extensive in my esp8266 & esp32 projects without the limitation of only "new in setup".
No big constructor either.
Trying to ...
- Wed Nov 25, 2020 1:49 pm
- Forum: General discussion
- Topic: Use of global/static objects
- Replies: 7
- Views: 4908
Use of global/static objects
LS,
Is there a limitation on the usage of static/global objects ?
When instantiating a global object from my local library the board freezes (both stm32f103 & stm32f411)'
Minimal sketch :
#include "CommandProcessing.h"
CommandHandler* commandHandler = new CommandHandler; -> Fails ...
Is there a limitation on the usage of static/global objects ?
When instantiating a global object from my local library the board freezes (both stm32f103 & stm32f411)'
Minimal sketch :
#include "CommandProcessing.h"
CommandHandler* commandHandler = new CommandHandler; -> Fails ...
- Fri Oct 16, 2020 9:40 am
- Forum: General discussion
- Topic: AttachInterrupt use for shared IRQ handlers
- Replies: 3
- Views: 8557
Re: AttachInterrupt use for shared IRQ handlers
Yes, agree on the PA0, PB0 interrupts.
On the interrupt handlers for multiple lines I still have the question.
Within esp8266/esp32, the core handles splitting the one interrupt handler into multiple for the application.
It loops over the attached lines and calls the right callback.
Is that also ...
On the interrupt handlers for multiple lines I still have the question.
Within esp8266/esp32, the core handles splitting the one interrupt handler into multiple for the application.
It loops over the attached lines and calls the right callback.
Is that also ...
- Thu Oct 15, 2020 11:03 am
- Forum: General discussion
- Topic: AttachInterrupt use for shared IRQ handlers
- Replies: 3
- Views: 8557
AttachInterrupt use for shared IRQ handlers
Hi,
I am new to STM32 but have experience with arduino framework in using esp8266 & esp32.
Using now a stm32f411ce
Question here is about interrupts/attachinterrupt.
I have read https://stm32f4-discovery.net/2014/08/stm32f4-external-interrupts-tutorial/
This states : 16 interrupt lines but only 7 ...
I am new to STM32 but have experience with arduino framework in using esp8266 & esp32.
Using now a stm32f411ce
Question here is about interrupts/attachinterrupt.
I have read https://stm32f4-discovery.net/2014/08/stm32f4-external-interrupts-tutorial/
This states : 16 interrupt lines but only 7 ...