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

Ported the DMA peripheral from pebble/qemu #23

Merged
merged 4 commits into from Dec 6, 2018

Conversation

Projects
None yet
2 participants
@baselsayeh

baselsayeh commented Nov 3, 2018

Currently,

  • Only uart tx and rx dma inturupt is implemented
  • Starting a dma from or to peripherals does not work but works in circular mode (uart with dma inturrupts works)
  • Half-transfer and error-transfer inturrupt is not implemented
  • Dma transfers pauses the emulation while dma transfers occures (needs multi-threaded timers and inturrupts)

baselsayeh added some commits Oct 31, 2018

re-added '#include <sys/sysmacros.h>' to fix compilation errors
It seems that gclibc 2.23 dropped '#include <sys/sysmacros.h>' from
sys/types.h, which is causing compilation errors on newer versions that
use functions from that file
ported the DMA peripheral from pebble/qemu (partially working)
Currently, UART (Transfer Complete) dma inturrupt only works (from
peripherals), but memory to memory works fine
Added circular mode in DMA
Note: it does not work with uart

@beckus beckus merged commit 745531e into beckus:stm32 Dec 6, 2018

@beckus

This comment has been minimized.

Owner

beckus commented Dec 6, 2018

Sorry for the delay. Thank you for submitting this - it's nice to see the list of supported peripherals grow.

@beckus

This comment has been minimized.

Owner

beckus commented Dec 6, 2018

I added another commit 9852410 to fix some minor compile warnings I was receiving with the new DMA code. I have my compiler set to treat warnings as errors (which I think is the default for QEMU if I recall correctly), and would prefer not to disable warnings (even though one of the changes was a bit ugly). These changes shouldn't have any effect, though I don't have a way to test right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment