Contact Us

STM32F105VBH6

Brand: ST
ST STM32F105VBH6 is a mcu & embedded component designed for general electronics and related applications. In stock at Superb Automation — request a quote for competitive pricing and fast delivery.
quote now

Product Specifications

STM32F105VBH6 — MCU & Embedded Processors | Superb Automation

STM32F105VBH6

ST — MCU & Embedded Processors

Product Overview

The STM32F105VBH6 from ST is a microcontroller / embedded processor engineered for real-time control, signal processing, and connectivity. STMicroelectronics is a European semiconductor leader with a strong portfolio in MCUs, power management, sensors, and analog ICs.

Superb Automation partners with leading brands including Qorvo, TI, ADI, XILINX, NVIDIA, Intel, ST, MACOM, Renesas, and Coilcraft to provide complete BOM and supply-chain solutions.

Key Features

  • ARM Cortex / RISC-V / proprietary core with high-performance real-time processing
  • Integrated flash memory and SRAM for efficient code execution
  • Rich peripheral set: UART, SPI, I2C, ADC, timers, PWM
  • Low-power modes for battery-operated and energy-sensitive applications
  • Hardware security features: secure boot, crypto accelerator, TRNG
  • Extensive development ecosystem with IDE, HAL, and RTOS support

Key Specifications

Core—
Max FrequencyMHz
FlashKB
SRAMKB
GPIO—
ADCbits
Interfaces—
Supply VoltageV
Operating Temp°C
Package—

Applications

Industrial Motor Control IoT Edge Nodes Consumer Electronics Automotive Body Control Smart Home & Appliances Medical Portable Devices

Request Quote — In Stock, 100% New & Original, Full Warranty

STM32F105VBH6: the Connectivity Line in a 10 mm Ball Grid Body

STM32F105VBH6 is the 128 Kbyte member of the STM32F105 connectivity line in the LFBGA100 package. The connectivity line is a different device from the F103 range in ways that matter to a bill of materials: two CAN controllers each with 512 bytes of dedicated SRAM, a USB 2.0 OTG controller with 1.25 Kbytes of its own SRAM and host negotiation support, a 12 channel DMA, two DAC channels, and an oscillator that accepts 3 to 25 MHz instead of the 4 to 16 MHz of the F103. The H in the code is the ball grid body and the 6 is the minus 40 to plus 85 C range.

Dedicated SRAM is the quiet advantage

On a general purpose part, a CAN controller and a USB engine share the system SRAM and the DMA arbitrates for it, which shows up as latency in the message path when both are busy. The connectivity line gives each engine its own buffer memory, so a CAN bridge that also enumerates as a USB device does not lose frames while the host is polling. This is the reason the connectivity line survives in gateway products even though its core runs at the same 72 MHz as the F103.

Values at a glance

ParameterValueNote
Core and clockCortex-M3, 72 MHzTrace macrocell, 1.25 DMIPS/MHz
Flash, SRAM128 Kbytes, 64 KbytesGeneral purpose SRAM, separate from the CAN and USB buffers
PackageLFBGA100, 10 by 10 mmLQFP100 and LQFP64 bodies carry the same density
I/O80 pins51 counts apply to the 64 pin body
CAN2 controllers, 2.0B active512 bytes of dedicated SRAM for the pair
USB2.0 full speed, device, host and OTGOn chip PHY with HNP, SRP and ID support, 1.25 Kbytes dedicated SRAM
Analog2 ADC, 12 bit, 16 channels; 2 DAC channelsUp to 2 MSPS in interleaved mode, 1 microsecond single conversion
EthernetNot present on this subfamily10/100 MAC belongs to the STM32F107xx codes only

The ball grid body and the 3 to 25 MHz oscillator

The wider oscillator range is not cosmetic: 25 MHz is a common Ethernet and USB reference frequency, and a board that carries an F107 device on a different position of the same product may already have a 25 MHz crystal. Sharing that clock across both device positions is possible on the connectivity line and not on the F103 range. In the 10 mm ball grid body the oscillator pins are on the same ball rows as the supply, so a crystal placed close to the ball array keeps the load capacitors short, which is what holds the frequency within the CAN tolerance over temperature.

Sourcing the ball grid connectivity part

The connectivity line is a smaller volume family than the F103 range, and the ball grid bodies are a fraction of that volume again, so a reel of the VBH code is usually a specific order rather than a catalogue item. Two things reduce the risk: knowing that the VBT code is the same device in the quad flat body, which may be acceptable if the board allows a revision, and holding a buffer of the exact part. A microcontroller cross reference note, a lead time plan, and a vendor consolidation review that puts the MCU and its transceivers with one supplier are how that is managed in practice.

Common questions

Can this part act as a USB host? Yes, the OTG controller supports host mode with the on chip PHY and needs only the ID pin and a 5 V switch for the port supply, which the F103 USB device port cannot do.

Are the two CAN controllers independent? They are separate controllers with their own filters and mailboxes, sharing the 512 bytes of dedicated SRAM, and they can run at different bit rates.

Is the part code compatible with the F103 range? Not at the register level for the new blocks: the CAN buffer arrangement, the OTG controller and the DMA are different. Code written for F103 peripherals generally moves, and code that pokes at the CAN filter registers has to be reviewed.