NUC130LE3CN Nuvoton Technology Corporation of America, NUC130LE3CN Datasheet - Page 155

• Manufacturer Part Number: NUC130LE3CN
• Description: IC MCU 32BIT 128KB FLASH 48LQFP
• Manufacturer: Nuvoton Technology Corporation of America
• Series: NuMicro™ NUC100r

Specifications of NUC130LE3CN

• Core Processor: ARM Cortex-M0
• Core Size: 32-Bit
• Speed: 50MHz
• Connectivity: CAN, I²C, IrDA, LIN, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, DMA, I²S, POR, PWM, WDT
• Number Of I /o: 35
• Program Memory Size: 128KB (128K x 8)
• Program Memory Type: FLASH
• Eeprom Size: -
• Ram Size: 16K x 8
• Voltage - Supply (vcc/vdd): 2.5 V ~ 5.5 V
• Data Converters: A/D 8x12b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 48-LQFP
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

NuMicro™ NUC130/NUC140 Technical Reference Manual
5.4.4.8
Handling Transactions with USB Device Peripheral
User can use interrupt or polling USB_INTSTS to monitor the USB Transactions, when
transactions occur, USB_INTSTS will be set by hardware and send an interrupt request to CPU (if
related interrupt enabled), or user can polling USB_INTSTS to get these events without interrupt.
The following is the control flow with interrupt enable.
When USB host has requested data from device controller, users need to prepare related data
into the specified endpoint buffer in advance. After buffering the required data, users need to write
the actual data length in the specified MAXPLD register. Once this register is written, the internal
signal “In_Rdy” will be asserted and the buffering data will be transmitted immediately after
receiving associated IN token from Host. Note that after transferring the specified data, the signal
“In_Rdy” will de-assert automatically by hardware.
Figure 5-13 Setup Transaction followed by Data in Transaction
Alternatively, when USB host wants to transmit data to the OUT endpoint in the device controller,
hardware will buffer these data to the specified endpoint buffer. After this transaction is
completed, hardware will record the data length in related MAXPLD register and de-assert the
signal “Out_Rdy”. This will avoid hardware accepting next transaction until users move out current
data in the related endpoint buffer. Once users have processed this transaction, the related
register “MAXPLD” needs to be written by firmware to assert the signal “Out_Rdy” again to accept
next transaction.
Publication Release Date: June 14, 2011
- 155 -
Revision V2.01