-
Notifications
You must be signed in to change notification settings - Fork 495
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
Fix for halt on connect and disconnect resume #304
Conversation
/morph test |
This PR is failing on all non-Kinetis devices - lpc1114, lpc4088dm, lpc824, nrf51. |
Thanks. I'll look into it. Do you have any details about the failures? |
It was failing only on the ConnectTest for those targets. I don't have access to the logs now so I can't give much more detail. |
Alright, thanks. I'll see if it fails on the LPC1768. |
/morph test |
50efd6b
to
8e79a23
Compare
/morph test |
- Control over halt on connect and disconnect resume was broken because the option flags were not being passed to the CortexM class.
/morph test |
CI results: Mac passed, Linux passed except for a device that's currently stuck in bootloader, Windows build machine is nonfunctional and failing. |
The halt on connect and disconnect resume features were broken due to the options not being properly passed down to the
CortexM
instance, and the change to clear the DHCSR upon disconnect. This changeset does just that.When a core is added in
CoreSightTarget.add_core()
, the halt on connect setting to set on the new core instance. (add_core()
is expected to be called before the core is inited.)For disconnect resume, the code in
Board.uninit()
to resume the target was removed. Instead, the resume parameter is passed to the target'sdisconnect()
method, which passes it toCortexM.disconnect()
for each core. The core will not clear DHCSR if resume is not requested.This change includes a comprehensive test for these features.