NXP Semiconductors K32 L2A Series, Справочное руководство, Страница: 256 / 1379

14.3.4 Clock Configuration
By default, the bootloader does not modify clocks. The Kinetis Bootloader in ROM will
use the clock configuration of the chip out of reset unless the clock configuration bits in
the FOPT register are cleared, or if a USB peripheral is enabled, or if a QuadSPI
peripheral is enabled.
• Alternate clock configurations are supported, by setting fields in the Bootloader
Configuration Area (BCA) shown in Table 14-3 .
• If the HighSpeed flag of the clockFlags configuration value is cleared, or if a USB
peripheral is enabled, the bootloader will enable the internal 48 MHz reference clock.
• In high speed mode, the core and bus clock frequencies are determined by the
clockDivider configuration value.
• The core clock divider is set directly from the inverted value of the clockDivider
unless a USB peripheral is enabled. If a USB peripheral is enabled and the inverted
value of the clockDivider is greater than 2, then the value is reduced to 2, in order to
keep the CPU clock above 20 MHz.
• The bus clock divider is set to 1, unless the resulting bus clock frequency would be
greater than the maximum supported value. In this case, the bus clock divider is
increased until the bus clock frequency is at or below the maximum.
• Note that the maximum baud rate of serial peripherals is related to the core and bus
clock frequencies. To achieve the desired baud rates, high speed mode should be
enabled in BCA.
14.3.5 Bootloader Entry Point / API Tree
To run the Kinetis Bootloader, a user application simply calls the runBootloader function.
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, which for the ROM is
0x1C00_0000; the API tree pointer is at address 0x1C00_001C.
The bootloader API tree is a structure that contains pointers to other structures, which
have the function and data addresses for the bootloader. The bootloader entry point is
always the 1st word of the API tree.
typedef struct BootloaderTree
{
void (*runBootloader)(void *arg); //!< Function to start the bootloader
executing.
standard_version_t version; //!< Bootloader version number.
const char *copyright; //!< Copyright string.
const bootloader_context_t *runtimeContext; //!< Pointer to the bootloader's runtime
context.
const flash_driver_interface_t *flashDriver; //!< Flash driver API.
const aes_driver_interface_t *aesDriver; //!< AES driver API.
Functional Description
K32 L2A Reference Manual, Rev. 2, 01/2020
256 NXP Semiconductors