-
Notifications
You must be signed in to change notification settings - Fork 134
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
DMA for more STM32 controllers #608
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
STM32F0{3,7}0xC / STM32F102 / devices modm-devices tells me about a second https://github.com/modm-io/modm-devices/blob/develop/devices/stm32/stm32f0-30.xml#L217 |
STM32F09{1,8} has a different problem: <vector position="10" name="DMA1_Ch2_3_DMA2_Ch1_2"/>
<vector position="11" name="DMA1_Ch4_7_DMA2_Ch3_5"/> I don't understand this error by now:
(occures on multiple devices) The Dma-SpiMaster has some interrupt flag definitions missing on some devices, looks easy to fix... Dma2 has only 2 channels on STM32L1? <channels device-size="c" instance="2">
<channel position="1">
<signal driver="spi" instance="3" name="rx"/>
</channel>
<channel position="2">
<signal driver="spi" instance="3" name="tx"/>
</channel>
</channels>
Maybe modm-devices is inconsistent/wrong here? (#608 (comment)) Miauu 🐈 |
Uff, I didn't expect there to be that many problems. The code responsible for parsing the DMA data is here, there are a lot of corrections, some of which are described in the PR. |
Looks to me like CubeMX data is partly wrong, also modm-devices is definitely wrong in some cases 😒 I'm not motivated to deal with this any further at the moment; maybe tomorrow I'll look into enabling DMA based on a positive list for some STM32s that I use. |
Some other issues I discovered: From time to time (when regenerating device file in modm-devices) I can't run the CI script on my Linux, because Python is unable to locate
WTF?! Update: |
Yeah, that's also what I would propose, I think this issue is overwhelming otherwise. It's very frustrating to work with the CubeMX data…
I'm sorry… It's on my todo list for #390.
No clue… I need to rewrite that to call lbuild directly instead of from the cmdline… |
I think thats a bad idea, because it will make debugging even harder (or in some cases nearly impossible). |
The underlying problem are some duplicate entry in modm-devices: <signal driver="tim" instance="1" name="ch3"/>
<signal driver="tim" instance="1" name="ch3"/> |
426aec2
to
5b114b2
Compare
5b114b2
to
293ab3c
Compare
293ab3c
to
bfb7826
Compare
bfb7826
to
98e7618
Compare
69a214e
to
1dc7916
Compare
1dc7916
to
8ca2f35
Compare
This was very easy thanks to the great work done by @mikewolfram in #371.
Tested on Nucleo-F303RE.