Arm Keil MDK v6 Essential and Professional editions are now available to buy as monthly or annual subscriptions from our Developer Tools store. Visit the store to get access to the tools suite today!

  1. Devices
  2. HT32F493xx Series
  3. HT32F49365/49395
  4. HT32F49395_100LQFP

HT32F49395_100LQFP

Holtek

  • Core

    Cortex-M4, 240 MHz

  • Family

    HT32F493xx Series

  • Sub-Family

    HT32F49365/49395

  • CMSIS Pack

    HT32F493x5_DFP

The HT32F49365/HT32F49395 devices are based on the high-performance Arm®Cortex®-M4 32-bit RISC core, operating at a frequency of up to 240 MHz. The Cortex®-M4 core features a Floating Point Unit (FPU) single precision which supports all Arm® single-precision data processing instructions and data types. It also implements a full set of DSP instructions and a Memory Protection Unit (MPU) which enhances application security.

The devices incorporate high-speed embedded memories (up to 1024 KBytes of internal Flash memory, 96 + 128 KBytes of SRAM), external SPI Flash (up to 16 MBytes addressing capability), and a wide range of enhanced GPIOs and peripherals connected to two APB buses. Any block of the embedded Flash memory can be protected by the “sLib” (security library), functioning as a security area with code-executable only.

The devices offer three 12-bit ADCs, two 12-bit DACs, eight general-purpose 16-bit timers plus two general-purpose 32-bit timers, and up to two PWM timers for motor control. They support standard and advanced communication interfaces including up to three I2Cs, four SPIs (all multiplexed as I2Ss), two SDIOs, eight USARTs/UARTs, an USBFS, and two CANs.

The HT32F49365/HT32F49395 devices operate in the -40 to +105 °C temperature range, from a 2.6 to 3.6 V power supply. A comprehensive set of power-saving mode allows the design of low-power application.

The HT32F49365/HT32F49395 are supplied in different package types. The entire HT32F49365/HT32F49395 series of devices are fully pin-to-pin, software and functionally compatible with each other, except that the configurations of peripherals are not completely identical, depending on the package types.