UCANS32K1SIC

Overview

NXP UCANS32K1SIC [8] is a CAN signal improvement capability (SIC) evaluation board designed for both automotive and industrial applications. The UCANS32K1SIC provides two CAN SIC interfaces and is based on the 32-bit Arm Cortex-M4F NXP S32K146 [9] microcontroller.

Hardware

  • NXP S32K146

    • Arm Cortex-M4F @ up to 112 Mhz

    • 1 MB Flash

    • 128 KB SRAM

    • up to 127 I/Os

    • 3x FlexCAN with 2x FD

    • eDMA, 12-bit ADC, MPU, ECC and more.

  • Interfaces:

    • DCD-LZ debug interface with SWD + Console / UART

    • Dual CAN FD PHYs with dual connectors for daisy chain operation

    • JST-GH DroneCode compliant standard connectors and I/O headers

    • user RGB LED and button.

More information about the hardware and design resources can be found at NXP UCANS32K1SIC [8] website.

Supported Features

The ucans32k1sic board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

ucans32k1sic/s32k146 target

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-M4F CPU1

arm,cortex-m4f

ADC

on-chip

NXP ADC122

nxp,adc12

CAN

on-chip

NXP FlexCAN CANFD controller2 1

nxp,flexcan-fd

Clock control

on-chip

NXP S32 clock generator IP node1

nxp,s32-clock

GPIO & Headers

on-chip

Kinetis GPIO5

nxp,kinetis-gpio

I2C

on-chip

NXP LPI2C controller1

nxp,lpi2c

Input

on-board

Group of GPIO-bound input keys1

gpio-keys

Interrupt controller

on-chip

ARMv7-M NVIC (Nested Vectored Interrupt Controller)1

arm,v7m-nvic

LED

on-board

Group of GPIO-controlled LEDs1

gpio-leds

on-board

Group of PWM-controlled LEDs1

pwm-leds

MMU / MPU

on-chip

NXP System Memory Protection Unit (SYSMPU)1

nxp,sysmpu

MTD

on-chip

Flash node1

soc-nv-flash

PHY

on-board

Simple GPIO controlled CAN transceiver2

can-transceiver-gpio

Pin control

on-chip

NXP PORT Pin Controller5

nxp,port-pinmux

on-chip

NXP PORT Pin Controller1

nxp,port-pinctrl

PWM

on-chip

NXP FlexTimer Module (FTM) PWM controller3

nxp,ftm-pwm

RTC

on-chip

NXP Real Time Clock (RTC)1

nxp,rtc

Serial controller

on-chip

NXP LPUART1 2

nxp,lpuart

SPI

on-chip

NXP LPSPI controller1 2

nxp,lpspi

SRAM

on-chip

Generic on-chip SRAM2

mmio-sram

Timer

on-chip

ARMv7-M System Tick1

arm,armv7m-systick

on-chip

NXP FlexTimer Module (FTM)3

nxp,ftm

Watchdog

on-chip

NXP watchdog (WDOG32)1

nxp,wdog32

Connections and IOs

This board has 5 GPIO ports named from gpioa to gpioe.

Pin control can be further configured from your application overlay by adding children nodes with the desired pinmux configuration to the singleton node pinctrl. Supported properties are described in dts/bindings/pinctrl/nxp,port-pinctrl.yaml.

LEDs

The UCANS32K1SIC board has one user RGB LED that can be used either as a GPIO LED or as a PWM LED.

RGB LED as GPIO LED

Devicetree node

Devicetree alias

Label

Pin

led1_red

led0

LED1_RGB_RED

PTD15

led1_green

led1

LED1_RGB_GREEN

PTD16

led1_blue

led2

LED1_RGB_BLUE

PTD0
RGB LED as PWM LED

Devicetree node

Devicetree alias

Label

Pin

led1_red_pwm

pwm-led0 / red-pwm-led

LED1_RGB_RED_PWM

PTD15 / FTM0_CH0

led1_green_pwm

pwm-led1 / green-pwm-led

LED1_RGB_GREEN_PWM

PTD16 / FTM0_CH1

led1_blue_pwm

pwm-led2 / blue-pwm-led

LED1_RGB_BLUE_PWM

PTD0 / FTM0_CH2

The user can control the LEDs in any way. An output of 0 illuminates the LED.

Buttons

The UCANS32K1SIC board has one user button:

Devicetree node

Label

Pin

sw0 / button_3

SW3

PTD15

Serial Console

The serial console is provided via lpuart1 on the 7-pin DCD-LZ debug connector P6.

Connector

Pin

Pin Function

P6.2

PTC7

LPUART1_TX

P6.3

PTC6

LPUART1_RX

System Clock

The Arm Cortex-M4F core is configured to run at 80 MHz (RUN mode).

Programming and Debugging

The ucans32k1sic board supports the runners and associated west commands listed below.

flash debug debugserver attach rtt
jlink ✅ (default) ✅ (default) ✅ ✅ ✅
trace32 ✅ ✅

Applications for the ucans32k1sic board can be built in the usual way as documented in Building an Application.

This board configuration supports Lauterbach TRACE32 [10] and SEGGER J-Link [11] West runners for flashing and debugging applications. Follow the steps described in Lauterbach TRACE32 Debug Host Tools and J-Link Debug Host Tools, to setup the flash and debug host tools for these runners, respectively. The default runner is J-Link.

Flashing

Run the west flash command to flash the application using SEGGER J-Link. Alternatively, run west flash -r trace32 to use Lauterbach TRACE32.

The Lauterbach TRACE32 runner supports additional options that can be passed through command line:

west flash -r trace32 --startup-args elfFile=<elf_path> loadTo=<flash/sram>
   eraseFlash=<yes/no> verifyFlash=<yes/no>

Where:

  • <elf_path> is the path to the Zephyr application ELF in the output directory

  • loadTo=flash loads the application to the SoC internal program flash (CONFIG_XIP must be set), and loadTo=sram load the application to SRAM. The default is flash.

  • eraseFlash=yes erases the whole content of SoC internal flash before the application is downloaded to either Flash or SRAM. This routine takes time to execute. The default is no.

  • verifyFlash=yes verify the SoC internal flash content after programming (use together with loadTo=flash). The default is no.

For example, to erase and verify flash content:

west flash -r trace32 --startup-args elfFile=build/zephyr/zephyr.elf loadTo=flash eraseFlash=yes verifyFlash=yes

Debugging

Run the west debug command to start a GDB session using SEGGER J-Link. Alternatively, run west debug -r trace32 to launch the Lauterbach TRACE32 software debugging interface.

Support Resources for Zephyr

References