You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 timenvm_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
The text was updated successfully, but these errors were encountered: