• 0

Statement of Volatility for Cmod A7


Question

9 answers to this question

Recommended Posts

  • 0
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".

Link to post
Share on other sites
  • 0

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

Link to post
Share on other sites
  • 0
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?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now