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

Investigate dual-bank OTA #30

Open
sahil-kale opened this issue Sep 20, 2023 · 0 comments
Open

Investigate dual-bank OTA #30

sahil-kale opened this issue Sep 20, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@sahil-kale
Copy link
Owner

Currently, the voyager bootloader does not explicitly offer support for dual-banked flash systems. However, a user can actually implement dual-banked flash by getting smart with the nvm_read function. A user can add a variable dictating what partition they want to write to that is accessed every time nvm_read is accessed, and based on that variable, returns the correct application size/crc/app start/end addresses.

I don't think this is something the bootloader should support by 'knowing' about the partition as it will deviate from making the bootloader agnostic. Instead, writing a guide and demo on this should be sufficient as the user can effectively control where in flash memory is written and implement dual/triple/n banked systems with this strategy. Might also need a demo

@sahil-kale sahil-kale added enhancement New feature or request good first issue Good for newcomers labels Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant