This demo is targeted towards the Nucleo-L496ZG board, with 1 MB internal Flash EEPROM and 320 kB internal RAM.

To compile the demo programs you can use the Keil MDK development environment.

To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable.

Before the bootloader can be used, it needs to be built and programmed into the STM32L496's internal flash memory. The steps in this section only need to be done once.

When using Keil MDK, simply open the project from within uVision. The project file (stm32l496.uvprojx) is located at: \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Boot\ide\. Once opened, select Project→Rebuild all target files from the menu to compile all the bootloader sources and link the together into the final executable.

The bootloader program is now ready to be programmed into the internal flash memory of the STM32L496. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports:

• \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Boot\bin\openblt_stm32l496.axf
• \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Boot\bin\openblt_stm32l496.srec

When using Keil MDK, simply open the project from within uVision. The project file (stm32l496.uvprojx) is located at: \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Prog\ide\. Once opened, select Project→Rebuild all target files from the menu to compile all the demo program sources and link the together into the final executable.

The output file is

• \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Prog\bin\demoprog_stm32l496.srec

To download the demo program \Target\Demo\ARMCM4_STM32L4_Nucleo_L496ZG_Keil\Prog\bin\demoprog_stm32l496.srec using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:

• Firmware updates using the RS232 communication interface
• Firmware updates using the USB communication interface