mbed-os

Author SHA1 Message Date

Author	SHA1	Message	Date
Andreas Rebert	01d06a9f51	LPC4088: Fix hardfault occuring after power-cycle Since revision `5499db1` (mbed-os-5.6.0) a hardfault occurs after a power-cycle. It doesn't occur after a reset when the application has been downloaded using drag-and-drop or via debugger. This is probably the reason why this problem isn't detected when testing new mbed releases. The hardfault occured in hal_sleep(). Adding a __NOP after __WFI solves the problem although I don't fully understand why. - Revision `ca661f9` is the last revision where the problem doesn't occur. - The problem doesn't occur when compiling with GCC instead of ARM compiler - This issue describes a similar, but not identical problem and led me to test adding a __NOP: https://github.com/ARMmbed/mbed-os/issues/5065	2018-04-11 11:13:43 +02:00
Bartek Szatkowski	6a045a49a9	Platform: Add sleep/deepsleep user facing functions Add sleep/deepsleep functions to platform layer which are replacing HAL functions with the same name, rename existing symbols in HAL layer to hal_sleep/hal_deepsleep. This way sleep functions are always available, even if target doesn't implement them, which makes the code using sleep clearer. It also enables us to make decision on in which builds (debug/release) the sleep will be enabled.	2017-01-19 09:39:29 +00:00
Christopher Haster	0bad622a16	restructure - Moved targets out to top level hal/targets -> targets hal/targets.json -> targets/targets.json	2016-09-30 19:18:09 -05:00

Andreas Rebert

LPC4088: Fix hardfault occuring after power-cycle

Since revision 5499db1 (mbed-os-5.6.0) a hardfault occurs after a power-cycle.
It doesn't occur after a reset when the application has been downloaded using
drag-and-drop or via debugger. This is probably the reason why this problem
isn't detected when testing new mbed releases.

The hardfault occured in hal_sleep(). Adding a __NOP after __WFI solves the
problem although I don't fully understand why.

- Revision ca661f9 is the last revision where the problem doesn't occur.
- The problem doesn't occur when compiling with GCC instead of ARM compiler
- This issue describes a similar, but not identical problem and led me to test adding a __NOP: https://github.com/ARMmbed/mbed-os/issues/5065

2018-04-11 11:13:43 +02:00

Bartek Szatkowski

6a045a49a9

Platform: Add sleep/deepsleep user facing functions

Add sleep/deepsleep functions to platform layer which are replacing HAL
functions with the same name, rename existing symbols in HAL layer
to hal_sleep/hal_deepsleep. This way sleep functions
are always available, even if target doesn't implement them, which makes
the code using sleep clearer. It also enables us to make decision on in
which builds (debug/release) the sleep will be enabled.

2017-01-19 09:39:29 +00:00

Christopher Haster

0bad622a16

restructure - Moved targets out to top level

hal/targets -> targets
hal/targets.json -> targets/targets.json

2016-09-30 19:18:09 -05:00

3 Commits (244d4b640543b23c94ac84e5301d6c12afc8e15a)