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

STM32 Low Power Timer feature updates #5459

Merged
merged 8 commits into from Dec 12, 2017

Conversation

Projects
None yet
5 participants
@jeromecoutant
Contributor

jeromecoutant commented Nov 8, 2017

Description

Updates done after several internal tests.

Status

READY

Test

RTC and LPT tests have been checked for all STM32 families

#5106 updates have also been verified

@jeromecoutant

This comment has been minimized.

Contributor

jeromecoutant commented Nov 8, 2017

| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_drivers-lp_timeout | OK | 62.38 | default |
| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_drivers-lp_timer | OK | 21.82 | default |
| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_drivers-rtc | OK | 26.83 | default |
| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_hal-lp_ticker | OK | 25.4 | default |
| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_hal-lp_us_tickers | OK | 18.1 | default |
| NUCLEO_F091RC-ARM | NUCLEO_F091RC | tests-mbed_hal-rtc_time | OK | 75.19 | default |
| NUCLEO_F103RB-ARM | NUCLEO_F103RB | tests-mbed_drivers-rtc | OK | 27.3 | default |
| NUCLEO_F103RB-ARM | NUCLEO_F103RB | tests-mbed_hal-lp_us_tickers | OK | 17.27 | default |
| NUCLEO_F103RB-ARM | NUCLEO_F103RB | tests-mbed_hal-rtc_time | OK | 43.21 | default |
| NUCLEO_F207ZG-ARM | NUCLEO_F207ZG | tests-mbed_drivers-rtc | OK | 25.94 | default |
| NUCLEO_F207ZG-ARM | NUCLEO_F207ZG | tests-mbed_hal-lp_us_tickers | OK | 15.76 | default |
| NUCLEO_F207ZG-ARM | NUCLEO_F207ZG | tests-mbed_hal-rtc_time | OK | 26.58 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_drivers-lp_timeout | OK | 62.35 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_drivers-lp_timer | OK | 22.0 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_drivers-rtc | OK | 26.68 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_hal-lp_ticker | OK | 25.38 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_hal-lp_us_tickers | OK | 17.89 | default |
| NUCLEO_F303ZE-ARM | NUCLEO_F303ZE | tests-mbed_hal-rtc_time | OK | 40.61 | default |
| NUCLEO_F446RE-ARM | NUCLEO_F446RE | tests-mbed_drivers-lp_timer | OK | 20.76 | default |
| NUCLEO_F446RE-ARM | NUCLEO_F446RE | tests-mbed_drivers-rtc | OK | 26.01 | default |
| NUCLEO_F446RE-ARM | NUCLEO_F446RE | tests-mbed_hal-lp_ticker | OK | 24.63 | default |
| NUCLEO_F446RE-ARM | NUCLEO_F446RE | tests-mbed_hal-lp_us_tickers | OK | 17.04 | default |
| NUCLEO_F446RE-ARM | NUCLEO_F446RE | tests-mbed_hal-rtc_time | OK | 23.31 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_drivers-lp_timeout | OK | 60.68 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_drivers-lp_timer | OK | 20.4 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_drivers-rtc | OK | 25.77 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_hal-lp_ticker | OK | 24.19 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_hal-lp_us_tickers | OK | 16.41 | default |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | tests-mbed_hal-rtc_time | OK | 20.14 | default |
| NUCLEO_L073RZ-ARM | NUCLEO_L073RZ | tests-mbed_drivers-lp_timer | OK | 24.27 | default |
| NUCLEO_L073RZ-ARM | NUCLEO_L073RZ | tests-mbed_drivers-rtc | OK | 29.41 | default |
| NUCLEO_L073RZ-ARM | NUCLEO_L073RZ | tests-mbed_hal-lp_ticker | OK | 27.7 | default |
| NUCLEO_L073RZ-ARM | NUCLEO_L073RZ | tests-mbed_hal-lp_us_tickers | OK | 20.48 | default |
| NUCLEO_L073RZ-ARM | NUCLEO_L073RZ | tests-mbed_hal-rtc_time | OK | 100.43 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_drivers-lp_timeout | OK | 62.99 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_drivers-lp_timer | OK | 22.01 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_drivers-rtc | OK | 26.94 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_hal-lp_ticker | OK | 25.49 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_hal-lp_us_tickers | OK | 18.36 | default |
| NUCLEO_L152RE-ARM | NUCLEO_L152RE | tests-mbed_hal-rtc_time | OK | 60.54 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_drivers-lp_timeout | OK | 61.59 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_drivers-lp_timer | OK | 21.01 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_drivers-rtc | OK | 26.12 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_hal-lp_ticker | OK | 24.82 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_hal-lp_us_tickers | OK | 17.42 | default |
| NUCLEO_L432KC-ARM | NUCLEO_L432KC | tests-mbed_hal-rtc_time | OK | 33.57 | default |
| NUCLEO_L476RG-ARM | NUCLEO_L476RG | tests-mbed_drivers-lp_timer | OK | 21.28 | default |
| NUCLEO_L476RG-ARM | NUCLEO_L476RG | tests-mbed_drivers-rtc | OK | 26.1 | default |
| NUCLEO_L476RG-ARM | NUCLEO_L476RG | tests-mbed_hal-lp_ticker | OK | 24.97 | default |
| NUCLEO_L476RG-ARM | NUCLEO_L476RG | tests-mbed_hal-lp_us_tickers | OK | 17.36 | default |
| NUCLEO_L476RG-ARM | NUCLEO_L476RG | tests-mbed_hal-rtc_time | OK | 32.06 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_drivers-lp_timeout | OK | 61.84 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_drivers-lp_timer | OK | 20.98 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_drivers-rtc | OK | 26.21 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_hal-lp_ticker | OK | 24.84 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_hal-lp_us_tickers | OK | 17.22 | default |
| NUCLEO_L496ZG-ARM | NUCLEO_L496ZG | tests-mbed_hal-rtc_time | OK | 32.2 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_drivers-lp_timeout | OK | 58.67 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_drivers-lp_timer | OK | 18.5 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_drivers-rtc | OK | 23.57 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_hal-lp_ticker | OK | 22.21 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_hal-lp_us_tickers | OK | 14.63 | default |
| DISCO_F413ZH-ARM | DISCO_F413ZH | tests-mbed_hal-rtc_time | OK | 26.41 | default |
| DISCO_F429ZI-ARM | DISCO_F429ZI | tests-mbed_drivers-rtc | OK | 23.52 | default |
| DISCO_F429ZI-ARM | DISCO_F429ZI | tests-mbed_hal-lp_us_tickers | OK | 14.66 | default |
| DISCO_F429ZI-ARM | DISCO_F429ZI | tests-mbed_hal-rtc_time | OK | 21.29 | default |
| DISCO_F469NI-ARM | DISCO_F469NI | tests-mbed_drivers-lp_timer | OK | 18.47 | default |
| DISCO_F469NI-ARM | DISCO_F469NI | tests-mbed_drivers-rtc | OK | 23.26 | default |
| DISCO_F469NI-ARM | DISCO_F469NI | tests-mbed_hal-lp_ticker | OK | 22.15 | default |
| DISCO_F469NI-ARM | DISCO_F469NI | tests-mbed_hal-lp_us_tickers | OK | 14.59 | default |
| DISCO_F469NI-ARM | DISCO_F469NI | tests-mbed_hal-rtc_time | OK | 20.72 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_drivers-lp_timeout | OK | 59.12 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_drivers-lp_timer | OK | 18.58 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_drivers-rtc | OK | 23.63 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_hal-lp_ticker | OK | 22.28 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_hal-lp_us_tickers | OK | 14.73 | default |
| DISCO_L475VG_IOT01A-ARM | DISCO_L475VG_IOT01A | tests-mbed_hal-rtc_time | OK | 29.56 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_drivers-lp_timeout | OK | 59.14 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_drivers-lp_timer | OK | 18.58 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_drivers-rtc | OK | 23.6 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_hal-lp_ticker | OK | 22.31 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_hal-lp_us_tickers | OK | 14.74 | default |
| DISCO_L476VG-ARM | DISCO_L476VG | tests-mbed_hal-rtc_time | OK | 29.67 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timeout | OK | 57.46 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer | OK | 18.3 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-rtc | OK | 23.21 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker | OK | 22.07 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_us_tickers | OK | 14.31 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-rtc_time | OK | 28.5 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_drivers-lp_timeout | OK | 58.83 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_drivers-lp_timer | OK | 18.3 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_drivers-rtc | OK | 23.31 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_hal-lp_ticker | OK | 22.09 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_hal-lp_us_tickers | OK | 14.34 | default |
| NUCLEO_F410RB-ARM | NUCLEO_F410RB | tests-mbed_hal-rtc_time | OK | 26.16 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_drivers-lp_timeout | OK | 58.7 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_drivers-lp_timer | OK | 18.38 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_drivers-rtc | OK | 23.23 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_hal-lp_ticker | OK | 22.09 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_hal-lp_us_tickers | OK | 14.38 | default |
| NUCLEO_F411RE-ARM | NUCLEO_F411RE | tests-mbed_hal-rtc_time | OK | 26.16 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_drivers-lp_timeout | OK | 58.77 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_drivers-lp_timer | OK | 18.41 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_drivers-rtc | OK | 23.24 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_hal-lp_ticker | OK | 22.12 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_hal-lp_us_tickers | OK | 14.54 | default |
| NUCLEO_F412ZG-ARM | NUCLEO_F412ZG | tests-mbed_hal-rtc_time | OK | 26.43 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_drivers-lp_timeout | OK | 58.75 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_drivers-lp_timer | OK | 18.19 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_drivers-rtc | OK | 23.41 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_hal-lp_ticker | OK | 21.95 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_hal-lp_us_tickers | OK | 14.27 | default |
| NUCLEO_F429ZI-ARM | NUCLEO_F429ZI | tests-mbed_hal-rtc_time | OK | 21.25 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_drivers-lp_timeout | OK | 58.86 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_drivers-lp_timer | OK | 18.38 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_drivers-rtc | OK | 23.49 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_hal-lp_ticker | OK | 22.26 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_hal-lp_us_tickers | OK | 14.49 | default |
| NUCLEO_F446ZE-ARM | NUCLEO_F446ZE | tests-mbed_hal-rtc_time | OK | 20.9 | default |

targets/TARGET_STM/rtc_api.c Outdated
void rtc_init(void)
{
RCC_OscInitTypeDef RCC_OscInitStruct = {0};
RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0};
if (rtc_inited) return;

This comment has been minimized.

@0xc0170

0xc0170 Nov 9, 2017

Member

Is this correct way to RTC init check? Shouldn't this rather check RTC register if RTC is already running ?

If an app goes through reset, this could lead to restarting RTC to loose the time as rtc_inited would become 0 during startup again. But RTC is running (keeping time).

* CK_SPRE_16BITS: 1s < wakeup period < (0xFFFF+ 1) x 1 s = 65536 s (18 hours)
* CK_SPRE_17BITS: 18h+1s < wakeup period < (0x1FFFF+ 1) x 1 s = 131072 s (36 hours)
*/
uint32_t WakeUpClock[6] = {RTC_WAKEUPCLOCK_RTCCLK_DIV2, RTC_WAKEUPCLOCK_RTCCLK_DIV4, RTC_WAKEUPCLOCK_RTCCLK_DIV8, RTC_WAKEUPCLOCK_RTCCLK_DIV16, RTC_WAKEUPCLOCK_CK_SPRE_16BITS, RTC_WAKEUPCLOCK_CK_SPRE_17BITS};

