Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

toggle RTT mode after RAM initialization #69

Merged
merged 2 commits into from
Sep 22, 2020
Merged

Conversation

japaric
Copy link
Member

@japaric japaric commented Sep 21, 2020

src/main.rs Outdated
log::warn!("device doesn't support HW breakpoints; HardFault will NOT make `probe-run` exit with an error code");
} else {
core.set_hw_breakpoint(vector_table.hard_fault & !THUMB_BIT)?;
bail!("device without HW breakpoints are not supported");
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FIXME: we should only bail if rtt_addr is Some

@@ -933,6 +943,7 @@ fn rtt_and_heap_info_from(
};

match name {
"main" => main = Some(symbol.address() as u32 & !THUMB_BIT),
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this symbol is guaranteed to exist in the final binary so we may want to do something else

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least when using cortex-m-rt it will always exist, I think

Copy link
Contributor

@jonas-schievink jonas-schievink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation looks good, would be good to resolve the FIXME before merging though

@jonas-schievink jonas-schievink merged commit df90d57 into main Sep 22, 2020
@japaric japaric deleted the blocking-rtt branch October 23, 2020 16:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RTT implementation should probably not default to blocking mode
2 participants