Closed
Description
Description
Target: DISCO_L475VG_IOT01A
Toolchain: GCC_ARM 6.3.1 20170620 (release)
mbed-cli: 1.10.0
mbed-os: f60e9a8075 (HEAD, tag: mbed-os-5.14.0-rc2, origin/mbed-os-5.14) Merge pull request #11476 from ARMmbed/release-candidate
Steps to reproduce:
- Create new project with
mbed new - Checkout mbed-os-5.14.0-rc2
- Add below to main.cpp (https://os.mbed.com/docs/mbed-os/development/tutorials/power-optimization.html)
#include "mbed.h"
#include "mbed_stats.h"
static DigitalOut led(LED1);
int main() {
while (1) {
led = !led;
wait_ms(2000);
mbed_stats_cpu_t stats;
mbed_stats_cpu_get(&stats);
printf("Uptime: %llu ", stats.uptime / 1000);
printf("Sleep time: %llu ", stats.sleep_time / 1000);
printf("Deep Sleep: %llu\n", stats.deep_sleep_time / 1000);
}
}
- Add
MBED_SLEEP_TRACING_ENABLEDto mbed_app.json macros. - Build with
mbed compile --target DISCO_L475VG_IOT01A --toolchain GCC_ARM --clean
Log output:
Below message is printed in a loop.
++ MbedOS Error Info ++
Error Status: 0x80010133 Code: 307 Module: 1
Error Message: Mutex: 0x2000267C, Not allowed in ISR context
Location: 0x8001FC1
Error Value: 0x2000267C
Current Thread: �0� Id: 0x0 Entry: 0x8002245 StackSize: 0x0 StackMem: 0x80039F5 SP: 0x10000490
For more info, visit: https://mbed.com/s/error?error=0x80010133&tgt=DISCO_L475VG_IOT01A
-- MbedOS Error Info --
= System will be rebooted due to a fatal error =
= Reboot count(=134268113) reached maximum, system will halt after rebooting
The message it self says the system will be halted, but that doesn't seem to happen.
Issue request type
[ ] Question
[ ] Enhancement
[x] Bug