-
Notifications
You must be signed in to change notification settings - Fork 51
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
Memory allocation issue on the NRF51DK board. #76
Comments
@marcuschangarm are the getInstance methoda for GattClient or SecurityManager getting called from an interrupt context? Does the fault happen on a central or a peripheral? Can you provide more information about the context in which the fault happens? Have you got a stack trace? I'm not too tied to the current implementation using @andresag01 Could you please work with @marcuschangarm to reproduce/investigate this issue? |
All my calls are through minar. The problem seems to surface in the gatt client event handler, but this feels more like a memory corruption problem since the location changes when I change the application.
|
ARM Internal Ref: IOTSFW-1284 |
It seems that this commit fixes the issue. |
After upgrading from v0.4.8 to v2.0.7 I'm getting hard faults when using GattClient.
I can circumvent the problem by reverting these two functions from:
https://github.com/ARMmbed/ble-nrf51822/blob/master/source/nRF5xGattClient.cpp#L19-L26
https://github.com/ARMmbed/ble-nrf51822/blob/master/source/nRF5xSecurityManager.cpp#L19-L25
To:
The test application used: https://github.com/ARMmbed/ble-blocktransfer-mbed
The text was updated successfully, but these errors were encountered: