Renesas RX110

To Next Page

APPLICATION NOTE

R01AN1666EJ0220 Rev. 2.20 Page 1 of 74

Dec 01, 2016

RX Family

ADC Module Using Firmware Integration Technology

Introduction

This module provides support for all features of the 12-bit A/D Converter on the RX110, RX111, RX113, RX130,

RX210, RX230, RX231, RX631, RX63N, RX64M, RX65N and RX71M.

Target Device

The following is a list of devices that are currently supported by this API:

• RX110, RX111, RX113, RX130 Groups

• RX210 Group

• RX230, RX231 Groups

• RX631, RX63N Groups

• RX64M Group

• RX65N Group

• RX71M Group

When using this application note with other Renesas MCUs, careful evaluation is recommended after making

modifications to comply with the alternate MCU.

Renesas RX110 Specifications

General

CPU Core	RXv1
Maximum Operating Frequency	32 MHz
Operating Voltage	1.8V to 5.5V
Operating Temperature	-40°C to +85°C
Package	LQFP, QFN
ADC	12-bit
Communication Interfaces	UART, I2C, SPI

Summary

Overview

API Information

2.1 Hardware Requirements

MCU peripheral and feature requirements for the ADC driver.

2.2 Hardware Resource Requirements

Details required hardware peripherals like S12ADa/b/c/e/f and GPIO.

2.3 Software Requirements

Lists dependencies like the Renesas Board Support Package (r_bsp).

2.4 Limitations

Notes on variations in A/D converter modes and usage guidelines.

2.5 Supported Toolchains

Lists tested toolchains, e.g., Renesas RX Toolchain v2.05.00.

2.6 Header Files

Specifies required header files for configuration and API definitions.

2.7 Integer Types

Mentions ANSI C99 "Exact width integer types" for portability.

2.8 Configuration Overview

Explains build-time configuration options in r_s12ad_rx_config.h.

2.9 Code Size

Details ROM and RAM code sizes based on optimization and configuration.

2.10 API Data Structures

Details data structures used in API functions for strong type checking.

2.10.1 MCU Common Interface Types

Defines callback event types and arguments for MCU-specific interfaces.

2.10.2 RX110 Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX110.

2.10.4 RX113 Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX113.

2.10.5 RX130 Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX130.

2.10.6 RX210 Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX210.

2.10.7 RX231 Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX231.

2.10.9 RX63 x Interface Types

Specifies ADC OPEN() argument definitions and trigger sources for RX63x.

2.10.10 RX64 M, RX71 M Interface Types

Specifies ADC OPEN() argument definitions and resolution types for RX64M/RX71M.

2.10.11 RX65 x Interface Types

Specifies ADC OPEN() argument definitions and modes for RX65x.

2.11 Return Values

Lists and explains ADC API error codes returned by functions.

2.12 Adding a FIT Module to Your Project

Describes methods for adding the FIT module to projects using the FIT plugin.

API Functions

3.1 Summary

Provides an overview of the functions included in the ADC driver design.

3.2 RADCOpen()

Initializes the ADC peripheral, sets mode, triggers, and priority.

3.3 RADCControl()

Manages channels, sensors, triggers, interrupts, and scan operations.

3.4 RADCRead()

Reads conversion results from a single channel, sensor, or register.

3.5 RADCReadAll()

Reads all potential channel sources for a snapshot of all values.

3.6 RADCClose()

Ends scans, disables interrupts, and removes power from the A/D peripheral.

3.7 RADCGetVersion()

Returns the driver version number at runtime.

Pin Setting

Demo Projects

5.1 s12 adintdemorskrx113

Demo using periodic interrupts from MTU0 to trigger ADC scans.

5.2 s12 adpolldemorskrx113

Demo scanning potentiometer via software trigger in an endless loop.

5.3 s12 adpolldemorskrx130