This comment has been minimized.

@0xc0170

0xc0170 Nov 9, 2017

Member

Do you think we can get more details in the commit message regarding this calculation of WakeUpClock ?I could think of how this is improving the time ( similar to what the comment says about, that this is choosing the best divider for RTC clock based on the period (if I read the code correctly)) ?

@jeromecoutant jeromecoutant force-pushed the jeromecoutant:PR_LPT_RTC branch Nov 15, 2017

@jeromecoutant jeromecoutant changed the title from STM32 small Low Power Timer feature updates to STM32 Low Power Timer feature updates Nov 15, 2017

@jeromecoutant

This comment has been minimized.

Contributor

jeromecoutant commented Nov 15, 2017

@0xc0170
RTC init function updated. (rtc_inited global variable removed)

Did also full rebase

Tested with LSE and LSI configuration with all STM32 families.

Thx

@0xc0170 0xc0170 added needs: CI and removed needs: work labels Nov 16, 2017

@jeromecoutant jeromecoutant force-pushed the jeromecoutant:PR_LPT_RTC branch to 1bfc307 Nov 16, 2017

@0xc0170 0xc0170 added needs: review and removed needs: CI labels Nov 16, 2017

HAL_RTC_SetDate(&RtcHandle, &dateStruct, RTC_FORMAT_BIN);
HAL_RTC_SetTime(&RtcHandle, &timeStruct, RTC_FORMAT_BIN);
if (HAL_RTC_SetDate(&RtcHandle, &dateStruct, RTC_FORMAT_BIN) != HAL_OK) {
printf("HAL_RTC_SetDate error\n");

This comment has been minimized.

@0xc0170

0xc0170 Nov 17, 2017

Member

could this use debug function rather than printf ? Or turn to error or?

@0xc0170 0xc0170 added needs: CI and removed needs: review labels Nov 22, 2017

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Nov 22, 2017

/morph build

@mbed-ci

This comment has been minimized.

mbed-ci commented Nov 22, 2017

Build : SUCCESS

Build number : 569
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5459/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@mbed-ci

This comment has been minimized.

@mbed-ci

This comment has been minimized.

@0xc0170 0xc0170 added needs: work and removed needs: CI labels Nov 22, 2017

@jeromecoutant jeromecoutant force-pushed the jeromecoutant:PR_LPT_RTC branch from a336d34 to 5dee163 Nov 23, 2017

@jeromecoutant

This comment has been minimized.

Contributor

jeromecoutant commented Nov 23, 2017

Conflict solved

Tests are OK for NUCLEO_F401RE on my side:

| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timeout | OK | 24.12 | default |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer | OK | 19.78 | default |

@0xc0170 0xc0170 added needs: CI and removed needs: work labels Nov 23, 2017

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Nov 23, 2017

/morph build

jeromecoutant added some commits Nov 7, 2017

STM32 LOW_POWER_TIMER update : rtc_api.c
Add RSF synchro during init
Set a better WakeUp clock for long wake up period in order to stay in sleep mode
Use rtc_isenabled function before init as rtc_init is called at each set_time call
STM32 LOW_POWER_TIMER update : sleep
RSF synchro after deepsleep is not specific to Low Power Timer feature
And we have to check if RTC is configured before synchro

@jeromecoutant jeromecoutant force-pushed the jeromecoutant:PR_LPT_RTC branch from 5dee163 to 17a5484 Dec 5, 2017

@jeromecoutant

This comment has been minimized.

Contributor

jeromecoutant commented Dec 5, 2017

@0xc0170
Minor updates done including the replacement of RTC_LSI macro.
Rebase also done.

@0xc0170

0xc0170 approved these changes Dec 5, 2017

@0xc0170 0xc0170 added needs: CI and removed needs: work labels Dec 5, 2017

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Dec 5, 2017

/morph build

@mbed-ci

This comment has been minimized.

mbed-ci commented Dec 5, 2017

Build : SUCCESS

Build number : 654
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5459/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@mbed-ci

This comment has been minimized.

@mbed-ci

This comment has been minimized.

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Dec 7, 2017

I cant reproduce the error. downloading the binaries from the latest test run, all OK on my device. Same happens for the local run from the latest master.

How I reproduced:

used binaries from the build above, run mbedgt -v -V -n tests-mbed_drivers-lp_timer,tests-mbed_drivers-lp_timeout and test results are

mbedgt: test suite report:
+-------------------+---------------+------------------------------+--------+--------------------+-------------+
| target            | platform_name | test suite                   | result | elapsed_time (sec) | copy_method |
+-------------------+---------------+------------------------------+--------+--------------------+-------------+
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | OK     | 13.08              | cp          |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | OK     | 13.11              | cp          |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | OK     | 13.39              | cp          |
+-------------------+---------------+------------------------------+--------+--------------------+-------------+
mbedgt: test suite results: 3 OK
mbedgt: test case report:
+-------------------+---------------+------------------------------+-------------------------------------+--------+--------+--------+--------------------+
| target            | platform_name | test suite                   | test case                           | passed | failed | result | elapsed_time (sec) |
+-------------------+---------------+------------------------------+-------------------------------------+--------+--------+--------+--------------------+
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Calls from ISR fail                 | 1      | 0
   | OK     | 0.1                |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | One-shot not restarted when elapsed | 1      | 0
   | OK     | 0.16               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Periodic repeats continuously       | 1      | 0
   | OK     | 0.21               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Restart changes timeout             | 1      | 0
   | OK     | 0.09               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Stopped timer can be started again  | 1      | 0
   | OK     | 0.17               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Timer can be stopped                | 1      | 0
   | OK     | 0.12               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Timer is created in stopped state   | 1      | 0
   | OK     | 0.07               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Timer started with infinite delay   | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_ticker | Timer started with zero delay       | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Calls from ISR fail                 | 1      | 0
   | OK     | 0.11               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | One-shot not restarted when elapsed | 1      | 0
   | OK     | 0.17               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Periodic repeats continuously       | 1      | 0
   | OK     | 0.21               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Restart changes timeout             | 1      | 0
   | OK     | 0.1                |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Stopped timer can be started again  | 1      | 0
   | OK     | 0.16               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Timer can be stopped                | 1      | 0
   | OK     | 0.11               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Timer is created in stopped state   | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Timer started with infinite delay   | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_drivers-lp_timer  | Timer started with zero delay       | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Calls from ISR fail                 | 1      | 0
   | OK     | 0.11               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | One-shot not restarted when elapsed | 1      | 0
   | OK     | 0.16               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Periodic repeats continuously       | 1      | 0
   | OK     | 0.21               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Restart changes timeout             | 1      | 0
   | OK     | 0.08               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Stopped timer can be started again  | 1      | 0
   | OK     | 0.16               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Timer can be stopped                | 1      | 0
   | OK     | 0.12               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Timer is created in stopped state   | 1      | 0
   | OK     | 0.06               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Timer started with infinite delay   | 1      | 0
   | OK     | 0.07               |
| NUCLEO_F401RE-ARM | NUCLEO_F401RE | tests-mbed_hal-lp_ticker     | Timer started with zero delay       | 1      | 0
   | OK     | 0.07               |
+-------------------+---------------+------------------------------+-------------------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 27 OK
mbedgt: completed in 44.26 sec

/morph test

@mbed-ci

This comment has been minimized.

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Dec 7, 2017

@kegilbert Can you please help to reproduce the above failure? 😕

@jeromecoutant

This comment has been minimized.

Contributor

jeromecoutant commented Dec 7, 2017

In the CI test bench, does each target start from a "switch off/unplug" state,
or all targets are always on?
(if they are always on, please unplug/plug NUCLEO_F401RE, thx)

@kegilbert

This comment has been minimized.

Contributor

kegilbert commented Dec 7, 2017

@jeromecoutant All targets are always on, we do soft resets after flashing as far as I know. I can unplug/plug in the NUCLEO_F401RE, is this a one off fix or do you need the devices to be disconnected completely before each CI run?

@kegilbert

This comment has been minimized.

Contributor

kegilbert commented Dec 7, 2017

I un/replugged the F401 boards, rekicking off test.
/morph test

@mbed-ci

This comment has been minimized.

@0xc0170 0xc0170 merged commit da43d65 into ARMmbed:master Dec 12, 2017

10 checks passed

AWS-CI uVisor Build & Test Success
Details
ci-morph-build build completed
Details
ci-morph-exporter build completed
Details
ci-morph-test test completed
Details
continuous-integration/jenkins/pr-head This commit looks good
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
travis-ci/events Local events testing has passed
Details
travis-ci/littlefs Local littlefs testing has passed
Details
travis-ci/mbed2 Local mbed2 testing has passed
Details
travis-ci/tools Local tools testing has passed
Details

@jeromecoutant jeromecoutant deleted the jeromecoutant:PR_LPT_RTC branch Dec 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment