ITM broken on Nucleo H743/H753 boards #346
Assignees
Comments
bcantrill
added a commit
that referenced
this issue
Dec 26, 2021
bcantrill
added a commit
that referenced
this issue
Dec 28, 2021
ITM broken on Nucleo H743/H753 boards (#346) SPI overruns are not handled, resulting in infinite loop (#349) SPI can suffer from overruns due to TX/RX asymmetry (#350) In addition to fixing these bugs, this work removes the Gimlet hostflash task from the H743/H753 boards -- and replaces it with the venerable ping.
This was referenced Dec 28, 2021
Merged
|
I think this gets at a higher-level question, which is: permanently assigning a SPI block on the Nucleo board is weird, since we tend to use the Nucleo boards as general purpose I/O widgets. I'm not sure what to do about this. |
bcantrill
added a commit
that referenced
this issue
Jan 10, 2022
This fixes the following bugs: - Spi.exchange() hangs if RX bytes exceeds TX bytes (#341) - ITM broken on Nucleo H743/H753 boards (#346) - SPI overruns are not handled, resulting in infinite loop (#349) - SPI can suffer from overruns due to TX/RX asymmetry (#350) In addition to fixing these bugs, this work removes the Gimlet hostflash task from the H743/H753 boards -- and replaces it with the venerable "ping" task (which demonstrates a panicking task).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tale of woe is in #345, but the synopsis is: ITM is (and has been) broken on the Nucleo H743/H753 boards due to TRACESWO being repurposed for SPI. We clearly need to pick another SPI block (or at the very least, pin for SPI3_SCK) to use on this board!
The text was updated successfully, but these errors were encountered: