sw_apps:zynq_fsbl: MD5 related changes in FSBL

Checksum Offset value for calculation for MD5 checksum
is modified to take the relative address from the
image start address instead of exact offset specified
in partition header.

Signed-off-by: Krishna Chaitanya <kpataka@xilinx.com>
Acked-by: Nirmala Pelluri <nirmala@xilinx.com>
This commit is contained in:
Krishna Chaitanya 2014-07-15 12:48:04 +05:30 committed by Jagannadha Sutradharudu Teki
parent 61ea3dd4bb
commit 1b9aa61b5d
2 changed files with 7 additions and 0 deletions

View file

@ -202,6 +202,10 @@
* 791245 - Use of xilrsa in fsbl
* Resolution: Rsa library is removed from fsbl source
* and xilrsa is used from BSP
* 10.00a kc 07/15/14 Fix for CR#804595 Zynq FSBL - Issues with
* fallback image offset handling using MD5
* Resolution: Updated the checksum offset to add with
* image base address
* </pre>
*
* </pre>

View file

@ -69,6 +69,8 @@
* only if partition owner was not set to u-boot
* 9.00a kc 04/16/14 Fix for CR#785778 FSBL takes 8 seconds to
* authenticate (RSA) a bitstream on zc706
* 10.00a kc 07/15/14 Fix for CR#804595 Zynq FSBL - Issues with
* fallback image offset handling using MD5
*
* </pre>
*
@ -468,6 +470,7 @@ u32 LoadBootImage(void)
*/
Status = ValidateParition(PartitionStartAddr,
(PartitionTotalSize << WORD_LENGTH_SHIFT),
ImageStartAddress +
(PartitionChecksumOffset << WORD_LENGTH_SHIFT));
if (Status != XST_SUCCESS) {
fsbl_printf(DEBUG_GENERAL,"PARTITION_CHECKSUM_FAIL\r\n");