I'd advise to:
- check the return value from radio.begin() (https://nrf24.github.io/RF24/classRF24.html#a048a20c73c7d9b2e02dcbae6fb9c4ba8)
- try to explicitly specify the SPI pins (e.g. https://github.com/stm32duino/wiki/wiki/API#change-default-spi-instance-pins)
- check the Nucleo pins you are ...
Search found 8 matches
- Sun Jun 20, 2021 9:09 am
- Forum: General discussion
- Topic: L432KC and NRF24L01
- Replies: 3
- Views: 2668
- Sat Jun 19, 2021 9:30 am
- Forum: General discussion
- Topic: diagnosing LowPower.deepSleep() behaviour
- Replies: 3
- Views: 3659
Re: diagnosing LowPower.deepSleep() behaviour
The workaround seems to be using LSE as a clock source for the RTC:
#include <STM32LowPower.h>
STM32RTC& rtc = STM32RTC::getInstance();
void setup() {
pinMode(PA10, OUTPUT);
// with LSE as a clock source, the MCU wakes up from deepSleep() as expected
rtc.setClockSource(STM32RTC::LSE_CLOCK ...
#include <STM32LowPower.h>
STM32RTC& rtc = STM32RTC::getInstance();
void setup() {
pinMode(PA10, OUTPUT);
// with LSE as a clock source, the MCU wakes up from deepSleep() as expected
rtc.setClockSource(STM32RTC::LSE_CLOCK ...
- Sat Jun 19, 2021 9:14 am
- Forum: General discussion
- Topic: diagnosing LowPower.deepSleep() behaviour
- Replies: 3
- Views: 3659
Re: diagnosing LowPower.deepSleep() behaviour
Thanks for you suggestion @mebab. There is a small delay already provisioned for in LowPower_stop() (called from LowPower.deepSleep()) - https://github.com/stm32duino/Arduino_C ... wer.c#L246
- Thu Jun 17, 2021 3:32 pm
- Forum: General discussion
- Topic: diagnosing LowPower.deepSleep() behaviour
- Replies: 3
- Views: 3659
diagnosing LowPower.deepSleep() behaviour
I'm trying to diagnose a strange deepSleep() behaviour on a custom designed PCB with STM32L412KBT6 with LSE. After a power up, the MCU deepSleeps/wakes up normally for 2-3 minutes, but after 2-3 minutes, the wake up does not happen.
Test setup:
- A single led is connected through a current limiting ...
Test setup:
- A single led is connected through a current limiting ...
- Tue Mar 23, 2021 5:12 pm
- Forum: General discussion
- Topic: [SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
- Replies: 6
- Views: 3972
Re: [SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
After updating STLink from V3J2M1 to V3J2M3 Mass Storage update method also works, thanks again @fpiSTM!
- Tue Mar 23, 2021 3:50 pm
- Forum: General discussion
- Topic: [SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
- Replies: 6
- Views: 3972
Re: code for Nucleo G431KB does not run with binary code size > ~65140 bytes
You can also take a look at the .map in the build directory to see if anything looks strange.
Thanks mlundin , I'm periodically running "arm-none-eabi-nm --size-sort" on the binary but there's not much I can quickly shave off at the moment for the code I'm working on. The sketch reproducing the ...
- Tue Mar 23, 2021 3:42 pm
- Forum: General discussion
- Topic: [SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
- Replies: 6
- Views: 3972
Re: code for Nucleo G431KB does not run with binary code size > ~65140 bytes
Thanks @fpiSTM, STM32Cube Programmer (SWD) as upload method nicely works as expected.
- Tue Mar 23, 2021 10:25 am
- Forum: General discussion
- Topic: [SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
- Replies: 6
- Views: 3972
[SOLVED] code for Nucleo G431KB does not run with binary code size > ~65140 bytes
Code with binary size larger than approximately 65140 bytes does not work on Board Nucleo-32 with Board Part Number: "Nucleo G431KB". Forum search did not yield any results. I've reproduced the behaviour with Serial to make the steps to reproduce easier.
Steps to reproduce:
1. Unzip the attached ...
Steps to reproduce:
1. Unzip the attached ...