Code Footprint

Final code footprint depends on many factors, such as target compiler, compilation flags; e.g. with or without code optimization, used applications, third-party crypto library to support the shielded communication, usage of the shielded communication itself, or I²C frame buffer size.

For the table below we used DAVE™ build-in compiler (ARM GCC) for the XMC4800 IoT Connectivity Kit. All numbers are aprox. The setup based on the Get Started Guide (SHA Fingerprint b6ae6d8).

The following generated map files were used for calculations:

• All Functions, -s Optimisation
• All Functions, -s Optimisation, No RSA Support
• All Functions, -s Optimisation, No RSA Support, No Shielded Communication

The following tool has been used to analyse map files: AMAP For all measurements optimization level "-Os" has been selected. The setup without optimization might take up to 100% of the showed here code footprint

A generic module	FLASH/RAM in kB	Part of the module	FLASH in kB	RAM1 in kB
OPTIGA™ Trust M hostcode	25.2 / 11.5 3	Core Functions3	2.7	2.9
		ECC + Protected Update + RND + TLS PRF	5.2
		RSA	1.4
		Infineon I2C protocol3	3.7
		Shielded Connection + 3rd party crypto	4 + 8.2	8.6

¹ Compile time memory allocation (.bss and .data sections, no heap included if it's used)

² Values include all features and mbed TLS as the third-party crypto provider

³ Mandatory modules, all others are optional.