-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bugged atdf definitions. #8
Comments
Repo with registers. |
Hi @luqasz , who have you been in contact with at Atmel/Microchip regarding this? I was also looking over the changes to the atdf files in luqasz/avr-registers, and I see that most of the corrections seems to be removing bitfields or adding bitfields (to avoid name collisions?) |
I've contacted them but guess what ? No reply. |
In a tangentially-related note (a different kind of "bugged atdf definition"): Even the latest pack files for ATmega (2.0.401) contain misspellings like "PRESACLE" for "PRESCALE", which unfortunately results in downstream projects like Being faithful to the original sources is great, but avoiding propagating trivial errors would be even better. Is there appetite in this project for applying certain transformations upon the That is, if I were to propose a PR that corrected this misspelling by applying string replacements to |
Tracked in DEVXML-4894 |
I will revive my atdf parser and repo to have original files in one dir and fixes in other. |
Hi.
While I was generating c++ headers (from original atdf files) with registers and their bit fields, I've noticed that they have lots of bugs and inconsistencies. I basicly do not trust them at all, and microchip does not respond to any mails and bug reports.
As we share common goal, I propose a solution to maintain a repository (I can do it as I have time) with all (hopefully) bugs and inconsistencies fixed.
I am thinking of a repo with yaml files (separate file for each chip) for easy parsing and reading/editting. Will post this repo here whe I will finish it.
The text was updated successfully, but these errors were encountered: