Specifications

ManualsBrandsAudio Design ManualsAmplifierTXi 6000

APPLICATION NOTE

R01AN1859EJ0100 Rev. 1.00 Page 1 of 15

Apr. 1, 2014

RX Family, M16C Family

Migrating from the M16C to the RX

Asynchronous Serial Communications (UART)

Abstract

This document describes migrating from the serial I/O UART mode in the M16C Family to the SCI asynchronous mode

in the RX Family.

Products

RX Family, M16C Family

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

modifications to comply with the alternate MCU.

Differences in Terminology

Item

RX Family

M16C Family

Serial communication interface

(SCI)

SCI Serial I/O

Asynchronous serial

communications mode

Asynchronous mode

UART mode (clock asynchronous

serial I/O mode)

SCI operating clock (clock source)

Clock source

Count source

Peripheral function operating clock

Peripheral module clocks:

PCLKA, PCLKB, PCLKC, PCLKD

Peripheral function clocks: f1,

fOCO40M, fOCO-F, fOCO-S,

fC32

Transmit buffer

TDR register

UiTB register (transmit buffer)

Transmit shift register

TSR register

UART transmit shift register

Receive buffer

RDR register

UiRB register

Transmit interrupt TXI interrupt

UARTi transmit interrupt (transmit

buffer empty)

Transmit complete interrupt (M16C)

Transmit end interrupt (RX)

TEI interrupt

UARTi transmit interrupt

(transmission completed)

Receive interrupt

RXI interrupt

UARTi receive interrupt

Function to select I/O of peripheral

functions for pins

MPC

Function select register,

input function select register

Note 1. Only available in the M32C Group and R32C Group.

Note 2. The MPC is not available in some groups.

R01AN1859EJ0100

Rev. 1.00

Apr. 1, 2014

Summary of content (18 pages)

