meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
adv:hardsectorconf [2022/06/13 06:35] – diskblitzadv:hardsectorconf [2022/07/26 20:30] – diskblitz
Line 170: Line 170:
 ex: ''"addrCksumType": "8xrl"'' ex: ''"addrCksumType": "8xrl"''
  
-=== dataCksumIndex ===+=== addrCksumIndex ===
 Int - //Required//\\ Int - //Required//\\
 Byte index of the start of the stored checksum relative to the address marker (0 = address marker). Byte index of the start of the stored checksum relative to the address marker (0 = address marker).
  
-ex: ''"addrCksumIndex": 257''+ex: ''"addrCksumIndex": 5''
  
 === addrCksumByteSize === === addrCksumByteSize ===
Line 202: Line 202:
 Byte index of the last byte of the address field that needs to be checksummed, relative to the address marker (0 = address marker). Byte index of the last byte of the address field that needs to be checksummed, relative to the address marker (0 = address marker).
  
-ex: ''"addrCksumToIndex": 256''+ex: ''"addrCksumToIndex": 4''
  
 === addrCksumInit === === addrCksumInit ===
Line 222: Line 222:
 ex: ''"addrCksumPoly": 4129'' ex: ''"addrCksumPoly": 4129''
  
-=== addrCksumRevIn ===+=== addrCksumRefIn ===
 Boolean\\ Boolean\\
-If true, then the data bytes will have their bit-endian reversed (eg: 0x80 becomes 0x01) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.+If true, then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.
  
-ex: ''"addrCksumRevIn": true''+ex: ''"addrCksumRefIn": true''
  
-=== addrCksumRevOut ===+=== addrCksumRefOut ===
 Boolean\\ Boolean\\
-If true, then the result of the checksum algorithm will have its bit-endian reversed on output. If no value is provided, then it defaults to ''false''.+If true, then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.
  
-ex: ''"addrCksumRevOut": true''+ex: ''"addrCksumRefOut": true''
  
 === addrEpilog === === addrEpilog ===
Line 440: Line 440:
 ex: ''"dataCksumPoly": 4129'' ex: ''"dataCksumPoly": 4129''
  
-=== dataCksumRevIn ===+=== dataCksumRefIn ===
 Boolean\\ Boolean\\
-If true, then the data bytes will have their bit-endian reversed (eg: 0x80 becomes 0x01) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.+If true, then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.
  
-ex: ''"dataCksumRevIn": true''+ex: ''"dataCksumRefIn": true''
  
-=== dataCksumRevOut ===+=== dataCksumRefOut ===
 Boolean\\ Boolean\\
-If true, then the result of the checksum algorithm will have its bit-endian reversed on output. If no value is provided, then it defaults to ''false''.+If true, then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.
  
-ex: ''"dataCksumRevOut": true''+ex: ''"dataCksumRefOut": true''
  
 === dataEpilog === === dataEpilog ===