NXP JN516X：2.4GHz无线微控制器，超低功耗与多种应用支持

需积分: 50 33 浏览量更新于2024-07-22 收藏 977KB PDF 举报

NXP的JN516x系列是一款高性能的无线微控制器，专为低功耗住宅自动化、Smart Energy、Light Link和Remote Control应用设计。该微控制器具有以下关键特性： 1. **无线通信能力**：基于IEEE 802.15.4标准，这使得它适用于ZigBee PRO、RF4CE网络协议，确保了与物联网设备的高效通信。其内置的2.4 GHz射频收发器支持高灵敏度接收（-95 dBm）和低发射功率（2.5 dBm），具备时间对齐功能，便于精确的距离测量。 2. **安全特性**：配备了128-bit AES加密处理器，确保数据传输的安全性。MAC加速器提供了高级功能，如自动应答、计时器管理及地址检查，简化了网络管理。 3. **低功耗设计**：具有嵌入式超低功耗睡眠振荡器，工作电流极低，仅需0.6 µA，且在唤醒模式下从IO接口的电流仅为0.12 µA。这显著延长了电池寿命，特别适合电池供电设备。 4. **内存选项**：三种不同的存储器配置可供选择，分别为JN5161（64 kB Flash / 8 kB RAM / 4 kB EEPROM）、JN5164（160 kB Flash / 32 kB RAM / 4 kB EEPROM）和JN5168（256 kB Flash / 32 kB RAM / 4 kB EEPROM），满足不同应用对存储空间的需求。 5. **微控制器核心**：采用32位RISC处理器，支持1到32 MHz的可编程时钟速度，提供变量宽度指令集以提升编码效率。同时，内置的多级指令流水线有助于提高处理性能。 6. **扩展接口**：带有2线式的I2C兼容串行接口，支持主从模式，方便与其他设备通信。此外，还有5个PWM（4个定时器和1个计数器）以及两个低功耗睡眠计数器，提供丰富的外设选项。 7. **其他功能**：内置电池供电的4通道ADC和温度传感器，以及支持大型开关矩阵的电容触摸板，使得这些微控制器能够集成多种传感和控制功能。 NXP JN516x系列微控制器以其强大的无线通信能力、低功耗特性和丰富的外设支持，成为物联网边缘设备的理想选择，广泛应用于需要高效连接、低能耗和多种传感器整合的应用场景。

16 JN-DS-JN516x v1.3 Production © NXP Laboratories UK 2013

4 Memory Organisation

This section describes the different memories found within the JN516x. The device contains Flash, RAM, and

EEPROM memory, the wireless transceiver and peripherals all within the same linear address space.

0xFFFFFFFF

Unpopulated

0xF0008000

RAM

0x04000000

0x02000000

FLASH Boot Code 8K

0x000C0000

0x00000000

0x00080000

Flash & EEPROM Registers

0x01000000

Peripherals

FLASH

Applications

Code

(256KB)

Figure 5: JN5168 Memory Map

4.1 FLASH

The embedded Flash consists of 2 parts: an 8K region used for holding boot code, and a 256K region (JN5168) used

for application code. The sector size of the application code is always 32K, for any size of Flash memory. The

maximum number of write cycles or endurance is, 10k guaranteed and typically 100k, while the data retention is

guaranteed for at least 10 years. The boot code region is pre-programmed by NXP on supplied parts, and contains

code to handle reset, interrupts and other events (see section 7). It also contains a Flash Programming Interface to

allow interaction with the PC-based Flash Programming Utility which allows user code compiled using the supplied

SDK to be programmed into the Application space. For further information, refer to the Flash Programmer User

Guide.[9]. The memory can be erased by a single or multiple sectors and written to in units of 256 bytes, known as

pagewords.

4.2 RAM

The JN516x devices contain up to 32Kbytes of high speed RAM, which can be accessed by the CPU in a single clock

cycle. It is primarily used to hold the CPU Stack together with program variables and data. If necessary, the CPU can

execute code contained within the RAM (although it would normally just execute code directly from the embedded

Flash). 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, allowing a quicker resumption of processing once woken.

4.3 OTP Configuration Memory

The JN516x devices contain a quantity of One Time Programmable (OTP) memory as part of the embedded Flash

(Index Sector). This can be used to securely hold such things as a user 64-bit MAC address and a 128-bit AES

security key. By default the 64-bit MAC address is pre-programmed by NXP on supplied parts; however customers

