Raspberry Pi EEPROM example - how to calculate lengths and checksums #3
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.
Hi, this is a great project!
I have a question (and contributions maybe?)
Please see the added
examples/rpi_eeprom.py
file. There are certain fields that can only be computed after the build (numatoms
,eeplen
) and others that additionally need to parse the raw value of various fields (crc
). The CRC is especially bad, since I have to do a lot of work that duplicates knowledge of the CRC:Am I missing an easier way to do this?