new rf receiver and transceiver with ready to use firmware

NXP and the NXP logo are trademarks of NXP B.V. All other product or service names are the property

of their respective owners. © 2017 NXP B.V.

PUBLIC

CAS HAMBURG, SECURE CAR ACCESS (SCA)

TOBIAS PILSAK

NEW RF RECEIVER AND

TRANSCEIVER WITH READY TO

USE FIRMWARE STACK

AMF-AUT-T2760 | AUG 2017

PUBLIC 1

AGENDA• Overview of Products and Applications

• New RF Receiver: NCK 2910 (Lizard)

− Hardware Features

− Customer Support Package

• RCI Firmware

− SPI Interface

− RCI Commands

− Configuration Concept + CDK

− Events

− Further Features

• RF Transceiver: NCK 2982 & NCF 2984

PUBLIC 2

Overview of Products and Applications

01.

PUBLIC 3

Secure Car Access: Applications

Remote Keyless

Entry (RKE)

Consisting of:

•Car theft protection

•Remote car door

lock and unlock

Passive Keyless

Entry (PKE)

Consisting of:

•Car Theft

protection

•Remote car door

lock and unlock

•Passive keyless

entry

•Passive Start

Immobilizer

•Car theft protection Car-key

communication:

•Remote start

•Car finder

•Alarm Systems

•Fuel level /

Charging state

•Door lock status

Smart Car

Management

Connected

Keyless Entry

•Car Access via

NFC enabled

phones/wearables

•NFC key

advantage: secure transport of keys

Advanced Car

Access

Consisting of:

•Car Theft protection

•Functional Security

•Localization

•Range detection

PUBLIC 4

SCA: Sub-GHz Multichannel RF Portfolio

TRANCEIVER CAR (TRx)Transceiver

Key Fob (TRx)RECEIVER CAR (Rx)

MantraC V2

NCK 2983

MantraCS

NCK 2982

MantraF

NCF 2984

SPARC

NCK 2913

COBRA

NCK 2912

LIZARD

NCK 2910

Pin to pin compatible

HVQFN48

Pin to pin compatible

HVQFN48

µC

RF Rx

(3Rx)

RF Rx

µC

RF TRx

µC

RF TRx

µC

µC

RF TRx

(3Rx)

RF Rx

µC

RF Rx*

HVQFN40

HVQFN32

Feature

MULTICHANNEL

WITH

SINGLE RECEPTION

MULTICHANNEL

WITH

SINGLE RECEPTION

MULTICHANNEL

WITH

TRIPLE RECEPTION

Product

*Second Rx only Chameleon

PUBLIC 5

New RF Receiver: NCK 2910

02.

PUBLIC 6

Specification & Block Diagram

Parameter Lizard Spec Typ.

CH BW 31 ch. filter BW settings (11.25 … 360 kHz)

RF frequency range 310 ... 915MHz (ISM-Bands)

Blocking: FSK, 45 kHz BW, +/-2 MHz 70dB

FSK, 45 kHz BW, +/-10 MHz 83dB

Selectivity FSK, 200 kHz BW, +/-250 kHz 57 dB

Sensitivity (no ext. IF filter needed) FSK, 45 kHz BW, 4 kchip/s, MAN enc. -119 dBm

FSK, 360kHz BW, 38.4 kchip/s, MAN enc. -110dBm

Max RF input 20dBm (no damage) / 5dBm (functional)

Data rate Max. 215kbit/s (ASK / FSK) NRZ

Supply Current: Single RF input 10.9 mA

Temperature -40°C to +125

ESD 2kV

System Noise Fig @434MHz 5dB (System)

Image rejection 60dB

RSSI Dynamic Range @45kHz BW 114dB

PUBLIC 7

Feature Overview

Feature Lizard

NCK2910

Lizard+

NCK2910x

Customer Value

Low RF Noise Figure ■ ■ Avoid ext. LNA (cost/current)

RF input ■ ■ Narrowband technology for reduced noise bandwidth, highest sensitivity and highest

selectivity

Simultaneous reception of

two independent signals□ □ No Rx Blindness, reduced curent consumption

Automatic Gain Control ■ ■ Large signal blocking, Highly programmable for highest flexibility, 2dB gain steps

Digital Automatic Frequency

Control■ ■ Frequency offset correction. Increased sensitivity for TPMS use case

Coherent ASK/OOK reception □ ■ Higher sensitivity

