lp_ticker and RTC tests failing for platforms based on STM32F412xx

[ashok-rao]

Description

• Type: Bug | Question
• Related PR's: Add new target USI WM-BN-BM-22 #6511 and Add support for target MTB_ADV_WISE_1530. #6423
• Priority: Major

---

Bug

Target
MTB_USI_BN-BM-22 and MTB_ADV_WISE_1530

Toolchain:
ARM

Expected behavior
All greentea tests should pass for the targets.

Actual behavior
LP_Ticker, LP_timer and RTC tests are failing on ARMCC 5.06 update 3.

Steps to reproduce
Run greentea on these 2 targets with ARMCC

Greentea logs are attached in the PR: #6511 (comment)
And failing tests for ADV_WISE_1530 are added as comments here: #6423 (comment)

[0xc0170]

STM32F412xx

@ARMmbed/team-st-mcd Is this known issue ? Please review

[jeromecoutant]

Hi

I know that NUCLEO_F412ZG is failing tests-mbed_drivers-lp_timeout since 5.8.1
Other LP tests are OK.
No known issue with RTC tests.

Note that we will not investigate on LP failed tests before the ticker branch merge.

[jeromecoutant]

We can discuss in parallel about your clock configuration:

• USI WM-BN-BM-22: I can see from the targets json file that you have a LSE and no HSE.
  This is OK, but could be a problem for tests part... as several tests check the accuracy of time with the us timer which is clocked in your case with HSI, the internal low cost clock.
  As you have an external LSE clock, idea could be to make a calibration procedure.

• MTB_ADV_WISE_1530: targets json file doesn't explicit your clock configuration, which is not correct.

[0xc0170]

Note that we will not investigate on LP failed tests before the ticker branch merge.

You are referring to the ticker hal specs feature branch? This then becomes known issue for 5.8.x - should these target have disabled low ticker as it is not fully functional?

[bcostm]

The tests-mbed_drivers-lp_timeout test is FAIL on many of our targets since 5.8.1. It was perfectly fine in 5.8.0 and the versions before. For sure something has been broken. But I don't understand how the 5.8.1 has been released ? Nobody has seen these FAILs ?

[0xc0170]

Looking at 5.8.1 - #6461 - tests were updated (timeout) - that would be the reason for the failures @fkjagodzinski Please confirm

[fkjagodzinski]

That is correct, #5106 which contains an update for LowPowerTimeout tests has been merged to 5.8.1.

[0xc0170]

so that update broke it. @fkjagodzinski Can you have look ? Is it a test or targets?

[fkjagodzinski]

I've checked the logs from #6511 (comment) and can see that some test suites are present only for ARM compiler:

• mbed-os-tests-mbed_drivers-lp_ticker,
• mbed-os-tests-mbed_drivers-lp_timeout,
• mbed-os-tests-mbed_drivers-lp_timer,
• mbed-os-tests-mbed_hal-lp_ticker.

Since I don't have any board with STM32F412ZG, I can only check that adding LOWPOWERTIMER definition in targets.json and running mbed test -t <toolchain> -m MTB_USI_WM_BN_BM_22 -c -n tests-mbed_drivers-lp_timeout on current master df47efc does actually produce a binary for all 3 compilers.

@ashok-rao could you run mbed test -t <toolchain> -m MTB_USI_WM_BN_BM_22 -n tests-mbed_drivers-lp_timeout -v for all ARM, GCC_ARM & IAR and paste the logs, please?

[ashok-rao]

@fkjagodzinski , I can't build those test suites now.. every time I try to build the tests (with clean compile), the tests for LP_timer, lp_ticker, lp_timeout are being skipped both with GCC and ARMCC.. any thoughts why it was being compiled in the earlier run (#6511) and is being skipped now? Or do you recommend to explicitly add LOWPOWERTIMER to targets.json and build again?

Build skips:
<snip>
  * MTB_USI_WM_BN_BM_22::ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TICKER
  * MTB_USI_WM_BN_BM_22::ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TIMEOUT
  * MTB_USI_WM_BN_BM_22::ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TIMER

and with GCC:

Build skips:
<snip>
  * MTB_USI_WM_BN_BM_22::GCC_ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TICKER
  * MTB_USI_WM_BN_BM_22::GCC_ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TIMEOUT
  * MTB_USI_WM_BN_BM_22::GCC_ARM::MBED-OS-TESTS-MBED_DRIVERS-LP_TIMER

[fkjagodzinski]

Yes, these tests are built only when LOWPOWERTIMER macro is defined, so you should either edit targets.json or use -D compile option.

[ashok-rao]

@fkjagodzinski But, we did not have LOWPOWERTIMER defined in targets.json for the commit 1df5c02 too. How come it was being built then..!