can use their own MAC address and override the default one. The user MAC address and other data can be written

to the OTP memory using the Flash programmer [9]. Details on how to obtain and install MAC addresses can be

found in the Flash Programmer User Guide. In addition 384bits are available, organised as three 128bit words, for

customer use for storage of configuration or other information.

4.4 EEPROM

The JN516x devices contain 4Kbytes of EEPROM. The maximum number of write cycles or endurance is, 100k

guaranteed and 1M typically while the data retention is guaranteed for at least 20 years. (The Persistent Data

Manager, includes a wear-levelling algorithm which can help to extend the endurance.) This non-volatile memory is

primarily used to hold persistent data generated from such things as the Network Stack software component (e.g.

network topology, routing tables). As the EEPROM holds its contents through sleep and reset events, this means

more stable operation and faster recovery is possible after outages. Access to the EEPROM is via registers mapped

into the Flash and EEPROM Registers region of the address map. The memory can be erased by a single or multiple

pages of 64 bytes. It can be written to in single or multiple bytes up to 64 bytes. The customer may use part of the

EEPROM to store its own data if desired by interfacing with the Persistent Data Manager. Optionally the PDM can

also store data in an external memory. For further information, please read - JenOS User Guide [12].

4.5 External Memory

An optional external serial non-volatile memory (eg Flash or EEPROM) with a SPI interface may be used to provide

additional storage for program code, such as a new code image or further data for the device when external power is

removed. The memory can be connected to the SPI Master interface using select line SPISEL0 (see fig 6 for details)

JN516x

Serial

Memory

SPISEL0

SPIMISO

SPIMOSI

SPICLK

SDO

SDI

CLK

Figure 6: Connecting External Serial Memory

The contents of the external serial memory may be encrypted. 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 the flash memory index section. When bootloading program code from external serial memory, the JN516x

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 transparent. For more details, including the how the program code encrypts

data for the external memory, see the application note Boot Loader Operation. [8]

4.6 Peripherals

All peripherals have their registers mapped into the memory space. Access to these registers requires 3 peripheral

clock cycles. Applications have access to the peripherals through the software libraries that present 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 allow bug-free application code to be developed more rapidly. For details, see

Peripherals API User Guide [4].

4.7 Unused Memory Addresses

Any attempt to access an unpopulated memory area will result in a bus error exception (interrupt) being generated.

18 JN-DS-JN516x v1.3 Production © NXP Laboratories UK 2013

5 System Clocks

Two system clocks are used to drive the on-chip subsystems of the JN516x. The wake-up timers are driven from a

low frequency clock (notionally 32kHz). All other subsystems (transceiver, processor, memory and digital and

analogue peripherals) are driven by a high-speed clock (notionally 32MHz), or a divided-down version of it.

The high-speed clock is either generated by the accurate crystal-controlled oscillator (32MHz) or the less accurate

high-speed RC oscillator ( 27-32MHz calibrated). The low-speed clock is either generated by the accurate crystal-

controlled oscillator (32.768kHz), the less accurate RC oscillator (centered on 32kHz) or can be supplied externally

5.1 High-Speed (32MHz) System Clock

The selected high-speed system clock is used directly by the radio subsystem, whereas a divided-by-two version is

used by the remainder of the transceiver and the digital and analogue peripherals. The direct or divided down version

of the clock is used to drive the processor and memories (32, 16, 8, 4, 2 or 1MHz).

High Speed

RC Oscillator

32MHz Crystal

Oscillator

Div by 1,2,4,8,16 or 32

Div by 2

PERIPHERAL SYSTEM CLOCK

CPU CLOCK

Figure 7 System and CPU Clocks

Crystal oscillators are generally slow to start. Hence to provide a fast start-up following a sleep cycle or reset, the fast

RC oscillator is always used as the initial source for the high-speed system clock. The oscillator starts very quickly

and will run at 25-32MHz (uncalibrated) or 32MHz +/-5% (calibrated). Although this means that the system clock will

be running at an undefined frequency (slightly slower or faster than nominal), this does not prevent the CPU and

Memory subsystems operating normally, so the program code can execute. However, it is not possible to use the

radio or UARTs, as even after calibration (initiated by the user software calling an API function) there is still a +/-5%

tolerance in the clock rate over voltage and temperature. Other digital peripherals can be used (eg SPI Master/Slave),

but care must be taken if using Timers due to the clock frequency inaccuracy.

Further details of the High-Speed RC Oscillator can be found in section 19.3.11.

On wake-up from sleep, the JN516x uses the Fast RC oscillator. It can then either:

• Automatically switch over to use the 32MHz clock source when it has started up.

• Continue to use the fast RC oscillator until software triggers the switch-over to the 32MHz clock source, for

example when the radio is required.

• Continue to use the RC oscillator until the device goes back into one of the sleep modes.

The use of the fast RC Oscillator at wake-up means there is no need to wait for the 32MHz crystal oscillator to

stabilise Consequently, the application code will start executing quickly using the clock from the high-speed RC

oscillator.

5.1.1 32MHz Crystal Oscillator

The JN516x contains the necessary on chip components to build a 32MHz reference oscillator with the addition of an

external crystal resonator and two tuning capacitors. The schematic of these components are shown in Figure 8.

The two capacitors, C1 and C2, should typically be 15pF 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. This oscillator provides the frequency reference for the radio and therefore it is essential that the

reference PCB layout and BOM are carefully followed. The electrical specification of the oscillator can be found in

Section 19.3.11. Please refer to Appendix B for development support with the crystal oscillator circuit. The oscillator

includes a function which flags when the amplitude of oscillation has reached a satisfactory level for full operation,

and this is checked before the source of the high-speed system clock is changed to the 32MHz crystal oscillator

XTALOUT

XTALIN

JN516x

Figure 8: 32MHz Crystal Oscillator Connections

For operation over the extended temperature range, 85 to 125 deg C, special care is required; this is because the

temperature characteristics of crystal resonators are generally in excess of +/-40ppm frequency tolerance defined by

the IEEE802.15.4 standard. The oscillator cell contains additional circuitry to compensate for the poor performance of

the crystal resonators above 100 deg C. Full details, including the software API function, can be found in the

application note JN516x Temperature-dependent Operating Guidelines [2]

5.1.2 High-Speed RC Oscillator

An on-chip High-Speed RC oscillator is provided in addition to the 32MHz crystal oscillator for two purposes, to allow

a fast start-up from reset or sleep and to provide a lower current alternative to the crystal oscillator for non-timing

critical applications. By default the oscillator will run at 27MHz typically with a wide tolerance. It can be calibrated,

using a software API function, which will result in a nominal frequency of 32MHz with a +/-1.6% tolerance at 3v and

25 deg C. However, it should be noted that over the full operating range of voltage and temperature this will increase

to +/-5%. The calibration information is retained through speed cycles and when the oscillator is disabled, so typically

the calibration function only needs to be called once. No external components are required for this oscillator. The

electrical specification of the oscillator can be found in Section 19.3.12.

5.2 Low-speed (32kHz) System Clock

The 32kHz system clock is used for timing the length of a sleep period (see Section 18). The clock can be selected

from one of three sources through the application software:

• 32kHz RC Oscillator

• 32kHz Crystal Oscillator

• 32kHz External Clock

Upon a chip reset or power-up the JN516x defaults to using the internal 32kHz RC Oscillator. If another clock source

is selected then it will remain in use for all 32kHz timing until a chip reset is performed.

5.2.1 32kHz RC Oscillator

The internal 32kHz RC oscillator requires no external components. The internal timing components of the oscillator

have a wide tolerance due to manufacturing process variation and so the oscillator runs nominally at 32kHz -10%

/+40%. To make this useful as a timing source for accurate wakeup from sleep, a frequency calibration factor derived

from the more accurate 16MHz clock may be applied. The calibration factor is derived through software, details can

be found in Section 11.3.1. Software must check that the 32kHz RC oscillator is running before using it. The oscillator

has a default current consumption of around 0.5uA, optionally this can be reduced to 0.375uA, however, the

剩余93页未读，继续阅读

qq_25160869

粉丝: 0
资源: 2

NXP JN516X：2.4GHz无线微控制器，超低功耗与多种应用支持

JN516X中文资料.pdf

JN516X产品简介

NXP TEF668X TEF6686 Full Datasheet 的完整数据手册

NXP Zigbee 3.0开发与JN516x微控制器实战指南

LPC213x系列微控制器用户手册及 datasheet

NXP LPC5411X嵌入式微控制器 datasheet详解

基于NXP JN516x 的 Zigbee 开发套件 -电路方案

数据转换/信号处理中的NXP推出全新小尺寸JN5168无线微控制器

nxp mcu datasheet

NXP mbed微控制器板示例程序_C语言_代码_相关文件_下载

最新资源