BPSK reception □ ■ Higher sensitivity

2 multiplexed antenna ■ ■ Enables different antenna matching and antenna diversity.

Customer Memory (non-

volatile)■ ■ Configuration and trimming

Remote control interface,

sophisticated auto-polling■ ■ No on-chip software effort. Plug and Play via simple 4- or 6-wire SPI

Temperature Sensor ■ ■ Internal on board temp sensor for crystal temperature drift compensation and support of

external temp sensor

GPIO ■ ■ High number of GPIO pins, ext. LNA, Antenna select…

Smart Power management ■ ■ Five different power states for low active and standby power consumption, ideal for battery

powered applications

Tiny Package ■ ■ Minimum board-space (5mm x 5mm)

PUBLIC 8

HARDWARE

PUBLIC 9

RF Receiver Subsystem : Feature Details

• Two single ended RF inputs available

• Attenuators can reduce RF signal before LNA

• LNA has fixed gain and NF ~ 3 (receiver NF ~ 5dB)

• Attenuators after LNA can reduce signal before mixer /

ADC

• IQ mixer used to generate baseband (IF) data for I & Q

• IF amplifiers amplify signals and feed them to ADC

• ADC (70dB SNR) converts to digital

• Further mixing and filtering and signal recovery in digital

• Usable IF bandwidth -385kHz to -25kHz and 25kHz to 385kHz

• IQ mismatch compensation

• AGC compensation

• Configurable channel filter (11.25kHz to 360kHz)

• RSSI and offset frequency detector/measurement

• ASK, FSK demodulation

• Manchester and NRZ operation with data-rate tolerance of up to +/-12%

• Signal monitors (signal property checks)

• Data processing unit with DMA interface

• Digital AFC to maximize sensitivity for applications with large frequency

offsets (e.g.TPMS)

Analogue Digital

0 to -36dB 26dB 0 to -30dB +/- 400kHz

(fixed)70dB

DR

+/- 400kHz

(fixed)

70dB

DR

Frontend Att. Baseband Att.

RF_IN_A RF_IN_B

PUBLIC 10

CUSTOMER SUPPORT PACKAGE

PUBLIC 11

Overview

Hardware

• Lizard Demo Board

• FTDI cable

• User Manual

Software

• RCI firmware (ready to

use firmware stack)

• Configuration

Development Kit

(CDK)

• Operation Manual

RCI

firmware

Remote Keyless

Entry (RKE)Quick Start Guide

• Collection of hardware

and software

• Describes the

interaction between

CDK and RCI device

• Reception Example

Description:

Additional Tools

Package Content

Hardware Setup

Software Setup

...

PUBLIC 12

Demo Board Concept

Shield Board

• Arduino compatible pinning

• PCB Antenna (RF_IN A)

• RF_A & RF_B

• External Power Supply (2.8 to 5.5V)

• Buttons

• LED‘s

• Interfaces: MDI, SPI, GPIOs

µC Board (FRDM)

(optional, not yet supported)

Lizard Nano Board

• Lizard IC

• XTAL

• RF Matching (434MHz)

• SAW filter (not placed)

• Interfaces: MDI, SPI, Power, GPIOs

• Size: 20 x 20mm

• Interfaces: MDI, SPI, GPIOs

PUBLIC 13

Lizard Nano Board (Schematic)

• IC in HVQFN32 package

• 10 GPIO with integrated SPI and transparent RX access (RxC,

RxD)

• Separate lines for Monitor and Download Interface

• 2 independent RF inputs with good isolation (~60dB)

• board allows for RF_IN_A to place SAW filter for improved

blocking

• 3 supply caps (100nF each), 1 LDO cap (15nF)

• 27.6MHz crystal with load caps

• RST_N reset pin with series resistor for EMC robustnes

PUBLIC 14

Lizard Nano Board (Layout)

PCB Layout / Pinning Features

• 2 layer PCB in size 20*20mm

• Bypass option for SAW at RX_IN_A

20m

m

20mm

• GND named pins have each a separated GND-Via without top

connections to avoid supply domain interference

• Crystal GND reference is GND_XO (pin 7) direct connection with

crystal on top layer

• Exposed die pad with 8 GND-Vias could be used as GND reference

(ie. test pin grounding)

SAW landing place

Frequency Indicator

XTAL

Lizard NCK2910

PUBLIC 15

Shield Boad with Nano Board

• The board is designed to demonstrate the RF received IC performances in 50Ohm environment. It

