Changes between Version 13 and Version 14 of gsc


Ignore:
Timestamp:
05/18/2018 11:43:28 PM (7 years ago)
Author:
Tim Harvey
Comment:

updated secure key size for Newport

Legend:

Unmodified
Added
Removed
Modified

  • gsc

    v13 v14  
    380380|| 0x000-0x0FF  || 0x50: 0x00-0xFF  || 256            || User EEPROM space           ||
    381381|| 0x100-0x17f  || 0x51: 0x00-0x7F  || 128            || '''Board Info''' EEPROM ^1^ ||
    382 || 0x180-0x1DF  || 0x51: 0x80-0xDF  || 96             || '''Secure Key''' EEPROM ^2^ ||
     382|| 0x180-0x1DF  || 0x51: 0x80-0xDF  || 96 ^5^         || '''Secure Key''' EEPROM ^2^ ||
    383383|| 0x1E0-0x1FF  || 0x51: 0xE0-0xFF  || 32             || Reserved                    ||
    384384|| 0x200-0x2FF  || 0x52: 0x00-0xFF  || 256            || User EEPROM space ^3^       ||
    … …  
    396396  * EEPROM_WP_ALL (R15.0) will dissalow user i2c writes to all EEPROM regions (does not affect ''secure key'' erasure cases)
    397397  * EEPROM_WP_BOARDINFO (R15.1) will dissallow user i2c writes to the ''Board Info'' EEPROM region
     398 5. The GSC v3 used on the Newport product family provides 128 bytes of '''Secure Key''' area instead of 96.
    398399
    399400=== EEPROM Secure Key Example ===
    400 The secure key is stored between 0x80 and 0xDF. This is 96 bytes long.
     401The secure key area starts at 0x51 offset 0x80 and extends for 96 bytes for GSC v1/v2 (Laguna/Ventana) and for 128 bytes for GSC v2 (Newport).
    401402
    402403To see the secure key, you can use the command i2cdump from the command line: (starts with the ASCII values of D3 and ends with w in below example)