Package1 - Revision history

Hexkyz: This one is really "Version" (see t186 cboot source)

2020-06-29T17:36:18Z

This one is really "Version" (see t186 cboot source)

2020-06-28T20:04:30Z

2020-05-31T15:04:47Z

Mariko

2020-04-11T17:18:04Z

Mariko

2020-04-11T17:17:13Z

2019-08-16T16:59:51Z

← Older revision		Revision as of 20:59, 16 August 2019
Line 56:		Line 56:

	=== Main ===		=== Main ===
	~~From firmware versions 1.0.0 to 6.1.0, the~~ bootloader poisons the exception vectors, cleans up memory (.bss and init_array), sets up hardware devices (including the security engine and fuses), does all the necessary checks, generates keys and finally decrypts and executes the next stage.		The bootloader poisons the exception vectors, cleans up memory (.bss and init_array), sets up hardware devices (including the security engine and fuses), does all the necessary checks, generates keys and finally decrypts and executes the next stage.

	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">
Line 149:		Line 149:
	</syntaxhighlight>		</syntaxhighlight>

	~~Starting with firmware version~~ 6.2.0~~, the~~ bootloader maintains most of its design, but passes execution to a [[TSEC]] payload and is left in an infinite loop.		[6.2.0+] The bootloader maintains most of its design, but passes execution to a [[TSEC]] payload and is left in an infinite loop.

	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">

2019-08-16T16:58:18Z

Memory controllers

← Older revision		Revision as of 20:58, 16 August 2019
Line 384:		Line 384:
	return mc_iram_reg_ctrl_val;		return mc_iram_reg_ctrl_val;
	</syntaxhighlight>		</syntaxhighlight>

			[6.2.0+] MC_IRAM_TOM is now set to 0x80000000 to allow TSEC to access IRAM and all MMIO.

	==== Key generation ====		==== Key generation ====

2018-12-03T22:38:16Z

generate_retail_keys: fix TSEC#TSEC_key_generation link

← Older revision		Revision as of 01:38, 4 December 2018
Line 483:		Line 483:

	===== generate_retail_keys =====		===== generate_retail_keys =====
	In order to generate retail keys, the bootloader starts by initializing TSEC and grabbing it's [[TSEC#~~Device_key_generation~~\|device key]]. Using static seeds and the SBK, the keyblob injected into the BCT's [[BCT#customer_data\|customer_data]] is validated and decrypted. The resulting keys will then be used to generate the master static key and the master device key.		In order to generate retail keys, the bootloader starts by initializing TSEC and grabbing it's [[TSEC#TSEC_key_generation\|device key]]. Using static seeds and the SBK, the keyblob injected into the BCT's [[BCT#customer_data\|customer_data]] is validated and decrypted. The resulting keys will then be used to generate the master static key and the master device key.

	See the pseudocode bellow for the detailed process.		See the pseudocode bellow for the detailed process.

2018-11-22T19:41:01Z

Header

2018-11-21T14:26:17Z

6.2.0 changes