KW40Z_Connectivity_Software_1.0.1 (KSDK_1.3.0); IAR 7.50
framework\Bootloader\Bootloader_OTAP_Serial
What hardware changes on new PCB will trigger a rebuild on the Bootloader_OTAP_Serial ?
If NO RTC 32KHz external quartz oscillator on new PCB then the boot loader code must be changed ?
Thank you,
Lucian
Project location framework\Bootloader
Target selection in project
or
Some parameters:
MCU_MKW40Z160
gEepromType_d=gEepromDevice_AT45DB021E_c
so gEepromType_d change should trigger a rebuild.
/* List of the EEPROM devices used on each of the FSL development boards */
gEepromDevice_None_c 0
gEepromDevice_InternalFlash_c 1
gEepromDevice_AT45DB161E_c 2 /* TWR-KW2x */
gEepromDevice_AT26DF081A_c 3 /* TWR-MEM */
gEepromDevice_AT45DB021E_c 4 /* TWR-KW4x*/
What about MCU change type from MCU_MKW40Z160 to MKW30Z ?
Linker gRomSize_c=0x28000 param
other parameters might be:
gEepromParams_WriteAlignment_c, gEepromWriteEnable_d, gSerialBootloaderEnable_c,
gSPI_HW_TYPE_c, gSerialBootloaderEnable_c, BOOTLOADER_CRC_ENABLE, BOOTLOADER_ENABLE_VERIFY,
BOOTLOADER_ENABLE_READ_CMD, BOOTLOADER_INT_WATCHDOG
What other HW PCB changes may trigger boot-loader re-builds ?
What about NO RTC 32KHz external quartz oscillator on new PCB ?
Thank you,
Lucian
32KHz XTAL is not a requirement for the bootloader, so, you're safe on that end. But, you'll loose some low power capabilities.
Here're some scenarios the will requiere a bootloader re-build:
- Any change in the bootloader configuration
- Use different IC
- Use a different SPI module
- Use different pins
- Use different memory
- Add extra functionality