Open GoogleCodeExporter opened 9 years ago
it seems some programs read the first byte after the nv number as the read
length and then limit the hex=>text conversion to that length
im not sure if it makes a difference, as i couldn't recommend anyone write the
'text' values in this case
i would suggest:
1. go to the log tab
2. find the nv item in question
3. copy the hex response, minus the last three bytes (crc, 7e), and the first
three bytes (26, nvItemnumber)
4. paste into the pass/nvitem in question with 0x prefixed to indicate a hex
write 0x[copied bytes]
maybe a nice feature would be the ability to right click and have the value
'toggle' back and forth between hex and text values
Original comment by chromableedstudios
on 4 May 2013 at 4:14
check out r84 to see the 'right click to show hex' in action
Original comment by chromableedstudios
on 8 May 2013 at 11:36
Original issue reported on code.google.com by
chromableedstudios
on 3 May 2013 at 2:34Attachments: