C8051F507-IM

C8051F50x Automotive & Industrial MCUs

The C8051F507-IM is a highly integrated automotive and industrial microcontroller (MCU) that is auto-grade qualified and tested to AEC-Q100 specification with enhanced temperature operation of up to 125 ºC. The C8051F507-IM features a powerful 8051 core with 50 MHz performance along with 32 kB Flash, 4.25 kB RAM. This MCU also offers integrated communication interfaces and a 12-bit, 25-ch., 200 ksps ADC and 2 comparators in a 5x5 mm, QFN32. With enhanced communication peripherals and robust peripheral set, the C8051F507-IM is ideal for motor control, sensor interface, parking assistance, seat position and adjustment, fluid level monitoring, and other automotive/industrial applications.

SPECS
TECH DOCS
SOFTWARE & TOOLS
QUALITY & PACKAGING
COMMUNITY & SUPPORT

SPECS

Key Specs

MCU Core 8051	MHz 50	Flash (kB) 32
RAM (kB) 4.25	CAN 0	EMIF 0
I2C 1	LIN 0	SPI 1
UART 1	Dig I/O Pins 25	ADC 12-bit, 25-ch., 200 ksps
DAC —	Comparators 2	PCA Channels 6
Timers 4	Package Type QFN32	Package Size (mm) 5x5

MCU Core

8051

MHz

Flash (kB)

RAM (kB)

4.25

CAN

EMIF

I2C

LIN

SPI

UART

Dig I/O Pins

ADC

12-bit, 25-ch., 200 ksps

DAC

—

Comparators

PCA Channels

Timers

Package Type

QFN32

Package Size (mm)

5x5

C8051F50x/1x Automotive and Industrial 8-bit MCU Development Kit

The easiest way to begin development with the C8051F50x automotive and industrial microcontroller family and the C8051F51x family is with the fully functional “out-of-the-box” C8051F500DK development kit.

C8051F50x/1x Automotive and Industrial 8-bit MCU Development Kit

MSRP $147.69

Add to Cart

Learn More

TECH DOCS

SOFTWARE & TOOLS

C8051F50x/1x Automotive and Industrial 8-bit MCU Development Kit

MSRP $147.69

Add to Cart

Learn More

QUALITY & PACKAGING

Quality Assurance, Environmental and Packaging Information

Silicon Labs targets a minimum of a 10-year lifecycle for all of its standard products and expects to produce the C8051F507-IM until at least March 2027.

The longevity date shown above is for the preferred revision of this part number, for a complete list of part number revisions, use the search button below.

As part of its ongoing commitment to supply continuity, Silicon Labs may provide pin-compatible and functionally equivalent replacement products if Silicon Labs determines, at its discretion, that supply chain adjustments, product improvements, market conditions, or similar business or technical issues make this necessary or advisable.

If for business, technical or other reasons beyond Silicon Labs’ reasonable control, Silicon Labs finds that it is necessary to discontinue a product, our policy is to issue an EOL notice that provides 6 months from notice to place final orders and 12 months from notice for final shipments. This policy complies with the JEDEC standard EIA/JESD48 that is commonly used in the semiconductor industry. We provide the required support for a product for its full life cycle.

Find and download additional quality, environmental, device composition, test results, shipping and supply chain information for Silicon Labs devices.

Search results will include:

Product Information
Packing Information
Quality System Certifications
Financial Information
Conflict Minerals (CMRT)
Environmental Information
- RoHS Certificate of Compliance
- REACH Declaration
- Detailed Device Composition (MDDS)
- MCD/FMD

Search Part Number

Qualification Data
Trade Compliance: ECC/HTS Codes
Supply Chain Information
IPC 1752-2 Class 6 (XML format)
ICP Test Reports
Halogen-Free Certificate of Compliance
PFOS/PFOA Certificate of Compliance
Supply Assurance Letter (Longevity)

COMMUNITY & SUPPORT

Debug Adapter Firmware Update Requires repeated update attempts

jpitt | 09/06/2024 | 03:31 PM

When a new version of a debug adapter firmware (fw) is available, Simplicity Studio (SSv5) will show a message asking if the user wants to update to the latest firmware version. When the update is selected it will sometimes fail, especially on Windows, usually with a timeout message. Silicon Labs is working on providing a fix to the issue through a combination of Simplicity Studio and Simplicity Commander updates (Simplicity Commander is used for all adapter fw updates, even through SSv5). Until a fix is available, the following procedure can be used to update the adapter firmware.
1. From the [Tools] menu, open Simplicity Commander.

2. Exit Simplicity Studio, but keep Simplicity Commander open. Simplicity Studio inadvertently interferes with the update process when the debug adapter is reset in bootloader mode.

3. In Simplicity Commander, click the [Select Kit...] button and then select the debug adapter to update. If an earlier adapter firmware update attempt failed, there may be a popup about the adapter being in 'bootloader mode', that is fine, just ignore the message and hit the [OK] button and proceed with the next step.

4. The [Kit] section of commander should be selected. In the [Update Kit] section click the [Browse...] button to find the update image to use. The various adapter firmware images for the debug adapter types that have been attached to the computer will have been automatically downloaded to the 'offline/hwtools/firmware' folder in the SSv5 installation folders (under Contents/Eclipse on MacOS). If only one adapter type has been attached, then there will only be one folder and the latest file in the folder should be selected. But there could be several adapter firmware folders from amongst this set:

