Skip to content
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

Support for ATTiny261A, ATTiny461A, ATTiny861A #177

Open
mbuesch opened this issue Jan 12, 2025 · 4 comments · May be fixed by #179
Open

Support for ATTiny261A, ATTiny461A, ATTiny861A #177

mbuesch opened this issue Jan 12, 2025 · 4 comments · May be fixed by #179
Labels
mcu-support Support for a new microcontroller

Comments

@mbuesch
Copy link
Contributor

mbuesch commented Jan 12, 2025

Tracking issue for ATTiny261A, ATTiny461A, ATTiny861A support.

Current WIP is available in this branch:
https://github.com/mbuesch/avr-device/tree/attinyx61a

mbuesch added a commit to mbuesch/avr-device that referenced this issue Jan 12, 2025
@Rahix
Copy link
Owner

Rahix commented Jan 12, 2025

Very nice! Be aware of the impending changes in #157 which will affect your changeset here. Patches will stay the same, though, now that we have moved to rust svdtools (which you have already pulled into your WIP branch I see)

@mbuesch
Copy link
Contributor Author

mbuesch commented Jan 12, 2025

Thanks for the hint. I will rebase on #157 once that is merged.
I need a bit of time to polish this anyway. But it seems to basically work as-is.

mbuesch added a commit to mbuesch/avr-device that referenced this issue Jan 12, 2025
@mbuesch
Copy link
Contributor Author

mbuesch commented Jan 12, 2025

One question regarding the svd toolchain:
The devices have a couple of fields that are split across two registers (ADMUX and ADREFS). Does the svd toolchain have support for that?
I currently chose to not implement the upper bits of these fields. Which is fine for now, IMO.

@Rahix
Copy link
Owner

Rahix commented Jan 12, 2025

No, split fields cannot be modelled, unfortunately. So far, we have dealt with this by giving the bigger part "double names". Although in practice that HAL code for such chips doesn't reference any enum names at all and instead just writes bare integers. See here for example:

https://github.com/Rahix/avr-hal/blob/d02ab21d17f06baadb5c0f2abf7cf3ea9c0a35b3/mcu/atmega-hal/src/adc.rs#L289-L322

@Rahix Rahix added the mcu-support Support for a new microcontroller label Jan 12, 2025
mbuesch added a commit to mbuesch/avr-device that referenced this issue Jan 18, 2025
@mbuesch mbuesch linked a pull request Jan 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mcu-support Support for a new microcontroller
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants