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

STM32F4: SPI::abort_transfer() causes incorrect data on the next transaction #182

Open
multiplemonomials opened this issue Aug 24, 2023 · 0 comments
Labels
Bug Dis is broken STMicro Only affects STMicro targets

Comments

@multiplemonomials
Copy link
Collaborator

Seeing an issue that's showing up in the SPI unit tests, specifically async_queue_and_abort() from the spi-basic test:
image
After the gap, the bytes should be "01 02 00 00", but instead the first two bytes are zeroes and the next two nonzero. Maybe it's somehow swapping the order of the first 4 bytes?

This issue seems to affect both interrupt and DMA SPI, so I don't think it's a DMA-specific problem.

I observed this on NUCLEO_F429ZI, but I wouldn't be surprised if it affects all STMicro targets with SPI IP v1.

@multiplemonomials multiplemonomials added Bug Dis is broken STMicro Only affects STMicro targets labels Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Dis is broken STMicro Only affects STMicro targets
Projects
None yet
Development

No branches or pull requests

1 participant