Logs can be found Test logs: http://mbed-os-ci.s3-website-eu-west-1.amazonaws.com/?prefix=jenkins-ci/ARMmbed/mbed-os/mbed-os-ci/mbed-os-5.12/artifacts/mbed-os-5.12/2/greentea-test/1406/ERROR/UBLOX_EVK_ODIN_W2/ARMC6/
This is in nightly. Wifi seems to be hard faulting for ARMC6.
5.12.0-rc1 nightly fails with this error.
[ ] Question
[ ] Enhancement
[X] Bug
cc @ARMmbed/team-ublox
@ARMmbed/mbed-os-ipcore Known issue or new one?
Thanks, Martin. Yes, we've also noticed and we are already working on it in ONME-4220.
Great! Once this is cloned to our jira, please link these 2 issues and fix should close this one.
My findings are that this commit introduced the issue (switching to ARMC6) and that the hard fault takes place when this line is executed.
The hard fault message is:
[1551962056.94][CONN][RXD] ++ MbedOS Error Info ++
[1551962056.94][CONN][RXD] Error Status: 0x80FF013D Code: 317 Module: 255
[1551962056.94][CONN][RXD] Error Message: Fault exception
[1551962056.96][CONN][RXD] Location: 0x801B64D
[1551962056.96][CONN][RXD] Error Value: 0x800D8BE
[1551962056.96][CONN][RXD] Current Thread: application_unnamed_thread Id: 0x2000742C Entry: 0x8010FD1 StackSize: 0x1000 StackMem: 0x20012940 SP: 0x2002FF18
[1551962056.98][CONN][RXD] For more info, visit: https://mbed.com/s/error?error=0x80FF013D&tgt=UBLOX_EVK_ODIN_W2
[1551962056.98][CONN][RXD] -- MbedOS Error Info --
[1551962056.98][CONN][RXD]
[1551962056.98][CONN][RXD] = System will be rebooted due to a fatal error =
[1551962056.99][CONN][WRN] UnicodeDecodeError encountered!
@ARMmbed/team-ublox , would you please take a look at this issue?
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-964
My findings are that this commit introduced the issue (switching to ARMC6) and that the hard fault takes place when this line is executed.
@ARMmbed/team-ublox , would you please take a look at this issue?
Is that correct the commit above is causing this hard fault? Any update?
cc @screamerbg
@ARMmbed/team-ublox Just want to confirm, the next driver update should have this resolved?
@0xc0170 here is internal jira for ARMC6 https://jira.u-blox.net/browse/TE_OM2-115. point is can u device a mechanism how to debug a ARMC6 (ODIN_w2) binary using eclipse. It would be good if u can have detail procedure.
@0xc0170 here is internal jira for ARMC6 https://jira.u-blox.net/browse/TE_OM2-115. point is can u device a mechanism how to debug a ARMC6 (ODIN_w2) binary using eclipse. It would be good if u can have detail procedure.
would you use mbed studio? I'll contact you over email to get more details
This is the official documentation we have : https://os.mbed.com/docs/mbed-os/v5.12/tutorials/eclipse.html
Isn't this sufficient to keep you running debugging session ? It uses eclipse + openOCD (odin supported there, not yet in pyOCD), or ST provides gdb as well?)
I also found private notebook describing how to set up openOCD with odin (it's almost 2 years old, might be still a good start): https://os.mbed.com/users/janjongboom/notebook/debugging-ublox_evk_odin_w2-with-openocd-and-visua/#
You should be able to debug armc6 application using gdb in eclipse. These 2 links should help you. Without much details where you are having issues, we might not be able to help further.
It might be good to start a new issue to get this eclipse + armc6 question further - I would recommend asking on the forum, there are users who use eclipse daily.
https://github.com/mbedmicro/pyOCD/tree/master/pyocd/probe/stlink
There seems to be some development regarding ST-Link support for pyOCD.
Sounds like we need to have proper documentation / guide on our Handbook how to set up the debugger for most commom UIs and debuggers.
For example gdbservers:
Then UIs:
have just fixed hard fault issue please see logs
mbed-os-wifi-test.txt
fix would be generated in next PR.
https://github.com/ARMmbed/mbed-os/pull/11370 generated @0xc0170