-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Xdot Lora #3835
Comments
Not an ST device... |
It is ST device |
I meant not an ST platform... This platform has been developped by Multitech using a ST mcu yes. |
I'll do. First thing would be to identify this within the multitech target, and see if this issue applies to a common code base that would affect other targets as well, then this could apply to ST platforms. |
cc @mfiore02 |
Is this on mbed OS 5.3.5? If so, downgrading to 5.3.1 might work due to #3823. |
@naushad-rahman @janjongboom @0xc0170 quick update... I have a NUCLEO_L152RE on hand and this app looks OK on that platform with mbed-os-5.3.6. I tested this app on the xDot starting with mbed-os-5.3.6. Versions 5.3.6 - 5.3.1 all had the same behavior.
Hard faults ad infinitum. Versions 5.3.0 - 5.2.0 also all had the same behavior.
No output after the first line. I can't go back any further since Callback was introduced in mbed-os-5.2.0. Debugging time! I'll post again when I know more. |
@janjongboom based on the progress we've made with #3823 I don't think this issue is related. |
It looks like the error is encountered during the context switch. Below is the stack trace and register info from the app compiled with mbed-os-5.3.6.
Entry 2 in the stack trace is in the processor's RAM, not FLASH. The ?? is also suspicious to me. I'm not a RTOS master, so I'm asking those who are: does the RTOS have components that execute out of RAM instead of FLASH? Or are we having some pointer issues? |
Works as of mbed-os-5.5.7 |
Description
I am trying to implement Callback function , Example sited by the mbed
I am getting Hard fault
output is
Hard FaulTh 1: 0
Th 2: 0
Th 3: 0
Bug
Target
XDot
Toolchain:
GCC_ARM
The text was updated successfully, but these errors were encountered: