Skip to content

Nuvoton: Enlarge required deep sleep latency #11020

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

Merged
merged 1 commit into from
Aug 14, 2019

Conversation

ccli8
Copy link
Contributor

@ccli8 ccli8 commented Jul 11, 2019

Description

This PR is to pass wake-up from deep-sleep test such as mbedmicro-rtos-mbed-systimer for Nuvoton targets when in tickless from lp-ticker mode.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Copy link
Contributor

@0xc0170 0xc0170 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question - why 1 fixes it ? why not 2 for instance - might be good to explain this in the commit itself. It's not just to pass the test - why it fails (what is this fixing, is there some reconfig in place that takes time and introducing this latency?). I might be asking too much but this might be helpful to know for a reader.

…iling

This test requires total latency (tot = h/w + s/w) (wakeup from deepsleep) be
under 1ms. To check the issue, measure total latency on Nuvoton targets:

TARGET      EXP(us)     EXP+TOL(us) ACT(us)
NANO130     42000       43000       42939
NUC472      42000       43000       42236
M453        42000       43000       43274
M487        42000       43000       42877
M2351       42000       43000       43213

Checking h/w spec, h/w latency (wakeup time from normal power-down mode) on
M487/M2351 is just 1us (n/a on other targets). S/W latency plays the major
part here.

S/W latency relies on system performance. On Nuvoton targets, 'LPTICKER_DELAY_TICKS'
possibly complicates the test. Anyway, to pass the test, add extra 1ms latency
(deep-sleep-latency) in targets.json for Nuvoton targets.
@ccli8 ccli8 force-pushed the nuvoton_wakeup_latency branch from 769a530 to 1e5a52a Compare July 12, 2019 05:43
@ccli8
Copy link
Contributor Author

ccli8 commented Jul 12, 2019

Add the commit message. According to h/w spec, h/w latency is 1us on Nuvoton targets. The total latency majorly comes from s/w latency. Dependent on system performance (cpu+cache+...), s/w latency ranges from 250us to 1250us on Nuvoton targets. Default tolerance is 1ms. Add extra 1ms tolerance for this test.

On non-Nuvoton target K64F, its total latency is 400us. Without its h/w spec, assuming its h/w latency is also small, s/w latency still plays the major part.

@ccli8
Copy link
Contributor Author

ccli8 commented Jul 18, 2019

Any update?

@ccli8
Copy link
Contributor Author

ccli8 commented Aug 8, 2019

@0xc0170

@0xc0170 0xc0170 self-requested a review August 9, 2019 11:51
Copy link
Contributor

@0xc0170 0xc0170 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the commit msg

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 9, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Aug 9, 2019

Test run: FAILED

Summary: 3 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_exporter
  • jenkins-ci/mbed-os-ci_dynamic-memory-usage
  • jenkins-ci/mbed-os-ci_greentea-test

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 12, 2019

Restarted entire CI pipeline (failures not related to this changeset).

@mbed-ci
Copy link

mbed-ci commented Aug 12, 2019

Test run: FAILED

Summary: 3 of 11 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_dynamic-memory-usage
  • jenkins-ci/mbed-os-ci_exporter
  • jenkins-ci/mbed-os-ci_greentea-test

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 13, 2019

Restarted tests, exporters have an issue on master, will be fixed

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 14, 2019

CI restarted

@mbed-ci
Copy link

mbed-ci commented Aug 14, 2019

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 3
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_pdmc-test

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 14, 2019

jenkins-ci/mbed-os-ci_pdmc-test

Not valid CI config, new jobs will have this fixed. All good

@0xc0170 0xc0170 merged commit a6c316a into ARMmbed:master Aug 14, 2019
@cyliangtw cyliangtw deleted the nuvoton_wakeup_latency branch March 9, 2023 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants