LPC1112FHN33/203,5 NXP Semiconductors, LPC1112FHN33/203,5 Datasheet - Page 312

• Manufacturer Part Number: LPC1112FHN33/203,5
• Description: ARM Microcontrollers - MCU Cortex-M0 16kB flash up to 4 kB SRAM
• Manufacturer: NXP Semiconductors

Specifications of LPC1112FHN33/203,5

• Rohs: yes
• Core: ARM Cortex M0
• Processor Series: LPC1112
• Data Bus Width: 32 bit
• Maximum Clock Frequency: 50 MHz
• Program Memory Size: 16 KB
• Data Ram Size: 4 KB
• On-chip Adc: Yes
• Operating Supply Voltage: 1.8 V to 3.6 V
• Operating Temperature Range: - 65 C to + 150 C
• Package / Case: HVQFN-33
• Mounting Style: SMD/SMT
• Factory Pack Quantity: 260

17.1 How to read this chapter
17.2 Features
17.3 General description
UM10398
User manual
17.3.1 Differences to fully-compliant CANopen
The C_CAN block is available in LPC11Cxx parts only (LPC11C00 series).
The on-chip drivers are stored in boot ROM and offer CAN and CANopen initialization and
communication features to user applications via a defined API. The following functions are
included in the API:
In addition to the CAN ISP, the boot ROM provides a CAN and CANopen API to simplify
CAN application development. It covers initialization, configuration, basic CAN
send/receive as well as a CANopen SDO interface. Callback functions are available to
process receive events.
While the bootloader uses the SDO communication protocol and the Object Dictionary
data organization method, it is not a fully CiA 301 standard compliant CANopen node. In
particular, the following features are not available or different to the standard:
•
•
•
•
•
•
•
•
•
•
•
•
UM10398
Chapter 17: LPC11Cxx C_CAN on-chip drivers
Rev. 12 — 24 September 2012
CAN set-up and initialization
CAN send and receive messages
CAN status
CANopen Object Dictionary
CANopen SDO expedited communication
CANopen SDO segmented communication primitives
CANopen SDO fall-back handler
No Network Management (NMT) message processing.
No Heartbeat Message, no entry 0x1017.
Uses proprietary SDO Abort Codes to indicate device errors
“Empty” SDO responses during SDO segmented download/write to the node are
shortened to one data byte, rather than full eight data bytes as the standard
describes. This to speed up the communication.
Entry [1018h,1] Vendor ID reads 0x0000 0000 rather than an official CiA-assigned
unique Vendor ID. This in particular because the chip will be incorporated into designs
of customers who will become the “vendor” of the whole device. The host will have to
use a different method to identify the CAN ISP devices.
All information provided in this document is subject to legal disclaimers.
Rev. 12 — 24 September 2012
© NXP B.V. 2012. All rights reserved.
User manual
312 of 538