allows application-like investigation.

• Board shape and the position of connectors fits the Freedom development platform (FRDM).

• Designed for quick SW development based of RCI and CDK.

• Jumper configurable supply voltage

Direct supply from Freedom platform 2.8

… 5.5V

External supply 2.8 … 5.5V

• Translator supported SPI

At Freedom platform connector J2

Allows SPI voltage level independent

supply dependency investigations

Translator support jumper configurable

suspend mode using Jumper 2

Features:FRDM Connectors

Buttons

LEDs

Optional ext. Power Supply

RF Inputs

PCB Antenna

SPI Connector

MDI Connector

PUBLIC 16

RCI Firmware

03.

PUBLIC 17

RCI Firmware

• The Remote Control Interface (RCI) firmware is provided by NXP

• The latest version is release 1.9 (week 31, 2017)

• Firmware updates are provided regularily via www.nxp.com

• Firmware provides:

− SPI Interface to communicate with host (µC)

− RCI Commands to control the RCI device via SPI

• The RCI Operation Manual describes the functions of the RCI firmware

PUBLIC 18

Release Package Overview

MDI

Connector

MRK III

2-link

Programmer

MDI

Connector

MRK III

2-link

Programmer

CDK InstallerRCI Firmware

PUBLIC 19

Main Concept• Lizard Demo Board

• FTDI cable

• User Manual

Remote

Keyless Entry

(RKE)

Customer

Development Kit

Creation of:

• RX configurations (e.g. TPMS)

• Polling configurations

• Device trimming

RCI

firmware

First step

Load configurations via RCI

commands

Second step

Control device via RCI

commands

Third step

Read received data/events

Remote

Keyless Entry

(RKE)

Host

(e.g. µC)

PUBLIC 20

SPI INTERFACE

PUBLIC 21

SPI Interface

• There are two SPI modes available:

• The 6-wire SPI mode enlarges the ordinary SPI by two additional control lines

− The INT_N line is set, if the RCI device has data to transmit

− The RDY_N line is a handshake for the CS_N of the master

SCK

MOSI

MISO

CS_N

INT_N

RDY_N

RCI device

(Slave)

Host

(Master)

SCK

MOSI

MISO

CS_N

RCI device

(Slave)

Host

(Master)

4-wire SPI 6-wire SPI

PUBLIC 22

SPI Interface: Example

Transmission completed

RCI device is ready to handle

the next command

CS_n is pulled up by host

RCI device has nothing

to transmit MISO to low

CS_N is pulled down by host

RCI device is ready

Pulls RDY_N line low

Host provides Clock and transmits

data to RCI device

Command: OS_SET_MODE 0x05,0x06,0x01,0x04,0x00,0xa6

PUBLIC 23

RCI COMMANDS

PUBLIC 24

RCI Commands

• The RCI commands are grouped according to their purpose

Device Configuration This set of commands is used to configure the device.

Operating State The Operating State implements the two fundamental device modes (Polling, Continuous

Reception) and selects an appropriate configuration.

RX Buffer The RCI device stores all received frames to a circular RX buffer, that works as a FIFO

(first-in-first-out). Each element in the FIFO is a message. This command set is necessary

to operate the RX circular buffer to read received frames.

Personality Used for system configuration management and device traceability means.

Debug These commands are intended for special debug interaction with the RCI device.

Wired Interface These commands offer control of the wired interface which is the primary method to control

the RCI device.

On Board Measurement The On Board Measurement commands are used to measure runtime parameters of the

device during operation.

Miscellaneous Commands These commands complete the control possibilities by general functions.

Event handling The RCI device generates events that are not triggered by any SPI interaction. These

events are the reboot, heartbeat and RF events. In case an event takes place an interrupt

is generated (if configured).

PUBLIC 25

RCI COMMAND STRUCTURE

PUBLIC 26

RCI Command Structure

• The RCI device is completely configured and controlled with RCI commands

Byte 0 Byte 1 Byte 2 … … Byte LEN

LEN: Length of

command

(excluding the

LEN byte)

Command Sub-command

Command

parameters

(optional)

Command data

(optional)

CRC: Check sum

to verify the

correct

transmission of

the command

DC_SET 0x07,0x71,0xf6,0x00,0x01,0xae,0x1d,0x5d

Host µC

RCI

firmware

PUBLIC 27

RCI Reply Message

• The RCI device replies to almost all RCI commands

• All reply messages have the following structure:

• „Status“ is 0x00 if command has been successfully executed

• Else the status byte contains an error code description in data sheet

• If the command requested data it is returned with this message (Data)

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 …Byte

LEN

LEN: Length

of reply

(excluding

the LEN

byte)

CommandSub-

command

Timestamp

(lo)

Timestamp

(hi)Status

Data

(if available)

CRC: Check

sum to verify

the correct

transmission

of the

command

Host µC

RCI

firmware

PUBLIC 28

Setting Value

Center Frequency 434 MHz

Data Rate 5 kBits/s

Modulation FSK

Frequency Deviation 20 kHz

Encoding NRZ (1 bit = 1 chip)

Length 2 Bytes

FSYNC 10110011 (in bits, inverted)

Task 1

Configure the receiver in Basic mode for the following frame:

Are you able to receive the frame?

Start Receive!

PUBLIC 29

Task 2

Change the modulation from NRZ to MANCHESTER:

Setting Value


Data Rate 2.5 kBits/s

Modulation FSK


Encoding Manchester (1 bit = 2 chips)

Length 2 Bytes

FSYNC 10110011 (in bits, inverted)

Are you still able to receive the frame?

Start Receive!

PUBLIC 30

Configuration Concept + CDK

PUBLIC 31

Device Configuration

• To operate the receiver at least one full receiver configuration setup is required

• A full receiver configuration consits of 9 different types:

− Local oscillator

− Digital frequency

− Baseband

− WUP/Frame

− WUP/Search

− Software

− Reception

− MIDMAP

− MID

• The device configuration is derived by CDK

PUBLIC 32

Multiple configuration

types can be defined,

seperated by an indexTrim values

Configuration Development Kit (CDK)

Configuration types

PUBLIC 33

Configuration Concept

up to 24 up to 20up to 32 up to 20 up to 32 up to 32 up to 32 up to 64 up to 16

Index 0 Index 1 ... Index 31





Configuration types

Number of configurations (RAM & EROM)

PUBLIC 34


up to 24 up to 20up to 32 up to 20 up to 32 up to 32 up to 32 up to 64 up to 16







0 0 0 0 0

Configuration types


PUBLIC 35

• A receiver configuration is used for:

− WUP search

− Frame reception

• Different receiver configurations can be used for WUP search and frame reception


up to 24 up to 20up to 32

WUP

up to 32 up to 32 up to 32 up to 64 up to 16


0 1 1 1 2 2 31 31

Configuration types



0 0 0 0 0 0 0 0 0 0

Frame

Reception Configuration #0

Reception Configurations are

used for „Cont. Reception“

and Polling

up to 20


PUBLIC 36

Continious Reception

• Receiver is configured based on one reception configuration

• The receiver is switched on and receives continiously


0 1 1 1 2 2 31 31

WUP Frame


Example:

timeCont. RX ON Cont. RX OFF

PUBLIC 37

Getting the Configurations with the CDK

• All configuration types are defined acording to the customer needs

• Configurations are calculated as follows:

Continious reception Polling

Select the reception configuration

Starts calculating of the

configurations. After calculation

they are transfered to the RCI

device and Cont. Reception is

started.

Starts calculating of the

configurations. After calculation

they are transfered to the RCI

device and the polling array is

defined. Polling is started

afterwards.

Define the polling array

PUBLIC 38

Getting the Configuration with the CDK

• Calculated configuration:

LEN CMDSub-

CMD

Configuration

index

Configuration

Type

Payload

calculated

by CDK

CRC

0x08 0x71 0xf6 0x00 0x09 0x00, 0x00 0x1f

Device Configuration

based on defined Use

Case

PUBLIC 39

Start Receive with this new

reception configuration!

Task 3

Make sure that the basic configurations of task 2 are set and enter the Advanced

mode:

a) Find the settings configured in the basic mode

b) Add a 2nd configuration by using the settings of the table below

Setting Value


Data Rate 2.5 kBits/s

Modulation FSK


Encoding Manchester

Length 2 Bytes

FSYNC 10110011 (inverted)

Only the Frequency differs

Are you able to receive the frame?

PUBLIC 40

Polling

• A polling consists of up to 16 slots

• Each slot consists of:

− Reception configuration and duration OR standby/repeat duration

• Auto polling can be configured on device boot polling starts automatically


0 1 1 1 2 2 31 31

WUP Frame


Example:

WUP Frame


time

Standby Repeat

