-
Notifications
You must be signed in to change notification settings - Fork 72
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
ATmega4809 support #62
Comments
Hmm, Rahix/atdf2svd#6 is the main blocker I think. I don't think it is well documented what needs to be done, though :( |
@Rahix after svd generation what I should do? How I can path svd?
Maybe I need to continue #26 (comment) ? |
Hmm, if you remove said |
Without
|
I think the right thing is option 1: The internal representation in |
For the rest, take a look at this commit: 2906134 You need to do all these things, too. |
I've created issue Rahix/atdf2svd#11 to track this. |
PR for Rahix/atdf2svd#11 done Still not sure how I can create patched version of svd and then generate |
|
Looks like I need to spend more time on this chip. Require probably same changes as in #26 (comment)
@Rahix can you please advice which topic in atdf2svd I should progress
The text was updated successfully, but these errors were encountered: