Skip to content

Conversation

@bruno-f-cruz
Copy link
Member

@bruno-f-cruz bruno-f-cruz commented Jun 23, 2024

  • Remove unused registers and rearrange device metadata to accommodate new functionality
  • Implement a new register for continuous streaming of sound or frequency generation state
  • Fix digital I/O interrupts and configuration
  • Stop frequency generation when going to standby mode

@bruno-f-cruz bruno-f-cruz changed the title Main v3.0 firmware release Jun 23, 2024
Copy link
Member Author

@bruno-f-cruz bruno-f-cruz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is a common typo across many firmware files that would be nice to fix

Copy link
Contributor

@glopesdev glopesdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments, otherwise looks good. The PR is still marked as draft, I guess one important thing we need to discuss before broad deployment is how to deal with firmware updates in cases of multi-microcontroller devices.

Would be nice if it is possible to have a uniform update procedure using the existing bootloader protocol, but maybe let us discuss this in a separate issue / PR.

@CLAassistant
Copy link

CLAassistant commented Jun 9, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@glopesdev glopesdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the device.yml and have some questions / suggestions that would be nice to review together. It might impact firmware naming a little bit, but hopefully not too hard to replace.

@glopesdev glopesdev marked this pull request as ready for review June 11, 2025 09:12
@glopesdev
Copy link
Contributor

glopesdev commented Jun 11, 2025

@filcarv @artursilva0 @bruno-f-cruz A reminder that another thing we need to do before merging is regenerate the interface. We might end up merging #24 first so we are able to check this automatically for every PR from now on.

P.S.: We also probably want to rebase this branch first so we make sure to use the latest version of the generators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants