[Statement of Volatility for Cmod A7]

On 9/9/2020 at 3:40 PM, Iceman2020 said:

Hi @JColvin, I need additional information. The USB controller circuit is a black box. So how exactly would the EEPROM be accessed by a user? Also, the doc references a Digilent API. Where is the API and can a user revert the EEPROM contents to factory default?

Hi @JColvin, the Xilinx 7-series product selection guide lists the distributed RAM as 400 kb for the XC7A35T. Also the last entry in the volatility statement still calls 1CSG326C instead of 1CPG236C. Can you please revise?

[Statement of Volatility for Cmod A7]

On 8/17/2020 at 4:13 PM, JColvin said:

Hi @Iceman2020,

...So I did. I have updated the original posting (direct link to post).

For my own personal curiosity, what are the Statements of Volatility needed for? The only non-volatile memory that users should typically interact with is the flash memory, but that can be easily over-written with a different board configuration or erased entirely, and messing with the EEPROM usually results in bricking the board such that it can't be recognized by the Xilinx software and can no longer be configured. If a known working configuration is needed, there are a number of examples including the out-of-box designs available on the Digilent GitHub (link).

Thanks,
JColvin

Hi @JColvin, I need additional information. The USB controller circuit is a black box. So how exactly would the EEPROM be accessed by a user? Also, the doc references a Digilent API. Where is the API and can a user revert the EEPROM contents to factory default?

[Statement of Volatility for Cmod A7]

Thanks for the updated docs and the additional information, @JColvin! The docs are needed for security compliance. 

[Statement of Volatility for Cmod A7]

On 8/7/2020 at 5:34 PM, JColvin said:

Hi @Iceman2020,

You are correct. I have edited the original posting to now contain this correction.

Thank you,
JColvin

Hi @JColvin

It looks like you only changed the last number and now it's actually an invalid part number. Can you replace all "1CSG326C" with "1CPG236C".

[Statement of Volatility for Cmod A7]

On 8/5/2020 at 5:01 PM, JColvin said:

Hi @Iceman2020,

I apologize for the delay, it look longer than expected. I have attached the two pdfs.

Let me know if you have any questions.

Thanks,
JColvin

Thanks, @JColvin. The attachments call CSG324 package but the FPGA device on the Cmod is CPG236.

[Statement of Volatility for Cmod A7]

On 7/27/2020 at 10:19 PM, JColvin said:

Hi @Iceman2020,

I ask for these materials for you.

Thanks,
JColvin

Hi @JColvin, any update on this?

[Statement of Volatility for Cmod A7]

Can you please create statement of volatility docs for Cmod A7-15T and Cmod A7-35T, similar to the thread below.