5 Best Practice and FAQ HCS08 and HCS12 Support

Table of Contents

About

Starting with Version V5.1.0, it is now possible to create projects for our products based on the HCS08 and HCS12 microcontroller. This chapter is supposed to start of users who have created projects with HCS08 or HCS12 based products in Developers Studio previously, but have no prior experience in Applics Studio. It should also give a short overview about the current support for these microcontrollers in Applics Studio and demonstrate the current differences in capability between Developers Studio and Applics Studio in regards to HCS08 and HCS12.

Restrictions

  • Graphical Blocks: The HCS08 and HCS12 microcontroller does not support the functionalities of the graphical blocks SET_PWM_FREQ, CURRENT_CONTROL, PWM_SET_FREQ and PWM_SET_DUTY from the MRS_Specific_Lib. Therefore, these blocks are not available while developing a HCS08 or HCS12 project in the Graphical Programming (GP).

Differences to Developers Studio

1. Folder structure: The new folder structure for the HCS08 and HCS12 projects is based on the current Applics Studio project template in use for S32K based products and can be seen below:

├───bin
│   ├───lib
│   └───prm
├───ds
└───src
    ├───app
    │   ├───user_api
    │   └───user_sources
    ├───bios
    ├───ds
    │   ├───can
    │   ├───dsl
    │   ├───gp
    │   ├───io
    │   ├───lin
    │   ├───module
    │   ├───parameter
    │   └───user
    ├───gp
    ├───includes
    ├───lin
    ├───mapping
    └───os

2. Compilation of the project: Developers Studio used to create the text file compiler_linker.txt in which all the commands for the compiler where saved. It was a common practice in Developers Studio to add additional user source files to the compiler_linker.txt to include them for the final .s19 binary. Within the Applics Studio the .s19 file gets created by using make. All source files in the folder ./src/app/user_sources will be also included by the default makefile and can therefore be used by the customer to include individual source files. Another way to include individual source files is to adjust the makefile which is located in the root of the created project. Be aware of the fact that in this case you probably also need to update the sub makefiles:

  • ./src/src.mk
  • ./src/app/app.mk
  • ./src/app/user_sources/app_user.mk

All the necessary tools like the linker or compiler remain the same as in Developers Studio.

3. Mapping layer: Another new part of the HCS08 and HCS12 project structure is the new mapping layer. The mapping layer maps functions from the current user API to the legacy user API of Developers Studio. This is necessary as the BSW for HCS08 and HCS12 products still expects these legacy function calls and to create backwards compatibility to existing developers studio projects.

Note: This implies that you have the option to code using the familiar functions from Developers Studio. However, it is advised to stick with the current user API provided by Applics Studio.

The topic Migration from HCS08-12 (Developers Studio) gives a quick overview of the functions which are mapped in the mapping layer.

4. Graphical Programming: Because Applics Studio is using Graphical Programming (GP) instead of Eagle, the code generation, especially for the graphcode, has changed. Therefore, there may be small differences in performance and memory consumption.