ARMclang support for S32K144

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ARMclang support for S32K144

1,070 Views
uChris
Contributor I

I have two different example uVision projects for the S32K144 MCU:

Both projects are for the S32K144EVB evaluation board and toggle a LED. The target is the S32K144HAxLL.

In the "Options for Target - Target" window I can select the compiler. I have two options there to select:

  • V5.06
  • V6.10.1

When I choose V5.06 it will use ARMCC and it gives me 1 error:
.\RTE\Device\S32K144HAxxxLLx\S32K144_64_flash.sct(11): error: L6236E: No section matches selector - no section to be FIRST/LAST.

When I choose V6.10.1 and I enable "Assemble by using ArmClang V6" in the "Options for Target - Asm" window, it will use ARMCLANG and it gives me 931 errors and all of them are caused by the startup file (e.g. see below):
RTE/Device/S32K144HAxxxLLx/startup_S32K144.S(2): error: unexpected token in argument list

When I keep V6.10.1 as compiler but disable the "Assemble by using ArmClang V6" option I get 10 errors, all caused by the startup file (e.g. see below):
RTE\Device\S32K144HAxxxLLx\startup_S32K144.S(123): error: A1163E: Unknown opcode __flash_vector_table__ , expecting opcode or Macro

The errors are the same for both of my projects. I did not change anything on the project or files, I only updated the software pack (S32_SDK_DFP 1.5.0). The CORE and startup are enabled in "Manage Run-Time Environment":
Capture.PNG

I have one major concern now:
Are the startup files not compatible with the available compilers? I want to use ARMclang but I don't want to use the versions that include Functional Savety. Which non-FuSa ARMclang versions are supported for the S32K144? Or is there anything else I do wrong?

0 Kudos
Reply
3 Replies

962 Views
kbernie
Contributor I

 


There are CMSIS-PACK examples for the S32K144

Open the Pack installer, C:\Keil_v5\uv4\PackInstaller.exe

- On the top left of the window, for "Search", type "S32K144" - the list below gets filtered.
- Select the device (entry with a green icon) from the list below – on the right side of the dialog updates with Software Packs relevant to this device.
- For the "Packs" tab, install the Keil:S32_SDK_DFP pack (if necessary).
- On the top right of the screen, select the yellow "Examples" tab.
- On the "CMSIS-RTOS (Keil RTX5) Blinky (S32K144-EVB)" row, click the "copy" button - a dialog pops up.
- Pick a directory, click both the check boxes, and press OK - a new Keil µVision session opens with the example.
- Build the project, Connect a USB cable to the board and start the debugger.


I tested this with Arm Compiler for Embedded v 6.19
Keil MDK v 5.38
using a MDK-Pro License

and these packs:
http://www.keil.com/pack/Keil.S32_SDK_DFP.1.5.0.pack
https://www.keil.com/pack/Keil.MDK-Middleware.7.16.0.pack
https://www.keil.com/pack/Keil.ARM_Compiler.1.7.2.pack
http://www.keil.com/pack/ARM.CMSIS.5.9.0.pack

… Opening the project and going to Project -> Options For Target ->Asm Tab, the "Assembler" option is set to "armclang (Auto Select)"


======

See also
- the Getting Started guide at www.keil.com/gsg
- Learning page www.keil.com/learn
- Creating applications at http://www.keil.com/support/man/docs/uv4/uv4_ca_packinstaller.htm

 

1,005 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello Christoph,

Both uVision and S32_SDK_DFP is a product of KEIL.

I would recommend contacting their support:

https://www.keil.com/support/

 

Thank you,

BR, Dnaiel

962 Views
kbernie
Contributor I
S32K144_64_flash.sct and startup_S32K144.S are NXP files. Keil might have packaged them into a .pack , but the content is from NXP.
0 Kudos
Reply