Note: If the wrong adapter firmware image is selected it will not hurt anything as that will be detected and the update will be aborted. So, in the worst case a trial and error approach can be used.

The various adapter firmware images exist because there are different board controller processors on the various debug adapters. The following is a guide for which adapter firmware group (examples S1015B, S1015D, S1015E, S1015F) should be used for the various Silicon Labs debug adapters.
S1007 - Older EFM32 development kits with 'DK' in part number
S1010 - EFM32 based starter kits, BRD2001A, BRD2100A
S1012 - BRD3201A, BRD3201B
S1014 - EFM32 based starter kits, BRD2010A, BRD2200A, BRD2201A, BRD2400A
S1015A_mcu_stk - EFM8 and EFM23 based starter kits, BRD5000A, BRD5001A, BRD5100A,
BRD5101A, BRD5200A, BRD5201A, BRD5202A, BRD5300A, BRD2012A, BRD2102A,
BRD2204A, BRD2204B, BRD2500A, BRD2501A
S1015B - Wireless mainboard BRD4001A and BRD4001B, also known as 'WSTK'.
S1015C - Thunderboards, BRD4160A, BRD4166A, BRD4166C, BRD5002A
S1015D - For the various small 'devkits' such as Thunderboards and the 26xx boards.
BRD1015A, BRD2503A, BRD2503B, BRD2600A, BRD2601B, BRD2602A,
BRD2603B, BRD2605A, BRD2608A, BRD2700A, BRD2701A, BRD2702A,
BRD2703A, BRD2704A, BRD2705A, BRD2710A, BRD2900A, BRD2901A,
  BRD2902A, BRD2903A, BRD2904A, BRD2905A, BRD4108A, BRD4184A,
  BRD4184B, BRD4314A, BRD4330A, BRD4331A
S1015E - Wireless pro kit - BRD4002A, also known as 'WPK'.
S1015F - Pro kit, EFM8 and EFM32 based 'B' and 'C' variant boards,
BRD2001B, BRD2010B, BRD2012B,
  BRD2100B,  BRD2102B, BRD2200C, BRD2201B, BRD2204C, BRD2400B,
  BRD2500B, BRD2501B, BRD2504A, BRD5000B, BRD5001B, BRD5100B,
  BRD5101B, BRD5200B, BRD5201B, BRD5202B, BRD5206B, BRD5207B,
BRD5208A, BRD5300B,
After opening the latest file in the appropriate folder, click the [Install Package] button. The progress of the update can be tracked in the Log Window. If the update fails, then close any dialog boxes and try again with the following two notes:
1. If an EMLINK failed message is received, then disconnect and reconnect the debug adapter before trying again.
2. If the blue LED near the USB connector is flashing fast (this has only been observed sometimes on Windows), then wait for the flashing to stop before trying again. My observation is that if the blue LED starts flashing for a long time when a debug adapter is connected, then rebooting the PC will resolve that issue.

The above procedure has worked every time it has been tried, sometimes it might take up to 4 or 5 attempts to update the firmware.

This issue will be fixed with the Simplicity Studio SV5.10.0 and Simplicity Commander 1v17p0 release.

Using Ethernet on MCU devices

Silicon Labs Admin | 07/09/2021 | 05:35 PM

Question

How can I use the CP2200 and the TCP/IP stack on devices other than the 'F34x/'F02x/'F12x?

Answer

https://community.silabs.com/s/article/ethernet-stack?language=en_US

Calibrate Internal Oscillator

Silicon Labs Admin | 07/09/2021 | 05:34 PM

Question

How do I calibrate the programmable internal oscillator to a non-factory value?

Answer

The programmable internal oscillator can be calibrated using a known clock source selected as SYSCLK. This SYSCLK frequency should be higher than that of the oscillator to be calibrated. The example code 'F330_LFO_Cal.C' shows how to measure the SYSCLK time between the falling and rising edges of the LFO using the timer in capture mode. After the frequency is measured, you can then modify the calibration register (OSCICL for HFO, OSCLCN for LFO) to fine-tune the oscillator to a desired frequency using the formula given in the 'Oscillators' chapter of the datasheet. This example code applies to the F33x devices only. For other devices, necessary changes should be made to the code before it can be used.

Notes:

Certain devices in the C8051Fxxxx family do not have a calibration register for the internal oscillators. These are the C8051F00x, C8051F01x, C8051F02x, adn C8051F2xx. They only have a clock divider that can operate on the fixed internal oscillator frequency. Nevertheless, that frequency can be measured using the method detailed above.
Some devices have more than one programmable internal oscillator. See the datasheet for details.
For the USB devices, calibrating the internal oscillator away from the factory preset will make it unusable as the USB clock.
On reset, all devices revert back to factory preset calibration values and derive SYSCLK from the internal oscillator frequency divide by 8.
For information pertinent to the oscillator(s) in your device, please refer to the respective datasheet under chapter 'Oscillators'.
For help with configuring the oscillators, please refer to Application Note 'AN102: Configuring the Internal and External Oscillators' available at: http://www.silabs.com/products/mcu/Pages/ApplicationNotes.aspx