
Originally Posted by
matekhr
Here is my idea about authorizations:
Attached screenshot shows extracted eeprom part of "elchips" firmware file. (sorry, elprog, I have to put a screenshot here, I can't explain without the picture).
Looking at the marked part, you'll see it consists of 5AA5 and A55A blocks. Now look at the authorizations screen of our xprog-m programmer. In case of full authorizations, we'll have total of 22 lines, 9th line is "Development tools" and shows "-" instead of "authorized". ARM micronas are two last lines, which are not authorized in our case.
Now look again at our screenshot - let's make a presumption that 5AA5 means "authorized", and A55A means "not authorized" or "-".
That idea works perfect for first 15 lines - we have 8 authorized lines, one not authorized and then 6 authorized.
Now comes a little messy part: 11 A55A's, 3 5AA5's, 1 A55A, 2 5AA5's and finally 8 A55A's.
Counting in total, we have 19 "authorized" lines (what is good), and we need 21 to make ARM micronas authorized, too.
According to that logic, two of eight A55A's in last "unauthorized" block must be changed to 5AA5 to become "authorized".
Maybe I'm totally wrong, but somehow it seems to me this could work. Because I repaired my xprog-m programmer in other way, and now works 100%, I would like someone (Bram380 maybe?) to test my idea.
Of course, I don't know will this work at all, what about checksums etc. - it's only an idea...
Bookmarks