-
Notifications
You must be signed in to change notification settings - Fork 85
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
Usb integrate #595
Merged
Merged
Usb integrate #595
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
in anticipation of starting to emulate the FS
we can now recover from an I2C timeout and get the PMIC data out, but mysteriously, when we leave the routine, the CPU hangs. I think fundamentally the I2C instability is due to something very wonky inside the chip itself, so the recovery only papers over an issue that is only fixed with a reboot...
also initialize the disk image with some default data
this is a pre-initialized, FAT12 image that is compatible with Windows (which is the harder of the OSes to please)
the curve 25519 accelerator hw is different on different targets so it can't be enabled for all of them all at once. This is going to be come a bigger problem as time goes on...
right now our patch set assumes a single HW configuration for cryptography accelerators. This isn't going to be true going forward. A more scalable approach to patching accelerators is going to be needed. For now, we're just falling back to software acceleration for the cramium target.
this doesn't protect against malicious tampering (because the public key is the developer key) but it will at least catch correctness errors in USB upload and filesystem behavior.
need code space to handle image verification. getting kind of heavy, but I think we're almost done.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update via USB in bootloader is now functional.
Can alternatively update the kernel or the application areas depending on the file copied in.
Trivial image validation is done - more work needs to happen on the security side, but this is good enough for development.
Loader updates have to happen once in kernel mode - or some other scheme has to be worked out because the code is XIP in the loader, so writing the code would essentially lead to failure.