Changes between Version 56 and Version 57 of jtag_instructions


Ignore:
Timestamp:
10/15/2025 03:51:21 PM (8 weeks ago)
Author:
Ryan Erbstoesser
Comment:

add note about secure jtag

Legend:

Unmodified
Added
Removed
Modified

  • jtag_instructions

    v56 v57  
    341341If still have difficulties, please contact Gateworks support at !support@gateworks.com
    342342
     343
     344
     345= Secure JTAG
     346If you are enabling Secure JTAG on your i.mx8mm boards (via setting SJC_LOCK via 'fuse prog -y 0 0 0x400') upon JTAG programming you will see something like:
     347{{{
     348Channel #      S01
     349--------------------------------------------------------------------------------
     350USB Open Rev    r0
     351JTAG_ID #00    CSD
     352JTAG_ID #01    MSP
     353Device Locked  00%
     354Challenge: 0x1B2A9209DAB4B890, Response:
     355}}}
     356
     357At this point you would enter the 56bit hex response (with or without leading 0x).
     358
     359The 64bit challenge key is a board-specific unique key (meant for you to store in a secure database associated with the 56bit response key). The 56bit response key is programmed into 0x600[0:31] and 0x610[0:23] (via 'fuse prog -y 8 0 <lowerbits>' and 'fuse prog -y 8 1 <upperbits>).
     360
     361You can also enter the response via a command-line argument '-c <56bithex>'.
     362
     363There isn't anything special you have to have installed other than a version of jtag_usbv4 later than Sep 27. Our latest version of jtag_usbv4 (v5.0-g34e7cc5) can be found at https://dev.gateworks.com/jtag/jtag_usbv4.
     364
    343365= JTAG Programmer Hardware
    344366Please see out JTAG hardware page here: [wiki:jtag JTAG Hardware PAGE]