NEW: Make the crypto test compatible with ATSHA204A. Eliminate the co… #18
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.
Hello,
My name is Bogdan Deac and I'm working for Digilent. We are going to replace the ATSHA204 chip, which is obsolete, with ATSHA204A for all CML boards that will be produced from now. We tested the ATSHA204A chip by running our internal manufacturing test and the nf1_cml_crypto_example. Everything works well except the Configuration Zone Test. The config word 3 should be 0xEE55 but we read 0xEE0E. The chip's datasheet mentions 0xEE55 as well. We started a support case with Microchip regarding this issue. Here is their answer: "Internal team has confirmed that this value can vary and software should not depend on any particular value. Therefore, reading different value from that mentioned in the datasheet is likely." Taking this into account I changed the crypto test to check the first configuration word only. In this way the test is compatible with ATSHA204A and is backward compatible with ATSHA204.
Best regards,
Bogdan Deac