Skip to content

Print info to determine cause of lp_ticker failure #4437

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

Conversation

c1728p9
Copy link
Contributor

@c1728p9 c1728p9 commented Jun 3, 2017

Print the RTC's TSR, IER and SR on boot to determine if a pending interrupt is the cause of the lp_ticker failure.

Print the RTC's TSR, IER and SR on boot to determine if a pending
interrupt is the cause of the lp_ticker failure.
@c1728p9
Copy link
Contributor Author

c1728p9 commented Jun 3, 2017

/morph test-nightly
cc @studavekar @bridadan

@mbed-bot
Copy link

mbed-bot commented Jun 3, 2017

Result: ABORTED

Your command has finished executing! Here's what you wrote!

/morph test-nightly
cc @studavekar @bridadan

Output

mbed Build Number: 431

Example Build failed!

@c1728p9
Copy link
Contributor Author

c1728p9 commented Jun 3, 2017

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented Jun 4, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 433

Test failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 5, 2017

WE should analyze this output:

[1496525856.21][CONN][RXD] TSR: 0x4ae82d4a
[1496525856.23][CONN][RXD] Enabled interrupts: 0x7
[1496525856.26][CONN][RXD] Pending interrupts: 0x0

@c1728p9
Copy link
Contributor Author

c1728p9 commented Jun 7, 2017

Problem fixed in #4453 so closing this.

@c1728p9 c1728p9 closed this Jun 7, 2017
@sg- sg- removed the do not merge label Jun 7, 2017
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

Successfully merging this pull request may close these issues.

4 participants