-
Notifications
You must be signed in to change notification settings - Fork 100
CMSIS-SVD to ioreg list conversion tool #259
Comments
Can you link to an example? Less typing is always appreciated. |
Linking in example svd file: http://www.keil.com/pack/doc/CMSIS/SVD/html/svd__example_pg.html |
Awesome. Even has the read-write type. Not a 1:1 mapping though, as we want GROUPNAME for the ioreg stuff. And each peripheral is an implementation of GROUPNAME (which is more device specific). I like how the interrupts are done also - a peripheral registers one or more interrupt numbers. |
@aethaniel Thanks for bringing this up. That would definitely help to add new chips. It's xml format and provided by manufacturer. We could write a parser to get relevant info for ioregs!. The one question I would have: is ioreg! stable and the way to go? So we can put effor there |
|
I've looked through one of those in detail (LPC11xx svd), it surely looks useful and will save us a lot of time. Will it make sense to unify all reg definitions in one file? So far I think that svd-to-ioreg generator could be a rather trivial chunk of ruby code. /cc @bgamari in here. |
It seems like an SVD-to- |
@tcr and I started implementing an SVD parser in Rust. It's generating semi-usable |
Looks very nice! I've checked it with lpc11xx svd and it looks promising. So far it seems that only the lack of |
disregard that. I didn't realise that the file name is hard coded and got it crashed right away. Still looks promising :) |
Closed by #267 landing? |
Yup, thanks for pointing out! |
Hi,
I'm totally rookie in Rust and Zinc but I'm really interested in this project for many reasons.
I would like to know if there is a need and/or a plan to convert CMSIS-SVD public files of various Cortex-M devices to a list ioreg macros?
If the SVD format (with or without complementary information like PDSC files) is suitable for such conversion, it could allow some community 'enablement' on lot of different devices.
The text was updated successfully, but these errors were encountered: