Skip to content
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

v2.20 fails to hold stable debugging connection with probe-run #15

Open
ctron opened this issue Sep 21, 2022 · 3 comments
Open

v2.20 fails to hold stable debugging connection with probe-run #15

ctron opened this issue Sep 21, 2022 · 3 comments

Comments

@ctron
Copy link

ctron commented Sep 21, 2022

Using https://github.com/knurling-rs/probe-run to flash firmware and run debugging works as expected for the micro:bit v2 (.00).

But it starts failing with the micro:bit .20.

Having the interface version 0256 is breaks after a bit with:

RTT error: Error communicating with probe: A core architecture specific error occurred
────────────────────────────────────────────────────────────────────────────────
Error: A core architecture specific error occurred

Caused by:
    0: Failed to read register DRW at address 0x0000000c
    1: An error specific to a probe type occurred
    2: Error handling CMSIS-DAP command Transfer
    3: Timeout in USB communication.
Ignore: probably some issue with flashing the firmware

Upgrading to the 0257 firmware it gets even worse:

(HOST) INFO  flashing program (35 pages / 140.00 KiB)
(HOST) INFO  success!
Error: An error with the usage of the probe occurred

Caused by:
    Operation timed out
@ctron
Copy link
Author

ctron commented Sep 21, 2022

I updated the original comment, as it looks like the upgrade to 0257 just somehow failed. Re-trying this a few times, I end up with 0257 behaving the way as 0256.

@ctron
Copy link
Author

ctron commented Sep 21, 2022

It looks like using cargo embed (0.13.0) instead of probe-run works.

@ctron
Copy link
Author

ctron commented Sep 21, 2022

cargo-embed faces the same (I guess) issue, but takes longer to reach this point. Instead of 5-30 seconds to break, the connection runs for around 15mins.

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

No branches or pull requests

1 participant