PAGE 1
APPLICATION NOTE RX Family, M16C Family R01AN1859EJ0100 Rev. 1.00 Apr. 1, 2014 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Abstract This document describes migrating from the serial I/O UART mode in the M16C Family to the SCI asynchronous mode in the RX Family. Products RX Family, M16C Family When using this application note with other Renesas MCUs, careful evaluation is recommended after making modifications to comply with the alternate MCU.
PAGE 2
RX Family, M16C Family Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Contents 1. Differences in Asynchronous Serial Communications ....................................................................... 3 2. Peripheral Functions Used ................................................................................................................. 4 3. Differences in Asynchronous Serial Communications .......................................................................
PAGE 3
RX Family, M16C Family 1. Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Differences in Asynchronous Serial Communications Table 1.1 lists the Differences in Asynchronous Serial Communications. Table 1.
PAGE 4
RX Family, M16C Family 2. Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Peripheral Functions Used Table 2.1 lists Peripheral Functions and Modes Used When Performing Asynchronous Communications. Table 2.1 Peripheral Functions and Modes Used When Performing Asynchronous Communications No. 1 3.
PAGE 5
RX Family, M16C Family 3.1 3.1.1 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Transmit/Receive Timing Differences in Transmitting Figure 3.1 shows the Differences in Timing When Transmitting 3 Bytes at a Time. 1 TXD pin M16C Family *1 Low TE bit in the UiC1 register 1 IR bit for the transmit interrupt 1 SCR.TE bit SCR.
PAGE 6
RX Family, M16C Family Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Table 3.2 lists Differences in Operation at Various Timing When Transmitting 3 Bytes at a Time. Table 3.
PAGE 7
RX Family, M16C Family 3.1.2 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Differences in Receiving Figure 3.2 shows the Differences in Timing When Receiving. 1 2 RXD pin M16C Family High Low RE bit in the UiC1 register 1 IR bit for the receive interrupt 1 SCR.RE bit SCR.
PAGE 8
RX Family, M16C Family Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Table 3.3 lists Differences in Operation at Various Timing When Receiving. Table 3.3 Differences in Operation at Various Timing When Receiving Timing  When reception is enabled  When reception starts   When reception is completed When a receive error occurs RX (RX210) Set the SCR.
PAGE 9
RX Family, M16C Family 3.2 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Differences in Setting Procedures The tables in this section list the steps for transmission and reception in asynchronous mode. Table 3.4 Differences in the Initial Setting Procedures When Transmitting and Receiving Data Step 1 2 3 4 5 6 7 8 9 10 11 RX (RX210) M16C (M16C/65C) Exiting the module-stop state SYSTEM.PRCR.WORD = 0xA502; MSTP(SCI0) = 0; N/A (no module-stop function) *1 SYSTEM.PRCR.
PAGE 10
RX Family, M16C Family Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Table 3.5 Differences in Transmit Interrupt Handling Step RX (RX210) 1 Write transmit data /* Write transmit data to the SCR.TDR register */ 2 Confirm last data was written if (Last data written? ) { 3 Disable TXI interrupt (only after last data is written) IEN(SCI0,TXI0) = 0; SCI0.SCR.BIT.TIE = 0; while (0 != SCI0.SCR.BIT.
PAGE 11
RX Family, M16C Family Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Table 3.7 Differences in Receive Interrupt Handling Step RX (RX210) M16C (M16C/65C) /* Read receive data from the U0RB register */ Determine the receive if( Did a receive error occur? ) 2 error { Processing when a /* Describe processing when an error 3 *1 receive error occurs N/A (no processing) occurs */ re_u0c1 = 0; Clear the receive error 4 u0mr = u0mr & 0xf8; (disable reception) } Note 1.
PAGE 12
RX Family, M16C Family 3.3 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Calculating the Bit Rate There are differences in calculating the bit rate between the RX Family and M16C Family. Table 3.9 lists the Differences in Calculating the Bit Rate. Table 3.9 Differences in Calculating the Bit Rate Item RX (RX210) M16C (M16C/65C) When the SEMR.
PAGE 13
RX Family, M16C Family 4. Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Appendix 4.1 Points on Migrating from the M16C to the RX This chapter explains points on migrating from the M16C to the RX. 4.1.1 Interrupts In the RX, if an interrupt request is received when all of the following conditions are met, the interrupt can be accepted.  The I flag (PSW.I flag) is 1.  Registers IER and IPR in the ICU are set to "interrupt enabled".
PAGE 14
RX Family, M16C Family 4.2 Migrating from the M16C to the RX Asynchronous Serial Communications (UART) I/O Register Macros Macro definitions listed in Table 4.3 can be found in the RX I/O register definitions (iodefine.h). The readability of programs can be achieved with these macro definitions. Table 4.3 lists examples of Macros. Table 4.3 Using Macros Macro Usage Example IR("module name", "bit name") IR(MTU0,TGIA0) = 0 ; The IR bit corresponding to MTU0.
PAGE 15
RX Family, M16C Family 5. Migrating from the M16C to the RX Asynchronous Serial Communications (UART) Reference Documents User’s Manual: Hardware RX210 Group User's Manual: Hardware Rev.1.50 (R01UH0037EJ) M16C/65C Group User's Manual: Hardware Rev.1.10 (R01UH0093) Refer to the corresponding UMH when using products other than the RX210 Group and M16C/65C Group. The latest versions can be downloaded from the Renesas Electronics website.
PAGE 16
RX Family, M16C Family Application Note Migrating From the M16C to the RX Asynchronous Serial Communications (UART) REVISION HISTORY Rev. Date 1.00 Apr. 1, 2014 Page — Description Summary First edition issued All trademarks and registered trademarks are the property of their respective owners.
PAGE 17
General Precautions in the Handling of MPU/MCU Products The following usage notes are applicable to all MPU/MCU products from Renesas. For detailed usage notes on the products covered by this document, refer to the relevant sections of the document as well as any technical updates that have been issued for the products. 1. Handling of Unused Pins Handle unused pins in accordance with the directions given under Handling of Unused Pins in the manual.
PAGE 18
Notice 1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the use of these circuits, software, or information. 2.