DLP-RFS-DK DLP Design, DLP-RFS-DK Datasheet - Page 9

• Manufacturer Part Number: DLP-RFS-DK
• Description: RF Development Tools DLP-RFS1231 development kit
• Manufacturer: DLP Design
• Type: RF Transceiversr

Specifications of DLP-RFS-DK

• Rohs: yes
• Product: Development Kit
• Tool Is For Evaluation Of: DLP-RFS1231
• Frequency: 915 MHz
• Operating Supply Voltage: 2.4 V to 3.6 V
• Dimensions: 1.5 in x 2 in x 1.53 in
• Interface Type: UART
• Maximum Operating Temperature: + 70 C
• Minimum Operating Temperature: 0 C
• For Use With: DLP-RFS1231

(UARTS, SPI) and facilities for implementing callback functions for the higher-level managers. The
design philosophy of this API is to provide the ability to move across the various MCU devices that
Renesas has to offer without significantly changing the high-level managers and application software.
The microcontroller API maintains a data structure called ucPrivateData that stores the addresses for
all Microcontroller API callback functions as well as timer and IO port “shadow” registers (used to
accommodate the fact that IO port control registers on the H8 38076 are write only). For details on
the API function calls, refer to Section 5.0.
4.1.7 UART MANAGER
The UART Manager provides an interrupt-driven, circular-buffered, transmit-and-receive interface for
UART0. The UART Manager API provides functions to configure the UART and to access the
transmit and receive buffers.
The transmit buffer is 255 bytes. To send a byte to the UART, call uartSendByte(). That byte is put
into the transmit buffer, and the transmit interrupt is enabled. The UART0 ISR will then remove that
byte from the transmit buffer and send it to the UART. To send a null-terminated string, call
uartSendString().
The receive buffer is 32 bytes. When the UART0 ISR receives a byte, it puts that byte into the receive
buffer. To determine if there are bytes in the buffer, call uartKBHit(). To retrieve the next byte in the
buffer, call uartGetByte().
Like all managers, the UART Manager has an initialization function that must be called at reset to put
the manager in a default state.
4.1.8 TIMER MANAGER
The Timer Manager provides the application and other managers with timer functionality by providing
a method of establishing timer events and registering callbacks when those events reach their
terminal count. The Timer Manager provides 500-microsecond resolution (although this resolution is
configurable via the Microcontroller API). The Timer Manager uses a single timer unit on the MCU.
The Timer manager is capable of registering 16 event timers. Each event timer is 16 bits for a
maximum of 32,768 seconds. An event timer can either be a continuous timer or a single-shot timer.
A continuous timer event is started by “registering” the event using a function call. The function call
provides the timer count and a callback function that is called when the event reaches the terminal
count. The function returns a timer “handle” which is used to refer to the timer event and remove the
timer event. Similar functions exist to register single-shot and elapsed-time events. For details on the
Timer Manager functions, refer to Section 5.0.10.
4.1.9 INTERRUPT MANAGER
The Interrupt Manager is used to control the enabling and disabling of interrupts, and it ensures that
interrupts cannot be inadvertently enabled in nested function calls.
© DLP Design, Inc.
Rev 1.1 (November 2012)
9