<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="-1">I have not got back to the ST Link, but I've been
trying to use Impact to independently verify the use of the
cryptech_upload script to reflash the bitstream PROM.<br>
<br>
Using cryptech_upload i get a checksum of CRC-32 0x6f23447b.<br>
<br>
Using the alpha_fmc.bit from the same tarball cryptech_upload is
extracting and generating a .mcs file as outlined in<br>
</font><a moz-do-not-send="true"
href="https://www.xilinx.com/support/documentation/application.../xapp586-spi-flash.pdf"><br>
<font size="-1"><cite class="iUh30">https://www.xilinx.com/support/documentation/application.../xapp586-spi-flash.pdf</cite></font></a><br>
<br>
<font size="-1">I get "All Checksum calculations are performed on
the address range spanned by the configuration file.<br>
'1': Calculated checksum matches expected checksum, 006303f92"
when programming with this generated .mcs<br>
The FPGA ready led comes on green but gives core error message
when trying to set masterkey.<br>
<br>
Re-flashed using the cryptech_upload --fpga --user wheel command.
</font><font size="-1"><font size="-1">Once again this command
resulted in a checksum of 0x6f23447b and core operations were
back to normal. I </font>then performed a "Get Device Checksum"
in impact and got this <br>
<br>
"All Checksum calculations are performed on the address range
spanned by the configuration file.<br>
ERROR:Cse - '1': The calculated checksum (0x063005bd) differs from
the expected checksum (0x06303f92).<br>
PROGRESS_END - End Operation."<br>
<br>
</font>
<div class="moz-cite-prefix">On 05/04/2018 12:00 AM, Rob Austein
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20180504050026.EC5EB2003E2BD5@minas-ithil.hactrn.net">
<pre wrap="">On Fri, 04 May 2018 00:00:10 -0400, Michael wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
One curious thing, if I use the "firmware upload" command while in
cryptech_console, I see the blue LED flash as described in the
documentation indicating the bootloader is being accessed. Calling
cryptech_upload from the terminal does not seem to reset to the
bootloader (no flashing blue LED)
</pre>
</blockquote>
<pre wrap="">
>From your description, cryptech_upload isn't getting that far in the
dialog. Add the --debug option if you want to see the details.
</pre>
</blockquote>
<br>
</body>
</html>