LPC1113FHN33/303,5 NXP Semiconductors, LPC1113FHN33/303,5 Datasheet - Page 314

• Manufacturer Part Number: LPC1113FHN33/303,5
• Description: ARM Microcontrollers - MCU Cortex-M0 24 kB flash up to 8kB SRAM
• Manufacturer: NXP Semiconductors

Specifications of LPC1113FHN33/303,5

• Rohs: yes
• Core: ARM Cortex M0
• Processor Series: LPC1113
• Data Bus Width: 32 bit
• Maximum Clock Frequency: 50 MHz
• Program Memory Size: 24 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

NXP Semiconductors
UM10398
User manual
17.4.2 CAN initialization
17.4.3 CAN interrupt handler
17.4.4 CAN Rx message object configuration
The CAN controller clock divider, the CAN bit rate is set, and the CAN controller is
initialized based on an array of register values that are passed on via a pointer.
void init_can (uint32_t * can_cfg, uint8_t isr_ena)
The first 32-bit value in the array is applied to the CANCLKDIV register, the second value
is applied to the CAN_BTR register.
The second parameter enables interrupts on the CAN controller level. Set to FALSE for
polled communication.
Example call:
ROM **rom = (ROM **)(0x1fff1ff8 + 2 * sizeof(ROM **));
uint32_t CanApiClkInitTable[2] = {
};
(*rom)->pCANAPI->init_can(&CanApiCanInitTable[0]);
When the user application is active, the interrupt handlers are mapped in the user flash
space. The user application must provide an interrupt handler for the CAN interrupt. In
order to process CAN events and call the callback functions the application must call the
CAN API interrupt handler directly from the interrupt handler routine. The CAN API
interrupt handler takes appropriate action according to the data received and the status
detected on the CAN bus.
void isr (void)
The CAN interrupt handler does not process CANopen messages.
Example call:
(*rom)->pCAND->isr();
For polled communication, the interrupt handler may be called manually as often as
required. The callback functions for receive, transmit, and error will be executed as
described and on the same level the interrupt handler was called from.
The CAN API supports and uses the full CAN model with 32 message objects. Any of the
message objects can be used for receive or transmit of either 11-bit or 29-bit CAN
messages. CAN messages that have their RTR-bit set (remote transmit) are also
supported. For receive objects, a mask pattern for the message identifier allows to receive
ranges of messages, up to receiving all CAN messages on the bus in a single message
object. See also
0x00000000UL, // CANCLKDIV
0x00004DC5UL // CAN_BTR
All information provided in this document is subject to legal disclaimers.
Section
Rev. 12 — 24 September 2012
16.7.3.4.
Chapter 17: LPC11Cxx C_CAN on-chip drivers
UM10398
© NXP B.V. 2012. All rights reserved.
314 of 538