Skip to content

Blinky doesn't work when using develop/release profile with external power #5070

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MarceloSalazar opened this issue Sep 11, 2017 · 4 comments

Comments

@MarceloSalazar
Copy link

MarceloSalazar commented Sep 11, 2017

Description


Bug

Target
u-blox-EVK-NINA-B1

Toolchain:
GCC_ARM

gcc 6.3.1

mbed-cli version:
1.2.0

mbed-os sha:
mbed OS 5.5.6 (98ba8ac)

DAPLink version:
243

Expected behavior
Blinky should just work fine with all profiles (debug, release, develop), regardless of whether you use the USB port or external power supply.

Actual behavior
Blinky doesn't work when using the develop and release profiles with external power supply of the NINA B1 platform. It does work well with the debug profile.
It seems the system goes to sleep and never wakes up.

This has been found when working with @NeilMacMullen and @pan-

@ghost
Copy link

ghost commented Sep 13, 2017

@MarceloSalazar : can you try the current master branch of mbed-os?

@MarceloSalazar
Copy link
Author

I've tried Blinky with mbed-os-5.6.0-rc1 and can see this working on NINA when using release/develop profiles.

@NeilMacMullen could you give it a try on your custom platform and confirm?

@pan-
Copy link
Member

pan- commented Sep 15, 2017

#5086 will also help new targets to avoid this issue in the future.

@MarceloSalazar
Copy link
Author

Confirmed it's solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants