AN3181

Class B software package

Doc ID 17286 Rev 2

13/31

3.2

Package organization

This section describes how the ST solution is organized.

3.2.1

Projects and workspaces included in the package

Three projects have been prepared for each package using different toolchains. The project

for IAR C-compiler is done under IAR EWSTM8 environment, while projects for both Cosmic

and Raisonance C-compilers are done as ST Visual Develop (STVD) project workspaces.

The corresponding Project.eww or Project.stw project file must be configured for a specific

STM8x device settings and adequate workspace configuration before any compilation.

3.2.2

Tool specific integration of the library

Each project covers all settings and includes needs for both compilation and linking

processes. User has to check the symbols defined for preprocessor at project settings as

these symbols configure the project main structure and used features. The user can make

detailed configurations at library parametric header file (see Section 3.3: Package

configuring and debugging). Predefined linker script files *.icf are included at IAR projects

for different microcontrollers. Linker script files *.lkf for STVD projects are generated

automatically and placed into DEBUG or RELEASE directories. User can make a copy of

these files, edit them and force compiler to use the overwritten file.

Reset handler must be modified to perform STL_StartUp function after reset before

standard C-compiler initialization starts. Therefore startup assembly file csstartup.s (IAR) or

startup.asm (Raisonance) must be modified in that way. For Cosmic, the reset handler is

changed at stm8_interrupt_vector.c file.

Caution:

Be careful when invariable memory checksum setting is configured for the project. It is

quite different for different compilers. IAR compiler uses project option setting applied at its

specific Checksum card window of linker. When Raisonance C-compiler is used, user

should define checksum range and its placement using user defines option declared at the

project settings:

●

CRCRANGE(begin_address, end_address) - continuous space under CRC

computation

●

CRCPLACE(crc_address) - placement of CRC result

●

FILLGAP(fill_constant) - setup of unused memory areas

Cosmic C-compiler requires to define all the segments under checksum computation (by

adding -ck parameter to each of them) and specific checksum segment keeping the

checksum descriptor table must be included into the project and allocated at invariable

memory additionally with applied -ik parameter.

Specific segments for Class B variables and checking stack overflow must be added into

project and allocated at variable memory, too. Double storage in CLASS_B_RAM and

CLASS_B_RAM_REV separated segments is necessary to ensure the redundancy of the

safety critical data (Class B). All other variables defined without any particular attributes are

considered as Class A variables and their storage area is not checked during the

transparent RAM test. The size and allocation of these segments can be modified at linker

script files or directly by project settings.