Troubleshooting

Troubleshooting

This section provides an overview of the most common errors you might encounter along with possible resolutions. The following problems are explained:

• Missing device
• Error instantiating RTE components
• Missing software components
• Updating configuration files
• Manual migration from Keil.ARM_Compiler pack
• Linker warning L6314W
• Linker errors using the RTX5 library
• Run-time exceptions due to wrong processor mode in RTX5
• Use of undeclared identifier CoreDebug error

Missing device

The following error occurs when you try to migrate a project to CMSIS v6 but you have not installed the Cortex_DFP pack:

Error instantiating RTE components

The following error occurs when you try to migrate a Keil RTX-based project but you have not installed the CMSIS-RTX pack:

Missing software components

Migrating Keil RTX5-based projects

The following warning is shown in the Validation Output window when you try to migrate a Keil RTX-based project:

Migrating projects

The following error comes up if the Device:Startup component requires a CMSIS-CORE component with a specific v5.x.x version.

In the Build Output window you might see:

Despite this warning, the build operation should work normally and the resulting binary will work fine on hardware. If you want to get rid of the error, check one of the following options.

A similar error can come up for any software component. Here is an example using MDK-Middleware:

    

        
        
            <require Cclass="CMSIS" Cgroup="CORE" Cversion="5.6.0"/>
        
    

    

        
        
            <require Cclass="CMSIS" Cgroup="CORE"/>
        
    

Updating configuration files

Moving a component from one pack to another has an additional implication. The Event Recorder component, for example, comes with a configuration file (EventRecorderConf.h). This configuration file is stored in the project under the RTE/Cclass folder. When you switch from one pack to the other, the Cclass name changes and a fresh copy of the original configuration file is copied to your project.

Manual migration from Keil.ARM_Compiler pack

As the components from the Keil.ARM_Compiler pack do not have 1:1 replacements, you need to deselect the old components and select the replacements from the two new packs (ARM.CMSIS-Compiler and ARM.CMSIS-View):

1. Compiler:EventRecorder migration

   Deselect the Compiler:Event Recorder component and select the CMSIS-View:Event Recorder component:

   

2. Compiler:I/O migration

   Deselect any component of Compiler:I/O and select the corresponding CMSIS-Compiler component:

   

   This table helps you to identify the correct components:

   Compiler:I/O:	CMSIS-Compiler:
   STDERR@Breakpoint	STDERR (API):Breakpoint
   STDERR@ITM	STDERR (API):ITM
   STDERR@User	STDERR (API):Custom
   STDIN@Breakpoint	STDIN (API):Breakpoint
   STDIN@ITM	STDIN (API):ITM
   STDIN@User	STDIN (API):Custom
   STDOUT@Breakpoint	STDOUT (API):Breakpoint
   STDOUT@EVR	STDOUT (API):EventRecorder
   STDOUT@ITM	STDOUT (API):ITM
   STDOUT@User	STDOUT (API):Custom
   TTY@Breakpoint	TTY (API):Breakpoint
   TTY@ITM	TTY (API):ITM
   TTY@User	TTY (API):Custom

Linker warning L6314W

With CMSIS v6, a linker warning as shown below may get reported:

    

        
        
            L6314W: No section matches pattern *(.bss.noinit)
        
    

This is due to the following entry in the Arm Compiler for Embedded scatter files:

    

        
        
            RW_NOINIT __RW_BASE UNINIT __RW_SIZE {
  *(.bss.noinit)
}
        
    

This section is created for usage with CMSIS-View’s Event Recorder , placing the event buffer in uninitialized memory so that it is persistent after a software reset.

Linker errors using the RTX5 library

In CMSIS v5, the RTX5 libraries were built using the compiler options -fshort-enums and -fshort-wchar. In CMSIS v6, the default compiler options are different. If you are using the new libraries with old build settings, you will encounter the linker error L6242W:

    

        
        
            .\Blinky.axf: Error: L6242E: Cannot link object Itx timer.o as its attributes are incompatible with the image attributes.
   ... wchart-16 clashes with wchart-32.
   ... packed-enum clashes with enum_is_int
        
    

Run-time exceptions due to wrong processor mode in RTX5

With the new Keil RTX5 v5.8.0, the default processor mode for thread execution has changed. Previously, it was:

    

        
        
            define OS_PRIVILEGE_MODE 1
        
    

This enabled the privileged mode for threads by default.

The new default is:

    

        
        
            define OS_PRIVILEGE_MODE 0
        
    

This results in exceptions at run-time when threads use privileged operations.

Use of undeclared identifier CoreDebug error

Some symbol names were changed in CMSIS v6 which might lead to the following error:

    

        
        
            /fsl_common_arm.c:126:9: error: use of undeclared identifier 'CoreDebug'
  126 |         CoreDebug->DEMCR |= CoreDebug_DEMCR_TRCENA_Msk;
      |         ^
        
    

This results in failing builds.

If an update is not possible or pushed out, we have created a header file that patches the changes and allows you to run older software with CMSIS v6.

    

        
        
            project:
  add-path:
    -  <known_location>       #directory of any files you would like to include. 
        
    

    

        
        
            project:
  misc: 
    - for-compiler: AC6
      C:
        - --include cmsis_5_to_6_patch.h
      CPP:
        - --include cmsis_5_to_6_patch.h