STM32F107RBT6
Product Specifications
STM32F107RBT6
ST — MCU & Embedded Processors
Product Overview
The STM32F107RBT6 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 Frequency | MHz |
| Flash | KB |
| SRAM | KB |
| GPIO | — |
| ADC | bits |
| Interfaces | — |
| Supply Voltage | V |
| Operating Temp | °C |
| Package | — |
Applications
Request Quote — In Stock, 100% New & Original, Full Warranty
STM32F107RBT6: Ethernet and Two CAN Buses at 128 Kbytes
STM32F107RBT6 is the 128 Kbyte version of the 64 pin Ethernet device: same LQFP64 body, same 51 I/O pins, same MAC with 4 Kbytes of dedicated buffer memory, same two CAN controllers and the same USB OTG port. It is the code that fits a bridge or a remote I/O node whose firmware is already written and validated, and it is the code that forces a decision when a new feature pushes the image past 128 Kbytes, because the RC code is the only step up in the same footprint.
The buffer memory is the reason this family beats a software stack on shared RAM
With 64 Kbytes of general purpose SRAM, a device that runs an RTOS with four tasks, a TCP stack and a CAN stack is working inside a fixed budget. The connectivity line eases that by giving the MAC 4 Kbytes, the USB engine 1.25 Kbytes and the CAN pair 512 bytes of memory that the application cannot allocate. Those buffers are not visible in the linker map, which is exactly the point: the network path keeps working while the application allocates the rest of the SRAM.
Values at a glance
| Parameter | Value | Note |
|---|---|---|
| Core and clock | Cortex-M3, 72 MHz | 12 channel DMA, trace macrocell on chip |
| Flash, SRAM | 128 Kbytes, 64 Kbytes | 256 Kbyte RC code is the next density in the same body |
| Package | LQFP64, 10 by 10 mm | No ball grid version of this body in the family |
| I/O | 51 pins | 16 external interrupt vectors |
| Ethernet | 10/100 MAC, RMII or MII | IEEE 1588 timestamp support in hardware |
| CAN | 2 controllers, 2.0B active | Independent bit rates and filter sets |
| USB | 2.0 full speed device, host, OTG | HNP and SRP support, ID pin for role selection |
| Temperature | Minus 40 to plus 85 C | Ambient limit, junction rated to 125 C |
128 Kbytes with a bootloader
A bootloader that supports a serial or network update occupies between 8 and 24 Kbytes depending on whether it carries a network stack of its own. That is a fifth of the flash on this part before the application starts, which is the single most common reason a project on the RB code moves to the RC code. Planning the flash map first, with the bootloader, the application, the parameter area and the update staging area each given a fixed range, avoids discovering the limit after the certificate store and the language tables have been linked in.
Keeping a validated board supplied
Where the firmware is fixed and the part is short, the substitution to the RC code is the least disruptive option because only the flash size changes. Where even that is unavailable, the open market is the remaining route, and it needs the discipline that goes with it: date code checks, a moisture sensitivity check on a part that has been in storage, and a functional test that exercises the network path rather than only the power rails. A cross reference record, an incoming inspection plan and an obsolescence position on the family cover that route in a way that survives an audit.
Common questions
Is the RB code pin identical to the RC code? Yes. Both are LQFP64 devices from the same family with the same pin definition, and the only difference is 128 against 256 Kbytes of flash.
Can the part run two Ethernet ports? No. There is one MAC in the device, and a second port needs an external switch or a second controller.
Does the MAC support 10 Mbit operation? Yes, with the same RMII or MII interface, and the reference clock requirement changes with the speed mode selected.