PUBLIC 41

Task 4

In the tasks before, you have successfully created two reception configurations!

Now, the receiver shall be able to receive on both channels. Use the polling array to

create a polling configuration.

The polling scheme should look as shown below:

time

Conf. 2Conf. 1

Duration 1

Search for

frame #1

Standby Repeat

Duration 2

Standby

mode

Duration 3

Search for

frame #2

Duration 4

Standby

mode

Polling scheme:

PUBLIC 42

Task 4

Task overview:

1) Configure the WUP Pattern to be 11111111 for both configurations

2) Configure a polling slot as shown below, using the previously made

configurations:

• Reception slot duration of 3.5 ms for both configurations

• Standby duration of 15 ms between the reception slots

3) How long must the transmitted WUP be to ensure the detection of the WUP?

Polling scheme:

time

Conf. 2Conf. 1

Duration 1

Search for

frame #1

Standby Repeat

Duration 2

Standby

mode

Duration 3

Search for

frame #2

Duration 4

Standby

mode

PUBLIC 43

Operation States

• RCI device can be operated in differnet states:

− Standby

− IDLE

− Sleep

− Continous Reception

− Polling

− Transport

− Reset

• The state can be controled via the RCI command OS_SET_MODE

PUBLIC 44

Example OS_SET_MODE command

LEN CMDSub-

CMD

Operating

modeParameter CRC

The length

is fix with

0x05

The command

is 0x06

because it is an

operating mode

command

The sub-

command is

0x01 because

the command is

OS_SET_MODE

In basic mode continuous

reception mode is entered

after the configuration. This

is made by setting this byte

to 0x03

If the device is set to continuous

reception (like in this case) it expects

the configuration index of the reception

configuration that is used. In basic

mode all indexes are set to 0x00

The last byte is a

check sum that

verifies the

command

0x05 0x06 0x01 0x06 0x00 8c

PUBLIC 45

EVENTS

PUBLIC 46

Events

• The following Events are available

− Reboot Event

Is the first event that is generated after reboot

Gives reasons for reboot

− Heartbeat Event

Configurable, if used periodically an event is generated by RCI firmware

− RSSI Event

Configurable, if used peridically an RSSI measurmenet is done

− RF Event

Configurable, several options:

PUBLIC 47

Events

• The following example shows the End Of Message (EOM) Event:

Transparent Mode activated

Received data is clocked out

During data reception

End of Message event is generated

after receiving the last byte; interrupt

is generated

EOM Message

PUBLIC 48

Task 5

• Enable following events:

WUP found

FSYNC found

EOM

• Select configuration 1 (the second configuration) for continuous reception

Are you able to get all events?

Start Receive!

• Repeat the reception by using polling

PUBLIC 49

FURTHER FEATURES

PUBLIC 50

Message ID scanning

• Up to 64 MIDs can be configured

• Up to 16 can be mapped to one MIDMAP

Preamble FSYNC Payload

ID Data

Received Frame:

Example: received ID 010100

MID 010100

Mask all

Offset 0

Data received and INT is given

PUBLIC 51

Autoflush

• In case Autoflush is used the last received fata can be clocked out immediately

without further RCI commands. Moreover, The frame is dealeated automatically

from the buffer after successfull read out.

PUBLIC 52

Polling Continious Reception

• It is possible to switch automatically from Polling to cont. Reception mode once a

frame has been received in polling.

PUBLIC 53

Frequency Temperature Compensation

• The Crystal Frequency Drift can be periodically compensated. Therefore a time

interval and a temperature correction table must be defined.

Temperature

ΔF

/F (

pp

m)

20 40 60 80-200

-4

8

4

6

10

-6

-2

-8

2

-10

Bootup

Initial Freq.

Compensation

Freq.

Compensation

1s

defined time interval

defined time interval

Freq. Compensation

Temp.

Measurement

Select

Index of

correction

table

Change

frequency

Example: Frequency Drift

PUBLIC 54

RF Transceiver: NCK 2982 & NCF 2984

03.

PUBLIC 55

Transceiver

• NCK 2982 & NCF 2984 are released NXP Transceivers and are already in use in

several automotive applications.

• Currently the devices require a custom firmware.

• NXP currently develops RCI for these devices.

• Receiver concept is the same as for Lizard available

• Transmitter concept is currently integrated in RCI/CDK available soon (Q4‘17)

new rf receiver and transceiver with ready to use firmware

Documents