-
Notifications
You must be signed in to change notification settings - Fork 171
iprintln!() fails to print after printing certain amount of data #229
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
Comments
How are you consuming ITM? For whatever it's worth, your example works for me with an ITM consumer that we have purpose built that consumes ITM via the TPIU; are you using the STLink/V2 on the Discovery and then OpenOCD? And is your program stopping, or is the ITM data being dropped? |
Thank you so much for testing the example on your side! 😸 (Using (gdb) n
Breakpoint 4, main () at src/main.rs:20
20 #[entry]
(gdb) n
(gdb) ^C
Program received signal SIGINT, Interrupt.
stim_practice::__cortex_m_rt_main () at src/main.rs:37
37 loop {
(gdb) |
Update: So far I've tested two devices and they both exhibit the same behavior. Both belong to the
At the moment, I'm not sure what's causing this. (guess: issue with OpenOCD?) |
Maybe try with probe-rs' ITM support? |
229: Fixed changed compile-fail messages r=jonas-schievink a=korken89 Fixed the errors now present in `compile-fail` tests. Co-authored-by: Emil Fresk <[email protected]>
Hello 🦀, when running the program below that repeatedly calls
iprintln!()
, it always stops printing at the same point in code, not finishing the printing tasks. It should print "Hello World ~" 77 times in a loop, but the program always stops printing in the middle of 26th invocation ofiprintln!()
.logs from ITM are stored locally in itm.txt, and the log is always the same as below
(no matter how many times I try running).
Is there a maximum limit of data that
iprintln!
can send in total?If not, I guess this should be considered a bug..
Metadata
stm32f407g-disc1
board to run this program.rustc --version --verbose
The text was updated successfully, but these errors were encountered: