AN2776

Why migrate from FWLib V1.0 to V2.0?

5/20

4.

Update of existing drivers to support the added peripheral instantiation and

miscellaneous additional changes. On this occasion, the APIs (application

programming interfaces) of some drivers were changed, leading to loss of compatibility

with FWLib V1.0. This applies to the drivers of the following peripherals: TIM, SPI,

DMA, USART and NVIC.

Note:

1

Loss of compatibility means that an application code based on one of the above listed

FWLib V1.0 peripheral drivers needs updating to work correctly with FWLib V2.0.

2

FWLib V2.0 comes with eighty-seven (87) examples that cover a wide range of the

peripheral functionalities.

If FWLib V1.0 is used in an application based on Medium-density STM32F10xxx devices

and migration to High-density STM32F10xxx devices is contemplated, two cases should be

considered:

●

The purpose of the migration is to use High-density devices only to benefit from the

larger sizes of embedded memories. In this case, you can still use FWLib V1.0. You

only need to update the development toolchain-specific files (linker, Flash loader, etc.)

●

The purpose of the migration is to use the additional peripherals introduced in High-

density devices. In this case, you have to migrate to FWLib V2.0. The development

toolchain-specific files also need updating (linker, Flash loader, etc.).