NXP Laboratories UK JN5139M4 JN5139-000-M04 Wireless Microcontroller User Manual JN DS JN513x

Download:
Mirror Download [FCC.gov]
Document ID	933298
Application ID	6xZ3HFV8vbt9UK8/WsierQ==
Document Description	Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	265.87kB (3323317 bits)
Date Submitted	2008-04-25 00:00:00
Date Available	2008-04-25 00:00:00
Creation Date	2007-10-26 14:59:07
Producing Software	Acrobat Distiller 7.0.5 (Windows)
Document Lastmod	2007-10-26 15:04:15
Document Title	JN-DS-JN513x
Document Creator	Acrobat PDFMaker 7.0.7 for Word
Document Author:	Jimi Simpson

Data Sheet – JN513x
IEEE802.15.4 and ZigBee Wireless Microcontrollers
Overview
The JN513x are a family of low power, low cost wireless microcontrollers
suitable for IEEE802.15.4 and ZigBee applications. Each device
integrates a 32-bit RISC processor, with a fully compliant 2.4GHz
IEEE802.15.4 transceiver, 192kB of ROM, a selection of RAM sizes
from 8kB to 96kB, and a rich mixture of analogue and digital peripherals.
The cost sensitive ROM/RAM architecture supports the storage of
system software, including protocol stacks, routing tables and
application code/data. Each device has hardware MAC and AES
encryption accelerators, power saving and timed sleep modes, and
mechanisms for security key and program code encryption. These
features all make for a highly efficient, low power, single chip wireless
microcontroller for battery-powered applications.
Block Diagram
RAM
8kB - 96kB
2.4GHz
Radio
O-QPSK
Modem
ROM
192kB
32-bit
RISC CPU
SPI
2-wire serial
Bootloader
Flash
Optional
Timers
IEEE802.15.4
MAC
Accelerator
XTAL
48-byte
OTP eFuse
UARTs
12-bit ADC,
comparators
Power
Management
128-bit AES
Encryption
Accelerator
11-bit DACs,
temp sensor
Features: Transceiver
•
•
2.4GHz IEEE802.15.4 compliant
128-bit AES security processor
•
MAC accelerator with packet
formatting, CRCs, address check,
auto-acks, timers
•
Integrated power management
and sleep oscillator for low power
•
On-chip power regulation for 2.2V
to 3.6V battery operation
•
Deep sleep current 0.2µA
•
Sleep current with active sleep
timer 1.3µA
•
Needs minimum of external
components (< US$1 cost)
•
Rx current 34mA
•
Tx current 34mA
•
Receiver sensitivity -97dBm
•
Transmit power +3dBm
Features: Microcontroller
•
32-bit RISC processor sustains
32MIPs with low power
•
192kB ROM stores system code,
including protocol stack
•
8kB, 16kB, 32kB or 96kB RAM
stores system data and optionally
bootloaded program code
•
48-byte OTP eFuse, stores MAC
ID on-chip, offers AES based code
encryption feature
Benefits
Applications
•
•
Robust and secure low power
wireless applications
•
•
Wireless sensor networks,
particularly IEEE802.15.4 and
ZigBee systems
4-input 12-bit ADC, 2 11-bit DACs,
2 comparators
•
2 Application timer/counters,
3 system timers
•
Home and commercial
building automation
•
2 UARTs (one for debug)
•
SPI port with 5 selects
2-wire serial interface
Up to 21 GPIO
•
Single chip integrates
transceiver and
microcontroller for wireless
sensor networks
Cost sensitive ROM/RAM
architecture, meets needs
for volume application
•
System BOM is low in
component count and cost
•
Remote Control
•
•
Hardware MAC ensures low
power consumption and low
processor overhead
•
Toys and gaming peripherals
•
•
Industrial systems
•
Telemetry and utilities
(e.g. AMR)
Industrial temperature range
(-40°C to +85°C)
•
Extensive user peripherals
•
Pin compatible with JN5121
for easy migration
© Jennic 2007
8x8mm 56-lead QFN
Lead-free and RoHS compliant
JN-DS-JN513x v1.4
Preliminary
Jennic
1 Introduction
1.1
1.2
1.3
1.4
1.5
Wireless Microcontroller
Wireless Transceiver
RISC CPU and Memory
Peripherals
Block Diagram
2 Pin Configurations
2.1
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
Pin Assignment
Pin Descriptions
Power Supplies
Reset
16MHz System Clock
Radio
Analogue Peripherals
Digital Input/Output
10
11
11
11
11
11
11
12
3 CPU
13
4 Memory Organisation
14
4.1
4.2
4.3
4.4
4.4.1
4.5
4.6
15
15
15
15
16
16
16
ROM
RAM
OTP eFuse Memory
External Memory
Secure External Memory Encryption
Peripherals
Unused Memory Addresses
5 System Clocks
17
5.1
5.2
17
17
16MHz Oscillator
32kHz Oscillator
6 Reset
18
6.1
6.2
6.3
6.4
18
19
19
20
Internal Power-on Reset
External Reset
Software Reset
Brown-out Detect
7 Interrupt System
21
7.1
7.2
7.2.1
7.2.2
7.2.3
7.3
System Calls
Processor Exceptions
Bus Error
Alignment
Illegal Instruction
Hardware Interrupts
21
21
21
21
21
22
8 Wireless Transceiver
23
8.1
8.1.1
8.1.2
8.2
23
24
24
25
Radio
Radio External components
Antenna Diversity
Modem
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.3.5
8.4
Baseband Processor
Transmit
Reception
Auto Acknowledge
Beacon Generation
Security
Security Coprocessor
25
26
26
27
27
27
27
9 Digital Input/Output
28
10 Serial Peripheral Interface
29
10.1
32
Programming Example
11 Intelligent Peripheral Interface
34
11.1
11.2
11.3
34
35
35
Data Transfer Format
JN513x Initiated Data Transfer
Remote Processor Initiated Data Transfer
12 Timers
36
12.1 Peripheral Timer / Counters
12.1.1
Pulse Width Modulation Mode
12.1.2
Capture Mode
12.1.3
Counter / Timer Mode
12.1.4
Delta-Sigma Mode
12.1.5
Timer / Counter Application
12.2 Tick Timer
12.3 Wakeup Timers
12.3.1
RC Oscillator Calibration
12.3.2
External 32kHz Clock Source
36
37
37
38
38
39
40
41
41
42
13 Serial Communications
43
13.1
13.2
13.3
44
44
45
Interrupts
UART Application
Programming Example
14 Two-Wire Serial interface
46
14.1
14.2
14.3
14.4
47
47
48
48
Connecting Devices
Multi-Master Operation
Clock Stretching
Programming Example
15 Analogue Peripherals
50
15.1 Analogue to Digital Converter
15.1.1
Operation
15.1.2
Supply Monitor
15.1.3
Temperature Sensor
15.1.4
Programming Example
15.2 Digital to Analogue Converter
15.2.1
Operation
15.2.2
Programming Example
15.3 Comparators
51
51
51
52
52
52
52
53
53
16 Power Management and Sleep Modes
55
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Jennic
16.1
16.1.1
16.2
16.2.1
16.3
16.3.1
16.3.2
16.3.3
16.4
Operating Modes
Power Domains
Active Processing Mode
CPU Doze
Sleep Mode
Wakeup Timer Event
DIO Event
Comparator Event
Deep Sleep Mode
55
55
55
55
55
56
56
56
56
17 Electrical Characteristics
57
17.1 Maximum ratings
17.2 DC Electrical Characteristics
17.2.1
Operating Conditions
17.2.2
DC Current Consumption
17.2.3
I/O Characteristics
17.3 AC Characteristics
17.3.1
Reset
17.3.2
Brown-out Detect
17.3.3
SPI Timing
17.3.4
Two-wire serial interface
17.3.5
Power Down and Wake-Up timings
17.3.6
32kHz Oscillator
17.3.7
16MHz Crystal Oscillator
17.3.8
Analogue to Digital Converters
17.3.9
Digital to Analogue Converters
17.3.10
Comparators
17.3.11
Temperature Sensor
17.3.12
Radio Transceiver
57
57
57
58
59
59
59
60
61
61
62
63
63
63
64
65
66
66
Appendix A Mechanical and Ordering Information
70
A.1
A.2
A.3
A.4
A.5
A.5.1
A.5.2
A.5.3
A.5.4
A.6
70
71
72
73
74
74
75
76
76
77
56pin QFN Package Drawing
PCB Decal
Ordering Information
Device Package Marking
Tape and Reel Information
Tape Orientation and Dimensions
Reel Information: 7” Reel
Reel Information: 13” Reel
Dry Pack Requirement for Moisture Sensitive Material
PCB Design and Reflow Profile
Appendix B Development Support
78
B.1
Crystal Oscillator
B.1.1
Crystal Equivalent Circuit
B.1.2
Crystal Load Capacitance
B.1.3
Crystal ESR and Required Transconductance
B.2
16MHz Oscillator
B.3
Applications Information
B.3.1
Typical Application Schematic
B.3.2
PCB Requirements
B.3.3
Supply Decoupling
78
78
79
79
81
82
82
83
84
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
B.3.4
B.3.5
B.3.6
B.3.7
B.3.8
B.3.9
B.3.10
B.3.11
B.3.12
B.3.13
B.3.14
B.3.15
B.3.16
B.3.17
B.3.18
Reference Oscillator Requirements
Reference Oscillator Layout Considerations
VCO Tune Circuit Component Specifications
VCO Tune Circuit Layout Considerations
Radio Front-End
Antennae
Ground Planes
Manufacturing Considerations
Bespoke Solutions - PCB Layout Suggestions
Using a Balun
Decoupling Capacitors
Internal Regulator Smoothing Capacitors
VREF
IBIAS
EMC
84
84
84
85
85
85
85
86
87
88
88
88
89
89
89
Appendix C
90
Related Documents
RoHS Compliance
Status Information
Disclaimers
Version Control
Contact Details
90
90
90
91
91
92
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Jennic
1 Introduction
The JN513x is an IEEE802.15.4 wireless microcontroller that provides a fully integrated solution for applications using
the IEEE802.15.4 standard in the 2.4 - 2.5GHz ISM frequency band [1], including ZigBee. It includes all of the
functionality required to meet the IEEE802.15.4 specification and has additional processor capability to run a wide
range of applications including but not limited to Remote Control, Home and Building Automation, Toys and Gaming.
The device includes a Wireless Transceiver, RISC CPU, on-chip memory and an extensive range of peripherals.
1.1 Wireless Microcontroller
Applications that transfer data wirelessly tend to be more complex than wired ones. Wireless protocols make
stringent demands on frequencies, data formats, timing of data transfers, security and other issues. Application
development must consider the requirements of the wireless network in addition to the product functionality and user
interfaces. To minimise this complexity, Jennic provides a series of software libraries that control the transceiver and
peripherals of the JN513x. These libraries, with functions called by an Application Programming Interface (API)
remove the need for the developer to understand wireless protocols and greatly simplify the programming
complexities of power modes, interrupts and hardware functionality. In addition, the JN513x is expected to be
programmed in the C high-level language and debugged using the JN5 series software developer kit.
In view of the above, the register details of the JN513x are not provided in the datasheet and access to all peripherals
is gained using API calls to the peripheral library. Extensive reference to such calls is made throughout the datasheet
and the convention used is to format the function call in the courier font e.g. vAHI_Init(). Full details of these
function calls can be found in the JN-RM-2001 Integrated Peripherals API [2].
An IEEE802.15.4 compliant wireless network can be developed using the IEEE802.15.4 MAC library described in JNRM-2002 802.15.4 Stack [3]. Applications over simple (point-point, star or tree) wireless networks can use this
library directly or more complex wireless mesh networks such as ZigBee or IPv6 can be built on top of the
IEEE802.15.4 library.
1.2 Wireless Transceiver
The Wireless Transceiver is highly integrated and, together with the IEEE802.15.4 MAC library requires little
knowledge of RF or wireless design.
The Wireless Transceiver comprises a low-IF 2.45GHz radio, an O-QPSK modem, a baseband controller and a
security coprocessor. The radio has a 200Ω resistive differential antenna port that includes all the required matching
components on-chip, allowing a differential antenna to be connected directly to the port, minimising the system BOM
costs. Connection to a single ported antenna can be achieved using a 200/50Ω 2.45GHz balun. In addition, the
radio also provides an output to control transmit-receive switching of external devices such as power amplifiers
allowing applications that require increased transmit power to be realised very easily.
(1)
The Security coprocessor provides hardware-based 128-bit AES-CCM, CBC , CTR and CCM* processing as
specified by the 802.15.4b standard. It does this in-band on packets during transmission and reception, requiring
minimal intervention from the CPU. It is also available for off-line use under software control for encrypting and
decrypting packets generated by software layers such as Zigbee and user applications. This means that these
algorithms can be off-loaded by the CPU, increasing the processor bandwidth available for user applications.
The transceiver elements (radio, modem and baseband) work together to provide 802.15.4 Medium Access Control
under the control of a protocol stack supplied with the device as a software library. Applications incorporating
IEEE802.15.4 functionality can be rapidly developed by combining user-developed application software with this
library. The facilities provided by this library to applications together with examples of their use are described in more
detail in [3].
(1) AES-CBC processing is only available off-line for use under software control.
1.3 RISC CPU and Memory
A 32-bit RISC CPU allows software to be run on-chip, its processing power being shared between the IEEE802.15.4
MAC protocol, other higher layer protocols and the user application. The JN513x has a unified memory architecture,
code memory, data memory, peripheral devices and I/O ports are organized within the same linear address space.
The device contains 192kBytes of ROM, a choice of 8k, 16k, 32k or 96kBytes of RAM and a 48-byte OTP eFuse
memory.
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
1.4 Peripherals
The following peripherals are available on-chip:
•
Master SPI port with five select outputs
•
Two UARTs
•
Two programmable Timer/Counters with capture/compare facility
•
Two programmable Sleep Timers and a Tick Timer
•
Two-wire serial interface (compatible with SMbus and I C)
•
Slave SPI port (shared with digital I/O)
•
Twenty-one digital I/O lines (multiplexed with UARTs, timers and SPI selects)
•
Four-channel, 12-bit, 100ksps Analogue-to-Digital converter
•
Two 11-bit Digital-to-Analogue converters
•
Two programmable analogue comparators
•
Internal temperature sensor and battery monitor
User applications access the peripherals using the Hardware Peripheral Library with a simple API. This allows
applications to use a tested and easily understood view of the peripherals allowing rapid system development. The
JN-RM-2001 Integrated Peripherals API [2] describes this interface in more detail.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Jennic
1.5 Block Diagram
Tick Timer
32-bit RISC CPU
Programmable
Interrupt
Controller
SPICLK
SPIMOSI
SPIMISO
SPISEL0
SPI
DIO0/SPISEL1
DIO1/SPISEL2
DIO2/SPISEL3/RFRX
DIO3/SPISEL4/RFTX
From Peripherals
RAM
8k - 96kB
ROM
192kB
OTP
eFuse
48-byte
UART0
DIO4/CTS0
DIO5/RTS0
DIO6/TXD0
DIO7/RXD0
UART1
DIO17/CTS1/IP_SEL
DIO18/RTS1/IP_INT
DIO19/TXD1
DIO20/RXD1
VB_xx
VDD1
Voltage
Regulators
VDD2
RESETN
1.8V
Timer0
DIO8/TIM0CK_GT
DIO9/TIM0CAP/CLK32K
DIO10/TIM0OUT
Timer1
DIO11/TIM1CK_GT
DIO12/TIM1CAP
DIO13/TIM1OUT
Reset
Wakeup
32kHz
Osc
2-wire
interface
WT1
DIO14/SIF_CLK/IP_CLK
DIO15/SIF_D/IP_DO
DIO16/IP_DI
WT0
Intelligent
Peripheral
Clock
Generator
XTALIN
XTALOUT
COMP1M
COMP1P
Comparator1
COMP2M
COMP2P
Comparator2
DAC1
2x
Clock
Wireless
Transceiver
Security
Coprocessor
DAC1
Baseband
Controller
DAC2
DAC2
Supply
Monitor
ADC1
ADC2
ADC3
ADC4
Modem
ADC
Radio
Temperature
Sensor
RFM
RFP
VCOTUNE
IBAIS
Figure 1: JN513x Block Diagram
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
DIO15/SIF_D/IP_DO
DIO14/SIF_CLK/IP_CLK
DIO13/TIM1OUT
DIO12/TIM1CAP
DIO11/TIM1CK_GT
DIO10/TIM0OUT
DIO9/TIM0CAP/CLK32K
VDD2
DIO8/TIM0CK_GT
DIO7/RXD0
DIO6/TXD0
DIO5/RTS0
DIO4/CTS0
DIO3/SPISEL4/RFTX
56
55
54
53
52
51
50
49
48
47
46
45
44
43
2 Pin Configurations
DIO16/IP_DI
42
DIO2/SPISEL3/RFRX
DIO17/CTS1/IP_SEL
41
DIO1/SPISEL2
VB_DIG2
40
VB_MEM
DIO18/RTS1/IP_INT
39
VSS1
DIO19/TXD1
38
DIO0/SPISEL1
DIO20/RXD1
37
SPISEL0
VSS2
36
SPIMOSI
RESETN
35
VB_DIG1
VSS3
34
SPIMISO
VSSS
10
33
SPICLK
XTALOUT
11
32
COMP2M
XTALIN
12
31
COMP2P
VB_SYN
13
30
DAC2
VCOTUNE
14
29
DAC1
15
16
17
18
19
20
21
22
23
24
25
26
27
28
VB_VCO
VDD1
COMP1M
COMP1P
IBIAS
RFP
VB_RF
RFM
VREF
ADC1
ADC2
ADC3
ADC4
VB_A
PADDLE
Figure 2: 56-pin QFN Configuration (top view)
Note: Please refer to Appendix B.3.11 for important applications
information regarding the connection of the PADDLE to the PCB.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Jennic
2.1 Pin Assignment
Pin No
Power supplies
Description
3, 13, 15, 21 28, 35,
40
VB_DIG2, VB_SYN, VB_VCO, VB_RF,
VB_A, VB_DIG1, VB_MEM
Regulated supply voltage
16, 49
VDD1, VDD2
Device supplies: VDD1 for analogue, VDD2 for digital
7,9,10,39, PADDLE
VSS2, VSS3, VSSS, VSS1, VSSA
Device grounds
RESETN
11, 12
XTALOUT, XTALIN
General
Reset output/input
System crystal oscillator
Radio
14
VCOTUNE
VCO tuning RC network
19
IBIAS
Bias current control
20, 22
RFP, RFM
Differential antenna port
Analogue Peripheral I/O
24, 25, 26, 27
ADC1, ADC2, ADC3, ADC4
ADC inputs
23
VREF
Analogue peripheral reference voltage
29, 30
DAC1, DAC2
DAC outputs
17, 18, 31, 32
COMP1M, COMP1P, COMP2P, COMP2M
Comparator inputs
Digital I/O
Primary Function
Alternate Function
33
SPICLK
SPI Clock
36
SPIMOSI
SPI Master Out Slave In
34
SPIMISO
SPI Master In Slave Out
37
SPISEL0
SPI Slave Select Output 0
38
DIO0
SPISEL1
DIO0 or SPI Slave Select Output 1
41
DIO1
SPISEL2
DIO1 or SPI Slave Select Output 2
42
DIO2
SPISEL3, RFRX
DIO2 or SPI Slave Select Output 3 or
Radio Receive Control Output
43
DIO3
SPISEL4, RFTX
DIO3 or SPI Slave Select Output 4 or
Radio Transmit Control Output
44
DIO4
CTS0
DIO4 or UART 0 Clear To Send Input
45
DIO5
RTS0
DIO5 or UART 0 Request To Send Output
46
DIO6
TXD0
DIO6 or UART 0 Transmit Data Output
47
DIO7
RXD0
DIO7 or UART 0 Receive Data Input
48
DIO8
TIM0CK_GT
DIO8 or Timer0 Clock/Gate Input
50
DIO9
TIM0CAP,CLK32K
DIO9 or Timer0 Capture Input or CLK32K
51
DIO10
TIM0OUT
DIO10 or Timer0 PWM Output
52
DIO11
TIM1CK_GT
DIO11 or Timer1 Clock/Gate Input
53
DIO12
TIM1CAP
DIO12 or Timer1 Capture Input or Antenna Diversity
54
DIO13
TIM1OUT
DIO13 or Timer1 PWM Output or Antenna Diversity
55
DIO14
SIF_CLK, IP_CLK
DIO14 or Serial Interface Clock or Intelligent Peripheral
Clock Input
56
DIO15
SIF_D, IP_DO
DIO15 or Serial Interface Data or Intelligent Peripheral
Data Out
DIO16
IP_DI
DIO16 or Intelligent Peripheral Data In
DIO17
CTS1, IP_SEL
DIO17 or UART 1 Clear To Send Input or Intelligent
Peripheral Device Select Input
DIO18
RTS1, IP_INT
DIO18 or UART 1 Request To Send Output or Intelligent
Peripheral Interrupt Output
DIO19
TXD1
DIO19 or UART 1 Transmit Data Output
DIO20
RXD1
DIO20 or UART 1 Receive Data Input
10
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
2.2 Pin Descriptions
2.2.1 Power Supplies
The device is powered from the VDD1 and VDD2 pins, each being decoupled with a 100nF ceramic capacitor. VDD1
is the power supply to the analogue circuitry; it should be decoupled to analogue ground. VDD2 is the power supply
for the digital circuitry; it should be decoupled to digital ground. A 10uF tantalum capacitor is required at the common
ground star point of analogue and digital supplies. Decoupling pins for the internal 1.8V regulators are provided
which require a 100nF capacitor located as close to the device as practical. VB_VCO, VB_RF, VB_A and VB_SYN
should be decoupled to analogue ground, while VB_MEM, VB_DIG1 and VB_DIG2 should be decoupled to digital
ground. See also Appendix B for connection details.
VSSA is the analogue ground, connected to the paddle of the device, while VSSS, VSS1, VSS2, VSS3 are digital
ground pins.
2.2.2 Reset
RESETN is a bi-directional active low reset pin that is connected to a 45kΩ internal pull-up resistor. It may be pulled
low by an external circuit, or can be driven low by the JN513x if an internal reset is generated. Typically, it will be
used to provide a system reset signal. Refer to section 6.2, External Reset, for more details.
2.2.3 16MHz System Clock
A crystal connected between XTALIN and XTALOUT drives the system clock. A capacitor to analogue ground is
required on each of these pins. Refer to section 5.1 16MHz Oscillator for more details.
2.2.4 Radio
A 200Ω balanced antenna (such as a printed circuit antenna) can be connected directly to the radio interface pins
RFM and RFP.
A single-ended 50Ω antenna such as a ceramic type or SMA connector for an external antenna requires the addition
of a 200/50Ω 2.45GHz balun transformer connected to the antenna pins. The balun differential port should be
connected to the antenna port with 200Ω balanced controlled impedance track. A 50Ω controlled impedance track
should be used to connect the unbalanced port of the balun to the antenna to ensure good impedance matching and
reduce losses and reflections.
A simple external loop filter circuit consisting of two capacitors and a resistor is connected to VCOTUNE. Refer to
section 8.1 Radio for more details.
An external resistor (43kΩ) is required between IBIAS and analogue ground to set various bias currents and
references within the radio.
2.2.5 Analogue Peripherals
Several of the analogue peripherals require a reference voltage to use as part of their operations. They can use
either an internal reference voltage or an external reference connected to VREF. This voltage is referenced to
analogue ground and the performance of the analogue peripherals is dependant on the quality of this reference.
There are four ADC inputs, two comparator inputs and two DAC outputs. The analogue I/O pins on the JN513x can
have signals applied up to 0.3v higher than VDD1. A schematic view of the analogue I/O cell is shown in Figure 3
Analogue I/O Cell.
In reset and deep sleep the analogue peripherals are all off and the DAC outputs are in a high impedance state.
During sleep the ADC and DAC’s are off, with the DAC outputs in a high impedance state and the comparator may
optionally be used as a wakeup.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
11
Jennic
VDD1
Analogue
I/O Pin
Analogue
Peripheral
VSSA
Figure 3 Analogue I/O Cell
2.2.6 Digital Input/Output
Digital I/O pins on the JN513x can have signals applied up to 2V higher than VDD2 and are therefore TTL-compatible
with VDD2 > 3V. For other DC properties of these pins see section 17.2.3 I/O Characteristics.
When used in their primary function all Digital Input/Output pins are bi-directional and are connected to weak internal
pull up resistors (45kΩ nominal) that can be disabled. When used in their secondary function (selected when the
appropriate peripheral block is enabled) then their direction is fixed by the function, although the pull up resistors will
remain enabled or disabled dependent upon how they were set.
A schematic view of the digital I/O cell is in Figure 4: DIO Pin Equivalent Schematic.
VDD2
Pu
OE
RPU
DIO[x] Pin
RPROT
VSS
IE
Figure 4: DIO Pin Equivalent Schematic
Each DIO pin configuration is programmed by functions in Hardware Peripheral Library. The pin direction is set by
calling the vAHI_DioSetDirection() function that enables OE and IE as required, or by enabling a peripheral
which uses the cell as part of its I/O. The use of the pull-up resistor Rpu for each pin is controlled through the
vAHI_DioSetPullup() routine in the peripheral library, the default state from reset is enabled.
In reset, the digital peripherals are all off and the DIO pins are set as high-impedance inputs. During sleep and deep
sleep, the DIO pins retain both their input/output state and output level that was set as sleep commences. If the DIO
pins were enabled as inputs and the interrupts were enabled these pins may be used to wake up the JN513x from
sleep.
12
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
3 CPU
The CPU of the JN513x is a 32-bit load and store RISC processor. It has been architected for three key
requirements:
•
Low power consumption for battery powered applications
•
High performance to implement a wireless protocol at the same time as complex applications
•
Efficient coding of high-level languages such as C/C++ provided with the Jennic Software Developers Kit
It features a linear 32-bit logical address space with unified memory architecture, accessing both code and data in the
same address space. Registers for peripheral units, such as the timers, UARTs and the baseband processor are
also mapped into this space.
The CPU contains a block of 32 32-bit General-Purpose (GP) registers together with a small number of special
purpose registers which are used to store processor state and control interrupt handling. The contents of any GP
register can be loaded from or stored to memory, while arithmetic and logical operations, shift and rotate operations,
and signed and unsigned comparisons can be performed either between two registers and stored in a third, or
between registers and a constant carried in the instruction. Operations between general or special-purpose registers
execute in one cycle (16/32MHz) while those that access memory require a further cycle to allow the memory to
respond.
The instruction set manipulates 8, 16 and 32-bit data; this means that programs can use objects of these sizes very
efficiently. Manipulation of 32-bit quantities is particularly useful for protocols and high-end applications allowing
algorithms to be implemented in fewer instructions than on smaller word-size processors, and to execute in fewer
clock cycles. In addition, the CPU supports hardware Multiply that can be used to efficiently implement algorithms
needed by Digital Signal Processing applications.
The instruction set is designed for the efficient implementation of high-level languages such as C. Access to fields in
complex data structures is very efficient due to the provision of several addressing modes, together with the ability to
be able to use any of the GP registers to contain the address of objects. Subroutine parameter passing is also made
more efficient by using GP registers rather than pushing objects on the stack. The recommended programming
method for the JN513x is by using C, which is supported by a software developer kit comprising a C compiler, linker
and debugger.
The CPU architecture also contains features that make the processor suitable for embedded, real-time applications.
In some applications, it may be necessary to use a real-time operating system to allow multiple tasks to run on the
processor. To provide protection for device-wide resources being altered by one task and affecting another, the
processor can run in either supervisor or user mode, the former allowing access to all processor registers, while the
latter only allows the GP registers to be manipulated. Supervisor mode is entered on reset or interrupt; tasks starting
up would normally run in user mode in a RTOS environment.
Embedded applications require efficient handling of external hardware events. Exception processing (including reset
and interrupt handling) is enhanced by the inclusion of a number of special-purpose registers into which the PC and
status register contents are copied as part of the operation of the exception hardware. This means that the essential
registers for exception handling are stored in one cycle, rather than the slower method of pushing them onto the
processor stack. The PC is also loaded with the vector address for the exception that occurred, allowing the handler
to start executing in the next cycle.
To improve power consumption a number of power-saving modes are implemented in the JN513x, described more
fully in section 16 - Power Management and Sleep Modes. One of these modes is the CPU doze mode, under
software control, the processor can be shut down and on an interrupt it will wake up to service the request.
The CPU clock may be optionally doubled using a 2x clock input. Using the 2x clock mode enables the CPU to
clocked at 32MHz and therefore able to sustain 32 MIPs.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
13
Jennic
4 Memory Organisation
This section describes the different memories found within the JN513x. The device contains ROM, RAM, OTP
memory, the wireless transceiver and peripherals all within the same linear address space.
0xFFFFFFFF
0xEFFFFFFF
0x980001FF
Intelligent Peripheral
Memory Block
0x98000000
0x90000013
Intelligent Peripheral
0x90000000
0x80000017
SPI
0x80000000
0x70000013
2-Wire Interface
0xF0018000
0x70000000
0x6000001B
RAM
(96kB)
Timer1
0x60000000
0x5000001B
0xF0008000
Timer0
(32kB)
0x50000000
0xF0004000
0xF0002000
0xF0000000
0x4000007F
(16kB)
(8kB)
UART1
0x40000000
0x3000007F
UART0
0x30000000
Unpopulated
0x2000000B
Peripherals
GPIO
0x20000000
0x10000F23
Analogue Peripherals
0x10000F00
0x10000000
0x10000E57
PHY Controller
0x04000000
RAM Echo
Security Coprocessor
0x10000E00
0x10000DFF
0x10000C00
0x100009FF
0x00030000
Baseband Controller
0x10000400
ROM
(192kB)
0x100000FF
System Controller
0x10000000
0x00000000
Figure 5: JN513x Memory Map
14
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
4.1 ROM
The ROM is 192K bytes in size, organized as 48k x 32-bit words and can be accessed by the CPU in a single clock
cycle. The ROM contents change for different versions of the device to support differing protocol stacks and
applications, all versions carry a default interrupt vector table and interrupt manager. Variants that can be used for
application or protocol development carry a boot loader, to allow code from external Flash memory to be bootloaded
into RAM at runtime. The operation of the boot loader is described in detail in Application Note JN-AN-1003 Boot
Loader Operation [4]. For development variants the interrupt manager routes interrupt calls to the application’s soft
interrupt vector table contained within RAM. Section 7 contains further information regarding the handling of
interrupts. Typical ROM contents for a development variant containing a ZigBee protocol stack is shown in Figure 6.
0x0002FFFF
Unused
ZigBee Stack
IEEE802.15.4
Stack
Boot Loader
Interrupt Manager
0x00000F00
0x00000000
Interrupt Vectors
Figure 6: Typical ROM contents
4.2 RAM
The JN513x contains 8k, 16k, 32k or 96k bytes of high speed RAM organized as 2k, 4k, 8k or 24k x 32-bit words
respectively. It can be used for both code and data storage and is accessed by the CPU in a single clock cycle. At
reset, a boot loader controls the loading of segments of code and data from an external memory connected to the SPI
port, into RAM. Software can control the power supply to the RAM allowing the contents to be maintained during a
sleep period when other parts of the device are un-powered.
4.3 OTP eFuse Memory
The JN513x contains 48-bytes of eFuse memory; this is one time programmable memory that is organised as 12 x
32-bit words, 4 words are reserved by Jennic, 2 of which support on-chip MAC ID. The remaining 8 words are fully
user programmable, designed to allow the storage of configuration and product information. If secure external
memory encryption is enabled then 4 words of the user eFuse are used for this (see section 4.4.1)
At a low level, programming of the eFuse requires a sequence of carefully controlled steps, therefore to simplify the
procedure, a simple API function call through software is provided that handles the various sequences required, this
is described in JN-RM-2001 Integrated Peripherals API [2]. For reliable programming operation, a minimum system
supply voltage VDD2 of 3.6V must be provided. If this condition is not satisfied, then programming reliability cannot
be guaranteed.
4.4 External Memory
An external memory with an SPI interface may be used to provide storage for program code and data for the device
when external power is removed. The memory is connected to the SPI interface using select line SPISEL0; this
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
15
Jennic
select line is dedicated to the external memory interface and is not available for use with other external devices. See
Figure 7 for connection details.
Serial
Memory
JN513x
SPISEL0
SS
SPIMISO
SDO
SPIMOSI
SDI
SPICLK
CLK
Figure 7: Connecting External Serial Memory
At reset, the contents of this memory are copied into RAM by the software boot loader. A number of types of memory
device may be used with the JN513x boot loader so long as they conform to the format of read instructions issued by
the boot loader over the SPI interface. See application note [4] JN-AN-1003 Boot Loader Operation for details on the
format of the read command and other details of the boot loader.
4.4.1 Secure External Memory Encryption
The contents of the external serial memory may be securely encrypted to protect against system cloning or intrusion.
The AES security processor combined with a user programmable 128-bit encryption key is used to encrypt the
contents of the external memory. The encryption key is stored in eFuse and is programmed through software control.
Initially after programming, the encryption feature is not active; this allows the system to continue to operate in an
unsecured mode. Enabling of the encryption feature is through software control, once enabled all programming
operations require authentication. Full details of the eFuse software functions may be found in JN-RM-2001
Integrated Peripherals API [2].
When bootloading program code from external serial memory, the JN513x automatically accesses the encryption key
to execute the decryption process. User program code, does not need to handle any of the decryption process, it is a
transparent process.
4.5 Peripherals
All peripherals have their registers mapped into the memory space. Access to these registers requires 3 clock
cycles. Applications have access to the peripherals through the peripherals library, which presents a high-level view
of the peripheral’s functions through a series of dedicated software routines. These routines provide both a tested
method for using the peripherals and operation of power and interrupts with the IEEE802.15.4 software protocol stack
allowing bug-free application code to be developed more rapidly. See JN-RM-2001 Integrated Peripherals API [2] for
more details.
4.6 Unused Memory Addresses
Any attempt to access an unpopulated memory area will result in a bus error exception (interrupt) being generated.
16
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
5 System Clocks
Two separate oscillators are used to provide system clocks: a crystal controlled 16MHz oscillator, using an external
crystal and an internal, RC based 32kHz oscillator.
5.1 16MHz Oscillator
The JN513x contains the necessary on-chip components to build a 16 MHz reference oscillator with the addition of an
external crystal resonator and two tuning capacitors. The schematic and layout of these components are shown in
Figure 8. The two capacitors, C1 and C2, should be 15pF ±5% and use a COG dielectric. Due to the small size of
these capacitors, it is important to keep the traces to the external components as short as possible. The on-chip
transconductance amplifier is compensated for temperature variation, and is self-biasing by means of the internal
resistor R1. The electrical specification of the oscillator can be found in section 17.3.6. For detailed application
support and specification of the crystal required see Appendix B.1.
JN513x
XTALIN
R1
C1
XTALOUT
C2
Figure 8: Crystal oscillator connections
The clock generated by this oscillator provides the reference for most of the JN513x subsystems, including the
transceiver, processor, memory and digital and analogue peripherals. The clock for the processor, RAM and ROM
may be optionally driven by a 2x clock that effectively clocks these at 32MHz.
5.2 32kHz Oscillator
The internal 32kHz RC oscillator requires no external components. It provides a low speed clock for use in sleep
mode. The clock is used for timing the length of a sleep period (see section 16 Power Management and Sleep
Modes) and also to generate the system clock used internally during reset. The internal timing components of the
oscillator have a wide tolerance due to manufacturing process variation and so the oscillator runs nominally at 32kHz
±30%. To make this useful as a timing source for accurate wakeup from sleep, a frequency calibration factor derived
from the more accurate 16MHz oscillator may be applied. The calibration factor is derived through software, details
can be found in section 12.3.1. For detailed electrical specifications, see section 17.3.5.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
17
Jennic
6 Reset
A system reset initialises the device to a predefined state and forces the CPU to start program execution from the
reset vector. The reset process that the JN513x goes through is as follows.
When power is applied, the 32kHz oscillator starts up and stabilises, which takes approximately 100μsec. At this
point, the 16MHz crystal oscillator is enabled and power is applied to processor and peripheral logic. The logic blocks
are held in reset until the 16MHz crystal oscillator stabilises, typically this takes 2.5ms.
Once the oscillator is up and running the internal reset is removed from the CPU and peripheral logic and the CPU
starts to run code beginning at the reset vector, consisting of initialisation code and then optionally the resident Boot
Loader (described in reference [4]).
Section 17.3.1 provides detailed electrical data and timing.
The JN513x has four sources of reset:
•
Internal Power-on Reset
•
External Reset
•
Software Reset
•
Brown-Out-Detect
Note: When the device exits a reset condition, device operating
parameters (voltage, frequency, temperature, etc.) must be met to ensure
operation. If these conditions are not met, then the device must be held in
reset until the operating conditions are met.
6.1 Internal Power-on Reset
For the majority of applications the internal power-on reset is capable of generating the required reset signal. When
power is applied to the device, the power-on reset circuit monitors the rise of the VDD supply. When the VDD
reaches the specified threshold, the reset signal is generated and can be observed as a rising edge on the RESETN
pin. This signal is held internally until the power supply and oscillator stabilisation time has elapsed, when the internal
reset signal is then removed and the CPU is allowed to run.
VDD
Internal RESET
RESETN Pin
Figure 9: Internal Power-on Reset
18
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
If the application requires a power supply reset to be used, i.e. removing and then applying VDD, it is important that
the device decoupling capacitors are completely discharged before the VDD is re-applied. Failure to do so may inhibit
the operation of the internal power-on reset circuit. If complete discharge is difficult to achieve then it is recommended
that the external reset circuit, as shown in Figure 10, be used.
VDD
JN513x
R1
10k
RESETN
C1
100nF
Figure 10: External Reset Generation
The external resistor and capacitor provide a simple reset operation when connected to the RESETN pin.
6.2 External Reset
An external reset is generated by a low level on the RESETN pin. Reset pulses longer than the minimum pulse width
will generate a reset during active or sleep modes. Shorter pulses are not guaranteed to generate a reset. The
JN513x is held in reset while the RESETN pin is low and when the applied signal reaches the Reset Threshold
Voltage (VRST) on its positive edge, the internal reset process starts.
Multiple devices may connect to the RESETN pin in an open-collector mode. The JN513x has an internal pull-up
resistor although an external pull-up resistor is recommended when multiple devices connect to the RESETN pin.
The pin is an input for an external reset, an output during the power-on reset and may optionally be an output during
a software reset. No devices should drive the RESETN pin high.
RESETN pin
Reset
Internal Reset
Figure 11: External Reset
6.3 Software Reset
A system reset can be triggered at any time by calling the Software Reset function, vAHI_SwReset() from the
peripheral library. This function can be executed within a users application, upon detection of a system failure for
example. The RESETN line can be driven low by the JN513x to provide a reset to other devices in the system (e.g.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
19
Jennic
external sensors). The reset output feature can be enabled or disabled for the software generated reset using the
function vAHI_DriveResetOut()within the peripheral library (the default state is disabled).
6.4 Brown-out Detect
A brown-out detect module is used to monitor the supply voltage to the JN513x; this can be used whilst the device is
awake or is in CPU doze mode. Dips in the supply voltage below a variable threshold can be detected and can be
used to cause the JN513x to perform a chip reset. Equally, dips in the supply voltage can be detected and used to
cause an interrupt to the processor, when the voltage either drops below the threshold or rises above it. Hysteresis is
built into the brown out detect module this is nominally 100mV.
The threshold voltage is selectable at levels of 2.1V, 2.4V, 2.5V or 2.6V through software control, this is described in
JN-RM-2001 Integrated Peripherals API [2].
20
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
7 Interrupt System
The interrupt system on JN513x is a hardware-vectored interrupt system. The JN513x provides several interrupt
sources, some associated with CPU operations (CPU exceptions) and others which are used by hardware in the
device. When an interrupt occurs the CPU stops executing the current program and loads its program counter with a
fixed hardware address specific to that interrupt. The interrupt handler or interrupt service routine is stored at this
location and is run on the next CPU cycle. Execution of interrupt service routines is always performed in supervisor
mode. Interrupt sources and their vector locations are listed in Table 1 below:
Interrupt Source
Vector Location
Interrupt Definition
Reset
0x100
Software or hardware reset
Bus Error
0x200
Bus error or attempt to access invalid physical address
Tick Timer
0x500
Tick Timer expiry
Alignment
0x600
Load/Store to naturally not aligned location
Illegal Instruction
0x700
Illegal instruction in instruction stream
Hardware Interrupts
0x800
Hardware Interrupt
System Call
0xC00
System Call Initiated by software (l.sys instruction)
Trap
0xE00
Caused by l.trap instruction
Table 1: Interrupt Vectors
7.1 System Calls
Executing the l.sys instruction causes a system call interrupt to be generated. The purpose of this interrupt is to
allow a task to switch into supervisor mode when a real time operating system is in use, see section 3 for further
details. It also allows a software interrupt to be issued, as does execution of the l.trap instruction.
7.2 Processor Exceptions
7.2.1 Bus Error
A bus error exception is generated when software attempts to access a memory address that does not exist, or is not
populated with memory or peripheral registers.
7.2.2 Alignment
Alignment exceptions are generated when software attempts to access objects that are not aligned to natural word
boundaries. 16-bit objects must be stored on even byte boundaries, while 32-bit objects must be stored on quad byte
boundaries. For instance, attempting to read a 16-bit object from address 0xFFF1 will trigger an alignment exception
as will a read of a 32-bit object from 0xFFF1, 0xFFF2 or 0xFFF3. Examples of legal 32-bit object addresses are
0xFFF0, 0xFFF4, 0xFFF8 etc.
7.2.3 Illegal Instruction
If the CPU reads an unrecognised instruction from memory as part of its instruction fetch, it will cause an illegal
instruction exception.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
21
Jennic
7.3 Hardware Interrupts
Hardware interrupts generated from the transceiver, analogue or digital peripherals and DIO pins are individually
masked using the Programmable Interrupt Controller (PIC). Management of interrupts is provided in the peripherals
library. Further details of interrupts are provided for the functions in their respective sections in this datasheet.
Interrupts are used to wake the JN513x from sleep. The peripherals, baseband controller, security coprocessor and
PIC are powered down during sleep but the DIO interrupts and optionally the wake-up timers and analogue
comparator interrupts remain powered to bring the JN513x out of sleep.
Wake-up
Timers
Baseband
Controller
Security
Coprocessor
Programmable
Interrupt
Controller
DIO Pins
UART0
Hardware
Interrupt
UART1
Timer0
Timer1
2-wire Serial
Interface
SPI Controller
Intelligent
Peripheral
Analogue
Peripheral
Figure 12: Programmable Interrupt Controller
22
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
8 Wireless Transceiver
The wireless transceiver comprises a 2.45GHz radio, an O-QPSK modem, a baseband processor, a security
coprocessor and PHY controller. These blocks, with protocol software provided as a library, implement an
IEEE802.15.4 standards-based wireless transceiver that transmits and receives data over the air in the unlicensed
2.4GHz band. IEEE802.15.4 wireless functionality is provided with the transceiver and the protocol software
described in JN-RM-2002 802.15.4 Stack [3]. Applications interface to the protocol software via an API interface that
corresponds to the SAP interfaces defined in the IEEE Std 802.15.4-2006 [1]
8.1 Radio
VGA
∑
PA
TX
DAC
IDATA
PA (I)
Trim
LOI
LOQ
VGA
PA
Power
DAC
QDATA
PA (Q)
Trim
RX
Calibration
LOI
LNA
VGA1
LOQ
VGA2
ADC
IF DATA
AGC
LOQ
VCO
90
PLL
Calibration
Reference
& BIAS
LOI
Figure 13: Radio Architecture
The radio comprises a low-IF receive path and a direct up-conversion transmit path, which converge at the TX/RX
switch. This switch includes the necessary matching components such that a 200Ω differential antenna may be
directly connected without external components. Alternatively, a balun can be used for single ended antennas.
The 16MHz crystal oscillator feeds a divider, which provides the frequency synthesiser with a reference
frequency. The synthesiser contains programmable feedback dividers, phase detector, charge pump and internal
Voltage Controlled Oscillator (VCO). The VCO has no external components, and includes calibration circuitry to
compensate for differences in internal component values due to process and temperature variations. The VCO is
controlled by a Phase Lock Loop (PLL) that has a loop filter comprising 3 external components. A programmable
charge pump is also used to tune the loop characteristic. Finally, quadrature (I and Q) local oscillator signals for the
mixer drives are derived.
The receiver chain starts with the low noise amplifier / mixer combination whose outputs are passed to the polyphase
bandpass filter. This filter provides the channel definition as well as image frequency rejection. The signal is then
passed to two variable gain amplifier blocks. The gain control for these stages, and the bandpass filter, is derived in
the automatic gain control (AGC) block within the Modem. The signal is conditioned with the anti-alias low pass filter,
before being converted to a digital signal with a flash ADC.
In the transmit direction, the digital I and Q streams from the Modem are passed to I and Q quadrature DAC blocks
which are buffered and low-pass filtered, before being applied to the modulator mixers. The summed 2.4 GHz signal
is then passed to the RF Power Amplifier (PA), whose power control can be selected from one of six settings. The
output of the PA drives the antenna via the RX/TX switch.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
23
Jennic
8.1.1 Radio External components
The VCO loop filter requires three external components and the IBIAS pin requires one external component as shown
in Figure 14. These components should be placed close to the JN513x pins and analogue ground.
VCOTUNE
15
4k7
1%
3n3F
19
VB_VCO
100nF
330pF
VSSA
IBIAS
43k
1%
VSSA
Figure 14: VCO Loop Filter and IBIAS
The radio is powered from a number of internal 1.8V regulators fed from the analogue supply VDD1, in order to
provide good noise isolation between the digital logic of the JN513x and the analogue blocks. These regulators are
also controlled by the baseband controller and protocol software to minimise power consumption. Decoupling for
internal regulators is required as described in section 2.2.1, Power Supplies.
8.1.2 Antenna Diversity
Support is provided for antenna diversity. Antenna diversity is a technique that maximises the performance of an
antenna system. It allows the radio to switch between two antennas that have very low correlation between their
received signals. Typically, this is achieved by spacing two antennas around 0.25 wavelengths apart or by using two
orthogonal polarisations. So, if a packet is transmitted and no acknowledgement is received, the radio system can
switch to the other antenna for the retry, with a different probability of success.
The JN513x provides two outputs that can be used to control an antenna switch; this enables antenna diversity to be
implemented easily. DIO12 is asserted on odd numbered retires and DIO13 is asserted on the first transmit and even
numbered retries.
24
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
8.2 Modem
The Modem performs all the necessary modulation and spreading functions required for digital transmission and
reception of data at 250kbps in the 2450MHz radio frequency band in compliance with the IEEE802.15.4 standard.
RX
Gain
O-QPSK
Demodulation
AGC
IF Signal
TX
Symbol
Detection
(Despreading)
RX Data
Interface
Spreading
TX Data
Interface
Pulse Shaping
O-QPSK
Modulation
Figure 15: Modem Architecture
The transmitter receives symbols from the baseband processor and uses the spreading function to map each unique
4-bit symbol to a 32-chip Pseudo-random Noise (PN) sequence. Offset-QPSK modulation and half-sine pulse
shaping is applied to the resultant spreading sequence to produce two independent quadrature phase signals (I and
Q), which are subsequently converted to analogue voltages in the radio transmit path.
The Automatic Gain Control (AGC) monitors the received signal level and adjusts the gain of the amplifiers in the
radio receiver to ensure that the optimum signal amplitude is maintained during reception.
The demodulator performs digital IF down-conversion and matched filtering and is extremely tolerant to carrier
frequency offsets in excess of ±80ppm without suffering any significant degradation in performance.
Symbol detection and synchronization is performed using direct sequence correlation techniques in conjunction with
searches for the Preamble and Start-of-Frame Delimiter (SFD) fields contained in the transmitted IEEE 802.15.4
Synchronization Header (SHR).
Features are provided to support network channel selection algorithms include Energy Detection (ED), Link Quality
Indication (LQI) and fully programmable Clear Channel Assessment (CCA).
The Modem provides a digital Receive Signal Strength Indication (RSSI) that facilitates the implementation of the
IEEE 802.15.4 ED function.
The LQI is defined in the IEEE 802.15.4 standard as a characterization of the strength and/or data quality of a
received packet. The Modem produces a signal quality metric based upon correlation magnitudes, which may be
used in conjunction with the ED value to formulate the LQI.
The CCA capability of the Modem supports all modes of operation defined in the IEEE 802.15.4 standard, namely
Energy above ED threshold, Carrier Sense and Carrier Sense and/or energy above ED threshold.
8.3 Baseband Processor
The baseband processor provides all time-critical functions of the IEEE802.15.4 MAC layer. Dedicated hardware
guarantees air interface timing is precise. The MAC layer hardware/software partitioning, enables software to
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
25
Jennic
implement the sequencing of events required by the protocol and to schedule timed events with millisecond
resolution, and the hardware to implement specific events with microsecond timing resolution. The protocol software
layer performs the higher-layer aspects of the protocol, sending management and data messages between endpoint
and coordinator nodes, using the services provided by the baseband processor.
Tx
Bitstream
Append
Checksum
Serialiser
Encrypt
Port
Tx/Rx
Frame
Buffer
Status
AES
AES
Codec
Codec
Supervisor
Radio
Inline
Security
Protocol Timing Engine
CSMA
CCA
Backoff
Control
Protocol
Timers
Control
Rx
Bitstream
Verify
Checksum
Deserialiser
Decrypt
Port
Processor
Bus
Figure 16: Baseband Processor
8.3.1 Transmit
A transmission is performed by software writing the data to be transferred into the Tx/Rx Frame Buffer, together with
parameters such as the destination address and the number of retries allowed, and programming one of the protocol
timers to indicate the time at which the frame is to be sent. This time will be determined by the software tracking the
higher-layer aspects of the protocol such as superframe timing and slot boundaries. Once the packet is prepared and
protocol timer set, the supervisor block controls the transmission. When the scheduled time arrives, the supervisor
controls the sequencing of the radio and modem to perform the type of transmission required. It can perform all the
algorithms required by IEEE802.15.4 such as CSMA/CA, GTS without processor intervention including retries and
random backoffs.
When the transmission begins, the header of the frame is constructed from the parameters programmed by the
software and sent with the frame data through the serialiser to the Modem. At the same time, the radio is prepared
for transmission. During the passage of the bitstream to the modem, it passes through a CRC checksum generator
that calculates the checksum on-the-fly, and appends it to the end of the frame.
If using slotted access, it is possible for a transmission to overrun the time in its allocated slot; the Baseband
Processor handles this situation autonomously and notifies the protocol software via interrupt, rather than requiring it
to handle the overrun explicitly.
8.3.2 Reception
In a reception, the radio is set to receive on a particular channel. On receipt of data from the modem, the frame is
directed into the Tx/Rx Frame Buffer where both header and frame data can be read by the protocol software. An
interrupt may be provided on receipt of the frame header. As the frame data is being received from the modem it is
passed through a checksum generator; at the end of the reception the checksum result is compared with the
checksum at the end of the message to ensure that the data has been received correctly.
During reception, the modem determines the Link Quality, which is made is made available at the end of the
reception as part of the requirements of IEEE802.15.4.
26
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
8.3.3 Auto Acknowledge
Part of the protocol allows for transmitted frames to be acknowledged by the destination sending an acknowledge
packet within a very short window after the transmitted frame has been received. The JN513x baseband processor
can automatically construct and send the acknowledgement packet without processor intervention and hence avoid
the protocol software being involved in time-critical processing within the acknowledge sequence. The JN513x
baseband processor can also request an acknowledge for packets being transmitted and handle the reception of
acknowledged packets without processor intervention.
8.3.4 Beacon Generation
In beaconing networks, the baseband processor can automatically generate and send beacon frames; the repetition
rate of the beacons is programmed by the CPU, and the baseband then constructs the beacon contents from data
delivered by the CPU. The baseband processor schedules the beacons and transmits them without CPU
intervention.
8.3.5 Security
The baseband processor supports the transmission and reception of secured frames using the Advanced Encryption
Standard (AES) algorithm transparently to the CPU. This is done by passing incoming and outgoing data through an
in-line security engine that is able to perform encryption and decryption operations on-the-fly, resulting in minimal
processor intervention. The CPU must provide the appropriate encrypt/decrypt keys for the transmission or
reception. On transmission, the key can be programmed at the same time as the rest of the frame data and setup
information.
During reception, the CPU must look up the key and provide it from information held in the header of the incoming
frame. However, the hardware of the security engine can process data much faster than the incoming frame data
rate. This means that it is possible to allow the CPU to receive the interrupt from the header of an incoming packet,
read where the frame originated, look up the key and program it to the security hardware before the end of the frame
has arrived. By providing a small amount of buffering to store incoming data while the lookup process is taking place,
the security engine can catch up processing the frame so that when the frame arrives in the receive frame buffer it is
fully decrypted.
8.4 Security Coprocessor
As well as being used during in-line encryption/decryption operations over a streaming interface and in external
memory encryption, it is also possible to use the AES core as a coprocessor to the CPU of the JN513x. To allow the
hardware to be shared between the two interfaces an arbiter ensures that the streaming interface to the AES core
always has priority, to ensure that in-line processing can take place at any time.
Arbiter
Processor
Interface
In-line
Interface
AES
Block
Encrpytion
Controller
AES
Encoder
Key Generation
Some protocols (for example ZigBee) require that security operations can be performed on buffered data rather than
in-line. A hardware implementation of the encryption engine significantly speeds up the processing of the contents of
these buffers. The AES library for the JN513x provides two operations vAHI_SecurityEncode() and
vAHI_SecurityDecode() which utilise the encryption engine in the device and allow the contents of memory
buffers to be transformed. Information such as the type of security operation to be performed and the encrypt/decrypt
key to be used must also be provided.
Figure 17: Security Coprocessor Architecture
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
27
Jennic
9 Digital Input/Output
There are 21 Digital I/O (DIO) pins, which can be configured as either an input or an output, and each has a
selectable internal pull-up resistor. Most DIO pins are multiplexed with alternate peripheral features of the device.
Once a peripheral is enabled it takes precedence over the device pins. Refer to the individual module sections for a
full description of the alternate peripherals functions. From reset, all peripherals are off and the DIO pins are
configured as inputs with the internals pull-ups turned on.
SPICLK, MOSI, MISO
SPI Port
SPISEL<4:0>
SPISEL<0>
TxD
RxD
UART 0
RTS
DIO<20:0>
CTS
MUX
TxD
Chip
Pins
RxD
UART 1
RTS
CTS
TIM0CK_GT
Counter/Timer 0
TIM0CAP
TIM0OUT
TIM1CK_GT
Counter/Timer 1
2-Wire Serial
Interface
TIM1CAP
TIM1OUT
SIF_CLK
SIF_D
IP_CLK
IP_DI
Intelligent
Peripheral
IP_DO
IP_SEL
IP_INT
RFTX
RFTX
Processor Bus
(Address, Data, Interrupts)
GPIO
Data / Direction
Registers
DIO<20:0>
Figure 18: DIO Block Diagram
When a peripheral is not enabled, the DIO pins associated with it can be used as digital inputs or outputs. Each pin
can be controlled individually with the direction being set using the vAHI_DioSetDirection() function. Reading
and writing to the pins is controlled using the vAHI_DioSetOutput() and u32AHI_DioReadInput() functions.
The individual pull-up resistors, RPU, are selected using the vAHI_DioSetPullup() function.
When configured as an input each pin can be used to generate an interrupt upon a change of state (selectable
transition either from low to high or high to low); the interrupt can be enabled or disabled. When the device is
sleeping, these interrupts become events that can be used to wake the device up. Selection of the interrupt transition
is done using vAHI_DioInterruptEdge(). Enabling and masking of DIO interrupts is done using
vAHI_DioInterruptEnable() while the status of a DIO interrupt is given by u32AHI_DioInterruptStatus().
See section 16 Power Management and Sleep Modes for further details on sleep and wakeup.
28
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
10 Serial Peripheral Interface
The Serial Peripheral Interface (SPI) allows high-speed synchronous data transfer between the JN513x and
peripheral devices. The JN513x operates as a master on the SPI bus and all other devices connected to the SPI are
expected to be slave devices under the control of the JN513x CPU. The SPI includes the following features:
•
Full-duplex, three-wire synchronous data transfer
•
Programmable bit rates up to 16Mbps
•
Programmable transaction size of 8,16 or 32 bits
•
Supports standard SPI modes 0, 1, 2, 3 to allow control over the relationship between clock and transmit /
receive data
•
Automatic slave select generation (up to 5 slaves)
•
Maskable transaction complete interrupt
•
LSB First or MSB First Data Transfer
SPICLK
SPIMOSI
Data
Clock Edge
Select
Data Buffer
SPIMISO
LSB
Clock
Divider
DIV
16 MHz
15
CHAR_LEN
31
SPI Bus
Cycle
Controller
Select
Latch
SPISEL [4..0]
Figure 19: SPI Block Diagram
The SPI bus employs a simple shift register data transfer scheme. Data is clocked out of and into the active devices
in a first-in, first-out fashion allowing SPI devices to transmit and receive data simultaneously.
There are three dedicated pins SPICLK, SPIMOSI, SPIMISO that are shared across all devices on the bus. MasterOut-Slave-In or Master-In-Slave-Out data transfer is relative to the clock signal SPICLK generated by the JN513x.
The JN513x provides five slave selects, SPISEL0 to SPISEL4 to allow five SPI peripherals on the bus. SPISEL0 is a
dedicated pin and SPISEL1 to 4, are alternate functions of pins DIO0 to 3 respectively. This allows a serial flash
memory to be connected to SPISEL0 and download to internal RAM via software from reset.
The interface can transfer 8, 16 or 32 bits without software intervention and can keep the slave select lines asserted
between transfers when required, to enable longer transfers to be performed.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
29
Jennic
SS
SO
SS
User
Defined
SI
SO
SO
SI
SO
42
JN513x
43
41
37
User
Defined
Slave 4
SPISEL1
SPISEL2
SPISEL3
SPISEL4
38
SI
SO
SI
SPISEL0
User
Defined
SS
SS
SS
User
Defined
Flash
Memory
Slave 3
Slave 2
SI
Slave 1
Slave 0
36
SPIMOSI
33
SPICLK
34 SPIMISO
Figure 20: Typical JN513x SPI Peripheral Connection
The data transfer rate on the SPI bus is determined by the SPICLK signal. The JN513x supports transfers at
selectable data rates from 16MHz to 250kHz selected by a clock divider. Both SPICLK clock phase and polarity are
configurable. The clock polarity controls if SCLK is high or low between transfers (and hence the polarity of the first
clock edge in a transfer). The clock phase and polarity determines which edge of SPICLK is used by the JN513x to
present new data on the SPIMOSI line; the opposite edge will be used to read data from the SPIMISO line. These
options are specified using the vAHI_SpiConfigure() function.
SPICLK
Polarity
Phase
Mode
Description
SPICLK is low when idle – the first edge is positive.
Valid data it output on SPIMOSI before the first clock and changes every
negative edge. SPIMISO is sampled every positive edge.
SPICLK is low when idle – the first edge is positive.
Valid data is output on SPIMOSI every positive edge. SPIMISO is sampled every
negative edge.
SPICLK is high when idle – the first edge is negative.
Valid data is output on SPIMOSI before the first clock edge and is changed
every positive edge. SPIMISO is sampled every negative edge.
SPICLK is high when idle – the first edge is negative.
Valid data is output on SPIMOSI every negative edge. SPIMISO is sampled
every positive edge.
The slave select outputs, SPISELn, are controlled using the vAHI_SpiSelect() function. If more than one SPISEL
line is to be used in a system they must be used in numerical order, for instance if 3 SPI select lines are to be used,
they must be SPISEL0, 1 and 2. The number of SPISEL lines to be used in a system is controlled using
vAHI_SpiConfigure(). A SPISEL line can be automatically deasserted between transactions if required, or it may
stay asserted over a number of transactions until removed by a call to vAHI_SpiSelect(). For devices such as
30
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
memories where a large amount of data can be received by the master by continually providing SPICLK transitions,
the ability for the select line to stay asserted is an advantage since it keeps the slave enabled over the whole of the
transfer.
A transaction commences with the SPI bus being set to the correct configuration using vAHI_SpiConfigure(),
and then the slave device being selected using vAHI_SpiSelect(). Transmit commences using the
vAHI_SpiStartTransferxx() function (where xx is either 8, 16 or 32 bits). This will cause data to be placed in
the FIFO data buffer and be clocked out, at the same time generating the corresponding SPICLK transitions. Since
the transfer is full-duplex, the same number of data bits is being received from the slave as it transmits. The data that
is received during this transmission can be read using u32AHI_SpiReadTransferxx() (again xx is either 8, 16 or
32 bits). If the master simply needs to provide a number of SPICLK transitions to allow data to be sent from a slave,
it can perform a vAHI_SpiStartTransferxx() using dummy transmit data. An interrupt can be generated when
the transaction has completed when enabled by vAHI_SpiConfigure(). Alternatively the interface can be polled
using the bAHI_SpiPollBusy() or vAHI_SpiWaitBusy() functions.
If a slave device wishes to signal the JN513x indicating that it has data to provide, it may be connected to one of the
DIO pins that can be enabled as an interrupt.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
31
Jennic
10.1 Programming Example
The following code example shows how to initialise the SPI and perform a simple read from a slave device. The
device being read requires 40 clocks to send an 8-bit instruction, a 24-bit address and retrieve the 8-bit data. This
cannot be achieved by a single transfer, so multiple transfers are combined without the automatic de-assertion of the
selects. The waveforms generated by the example code are illustrated in Figure 21.
Programming Example
PRIVATE void vReadFromFlash(uint32 u32Addr,
uint32 u32NumWords,
uint32 *pau32Buffer )
#define FLASHREADCMD 0x03
#define SPI_SLCT_NONE 0x00
uint32 u32Temp;
uint32 i;
vAHI_SpiConfigure(
1,
/* number of slave select
lines in use */
E_AHI_SPIM_MSB_FIRST,
/* send data MSB first */
E_AHI_SPIM_TXNEG_EDGE,
/* TX data to change on
negative edge */
E_AHI_SPIM_RXNEG_EDGE,
/* RX data to change on
negative edge */
0,
/* Generate 16MHz SPI clock */
E_AHI_SPIM_INT_DISABLE,
/* Disable SPI interrupt */
E_AHI_SPIM_AUTOSLAVE_DSABL); /* Disable auto slave select
*/
/* combine read cmd & addr into single value to be sent over SPI */
u32Temp = (u32Addr & 0x00FFFFFF) | (FLASHREADCMD << 24);
/* select spi device */
vAHI_SpiSelect(E_AHI_SPIM_SLAVE_ENBLE_0);
/* send read cmd and address location */
vAHI_SpiStartTransfer32(u32Temp);
vAHI_SpiWaitBusy();
for (i=0; i<=u32NumWords; i++)
/* read data 4 bytes at a time */
vAHI_SpiStartTransfer32(u32Addr);
vAHI_SpiWaitBusy();
/* copy into temp variable */
u32Temp = u32AHI_SpiReadTransfer32();
/* copy to buffer */
memcpy( (pau32Buffer+i), &u32Temp, sizeof(u32Temp) );
/* deselect select spi device */
vAHI_SpiSelect(SPI_SLCT_NONE);
32
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
Instruction Transaction
SPISEL
10
28
29
30
31
SPICLK
Instruction (0x03)
24-Bit Address
SPIMOSI
23
MSB
22
21
SPIMISO
Read Data Bytes Transaction(s) 1-N
SPISEL
10
28
29
30
31
SPICLK
SPIMOSI
SPIMISO
Changes every spi clk but value is unused by peripheral
MSB
Octet 0
MSB
Octet 4N-3
LSB
Octet 4N-1
Figure 21: SPI Transaction Waveforms (Mode = 0)
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
33
Jennic
11 Intelligent Peripheral Interface
The Intelligent Peripheral (IP) Interface is provided for systems that are more complex, where there is a processor
that requires a wireless peripheral. As an example, the JN513x may provide a complete IEEE802.15.4, ZigBee or
other wireless network to a phone, computer, PDA, set-top box or games console. No resources are required from
the main processor compared to a transceiver as the complete wireless protocol may be run on the internal JN513x
CPU. The wireless peripheral may be controlled via one of the UARTs but the IP interface is intended to provide a
high-speed, low-processor-overhead interface.
The intelligent peripheral interface is a SPI slave interface and uses pins shared with other DIO signals. The
interface is designed to allow message passing and data transfer. Data received and transmitted on the IP interface
is copied directly to and from a dedicated area of memory without intervention from the CPU. This memory area, the
intelligent peripheral memory block, contains 64 32-bit word receive and transmit buffers.
System Processor
(e.g. in cellphone, computer)
JN513x
Intelligent
Peripheral
Interface
IP_INT
SPIINT
IP_DO
SPIMISO
IP_DI
SPIMOSI
IP_SEL
SPISEL
IP_CLK
SPICLK
SPI
MASTER
CPU
Figure 22: Intelligent Peripheral Connection
The interface conforms to the SPI protocol as described in section 10. It is possible to select the clock edge of
IP_CLK on which data on the IP_DIN line of the interface is sampled, and the state of data output IP_DOUT is
changed. The order of transmission is MSB first. The IP_DO data output is tri-stated when the device is inactive, i.e.
the device is not selected via IP_SEL. An interrupt output line IP_INT is available so that the JN513x can indicate to
an external master that it has data to transfer.
The IP interface signals IP_CLK, IP_DO, IP_DI, IP_SEL, IP_INT are alternate functions of pins DIO14 to 18
respectively.
11.1 Data Transfer Format
Transfers are started by the remote processor asserting the IPSEL line and terminated by the remote processor deasserting IP_SEL.
Data transfers are bi-directional and traffic in both directions has a format of status byte, data length byte (of the
number of 32-bit words to transfer) and data packet (from the receive and transmit buffers). The first byte transferred
in either direction is a status byte with the following format:
Bit
Field
Description
7:2
RSVD
Reserved, set to 0.
TXQ
1: Data queued for transmission
RXRDY
1: Buffer ready to receive data
Table 2: IP Status Byte Format
If data is queued for transmission and the recipient has indicated that they are ready for it (RXRDY in incoming status
byte was 1), the next byte to be transmitted is the data length in words. If either the JN513x or the remote processor
34
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
has no data to transfer, then the data length should set to zero. The transaction can be terminated by the master
after the status byte has been sent if it is not possible to send data in either direction. This may be because neither
party has data to send or because the receiver does not have a buffer available. If the data length is non-zero, the
data in the JN513x transmit memory buffer is sent, beginning at the start of the buffer. At the same time that data
bytes are being sent from the transmit buffer, the JN513x receive buffer is being filled with incoming data, beginning
from the start of the buffer.
The remote processor, acting as the master must determine the larger of its incoming or outgoing data transfers and
deassert IP_SEL when all of the transmit and receive data has been transferred. The data is transferred into or out of
the buffers starting from the lowest address in the buffer, and each word is assembled with the MSB first on the serial
data lines.
IP_SEL
IP_CLK
IP_DI
Status (8 bit)
IP_DO
padding (8 bit)
padding (8 bit)
data length or 0s (8 bit)
N words of data
Status (8 bit)
data length or 0s (8 bit)
N words of data
Figure 23: Intelligent Peripheral Data Transfer Waveforms
11.2 JN513x Initiated Data Transfer
To send data, the data is written into either buffer 0 or 1 of the intelligent peripheral memory area. Then the buffer
number is written together with the data length using bAHI_IpSendData(). If the call is successful, the interrupt
line IP_INT will signal to the remote processor that there is a message ready to be sent from the JN513x. When a
remote processor starts a transfer to the JN513x by deasserting IP_SEL, then IP_INT is deasserted. If the transfer is
unsuccessful and the data is not output then IP_INT is reasserted after the transfer to indicate that data is still waiting
to be sent.
The interface can be configured to generate an internal interrupt whenever a transaction completes (for example
IP_SEL becomes inactive after a transfer starts). It is also possible to mask the interrupt. The end of the
transmission can be signalled by an interrupt, or the interface can be polled using the function bAHI_IpTxDone()
To receive data the interface must first be initialised using vAHI_IpEnable(). When this is done, the bit RXRDY
sent in the status byte from the IP block will show that data can be received by the JN513x. Successful data arrival
can be indicated by an interrupt, or the interface can be polled using bAHI_IpRxDataAvailable(). Data is then
retrieved using bAHI_IpReadData().
To send and receive at the same time, the transmit and the receive buffers must be set to be different.
11.3 Remote Processor Initiated Data Transfer
The remote processor (master) may initiate a transfer to send data to the JN513x by asserting the slave select pin,
IP_SEL, and generating its status byte on IP_DI with TXRDY set. After receiving the status byte from the JN513x, it
should check that the JN513x has a buffer ready by reading the RXRDY bit. If the RXRDY bit is 0 indicating that the
JN513x cannot accept data, it should terminate the transfer by deasserting IP_SEL unless it is receiving data from
the JN513x. If the RXRDY bit is 1, indicating that the JN513x can accept data, then the master should generate a
further 8 clocks on IP_CLK in order to transfer its own message length on IP_DI. The master should continue
clocking the interface until sufficient clocks have been generated to send all the data specified in the length field to
the JN513x. The master should then deassert IP_SEL to show the transfer is complete.
The master may initiate a transfer to read data from the JN513x by asserting the slave select pin, IP_SEL, and
generating its status byte on IP_DI with RXRDY set. After receiving the status byte from the JN513x, it should check
that the JN513x has a buffer ready by reading the TXRDY bit. If the TXRDY bit is 0, indicating that the JN513x does
not have data to send, it should terminate the transfer by deasserting IP_SEL unless it is transmitting data to the
JN513x. If the TXRDY bit is 1, indicating that the JN513x can send data, then the master should generate a further 8
clocks on IP_CLK in order to receive the message length on IP_DO. The master should continue clocking the
interface until sufficient clocks have been generated to receive all the data specified in the length field from the
JN513x. The master should then deassert IP_SEL to show the transfer is complete.
Data can be sent in both directions at once and the master must ensure both transfers have completed before
deasserting IP_SEL.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
35
Jennic
12 Timers
12.1 Peripheral Timer / Counters
Two general-purpose timer / counter units are available that can be independently configured to operate in one of five
modes. The timers have the following features:
prescale
•
16-bit prescaler, divides system clock by of 2
•
Clocked from internal system clock
•
16-bit counter, 16-bit Rise and Fall (period) registers
•
Timer: can generate interrupts off Rise and Fall counts. Can be gated by external signal
•
Counter: counts number of transitions on external event signal. Can use low-high, high-low or both
transitions
•
PWM/Single pulse: outputs repeating Pulse Width Modulation signal or a single pulse. Can set period and
mark-space ratio
•
Capture: measures times between transitions of an applied signal.
•
Delta-Sigma: Return-To-Zero (RTZ) and Non-Return-to-Zero (NRZ) modes
value as the clock to the timer
Int Enable
INT
Interrupt
Generator
Rise
Capture
Generator
TIMxCAP
OE
Fall
TIMxOUT
Capture
Enable
Gate
Sys Clk
PWM/Δ−Σ
Counter
Gate
Edge
Select
PWM/DeltaSigma
Delta-Sigma
Prescaler
TIMxCK_GT
PWM/Δ−Σ
Reset
Reset Generator
S/w
Reset
System
Reset
Single
Shot
Figure 24: Timer Unit Block Diagram
The clock source for the timer unit is fed from the 16MHz system clock. This clock passes to a 16-bit prescaler where
prescale
value. For example, a prescale value
a value of 0 leaves the clock unmodified and other values divide it by 2
of 2 applied to the 16MHz system clock source results in a timer clock of 4MHz. The value of the prescaler is set
using the vAHI_TimerEnable() function.
36
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
The counter is optionally gated by a signal on the clock / gate input (TIMxCK_GT). If the gate function is selected
(using vAHI_TimerClockSelect()) the counter is frozen when the clock/gate input is high.
If enabled using the vAHI_TimerEnable() function, an interrupt is generated whenever counter is equal to the
value stored in either of the High or Low registers.
The internal Output Enable (OE) signal enables or disables the timer output.
The Timer 0 signals CK_GT, CAP and OUT are alternate functions of pins DIO8, 9 and 10 respectively and Timer 1
signals CK_GT, CAP and OUT are alternate functions of pins DIO11, 12, and 13 respectively. Selection of either the
Timer or DIOx functionality is through software, in either case the timer still functions internally.
12.1.1 Pulse Width Modulation Mode
Pulse Width Modulation (PWM) mode allows the user to specify an overall cycle time and pulse length within the
cycle. The pulse can be generated either as a single shot or as a train of pulses with a repetition rate determined by
the cycle time.
In this mode, the cycletime and low periods of the PWM output signal can be set by the values of two independent
16-bit registers (Fall and Rise). The counter increments and its output is compared to the 16-bit Rise and Fall
registers. When the counter is equal to the Rise register, the PWM output is set to high; when the counter reaches
the Fall value, the output returns to low. In continuous mode, when the counter reaches the Fall value, it will reset
and the cycle repeats. Depending upon the mode of operation either the vAHI_TimerStartRepeat() function or
the vAHI_TimerStartSingleShot() is used to set the values of the High and Low registers. The PWM
waveform is available on TIMxOUT when the output driver is enabled using vAHI_TimerEnable().
Rise
Fall
Figure 25: PWM Output Timings
12.1.2 Capture Mode
The capture mode can be used to measure the time between transitions of a signal applied to the capture input
(TIMxCAP). The mode is selected and the counter started by vAHI_TimerStartCapture(). On the next low-tohigh transition of the captured signal, the count value is stored in the Rise register, and on the following high-to-low
transition, the counter value is stored in the Fall register. The pulse width is the difference in counts in the two
registers multiplied by the driving clock (in all cases this must be the 16MHz clock and so the prescaler must be set to
0). The counter is stopped and Low and High registers read with vAHI_TimerReadCapture(). The values in the
High and Low registers will be updated whenever there is a corresponding transition on the capture input, and the
value stored will be relative to when the mode was started. Therefore, if multiple pulses are seen on TIMxCAP before
the counter is stopped only the last pulse width will be stored.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
37
Jennic
CLK
CAPT
tRISE
tRISE
tFALL
tFALL
Capture Mode Enabled
Rise
Fall
14
Figure 26: Capture Mode
12.1.3 Counter / Timer Mode
The counter/timer can be used to generate timing or count interrupts for software to use. As a timer the clock source
is from the system clock, prescaled if required. The timer period is programmed into the Fall register and the Fall
register match interrupt enabled. The timer is started either as a single-shot or repeating timer
(vAHI_TimerStartSingleShot() or vAHI_TimerStartRepeat()), and generates an interrupt when the
counter reaches the Fall register value.
When used to count external events on TIMxCK_GT the clock source is selected from the input pin and the number
of events programmed into the Fall register. The Fall register match interrupt is enabled and the counter started,
usually in single shot mode. An interrupt is generated when the programmed number of low-to-high transitions is
seen on the input pin.
12.1.4 Delta-Sigma Mode
A separate delta-sigma mode is available, allowing a low speed delta-sigma DAC to be implemented with up to 16-bit
resolution. This requires that a resistor-capacitor network is placed between the output DIO pin and digital ground. A
stream of pulses with digital voltage levels is generated which is integrated by the RC network to give an analogue
voltage. A conversion time is defined in terms of a number of clock cycles. The width of the pulses generated is the
period of a clock cycle. The number of pulses output in the cycle, together with the integrator RC values will
determine the resulting analogue voltage. For example, generating approximately half the number of pulses that
make up a complete conversion period will produce a voltage on the RC output of VDD1/2, provided the RC time
constant is chosen correctly. During a conversion, the pulses will be pseudo-randomly dispersed throughout the
cycle in order to produce a steady voltage on the output of the RC network.
The output signal is asserted for the number of clock periods defined in the High register set by
16
vAHI_TimerStartDeltaSigma(), with the total period being 2 cycles. For the same value in the High register
the pattern of pulses on subsequent cycles is different, due to the pseudo-random distribution.
The delta-sigma convertor output can operate in a Return-To-Zero (RTZ) or a Non-Return-to-Zero (NRZ) mode. The
NRZ mode will allow several pulses to be output next to each other. The RTZ mode ensures that each pulse is
separated from the next by at least one period. This improves linearity if the rise and fall times of the output are
different to one another. Essentially, the output signal is low on every other output clock period, and the conversion
cycle time is twice the NRZ cycle time ie 217 clocks. The integrated output will only reach half VDD2 in RTZ mode,
since even at full scale only half the cycle contains pulses. Figure 27 and Figure 28 illustrate the difference between
RTZ and NRZ for the same programmed number of pulses.
38
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
217
Conversion cycle 1
Conversion cycle 2
Figure 27: Return To Zero Mode in Operation
Conversion cycle 1
216
Conversion cycle 2
Figure 28: Non-Return to Zero Mode
12.1.5 Timer / Counter Application
Figure 29 shows an application of the JN513x timers to provide closed loop speed control. Timer 0 is configured in
PWM mode to provide a variable mark-space ratio switching waveform to the gate of the NFET. This in turn controls
the power in the DC motor.
Timer 1 is configured to count the rising edge events on the clk/gate pin over a constant period. This converts the
tacho pulse stream output into a count proportional to the motor speed. This value is then used by the application
software executing the control algorithm.
+12V
JN513x
Timer 0
Timer 1
1N4007
48
CLK/GATE
50
CAPTURE
51
PWM
52
CLK/GATE
53
CAPTURE
54
PWM
Tacho
IRF521
1 pulse/rev
Figure 29: Closed Loop PWM Speed Control Using JN513x Timers
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
39
Jennic
12.2 Tick Timer
The JN513x contains a hardware timer that can be used for generating timing interrupts to software. It may be used
to implement regular events such as ticks for software timers or an operating system, as a high-precision timing
reference or can be used to implement system monitor timeouts as used in a watchdog timer. Features include:
•
32-bit counter
•
28-bit match value
•
Maskable timer interrupt
•
Single-shot, Restartable or Continuous modes of operation
Match Value
Match
Tick Timer
Interrupt
SysClk
Counter
Reset
Int
Enable
Run
Mode
Control
Mode
Figure 30: Tick Timer
The Tick Timer is clocked from the CPU clock (16 or 32MHz), which is fed to a 32-bit wide resettable up-counter,
gated by a signal from the mode control block. A match register allows comparison between the counter and a
programmed value. The match value, measured in 16 or 32MHz clock cycles can be programmed using
vAHI_TickTimerInterval(), in the range 0 to 0x0FFFFFFF. The output of the comparison can be used to
generate an interrupt if the interrupt is enabled and used in controlling the counter in the different modes. The mode
is programmed using vAHI_TickTimerConfigure(), which also resets the counter to zero.
The interrupt is enabled by vAHI_TickTimerIntEnable(). The interrupt state is returned by
bAHI_TickTimerIntStatus() and if an interrupt is generated it can be cleared by
vAHI_TickTimerIntPndClr().
If the mode is programmed as single shot, the counter begins to count from zero until the match value is reached.
The match signal will be generated which will cause an interrupt if enabled, and the counter will stop counting. The
counter can be restarted by reprogramming the mode using vAHI_TickTimerConfigure().
If the mode is programmed as restartable, the operation of the counter is the same as for the single shot mode,
except that when the match value is reached the counter is reset and begins counting from zero. An interrupt will be
generated when the match value is reached if it is enabled.
Continuous mode operation is similar to restartable, except that when the match value is reached, the counter is not
reset but continues to count. An interrupt will be generated when the match value is reached if enabled.
40
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
12.3 Wakeup Timers
Two 32-bit wakeup timers are available in the JN513x driven from the 32kHz internal clock. They may run during
sleep periods when the majority of the rest of the device is powered down, to time sleep periods or other long period
timings that may be required by the application. The wakeup timers do not run during deep sleep and may optionally
be disabled in sleep mode through software control. When a wakeup timer expires it typically generates an interrupt,
if the device is asleep then the interrupt may be used as an event to end the sleep period. See Section 16 for further
details on how they are used during sleep periods. Features include:
•
32-bit down-counter
•
Optionally runs during sleep periods
•
Clocked from 32 kHz RC oscillator
A wakeup timer consists of a 32-bit down counter clocked from the 32 kHz internal clock. An interrupt or wakeup
event can be generated when the counter reaches zero. On reaching zero the counter will continue to count down
until stopped, which allows the latency in responding to the interrupt to be measured. If an interrupt or wakeup event
is required, the timer interrupt should be enabled using vAHI_WakeTimerEnable() before loading the count value
for the period. The count value is loaded using vAHI_WakeTimerStart() and causes the counter to begin to
count down to zero; the counter can be stopped at any time using vAHI_WakeTimerStop(). The counter will
remain at the value it contained when the timer was stopped and no interrupt will be generated. The status of the
timers can be checked using the u8AHI_WakeTimerStatus() function, which indicates if the timers are running.
The timers can be checked to see if they have expired using u8AHI_WakeTimerFiredStatus() which is useful
when the timer interrupts are masked. If a timer has expired then the fired status will be reset by the function.
12.3.1 RC Oscillator Calibration
The RC oscillator used to time sleep periods is designed to require very little power to operate and be self-contained,
requiring no external timing components and hence is lower cost. As a consequence of using on-chip resistors and
capacitors, the inherent absolute accuracy and temperature coefficient is lower than that of a crystal oscillator, but
once calibrated the accuracy approaches that of a crystal oscillator. Sleep time periods should be as close to the
desired time as possible in order to allow the device to wake up in time for important events, for example beacon
transmissions in the IEEE802.15.4 protocol. If the sleep time is accurate, the device can be programmed to wake up
very close to the calculated time of the event and so keep current consumption to a minimum. If the sleep time
is less accurate, it will be necessary to wake up earlier in order to be certain the event will be captured. If the device
wakes earlier, it will be awake for longer and so reduce battery life.
In order to allow sleep time periods to be as close to the desired length as possible, the true frequency of the RC
oscillator needs to be determined to better than the initial 30% accuracy. The calibration factor can then be used to
calculate the true number of nominal 32kHz periods needed to make up a particular sleep time. A calibration
reference timer, clocked from the crystal oscillator, is provided to allow comparisons to be made between the RC
clock and the 16MHz crystal oscillator when the JN513x is awake. Operation is as follows:
•
Wakeup timer0 is disabled and programmed with a number of 32kHz ticks
•
Calibration mode is enabled which causes the Calibration Reference counter to be zeroed. Both counters
start counting, the wakeup timer decrementing and the calibration counter incrementing
•
When the wakeup timer reaches zero the Reference Counter is stopped, allowing software to read the
number of 16MHz clock ticks generated during the time represented by the number of 32kHz ticks
programmed in the wakeup timer. The true period of the 32kHz clock can thus be determined and used
when programming a wakeup timer to achieve a better accuracy and hence more accurate sleep periods
The RC oscillator has a good temperature coefficient for an oscillator of its class (see section 17.3.5) however this
should be taken into account for any given application, when planning the wake up events and the time interval
between calibrations.
A calibration can be performed by calling u32AHI_WakeTimerCalibrate(), which calibrates over twenty 32kHz
ticks and returns the number of 16MHz ticks recorded. For a RC oscillator running at exactly 32kHz the value
returned should be 10000. If the oscillator is running faster than 32kHz the count will be less than 10000, if running
slower the value will be higher. For a calibration count of 9000, indicating that the RC oscillator period is running at
approximately 35kHz, to time for a period of 2 seconds the timer should be loaded with 71,112 ((10000/9000) *
(32000*2)) rather than 64000.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
41
Jennic
12.3.2 External 32kHz Clock Source
It is possible to change the source of 32kHz clock used for the sleep timers, to an externally supplied 32kHz
reference clock on the CLK32K input (DIO9). This mode could allow the timer clock to be sourced from a very stable
oscillator model, allowing more accurate sleep cycle timings.
42
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
13 Serial Communications
The JN513x has two independent Universal Asynchronous Receiver / Transmitter (UART) serial communication
interfaces. These provide similar operating features to the industry standard 16550A device operating in FIFO mode.
Each interface performs serial-to-parallel conversion on incoming serial data and parallel-to-serial conversion on
outgoing data from the CPU to external devices. In both directions, a 16-byte deep FIFO buffer allows the CPU to
read and write multiple characters on each transaction. This means that the CPU is freed from handling data on a
character-by-character basis, with the associated high processor overhead. The UARTs have the following features:
•
Emulates behaviour of industry standard NS16450 and NS16550 UARTs
•
16 byte transmit and receive FIFO buffers reduce interrupts to CPU, with direct access to fill levels of each
•
Adds / deletes standard start, stop and parity communication bits to or from the serial data
•
Independently controlled transmit, receive, status and data sent interrupts
•
Optional modem flow control signals CTS and RTS
•
Fully programmable data formats: baud rate, start, stop and parity settings
•
False start bit detection
•
Internal diagnostic capabilities: loop-back controls for communications link fault isolation
•
Flow control by software or automatically by hardware
Divisor
Latch
Register
Interrupt
ID
Register
Internal
Interrupt
Interrupt
Logic
Line
Status
Register
Processor Bus
Interrupt
Enable
Register
RTS
CTS
Modem
Signals
Logic
Baud Generator
Logic
Line
Control
Register
Receiver
Logic
Receiver FIFO
Modem
Status
Register
Modem
Control
Register
FIFO
Control
Register
Receiver Shift
Register
RXD
Transmitter
Logic
Transmitter FIFO
Transmitter Shift
Register
TXD
Figure 31 UART Block Diagram
The serial interface characteristics are programmed using the peripheral library call vAHI_UartSetControl(). This
sets the number of data bits (5, 6,7 or 8), even, odd, set-at-1, set-at-0 or no-parity detection and generation and
single or multiple stop bit generation (for 5 bit data, multiple is 1.5 stop bits; for 6, 7 or 8 data bits, multiple is 2 bits).
The baud rate is programmable between 4800, 9600, 19.2k, 38.4k, 76.8k and 115.2 kbaud via the
vAHI_UartSetClockDivisor() function. For higher or non-standard baud rates, the registers of the UART may
be accessed directly to achieve the desired programming.
Two hardware flow control signals are provided: Clear-To-Send (CTS) and Request-To-Send (RTS). CTS is an
indication sent by an external device to the UART that it is ready to receive data. RTS is an indication sent by the
UART to the external device that it is ready to receive data. Both signals are active low. RTS is controlled from
software using the vAHI_UartSetControl() function, while the value of CTS can be read using
u8AHI_UartReadModemStatus(). The result of this routine also indicates if the state of CTS has changed,
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
43
Jennic
indicating that the connected device has signalled the UART that it can begin transmitting. Monitoring and control of
CTS and RTS is a software activity, normally performed as part of interrupt processing. The signals do not control
parts of the UART hardware, but simply indicate to software the state of the UART external interface. Alternatively,
the software can set the Automatic Flow Control mode where the hardware controls the value of the generated RTS
(negated if the receive FIFO fill level is 15 and another character starts to be received, and asserted when the receive
FIFO is read), and only transmits data when the incoming CTS is asserted.
Characters are read one byte at a time from the Receive FIFO using the u8AHI_UartReadData() routine and are
written to the Transmit FIFO using vAHI_UartWriteData(). The Transmit and Receive FIFOs can be cleared and
reset independently of each other using vAHI_UartReset(). The status of the transmitter can be checked using
u8AHI_UartReadLineStatus(), which indicates if the transmit FIFO is empty, and if there is a character being
transmitted. The status of the receiver is also checked using this call, which can indicate if conditions such as parity
error, framing error or break indication have occurred. It also shows if an overrun error occurred (receive buffer full
and another character arrives) and if there is data held in the receive FIFO.
UART 0 signals CTS, RTS, TXD and RXD are alternate functions of pins DIO4, 5, 6 and 7 respectively and UART 1
signals CTS, RTS, TXD and RXD are alternate functions of pins DIO17, 18, 19 and 20 respectively. If CTS and RTS
are not required on the devices external pins, then they may be disabled through software control, this allows the
alternate DIOx to be used instead
13.1 Interrupts
Interrupt generation is controlled for the UART block using the vAHI_UartSetInterrupt() routine, and are
divided into four categories:
•
Received Data Available: Is set when data in the Rx FIFO queue reaches a particular level (the trigger level can
be configured as 1, 4, 8 or 14) or if no character has been received for 4 character times.
•
Transmit FIFO Empty: Is set when the last character from the TX FIFO is read and starts to be transmitted.
•
Receiver Line Status: Is set when one of the following occur (1) Parity Error - the character at the head of the
receive FIFO has been received with a parity error, (2) Overrun Error - the FIFO is full and another character
has been received at the Receiver shift register, (3) Framing Error - the character at the head of the receive
FIFO does not have a valid stop bit and (4) Break Interrupt – occurs when the RxD line has been held low for an
entire character. The source of the interrupt is determined using u8AHI_UartReadLineStatus()
•
Modem Status: Generated when the CTS (Clear To Send) input control line changes.
13.2 UART Application
The following example shows the UART connected to a 9-pin connector compatible with a PC. The software
developer kit uses such an interface as the debugger interface between the JN513x and a PC. As the JN513x device
pins do not provide the RS232 line voltage a level shifter is used.
44
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
PC COM Port
JN513x
47
UART0
45
46
RXD
RTS
RS232
Level
Shifter
TXD
CTS
44
Pin
Signal
CD
RD
TD
DTR
SG
DSR
RTS
CTS
RI
Figure 32 JN513x Serial Communication Link
13.3 Programming Example
The following code shows the peripheral library calls to configure UART0 and output the message ‘Hello World’
Programming Example
/* Set up uart0 */
vAHI_UartEnable(E_AHI_UART_0);
/* set baud rate */
vAHI_UartSetClockDivisor(0, E_AHI_UART_RATE_38400);
/* set parity, start bits, number data bits */
vAHI_UartSetControl(E_AHI_UART_0,
E_AHI_UART_EVEN_PARITY,
E_AHI_UART_PARITY_DISABLE,
E_AHI_UART_WORD_LEN_8,
E_AHI_UART_1_STOP_BIT,
E_AHI_UART_RTS_HIGH);
/* output message */
char acstring[] = “Hello World”;
char *pcstring = acstring;
while (*pcstring)
vAHI_UartWriteData(E_AHI_UART_0, *pcstring);
pcstring++;
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
45
Jennic
14 Two-Wire Serial interface
The JN513x includes an industry standard two-wire synchronous serial interface (SIF) that provides a simple and
efficient method of data exchange between devices. The system uses a serial data line (SIF_D) and a serial clock
line (SIF_CLK) to perform bi-directional data transfers and includes the following features:
•
Compatible with both I2C and SMbus peripherals
•
Multi-master operation
•
Software programmable clock frequency
•
Clock stretching and wait state generation
•
Software programmable acknowledge bit
•
Interrupt or bit-polling driven byte-by-byte data-transfers
•
Bus busy detection
•
Support for 7 and 10 bit addressing modes
Prescale
Register
Clock
Generator
Command
Register
SIF_CLK
Processor Bus
Byte
Command
Controller
Bit
Command
Controller
SIF_D
Status
Register
Transmit
Register
Data I/O
Shift
Register
Receive
Register
Figure 33: SIF Block Diagram
The prescale register, set using the vAHI_SiConfigure() function, allows the interface to be configured to operate
at up to 400kbit/s. The clock generator handles the clock stretching required by some slave devices.
The Byte Command Controller handles traffic at the byte level. It takes data from the Command Register and
translates it into sequences based on the transmission of a single byte. By setting the start, stop, read, write and
acknowledge control bits in the command register using the vAHI_SiSetCmdReg() function it is possible to
generate read or write sequences on the bus.
The data I/O shift register contains the data associated with the current transfer. During a read operation, data is
shifted into this register from the SIF_D line. When the read is complete the byte is copied into the receive register
and can be accessed using the u8AHI_SiReadData8() function.
During a write operation the contents of the transmit register are copied into the shift register and then onto the SIF_D
line. The transmit register can be accessed using the vAHI_SiWriteData8() function. It is possible to generate
an interrupt upon the completion of a byte transmission or reception. If required this interrupt can be enabled by
using the vAHI_SiConfigure() function.
46
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
If interrupt-driven communication is not desired it is possible to poll the status of the interface by using the
bAHI_SiPollBusy() and bAHI_SiPollTransferInProgress() functions.
The first byte of data transferred by the device after a start bit is the slave address. The JN513x supports both 7-bit
and 10-bit slave addresses by generating either one or two address transfers. Only the slave with a matching
address will respond by returning an acknowledge bit. The slave address to be used is set using the
vAHI_SiWriteSlaveAddr() function.
The SIF signals SIF_CLK, SIF_D are alternate functions of pins DIO14 and 15 respectively.
14.1 Connecting Devices
The clock and data lines, SIF_D and SIF_CLK, are alternate functions of DIO lines 14 and 15 respectively. The serial
interface function of these pins is selected when the interface is enabled using the vAHI_SiConfigure() function.
They are both bi-directional lines, connected internally to the positive supply voltage via weak (45kΩ) programmable
pull-up resistors. However, it is recommended that external 4.7kΩ pull-ups be used for reliable operation at high bus
speeds, as shown in Figure 34. When the bus is free, both lines are HIGH. The output stages of devices connected
to the bus must have an open-drain or open-collector in order to perform the wired-AND function. The number of
devices connected to the bus is solely dependent on the bus capacitance limit of 400pF.
Vdd
JN513x
RP
55
SIF
RP
Pullup
Resistors
SIF_CLK
SIF_D
56
D1_IN
D1_OUT
CLK1_IN
D2_IN
CLK2_IN
CLK1_OUT
D2_OUT
CLK2_OUT
DEVICE 1
DEVICE 2
Figure 34: Connection Details
14.2 Multi-Master Operation
The interface provides a true multi-master bus including collision detection and arbitration that prevents data
corruption. If two or more masters simultaneously try to control the bus, a clock synchronization procedure
determines the bus clock. Because of the wired-AND connection of the interface, a high-to-low transition on the bus
affects all connected devices. This means a high-to-low transition on the SIF_CLK line causes all concerned devices
to count off their low period. Once a devices clock input has gone low, it will hold the SIF_CLK line in that state until
the clock high state is reached. Due to the wired-AND connection, the SIF_CLK line will therefore be held low by the
device with the longest low period, and held high by the device with the shortest high period.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
47
Jennic
Start counting
low period
Start counting
high period
Wait
State
SIF_CLK1
Master1 SIF_CLK
SIF_CLK2
Master2 SIF_CLK
SIF_CLK
Wired-AND SIF_CLK
Figure 35: Multi-Master Clock Synchronization
14.3 Clock Stretching
Slave devices can use clock stretching to slow down the transfer bit rate. After the master has driven SIF_CLK low,
the slave can drive SIF_CLK low for the required period and then release it. If the slave’s SIF_CLK low period is
greater than the master’s low period the resulting SIF_CLK bus signal low period is stretched thus inserting wait
states.
Clock held low
by Slave
SIF_CLK
Master SIF_CLK
SIF_CLK
Slave SIF_CLK
SIF_CLK
Wired-AND SIF_CLK
Figure 36: Clock Stretching
14.4 Programming Example
The two-wire serial interface protocol is implemented by a combination of hardware and software. Normally, a
standard communication cycle consists of four parts:
•
Start signal generation
•
Slave address transfer
•
Data transfer
•
Stop signal generation
The hardware API supports several calls to support the protocol on the interface. All bit-level timing is implemented
by dedicated hardware within the JN513x. The following code example shows how to read a set of values for a slave
device into a buffer. A typical application would be data logging from a sensor.
Note that bAHI_SiPollTransferInProgress() function is used to block execution until a byte has been
transferred. Higher performance applications should use interrupts to detect end of transfer, running the two-wire
interface as a background task outside the main program thread.
The waveforms below illustrate the operation of the bSIFRead() function listed on the following page.
Repeated x u32Length
Slave Address Transfer
Slave Data Transfer
SIF_CLK
SIF_D
7-bit address 0x4E
Rd
Ack
D7
D6
D5
D4
D3
D2
D1
D0
NAck P
Figure 37: Read From Slave Device
48
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
Programming Example
PRIVATE bool_t bSIFRead(uint8 u8SlaveAddress, uint8 *pau8ReadBuffer, uint32
u32Length)
int i;
for (i=0; i45
dB
Spurious emissions
(RX)
-57
-47
Intermodulation
protection
RSSI linearity
40
-3
+3
dBm
30MHz to 1GHz
1GHz to 12GHz
dB
For 1% PER at with wanted signal
3dB above sensitivity. Modulated
Interferers at 2 & 4 channel
separation
dB
-95 to -10dBm.
Available through Hardware API
Transmitter Characteristics
Transmit power
0.5
dBm
Transmit power (boost)
+2.5
dBm
Output power control
range
-30
dB
Spurious emissions
(TX)
-36
-43
dBm
-47
EVM
15
25
Transmit Power
Spectral Density
-48
-20
dBc
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Nominal
in 5 6dB steps
30MHz to 1GHz,
1GHz to12.5GHz,
The following exceptions apply
1.8 to 1.9GHz & 5.15 to 5.3GHz
At maximum output power
At greater than 3.5MHz offset, as
per 802.15.4, section 6.5.3.1
67
Jennic
17.3.12.2 Radio parameters: 2.2-3.6V, -40ºC
Parameter
Min
Typical
Max
Unit
Notes
Receiver Characteristics
Receive sensitivity
-97
Maximum input signal
Adjacent channel
rejection
-1 channel / +1 channel
dBm
Nominal for 1% PER, as per
802.15.4 section 6.5.3.3
dBm
For 1% PER, measured as
sensitivity
31 / 35
dB
For 1% PER with wanted signal
3dB above sensitivity, as per
802.15.4 section 6.5.3.4
Alternate channel
rejection
41
dB
For 1% PER with wanted signal
3dB above sensitivity, as per
802.15.4 section 6.5.3.4
Other in band rejection
45
dB
2.4 to 2.4835 GHz, excluding
adjacent channels
For 1% PER with wanted signal
3dB above sensitivity, measured
as per 802.15.4 section 6.5.3.4
Out of band rejection
TBA
Spurious emissions
(RX)
-57
-47
Intermodulation
protection
RSSI linearity
35
-3
+3
dBm
30MHz to 1GHz
1 to 12GHz
dB
For 1% PER at with wanted signal
3dB above sensitivity. Modulated
Interferers at 2 & 4 channel
separation
dB
-95 to -10dBm.
Available through Hardware API
Transmitter Characteristics
Transmit power
1.8
dBm
Transmit power (boost)
+3.0
dBm
Output power control
range
-30
dB
Spurious emissions
(TX)
-36
-43
dBm
-47
68
EVM
20
25
Transmit Power
Spectral Density
-50
-20
dBc
JN-DS-JN513x v1.4
Preliminary
Nominal
in 5 6dB steps
30MHz to 1GHz,
1GHz to12.5GHz,
The following exceptions apply
1.8 to 1.9GHz &
5.15 to 5.3GHz
At maximum output power
At greater than 3.5MHz offset, as
per 802.15.4, section 6.5.3.1
© Jennic 2007
Jennic
17.3.12.3 Radio parameters: 2.2-3.6V, +85ºC
Parameter
Min
Typical
Max
Unit
Notes
Receiver Characteristics
Receive sensitivity
-92
Maximum input signal
Adjacent channel
rejection
-1 channel / +1 channel
dBm
Nominal for 1% PER, as per
802.15.4 section 6.5.3.3
dBm
For 1% PER, measured as
sensitivity
27 / 35
dB
For 1% PER with wanted signal
3dB above sensitivity, as per
802.15.4 section 6.5.3.4
Alternate channel
rejection
41
dB
For 1% PER with wanted signal
3dB above sensitivity, as per
802.15.4 section 6.5.3.4
Other in band rejection
43
dB
2.4 to 2.4835 GHz, excluding
adjacent channels
For 1% PER with wanted signal
3dB above sensitivity, measured
as per 802.15.4 section 6.5.3.4
Out of band rejection
TBA
Spurious emissions
(RX)
-57
-47
Intermodulation
protection
RSSI linearity
35
-3
+3
dBm
30MHz to 1GHz
1GHz to 12GHz
dB
For 1% PER at with wanted
signal 3dB above sensitivity.
Modulated Interferers at 2 & 4
channel separation
dB
-95 to -10dBm.
Available through Hardware API
Transmitter Characteristics
Transmit power
Transmit power (boost)
Output power control
range
-3.0
dBm
dBm
-30
dB
Spurious emissions
(TX)
-36
-43
dBm
-47
EVM
12
25
Transmit Power
Spectral Density
-46
-20
dBc
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
Nominal
in 5 steps of 6dB
30MHz to 1GHz,
1GHz to12.5GHz,
The following exceptions apply
1.8 to 1.9GHz &
5.15 to 5.3GHz
At maximum output power
At greater than 3.5MHz offset, as
per 802.15.4, section 6.5.3.1
69
Jennic
Appendix A Mechanical and Ordering Information
A.1 56pin QFN Package Drawing
Controlling Dimension: mm
Symbol
A1
A2
A3
D1
D2
E1
E2
υ1
millimetres
Min.
-----0.00
-----0.2
6.20
6.20
0.30
0°
0.09
Nom.
-----0.01
0.65
0.20 Ref.
Max.
0.9
0.05
0.7
0.25
0.3
8.00 bsc
7.75 bsc
6.40
8.00 bsc
7.75 bsc
6.40
0.40
0.50 bsc
-----------
6.60
6.60
0.50
12°
------
Tolerances of Form and Position
aaa
bbb
ccc
70
JN-DS-JN513x v1.4
Preliminary
0.10
0.10
0.05
© Jennic 2007
Jennic
A.2 PCB Decal
The following PCB decal is recommended; all dimensions are in millimetres (mm).
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
71
Jennic
A.3 Ordering Information
Ordering Format:
JN513x - XXX - Y1Y2Y3
Part Numbers:
XXX:
Y1:
JN5131
Wireless microcontroller - 8kB RAM
JN5132
Wireless microcontroller - 16kB RAM
JN5133
Wireless microcontroller - 32kB RAM
JN5139
Wireless microcontroller - 96kB RAM
ROM Variant:
001
IEEE802.15.4 stack
Z01
ZigBee stack
Package Variant:
Y2:
Temperature Range / Device Status:
Y3:
Punched 56 lead, 0.5mm pitch 8x8mm Quad Flat No Leads (QFN)
-40°C to +85°C - Industrial Temperature Range
Shipping:
Trays (up to 260 devices)
Tape mounted 2500 devices on a 13” reel
Tape mounted 1000 devices on a 7” reel
Tape mounted 500 devices on a 7” reel
Tape mounted upto 100 devices (no reel)
Ordering Examples:
72
Part Number
Description
JN5131-001-AIR
JN5131 IEEE802.15.4 Wireless Microcontroller – up to 260 devices in a tray
JN5133-Z01-AIV
JN5133 ZigBee Wireless Microcontroller - 1000 devices on a 7” reel
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
A.4 Device Package Marking
The diagram below shows the package markings for JN513x devices. The package on the left along with the legend
information below it, shows the general format of package marking. The package on the right shows the specific
markings for a JN5139-Z01 device, that came from assembly build number 1000004 and was manufactured week 4
of 2007.
Jennic
Jennic
JNXXXX-SSS
JN5139-Z01
FFFFFFF
YYWW
1000004
0704
Legend:
JN
Jennic
XXXX
4 digit part number, for example 5139, 5132
SSS
3 digit software ROM identifier
FFFFFFF
7 digit assembly build number
YY
2 digit year number
WW
2 digit week number
Where this Data Sheet is denoted as “Advanced” or “Preliminary”, devices will be either Engineering or Prototype
Samples. Devices of this status have an R suffix after the software ROM identifier, for example JN5139-Z01R.
Devices may also have an additional digit immediately after the R suffix, for example R1, R2, R3 etc. This additional
digit is use to identify different revisions of engineering or prototype silicon during these product phases.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
73
Jennic
A.5 Tape and Reel Information
A.5.1 Tape Orientation and Dimensions
The general orientation of the 56QFN package in the tape is as shown in Figure 42.
Figure 44: Tape and Reel orientation
Figure 43 shows the detailed dimensions of the tape used for 8x8mm 56QFN devices.
Reference
Ao
Bo
Ko
Dimensions (mm)
8.30 ±0.10
8.30 ±0.10
1.10 ±0.10
12.00 ±0.10
0.30 ±0.10
16.00 +0.30/-0.10
Figure 45: Tape Dimensions
74
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
A.5.2 Reel Information: 7” Reel
Surface Resistivity
Between 10e9 – 10e11 Ohms Square
Material
High Impact Polystyrene, environmentally friendly, recyclable
All dimensions and tolerances are fully compliant with EIA-481-B and are specified in millimetres.
6 window design with one window on each side blanked to allow adequate labelling space.
Tape Width
B (min)
W (min)
W (max)
16
180
1.5min
13 ±0.2
60 +0.1 –0.0
16.40
17.90
Figure 46: Reel Dimensions
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
75
Jennic
A.5.3 Reel Information: 13” Reel
Surface Resistivity
Between 10e9 – 10e11 Ohms Square
Material
High Impact Polystyrene with Antistatic Additive
All dimensions and tolerances are fully compliant with EIA-481-B and are specified in millimetres.
3 window design to allow adequate labelling space.
Tape Width
B (min)
D (min)
N (min)
W (min)
W (max)
16
330
1.5
13 +0.5 -0.2
20.2
100
15.90
19.40
Figure 47: Reel Dimensions
A.5.4 Dry Pack Requirement for Moisture Sensitive Material
Moisture sensitive material, as classified by JEDEC standard J-STD-033, must be dry packed. The 56 lead QFN
package is MSL2A/260°C, and is dried before sealing in a moisture barrier bag (MBB) with desiccant bag weighing at
67.5 grams of activated clay and a 6 spot humidity indicator card (HIC) meeting MIL-L-8835 specification. The MBB
has a moisture-sensitivity caution label to indicate the moisture-sensitive classification of the enclosed devices.
76
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
A.6 PCB Design and Reflow Profile
PCB and land pattern designs are key to board level reliability, and Jennic strongly recommends that users follow the
design rules listed in IPC-SM-782. For reflow profiles, it is recommended to follow the reflow profile in Figure 48 as a
guide, as well as the paste manufacturers guidelines on peak flow temperature, soak times, time above liquidus and
ramp rates.
Figure 48: Reflow Profile
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
77
Jennic
Appendix B Development Support
B.1 Crystal Oscillator
16MHz Crystal Requirements
Parameter
Min
Typ
Crystal Frequency
Max
Notes
16MHz
Crystal Tolerance
40ppm
Crystal ESR (Rm) 1
20Ω
60Ω
Crystal Load Capacitance (CL)
9pF
External Capacitors (C1 & C2)
15pF
Including temperature
and aging
See below for more
details
See below for more
details
Total external
capacitance needs to be
2*CL. , allowing for stray
capacitance from chip,
package and PCB
B.1.1 Crystal Equivalent Circuit
Cs
Rm
Lm
C1
Where
Cm
C2
Cm is the motional capacitance
Lm is the motional inductance. This together with Cm defines the oscillation frequency (series)
Rm is the equivalent series resistance ( ESR ).
CS
78
is the shunt or package capacitance and this is a parasitic
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
B.1.2 Crystal Load Capacitance
The crystal load capacitance is the total capacitance seen at the crystal pins, from all sources. As the load
capacitance (CL) affects the oscillation frequency by a process known as ‘pulling’, crystal manufacturers specify the
frequency for a given load capacitance only. A typical pulling coefficient is 15ppm/pF, to put this into context the
maximum frequency error in the IEEE802.15.4 specification is +/-40ppm for the transmitted signal. Therefore, it is
important for resonance at 16MHz exactly, that the specified load capacitance is provided.
The load capacitance can be calculated using:
CL
CT 1 × C T 2
CT 1 + C T 2
CT 1 = C1 + C1P + C1in
Total capacitance
C1 is the capacitor component
C1P is the PCB parasitic capacitance. With the recommended layout this is about 1.6pF
C1in is the on-chip parasitic capacitance and is about 1.4pF typically.
Similarly for CT 2
Where
Hence for a 9pF load capacitance, and a tight layout the external capacitors should be 15pF
B.1.3 Crystal ESR and Required Transconductance
The resistor in the crystal equivalent circuit represents the energy lost. To maintain oscillation, power must be
supplied by the amplifier, but how much? Firstly, the Pi connected capacitors C1 and C2 with CS from the crystal,
apply an impedance transformation to Rm, when viewed from the amplifier. This new value is given by:
⎞
⎛
Rˆ m = Rm⎜⎜ CS +CL ⎟⎟
CL ⎠
⎝
The amplifier is a transconductance amplifier, which takes a voltage and produces an output current. The amplifier
together with the capacitors C1 and C2, form a circuit, which provides a negative resistance, when viewed from the
crystal. The value of which is given by:
RNEG =
Where
gm
CT 1 × CT 2 × ω 2
gm is the transconductance
ω is the frequency in rad/s
Derivations of these formulas can be easily found in textbooks.
In order to give quick and reliable oscillator start-up, a common rule of thumb is to set the amplifier negative
resistance to be a minimum of 4 times the effective crystal resistance. This gives
gm
CT 1 × CT 2 × ω 2
© Jennic 2007
CS +CL ⎞⎟
≥ 4R
CL ⎟⎠
⎛
m ⎜⎜
⎝
JN-DS-JN513x v1.4
Preliminary
79
Jennic
This can be used to give an equation for the required transconductance.
gm ≥
4 Rm×ω 2[CS (CT 1+CT 2)+CT 1×CT 2]2
CT 1×CT 2
Example: Using typical parameters of Rm =40Ω, CS =1pF and CT 1 = CT 2 =18pF ( for a load capacitance of 9pF), the
equation above gives the required transconductance ( gm ) as 647uA/V. The JN513x has a typical value for
transconductance of 1.25mA/V
The example and equation illustrate the trade-off that exists between the load capacitance and crystal ESR. For
example, a crystal with a higher load capacitance can be used, but the value of max. ESR that can be tolerated is
reduced. Also note, that the circuit sensitivity to external capacitance [ C1 , C2 ] is a square law.
Below is measurement data showing the variation of the crystal oscillator amplifier transconductance with
temperature and supply voltage, notice how small the variation is. Circuit techniques have been used to apply
compensation, such that the user need only design for nominal conditions.
Transconductance (mA/V)
Crystal Oscillator Transconductance Versus Temperature
(VDD=3V)
1.285
1.28
1.275
1.27
1.265
1.26
1.255
1.25
1.245
-40
-20
20
40
60
80
100
Temperature (C)
Transconductance (mA/V)
Crystal Oscillator Transconductance Versus Supply Voltage
(Temp=25C)
1.32
1.3
1.28
1.26
1.24
1.22
1.2
2.2
2.4
2.6
2.8
3.0
3.2
3.4
3.6
Supply Voltage (VDD)
80
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
B.2 16MHz Oscillator
The JN513x contains the necessary on-chip components to build a 16 MHz reference oscillator with the addition of an
external crystal resonator and two tuning capacitors. The schematic of these components are shown in Figure 49.
The two capacitors, C1 and C2, should be 15pF ±5% and use a COG dielectric. For a detailed specification of the
crystal required see Appendix B.1.
JN513x
XTALIN
R1
XTALOUT
C1
C2
Figure 49: Crystal oscillator connections
The clock generated by this oscillator provides the reference for most of the JN513x subsystems, including the
transceiver, processor, memory and digital and analogue peripherals.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
81
Jennic
B.3 Applications Information
B.3.1 Typical Application Schematic
Vcc
Timers
Two Wire
Serial Port
SPISEL4
TXD0
CTS0
RTS0
VDD2
TIM0CK_GT
UART 0
RXD0
TIM0OUT
TIM0CAP
TIM1CK_GT
TIM1CAP
TIM1OUT
UART 1
SIF_CLK
SIF_D
C13
SPI Selects
43
I/O Line
SPISEL3
CTS1
SPISEL2
VB_PROT
VB_MEM
RTS1
C7
VSS1
Jennic
TXD1
RXD1
SPISEL1
SPISEL0
MOSI
VSS2
RESET
VB_APP
RESETN
IC1: JN513x
VSS3
C10
MISO
C15
C11
C5
SPICLK
VSSS
Y1
IC2
Serial
Flash
Memory
C6
XTALOUT
COMP2M
XTALIN
COMP2P
VB_SYN
Vcc
SS
Vcc
SDO
HOLD
WP
CLK
Vss
SDI
DAC2
VCOTUNE
29
DAC1
C2
R9
C3
C1
VB_A
ADC4
ADC3
ADC2
ADC1
VREF
RFM
VB_RF
RFP
VDD1
COMP1P
IBIAS
C8
COMP1M
R4
VB_VCO
15
C9
C4
Vcc
C12
Analogue IO
Printed Antenna
Figure 50: Application Schematic
Components
Values
C1, C2, C3, C4, C5, C6, C7, C12, C13, C15
100nF
C10, C11
15pF (COG)
C9
3n3F
C8
330pF (COG)
R4
4k7Ω
R9
43kΩ
Y1
TSX-10A 16MHz Crystal TN4-25820
IC1
JN513x
IC2
128kB Serial Flash
Table 3: Bill of Materials
82
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
B.3.2 PCB Requirements
Jennic recommend that a standard 4–layer printed circuit board be used for design, with the individual layers
organised as shown below in Figure 51.
Copper (0.5 oz – 17 µm)
Dielectric FR4 pre-preg 0.009” x 1
Copper (0.5 oz – 17 µm)
Dielectric FR4 0.02” x 1
Copper (0.5 oz – 17 µm)
Dielectric FR4 pre-preg 0.009” x 1
Copper (0.5 oz – 17 µm)
Top Metal
Dielectric 1
Mid 1 metal
Dielectric 2
Mid 2 metal
Dielectric 3
Bottom metal
Total
Dim (mm)
0.017
0.2286
0.017
0.508
0.017
0.2286
0.017
Description
0.5 oz copper
Er = TBD
0.5 oz copper
Er = TBD
0.5 oz copper
Er = TBD
0.5 oz copper
1.0332 mm
Dimension
Tolerance
Dimension A
TBD
Dimension B
TBD
Dimension A
TBD
NOT TO SCALE
Figure 51: PCB Cross-Section
From top to bottom, the layers are:
•
Component
•
Ground
•
Digital tracks
•
Power and tracks
The material is standard FR4. While no special measures are required for the board design, it is recommended that
Class 1 tolerances be used.
Note: The Jennic PCB layout assumes the layers defined above. If a different PCB thickness
is used then the RF track thickness and layout will need to be re-assessed.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
83
Jennic
B.3.3 Supply Decoupling
C12 is the decoupling capacitor for the analogue areas of IC1. It is placed as close as possible to the IC1 pin VDD1.
C13 is the decoupling capacitor for the digital areas of IC1. It is also used to decouple the supply on the Flash
memory due to:
•
placement of the Flash memory power pin (IC2 Pin 8) next to the IC1 Pin VDD2
•
the fact that the Flash memory is only used during booting (unless reprogramming), so the RF areas of the
device are not active.
B.3.4 Reference Oscillator Requirements
The device contains the necessary on-chip components to build a 16-MHz reference oscillator with the addition of an
external crystal resonator. The schematic in Figure 50: Application Schematic shows the crystal circuit in the form
of capacitors C10 and C11, together with a crystal resonator Y1.
The reference crystal serves many purposes, including the provision of a reference for the 32-bit RISC processor,
PHY controller, radio synthesiser and analogue peripherals. In addition, the crystal also provides timing references
for external I/O (e.g. on-chip UARTs) and timer counters. Thus, it is important that the crystal reference is specified
and built correctly to ensure that the system functions properly.
The external crystal resonator, Y1, is connected to IC1 via two coupling capacitors, C10 and C11, that 15 pF ±5%
and use a C0G dielectric – the 15 pF will need to vary for alternate crystals. This is important, in order to ensure that
the oscillator Q-factor is maximised and the temperature co-efficient is minimised.
The choice of crystal resonator is important for the following reasons:
•
Resonator tolerance: A number of parameters, ranging from on-chip timings to radio centre-frequency, are
derived directly from the tolerance of the crystal. As indicated in the component list, we recommend that a total
tolerance of less than ±35 ppm is used, as the maximum permissible offset specified in IEEE 802.15.4 is ±40
ppm. Also note that this tolerance should include both temperature and ageing effects imparted on the
resonator.
•
Resonator load capacitance: The active oscillator components on the JN5121 and JN513x series devices are
designed for a crystal resonator with load capacitance of 9 pF. This is a standard loading, and resonators of
this type are widely available.
B.3.5 Reference Oscillator Layout Considerations
The layout of the oscillator circuit is such that the components are close together. This improves the performance of
the oscillator by reducing parasitic impedance and the likelihood of cross-talk.
We also recommend that the symmetry of layout be maximised in order to avoid uneven loading of the crystal
resonator.
B.3.6 VCO Tune Circuit Component Specifications
Jennic wireless microcontroller devices employ an RF Phase Locked Loop (PLL). With respect to the schematic in
Figure 50: Application SchematicError! Reference source not found., the only external components required on
the printed circuit board are two capacitors, C8 and C9, together with the resistor R4.
84
Caution: It is essential that the component values advised here
are followed, since their substitution could lead to failure in the
PLL.
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
B.3.7 VCO Tune Circuit Layout Considerations
The layout of these components is such that all three components are close together, and close to the VCO_TUNE
and VB_VCO pins on the wireless microcontroller IC. This improves the performance of the PLL by reducing parasitic
impedance and the likelihood of cross-talk.
B.3.8 Radio Front-End
The radio part of the wireless microcontroller device has an internal transmit-receive switch connected to the external
pins on the chip (RF- and RF+). The PHY controller configures the switch between transmit and receive. In both
configurations, the connection to the device is a differential 200-ohm configuration. As an example of how this may
be used, the 200-ohm differential antenna connection (RF- and RF+) can be fed to a miniature balun to convert to a
single-ended 50-ohm microstrip line which, in turn, can be connected to a small ceramic antenna.
Note: The PCB layout is very important for all of the external radio
connections and associated power supplies. In this respect, the tolerances
indicated in Figure 51 are particularly important.
B.3.9 Antennae
There are many different antenna configurations that could function for a 2.4-GHz transceiver. The free-space
wavelength at 2.4 GHz is approximately 12 cm, which means that a standard half-wave dipole would be
approximately 6 cm.
When advising on antenna design, it is dangerous to generalise. However, designers of any low-power radio device
must strive to ensure that as little power as possible is wasted in producing a radio signal transmission. This involves
careful consideration of the terms antenna efficiency, antenna directivity and antenna gain:
•
Antenna Efficiency: This is a measure of how much energy fed into the antenna feed is actually retained in the
radio transmission. For example, a small antenna may exhibit an efficiency of approximately 50%, which
means that half the power fed into or out of the antenna is wasted. Clearly, it is important to keep efficiency as
high as possible. However, small antennae exhibit lower efficiency than large antennae.
•
Antenna Directivity: An antenna radiation pattern indicates in which direction the power fed into an antenna
actually radiates. In situations where antennae can be aligned to “see” each other, this can be advantageous.
However, many situations do not allow this, since a path from one device to another may occur in any direction.
In general, larger antennae have a greater ability to radiate in a specific direction. In antenna terminology, this
is called the “directivity”. For instance, an antenna with a directivity of 3 dBi has the ability to radiate twice as
much power in one direction when compared with a theoretical omni-directional antenna. This is fine if both
antennae are aligned in this direction, but it is not good if they are misaligned.
•
Antenna Gain: Often, the term “gain” is used when discussing antennae. This term should be treated with
some caution since it is the product of efficiency and directivity. A poor-efficiency antenna with a high directivity
can still exhibit a reasonable gain; however, power is still being wasted somewhere!
A list of antennae and suppliers can be found in the Application Note Antennae for use with JN51xx (JN-AN-1030),
available on the Jennic web site.
B.3.10 Ground Planes
The recommendation for a four-layer design allows the best use of the ground planes, with this in mind the following
restrictions should be placed on the layout:
•
All RF signals are confined to the top layer.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
85
Jennic
•
The second layer is Ground and has no tracks on it. This allows the best return path for all RF signals and will
reduce noise effects.
•
The bottom layer contains all other signals and the Vcc power supply for the module.
•
The ground planes on all layers stop BEFORE the antenna, so that the performance of the antenna is not
affected. The recommended antenna clearance for a surface-mounted ceramic antenna is shown below.
20
CLEARANCE
(no ground plane)
ANTENNA
CHIP
50 Ω transmission line
20
20
CLEARANCE
(no ground plane)
Dimensions in mm
Figure 52: Antenna Clearance Recommendations
B.3.11 Manufacturing Considerations
The TQFN package must be considered carefully when using reflow solder techniques. The following are
recommendations:
•
The decal is shown in Figure 53. The pad stacks used are 0.25 mm by 1 mm for the smaller pads, and a 6.4mm square pad for the paddle.
Figure 53: Recommended PCB Decal for 56QFN Package
•
86
The solder mask used is shown in Figure 54. The pad stacks used are
0.25 mm by 1 mm for the smaller pads, and two 2-mm square pads to apply paste to the paddle. The solder
paste mask has a thickness of 6 thou (0.152 mm).
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
Figure 54: Recommended Solder Paste Mask for 56QFN Package
•
Nine vias are applied to the paddle. These allow excess solder paste and heated air to be vented away from the
device, preventing the device from being lifted during soldering.
Figure 55: Vias on the Paddle of the 56QFN Package
B.3.12 Bespoke Solutions - PCB Layout Suggestions
The list presented below provides some key suggestions when using a wireless microcontroller on a bespoke, multilayer PCB. Clearly, the list is not exhaustive and you may have more detailed considerations in using mixed-signal
integrated circuits.
•
Shared vias: Often in layout, it is convenient for a number of components to share a return to Analog Ground.
Examples include bypass capacitors and reference setting resistors. We recommend that all components are
given a separate via to ground. This avoids noise feed-through and poor isolation issues that often occur if a
via is shared.
•
Oscillator circuit: We recommend that tracks from the oscillator pins are kept to the same length and, ideally,
on the top layer. This avoids asymmetrical loading of the crystal resonator. The placement of the two capacitors
should be symmetrical to the crystal. This also avoids asymmetrical loading of the reference oscillator.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
87
Jennic
•
VCOTune circuit: The components defined in the schematic should be used in order to set the PLL bandwidth
correctly. It is also essential to keep these components close to the chip, with minimum track lengths.
•
B.3.13 Using a Balun
When using a single ended antenna, the wireless microcontroller will use a balun and should be connected as
indicated in Figure 56.
The tracks between IC1 pins RF+ and RF-, and the balanced side of the balun, are on the top layer. These are
impedance-controlled tracks, designed to provide the 200-ohm differential matched impedance required by the device
at its RF port. With the exception of the via connected to the VB_RF pin, other nearby tracks should be placed such
that there is at least three times the track width of unbroken ground on either side and underneath the tracks.
The other side of the balun should be connected to the antenna. This track is an unbalanced microstrip RF track
operating at 2.4 GHz. It should be impedance controlled to 50 ohms for a good RF input match.
Top View
GND plane to be
cut underneath
differential tracks
To wireless microcontroller
Track widths to
give 200 ohm
differential line
GND
BALUN
Track width
to give 50
ohm line
GND
Figure 56: Connecting the Balun
B.3.14 Decoupling Capacitors
Three capacitors should be used:
•
Two ceramic 100-nF capacitors - one should be placed close to pin VDD1, the other should be placed close to
pin VDD2
•
One 10-µF electrolytic capacitor connected to ground - if the PCB is a module then place this capacitor close to
the point where the power enters the module.
B.3.15 Internal Regulator Smoothing Capacitors
A ceramic 100-nF capacitor should be connected to each of the following pins. Place these capacitors close to the
device and make the tracks as thick as possible to improve RF bypass/decoupling. Some pins require an additional
47-pF capacitor. Details are given below.
88
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
Pin Name
47-pF Capacitor Required
VP_PROT
VB_SYN
VB_VCO
VB_RF
VB_A
VB_APP
VB_MEM
B.3.16 VREF
A ceramic 100-nF capacitor should be placed as close as possible to the VREF pin.
B.3.17 IBIAS
A 43-kΩ resistor should be connected as close as possible to the IBIAS pin.
B.3.18 EMC
For good EMC performance, it is necessary to minimise any ground loops when laying out the PCB.
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
89
Jennic
Appendix C
Related Documents
[1] IEEE Std 802.15.4-2003 IEEE Standard for Information technology – Part 15.4 Wireless Medium Access Control
(MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (LR-WPANs)
[2] JN-RM-2001 Integrated Peripherals API
[3] JN-RM-2002 802.15.4 Stack API
[4] JN-AN-1003 Boot Loader Operation
RoHS Compliance
JN513x devices meet the requirements of Directive 2002/95/EC of the European Parliament and of the
Council on the Restriction of Hazardous Substance (RoHS).
Status Information
The status of this Data Sheet is Preliminary.
Jennic products progress according to the following format:
Advanced
The Data Sheet shows the specification of a product in planning or in development.
The functionality and electrical performance specifications are target values and may be used as a guide to the final
specification. Integrated circuits are identified with an R suffix, for example JN5139-Z01R.
Jennic reserves the right to make changes to the product specification at anytime without notice.
Preliminary
The Data Sheet shows the specification of a product that is in production, but is not yet fully qualified.
The functionality of the product is final. The electrical performance specifications are target values and may used as a
guide to the final specification. Integrated circuits are identified with an R suffix, for example JN5139-Z01R.
Jennic reserves the right to make changes to the product specification at anytime without notice.
Production
This is the final Data Sheet for the product.
All functional and electrical performance specifications, including minimum and maximum values are final.
This Data Sheet supersedes all previous document versions.
Jennic reserves the right to make changes to the product specification at anytime to improve its performance.
90
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007
Jennic
Disclaimers
The contents of this document are subject to change without notice. Jennic reserves the right to make changes,
without notice, in the products, including circuits and/or software, described or contained herein in order to improve
design and/or performance. Information contained in this document regarding device applications and the like is
intended through suggestion only and may be superseded by updates. It is your responsibility to ensure that your
application meets with your specifications.
Jennic warrants performance of its hardware products to the specifications applicable at the time of sale in
accordance with Jennic’s standard warranty. Testing and other quality control techniques are used to the extent
Jennic deems necessary to support this warranty. Except where mandatory by government requirements, testing of
all parameters of each product is not necessarily performed.
Jennic assumes no responsibility or liability for the use of any of these products, conveys no license or title under any
patent, copyright, or mask work right to these products, and makes no representations or warranties that these
products are free from patent, copyright, or mask work infringement, unless otherwise specified.
Jennic products are not intended for use in life support systems, appliances or systems where malfunction of these
products can reasonably be expected to result in personal injury, death or severe property or environmental damage.
Jennic customers using or selling these products for use in such applications do so at their own risk and agree to fully
indemnify Jennic for any damages resulting from such use.
All trademarks are the property of their respective owners.
Version Control
Version
Notes
1.0
22rd December 2006 - First Release
1.1
9th February 2007 – Added solder reflow profile
1.2
16th July 2007 – uplifted to Preliminary status, typical specification updates, internal reset modifications
1.3
31st July 2007 – updates to DC current consumptions
1.4
26th October 2007 – updated applications information, added PCB decal including paddle details
© Jennic 2007
JN-DS-JN513x v1.4
Preliminary
91
Jennic
Contact Details
Corporate Headquarters
Jennic Ltd, Furnival Street
Sheffield S1 4QT, UK
Tel: +44 (0)114 281 2655
Fax: +44 (0) 114 281 2951
info@jennic.com
www.jennic.com
Jennic Ltd Japan
Osakaya building 4F
1-11-8 Higashigotanda Shinagawa-ku
Tokyo 141-0022, Japan
Tel: +81 3 5449 7501
Fax: +81 3 5449 0741
info@jp.jennic.com
www.jennic.com
Jennic Ltd Taiwan
19F-1, 182, Sec.2 Tun Hwa S. Road.
Taipei 106, Taiwan
Tel: +886 2 2735 7357
Fax: +886 2 2739 5687
info@tw.jennic.com
www.jennic.com
Jennic America Inc - West Coast Office
1322 Scott Street, Suite 203
Point Loma, CA 92106, USA
Tel: +619 223 2215
Fax: +619 223 2081
info@us.jennic.com
www.jennic.com
Jennic America Inc - East Coast Office
1060 First Avenue, Suite 400
King of Prussia, PA 19406, USA
Tel: +1 484 868 0222
Fax: +1 484 971 5015
info@us.jennic.com
www.jennic.com
Jennic Ltd Korea
701, 7th Floor, Kunam Bldg.,
831-37, Yeoksam-Dong, Kangnam-ku
Seoul
135-080
Korea
Tel: +82 2 552 5325
Fax: +82 2 3453 8802
info@kr.jennic.com
www.jennic.com
92
JN-DS-JN513x v1.4
Preliminary
© Jennic 2007

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : No
Encryption                      : Standard V2.3 (128-bit)
User Access                     : Print, Copy, Annotate, Fill forms, Extract, Print high-res
Page Mode                       : UseOutlines
XMP Toolkit                     : 3.1-702
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Creator Tool                    : Acrobat PDFMaker 7.0.7 for Word
Modify Date                     : 2007:10:26 15:04:15+01:00
Create Date                     : 2007:10:26 14:59:07+01:00
Metadata Date                   : 2007:10:26 15:04:15+01:00
Format                          : application/pdf
Title                           : JN-DS-JN513x
Creator                         : Jimi Simpson
Document ID                     : uuid:a0f42cab-39be-473c-98f5-673fb8a72128
Instance ID                     : uuid:ff19b07c-e4eb-46f6-8d75-7f7ad7b50a19
Version                         : 1.4
Date 0020completed              : 4th-October-2007
Doc 0020 Ref                    : SP001156
Status                          : Preliminary
Company                         : Jennic
Page Count                      : 92
Page Layout                     : OneColumn
Author                          : Jimi Simpson
Date Completed                  : 4th-October-2007
Doc Ref                         : SP001156

EXIF Metadata provided by EXIF.tools