NXP Semiconductors Kinetis KE1xZ256, Reference Manual

Page: 501 / 1325

NOTE
The flashloader and flash-resident bootloader do not support
this feature (flash driver API tree).
To get the address of the entry point, the user application reads the word containing the
pointer to the bootloader API tree at offset 0x1C of the bootloader’s vector table. The
vector table is placed at the base of the bootloader’s address range.
22.4.2 Flash driver API Tree
The bootloader API tree is a structure that contains pointers to other structures, which
have the function and data address for the bootloader. The Flash driver API tree entry is
always the 5th word of the API tree.
The prototype of the entry point is:
flash_driver_interface_t flashDriver;
There are several slightly different versions of the flash driver API among different
targets with ROM bootloader.
Table 22-33. Different versions of the flash driver
Flash driver API
version
Supported targets
V1.0 KL03Z4 KL43Z4 KL33Z4 KL27Z4 KL17Z4
V1.1 KL27Z644 KL17Z644
V1.2 KL13Z644 KL33Z644 K80F256 K81F256 K82F256 KL81Z7 KL82Z7 KL28Z7
There are minor differences in the flash driver interface among the flash driver API
versions. See the definitions below.
typedef union BootloaderVersion
{
struct
{
uint32_t bugfix : 8; //!lt; bugfix version [7:0]
uint32_t minor : 8; //!lt; minor version [15:8]
uint32_t major : 8; //!lt; major version [23:16]
uint32_t name : 8; //!lt; name [31:24]
} B;
uint32_t version; //!lt; combined version numbers
} standard_version_t;
//! @brief Interface for the flash driver.
typedef struct FlashDriverInterface
{
#if !defined(FLASH_API_TREE_1_0)
standard_version_t version; //!lt; flash driver API version number.
#endif
Chapter 22 Kinetis ROM Bootloader
Kinetis KE1xZ256 Sub-Family Reference Manual, Rev. 3, 07/2018
NXP Semiconductors 501