I'm trying to get some Rust-code onto the Due.
There's very helpful tool that generates a code representation of the hardware based on a valid SVD file:
There's a big list available, including the ATSAM3X8E:
Sadly the file of interest (ATSAM3X8E.svd) gives me an error:
$ svd2rust -i ATSAM3X8E.svd
According to this link this is due to a missing mandatory field:
opened 04:03PM - 21 Dec 16 UTC
closed 12:01AM - 10 Jun 17 UTC
Once #43 lands, I think we should be ready to test generating *all* the peripher… als that a SVD contains. `svd2rust -i $svd` would give us the full list of peripheral then we can use `svd2rust -i $svd $peripheral` for each peripheral in that list.
We could even repeat this approach for several SVD files in the cmsis-svd repo. We should be careful to not overdo ourselves and end up with unreasonable test times though.
Does anyone know if there's a fixed version out there or can this file be fixed manually by translating the missing information from the datasheet?
I don't know if it might help, but these tutorials show how you can use RUST with a DUE:
http://hannobraun.de/embedded/
Thank you. The sources are a bit outdated and he references the same source I'm having problems with. But there are still a lot of useful informations that'll help me.