View Single Post
      05-25-2016, 05:48 PM   #1131
Exotic Hadron
X Eins in der Luft
12
Rep
81
Posts

Drives: X1
Join Date: Sep 2010
Location: Leningrad, Rußland

iTrader: (0)

Possible reason for 0xD1 returned by FSC decoder

Quote:
Originally Posted by pikcachu View Post
for some reason now one of the generators says:

"version after create() = 0xD1"
This was asked a long time ago, but since it is the most relevant GOOG result, and there doesn't seem to be an answer (except for 0x20h extra ASCII symbols) in here, I'd love to add another explanation.

The reason could be that the size of FSC/HEX file is incorrect. I've had this 0xD1 error when I've left an extra byte in edited generalPersistencyData_DiagnosticSWTController file.

If you edit this file to extract the 1B sequence, please be attentive to four bytes that prepend the 01 01 00 1B ... sequence of generalPersistencyData_DiagnosticSWTController. These four bytes (if you read them in reversed order) provide the length of 1B file (the number of bytes you must cut starting from 01 01 00 1B ... sequence [typically at 0x270 offset]).

The 1B length is typically 319 bytes, but it can be longer. If you cut out an incorrect number of bytes, FSC tool will return

Quote:
"version after create() = 0xD1"
Hope it helps other rookies like myself.
Appreciate 1