www.PEmicro.com - P&E Microcomputer Systems

PEmicro STM32 high-speed Cyclone Flash Programmers get your job done FASTER

PEmicro Blogger (www.pemicro.com) — Wed, 11 Mar 2026 16:32:17 EST

Source: www.pemicro.com

PEmicro is a highly-specialized developer of very high-speed STM32 flash programmers with over 40 years of experience and over 30,000 customers worldwide, proudly providing the best and fastest customer service and product support in the industry.

Our Cyclone LC and FX STM32 programmers are known for these features:

Support for virtually the full catalog of STM32 parts.
Very high speed programming.
Extremely reliable and robust programmers after decades of experience.
Strong security features (like encrypted images and support for STM32-specific security features).
Multiple operating modes (PC-controlled, cloud-controlled, stand-alone, one-button push programming, gang programming via SDK, etc)
Powerful Native Control & Automation SDK for most operating systems (Windows, Linux, macOS), and most popular programming languages like C, C++, Python, Java, Rust, LabView, Microsoft Visual C, Microsoft Visual C#, Delphi/FPC, and Microsoft Visual Basic.
Support for cloud-based remote programming and monitoring using our PEcloud, offering the industry's strongest IP protection.

Click the image bellow to get technical and pricing information about our Cyclone LC and FX flash programmers for STM32.

Cyclone Programmer - Error Code List

PEmicro Blogger (www.pemicro.com) — Wed, 04 Mar 2026 22:34:46 EST

Source: www.pemicro.com

The Cyclone Production Programmers are highly repeatable programmers designed to program large volumes of devices. While they can run completely stand-alone, they are more commonly controlled via the Cyclone Control SDK or Cyclone Control Console. Part of the process of programming devices is for the programmer to detect and return errors to the callee when they occur. Most commonly these are related to defective boards being programmed or bad connectivity, but there are also many very obtuse errors which could be returned but most of which will never be seen during normal use. The error codes returned have associated descriptions provided automatically via the SDK, Console, and on the screen of the programmer itself. Some customers have asked for a full list of error codes they could possibly get. This list of possible error codes can be displayed via the cyclonecontrolconsole application.

Configure a Programming Image to Synchronize with PEcloud

PEmicro Blogger (www.pemicro.com) — Tue, 17 Feb 2026 14:21:02 EST

Source: www.pemicro.com

In today’s fast-paced manufacturing environments, programming images are evolving to be more than static files that sit on a local PC or server. By generating programming images that are synchronized with the cloud, the user gains many benefits — Remote Visibility into the programming process, Enhanced control, easy distribution, history of program jobs and logged data.

Added Support for Nuvoton M253 devices

PEmicro Blogger (www.pemicro.com) — Tue, 17 Feb 2026 10:16:11 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG v9.97, PEMicro’s development and production tools now include support for Nuvoton M253 series of devices. The M253 series is based on the Arm Cortex-M23 with up to 128KB of Flash and 16KB or SRAM. Each device's algorithm supports both the APROM and LDROM regions of flash for the respective device's flash memory size.

New device support added for the following part numbers: M253LD3AE, M253LD3BE, M253LE3AE, M253LE3BE, M253ZE3AE, M253ZE3BE.

Added Support for Autochips AC7805x Devices

PEmicro Blogger (www.pemicro.com) — Tue, 17 Feb 2026 10:08:29 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG v9.97, PEMicro’s development and production tools now include support for Autochips AC7805x devices. Each device includes algorithms for both the main flash region and the Control Information 8KB region.

New device support added for the following part numbers: AC78056FD, AC78056FE, AC78056HD, AC78056HE, AC78056MD, AC78056ME, AC78058FD, AC78058FE, AC78058HD, AC78058HE, AC78058MD, AC78058ME

Added Support for Nordic Semiconductor nRF54L Devices

PEmicro Blogger (www.pemicro.com) — Tue, 17 Feb 2026 10:02:35 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG v9.97, PEMicro’s development and production tools now include support for Nordic Semiconductor nRF54L devices. The nRF54L series is the successor to the nRF52 series and offers double the processing power and triple the processing efficiency. The nRF54L is a Cortex-M33 based device that enabled creation of IoT products with reliable wireless communication and processing performance.

New device support added for the following part numbers: nRF54L05, nRF54L10, nRF54L15.

Added Support for Additional Nordic nRF91 Devices

PEmicro Blogger (www.pemicro.com) — Tue, 17 Feb 2026 09:28:52 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG v9.97, PEMicro’s development and production tools now include support for Nordic Semiconductor nRF9151 and nRF9161 devices. The nRF9151/9161 are Cortex-M33 based modules with 1MB of flash and 256MB of RAM and are specifically designed for cellular IoT and DECT NR+ applications. The new algorithms, "Nordic_nRF9151_1MB.arp" and "Nordic_nRF9161_1MB.arp", support the nRF9151 and nRF9161 devices respectively.

With this support, the User information configuration registers (UICR) region at 0x00FF8000-0x00FF8FFF is available for reprogramming. To reprogram the UICR region, the EM Erase module command needs to be run first to erase the region.

If there are any issues connecting to the target, particularly when it is erased, then the "mass erase upon connection to target" checkbox should be selected. This checkbox can be found in the connection manager of PROGACMP or the Power and Communication settings tab in the Image Creation utility.

Improved Wireless Stack Support for the STMicroelectronics STM32WB Devices

PEmicro Blogger (www.pemicro.com) — Mon, 16 Feb 2026 14:57:13 EST

Source: www.pemicro.com

With the release of Cyclone software v11.70 and PROG v10.00, PEMicro’s development and production tools now support additional Wireless Stack features for the STM32WB5x, STM32WB3x, and STM32WB1x devices. The latest PROG and Cyclone support now enables selecting .BIN files for the FUS Operator, Wireless Stack, or the FUS FW. A new command has been added to start the wireless stack in case the FUS begins running. In PROGACMP, there is an additional command to read the FUS FW version from the target to determine which FUS FW version to upgrade.

Add Support For GigaDevice GD32H759

PEmicro Blogger (www.pemicro.com) — Fri, 13 Feb 2026 15:44:41 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG-HL-ARM software v9.94, PEmicro development and production programmers now support the GigaDevice GD32H759 microcontrollers.

The GD32H759 contains a High Performance 600MHz Cortex®-M7 with up to 4 MB of flash program memory. The GD32H7 MCU series is ideal for signal processing, high-accuracy motor control, digital power supplies, energy storage, audio/voice recognition, and graphic/image applications. Thanks to its ultra-high CPU core clock speed and large memory size, the product also supports applications requiring intensive processing capabilities, such as machine learning (ML)).

Add Support For GigaDevice GD32E51x Series

PEmicro Blogger (www.pemicro.com) — Fri, 13 Feb 2026 15:36:27 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG-HL-ARM software v9.94, PEmicro development and production programmers now support the GigaDevice GD32E513/GD32E517/GD32E518 series microcontrollers.

The GD32E5 series of MCUs is a 32-bit general-purpose microcontroller based on the ARM® Cortex®-M33 core with 512 KB of flash program memory. The GD32E5 series of MCUs is suitable for a wide range of application scenarios such as high-precision industrial control, digital power supply, motor inverters, measuring instruments, mixed-signal processing, high-end consumer products, and many other industries.

Add Support for Silicon Labs EFR32FG23L

PEmicro Blogger (www.pemicro.com) — Fri, 13 Feb 2026 15:32:34 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG-HL-ARM software v9.94, PEmicro development and production programmers now support the Silicon Labs EFR32FG23L microcontrollers.

The EFR32FG23L contains a High Performance 32-bit 78 MHz ARM Cortex®-M33 with up to 128 KB of flash program memory. The EFR32FG23L Sub-GHz solution is an ultra-low power, cost-effective SoC designed with optimal flash and RAM for a diverse set of applications. The single die, multi-core solution, provides best-in-class link budget, low power consumption with fast wakeup times, and an integrated power amplifier to enable the next generation of secure connectivity for IoT devices. The FG23L provides efficiency and reliability, making it suitable for applications such as home and industrial automation, key fobs and smart city sensor nodes.

Add Support for Silicon Labs EFR32ZG23

PEmicro Blogger (www.pemicro.com) — Fri, 13 Feb 2026 15:21:29 EST

Source: www.pemicro.com

With the release of Cyclone software v11.68 and PROG-HL-ARM software v9.94, PEmicro development and production programmers now support the Silicon Labs EFR32ZG23 microcontrollers.

The EFR32ZG23 MCU contains a High-Performance 32-bit 78 MHz ARM Cortex®-M33 with up to 512 KB of flash program memory. While the EFR32ZG23 devices are the ideal solution for Z-Wave, they can also support other protocols including Wi-SUN, Amazon Sidewalk, and Wireless M-BUS IoT applications. The single die, multi-core solution, provides industry leading security, low power consumption with fast wakeup times, and an integrated power amplifier to enable the next generation of secure connectivity for IoT devices.

Legacy V1 license

PEmicro Blogger (www.pemicro.com) — Fri, 13 Feb 2026 11:53:19 EST

Source: www.pemicro.com

PEmicro software, like the ICD debugger and the PROG programmer, used to ship with a Version 1 "V1" software licenses (sometimes referred to as a legacy V1 license). This was a licensing allowing the software usage tied to a particular PC. These V1 licenses are no longer supported by PEmicro software. Only V2 hardware licenses are supported. What that means is that V1 license transfers/adjustments/modifications are no longer possible by the user or PEmicro staff. Users will need to purchase a new V2 license (V1 licenses are so old at this point that promotional upgrade pricing is no longer available). The V2 license is tied to the PEmicro Multilink and Cyclone hardware and not the PC giving the user more flexibility.

The blogpost about updates to PROG software licensing can be found here: https://www.pemicro.com/blog/index.cfm?post_id=191

The blogpost about updates to ICD and PKG software licensing can be found here: https://www.pemicro.com/blog/index.cfm?post_id=215

It is recommended to users to check their multilink or cyclone hardware whether it can support V2 licenses. They can do so by reading our blogpost about it here:
https://www.pemicro.com/blog/index.cfm?post_id=212

V1 license is identified by the license installation code starts with the value "V1"

V2 license is identified by the license installation code starts with the value "V2"

It is recommended that users read our transition guide for hardware so they know what to expect with the latest hardware offerings:

https://www.pemicro.com/blog/index.cfm?post_id=284

https://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320187

STMicroelectronics: Securing STM32U0, STM32U3, and STM32U5 Devices with RDP

PEmicro Blogger (www.pemicro.com) — Sun, 30 Nov 2025 12:37:57 EST

Source: www.pemicro.com

PEmicro's development tools and production programmers now support Life-cycle management with readout protection (RDP) for the STM32U0, STM32U3, and STM32U5 device families. The RDP mechanism enables secure protection over the devices memory and debug access varying by the RDP level. The protections provided by each RDP level is described in the Table below:

The RDP level can be trasitioned to a higher level by programming the RDP value in the user area of the option bytes. Regression of the RDP level can be accomplished by provisioning the OEM password to verify access.

This article will explore how this process is handled with our tools.

Will a new Hardware licenses for a specific software work with older versions of the software?

PEmicro Blogger (www.pemicro.com) — Wed, 29 Oct 2025 13:14:12 EST

Source: www.pemicro.com

As long as your older software supports hardware licenses, a new hardware license installed in a Multilink/Cyclone should enable it just fine. Essentially the check is, if the software build date is older than one year after the hardware license date and it matches the product, it is good.

Debug/Programming Communications Protocols

PEmicro Blogger (www.pemicro.com) — Tue, 28 Oct 2025 14:54:50 EST

Source: www.pemicro.com

Different families/architectures use different debug communications protocols. The protocols are used by the Multilinks and Cyclones as appropriate to program and debug the microcontrollers and microprocessors. Here is a summary by device manufacturer:

NXP

Kinetis is arm-based and uses the SWD or JTAG protocols.

S32 is arm-based and uses the SWD or JTAG protocols.

LPC is arm-based and uses the SWD or JTAG protocols.

i.MX is arm-based and uses the SWD or JTAG protocols.

HC08 uses the MON08 serial protocol.

HCS08 uses the Background Debug Mode protocol.

HC(S)12(X) uses the Background Debug Mode protocol.

S12Z uses the Background Debug Mode protocol.

ColdFire V1 uses the Background Debug Mode protocol.

ColdFire V2/V3/V4 uses the Background Debug Mode protocol.

RS08 uses the Background Debug Mode protocol.

Power MPC5xx/8xx uses the Background Debug Mode protocol.

DSC uses the JTAG and ONCE protocols.

CPU3xx uses the Background Debug Mode protocol.

Qorivva MPC5xxx uses the JTAG + Nexus protocols.

68HC16 uses the Background Debug Mode protocol.

MAC7xxx uses the JTAG protocol.

MCORE uses the JTAG protocol.

STMicroelectronics

SPC5 uses the JTAG + Nexus protocols.

STM8 uses the SWIM protocol.

STM32 is arm-based and uses the SWD or JTAG protocols.

Renesas

H8 and H8S/Tiny uses the OCD protocol.

MC16C and M16C80 uses the OCD protocol.

M32C uses the OCD protocol.

R8C uses the OCD protocol.

RH850 uses the JTAG protocol.

RL78 uses the Serial TOOL protocol.

RX600 uses the JTAG and FINE protocol.

Infineon

TriCore uses the DAP and JTAG protocols.

Other

Arm-based devices use the SWD or JTAG protocols.

Troubleshooting ColdFire V2/V3/V4 Communications

PEmicro Blogger (www.pemicro.com) — Fri, 24 Oct 2025 18:37:00 EST

Source: www.pemicro.com

Problem : I can't connect to my ColdFire V2, V3, or V4 device. I get the message "Device Detected:Generic 52xx".

Answer :

When your device is detected as "Generic 52xx," it usually indicates a communication problem between the debugger/programmer and the target ColdFire V2/V3/V4 device. This message often occurs when the PEmicro hardware can't read the device ID. This can be due to connection issues, signal noise, delays in the hardware setup, or custom adapters and cables causing problems.

Here are some suggestions:

1. Verify your hardware connections carefully. Make sure you are connecting all required pins for the ColdFire BDM interface on your device (e.g., all 26 pins if applicable).

2. If your device is a MCF5272 or the MCF5206E, this requires the use of the ColdFire synchronous adapter cable (PEmicro part # CABLE-CF-ADAPTER). This is a specialty ribbon cable with built in electronics to synchronize the debug signals. This is not needed for other ColdFire devices.

3. The debug communications speed may be too fast. This can happen if you are using the Multilink FX or the Cyclone FX. Try lowering the debug shift frequency in the connection manager or programming software settings. Lower speeds can often overcome signal integrity issues caused by extra hardware or longer cables.

4. There is a reset driver in the system which is affecting entry into debug mode. Specify a reset delay to make sure the PEmicro hardware waits after releasing reset and before attempting debug communications. A value of 300 (milliseconds) should work for most reset drivers.

5. Sometimes a target board connecting the PSTCLK signal to the debug connector can cause problems during debug communications (the PSTCLK is only necessary for the MCF5272 or MCF5206E). This is because the PSTCLK can be in the hundreds of MHZ and running it on a long ribbon cable will distort the signal and cause the MCU to no longer run properly.

6. If the target processor has a PSTALL signal instead of the four PST[3:0] signals, you should connect the PSTALL signal directly to all four PST[3:0] lines on the programmer/debugger debug header. This allows proper communication with the processor which only provides a single PSTALL output instead of separate PST0 - PST3 signals.

7. If you have an oscilloscope, check the signals on the BDM lines (RESET, BKPT, DSCLK, DSI, DSO) to confirm they toggle as expected according to the ColdFire debug protocol to enter debug mode.

8. If your device is a ColdFire V1 (such as 51QE96), the PROGCFZ software will detect the device as Generic 52xx because it is not designed for that device; you will need the PROGCFV1 software instead for proper support.

9. Verify the power in the target system is correct.

Determining Which Hardware (Multilink, Cyclone) is compatible with ICD, PROG, and UNIT software versions

PEmicro Blogger (www.pemicro.com) — Wed, 22 Oct 2025 15:17:03 EST

Source: www.pemicro.com

PEmicro sells several models of the Multilink and Cyclone Programmers. PEmicro also sells different flavors of the PROG, ICD, GDB, PKG, and UNIT software products. It can be confusing to the customer which hardware can be used with a specific orderable software. This is actually relatively easy to determine however.

Each of the orderable part numbers for the PROG (PROG Flash Programming Software), ICD (ICD In-Circuit Debugger Software), GDB (GDB Server Plug-In for Eclipse-based ARM IDEs), PKG (PKG Software Packages) and UNIT (UNIT Library Modules) products indicate which product families (architectures) they are designed to work with as well as which Multilink and Cyclone orderable part numbers support them. This information is on the Pricing tab of each product which lists all of the orderable part numbers for that software product and which architectures and hardware products (multilink and cyclone) are compatible.

NXP Semiconductor (formerly Freescale, Formerly Motorola) Device Support

PEmicro Blogger (www.pemicro.com) — Wed, 22 Oct 2025 15:14:25 EST

Source: www.pemicro.com

NXP Semiconductor (formerly Freescale, Formerly Motorola) Device Support

Part numbers are not case sensitive so ignore capitalization. Where programming is being done, for volume programming is done we generally recommend the Cyclone Programmer (any version) over the "PROG Flash Programming Software" as it is designed more for this scenario.

All algorithms are included in the Cyclone Installer as well as the appropriate PROG installer as well as coming with our plug-ins for many IDEs like CodeWarrior, MCU Xpresso IDE, and S32 design studio.

PEmicro supports NXP Arm devices as described here: https://www.pemicro.com/partners/index.cfm?manufacturer_id=1. This includes almost all devices in the families : MCX, LPC, i.MX RT, S32K, S32, and Kinetis. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-ARM also supports these devices with a Multilink LC/FX. Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development with NXP IDEs including NXP Codewarrior (older Kinetis parts), MCUXPresso IDE or MCUXpresso VSCode Plugin (for MCX, i.MX RT, LPC, and newer Kinetis Parts), and S32 Design Studio (for S32 devices). The debug protocols most used for these devices are JTAG and SWD.

Pemicro supports most NXP devices which start with FS32K. We refer to this family specifically as the S32K family or more broadly as part of the S32 Family (which supports more than just the K devices). Similarly we support some devices in the V, G, M, and N families as well (part numbers starting with FS32V, FS32G, FS32M, and FS32N). The customer can see specific device support here : https://www.pemicro.com/partners/index.cfm?manufacturer_id=1. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-ARM also supports these devices with a Multilink LC/FX. NXP S32 Design Studio with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

Pemicro supports all NXP devices which have 9s08 in the part number. We refer to this product family as the MCS08, HCS08, 9S08, or MC9S08 family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-HCS08 also supports these devices with a Multilink LC/FX. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

Pemicro supports all NXP devices which have 9s12z in the part number. We refer to this product family as the S12Z family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-S12Z also supports these devices with a Multilink LC/FX. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

Pemicro supports all NXP devices which have 9s12 or mc912 or hc12 in the part number but do not have a z character after the 12. We refer to these product families (there are two families the HC12 is a bit older and the parts with an "s" character are newer) as the HCS12 and HC12 families and sometime we refer to them generically as the HC(S)12(X) families of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-12Z also supports these devices with a Multilink LC/FX. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

Pemicro supports all NXP devices which have hc908 or hc08 or mc908 in the part number. We refer to this product family as the HC08 family of devices. We refer to the debug protocol specific to this family as MON08. The Cyclone FX and Cyclone LC support these parts for programming. Version 6 of NXP Codewarrior (a Legacy product) with a Cyclone LC/FX supports these devices for debug and development. The Multilink LC/FX does not support these devices.

PEmicro support all NXP devices with an mcf51 in the part number. We refer to this product family as the ColdFire V1 or ColdFire V1+ family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-CFV1 also supports these devices with a Multilink LC/FX. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

PEmicro support all NXP devices with an mcf52 or mcf53 or mcf54 in the part number. We refer to this product family as the ColdFire V2/V3/V4 family of devices which is comprised of the ColdFire V2 and ColdFire V3 and ColdFire V4 families. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-CFZ also supports these devices with a Multilink LC/FX. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

Pemicro supports all NXP devices which have 9rs08 in the part number. We refer to this product family as the RS08 family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The Cyclone FX and Cyclone LC support these parts. The "PROG Flash Programming Software" which has the part number PROG-HL-RS08 also supports these devices with a Multilink LC/FX as long as the ML-MLFX-RS08-ADPT adapter is installed. NXP Codewarrior with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development, though the Multilinks require the ML-MLFX-RS08-ADPT adapter whereas the Cyclone supports it directly.

Pemicro does not support NXP devices which start with mpc51 or mpc52.

PEmicro supports all NXP devices with an mpc55?? or mpc56?? or mpc57?? in the part number where the ? signifies a digit and not a letter. We refer to this product family as the Qorivva MPC5xxx or PPCNexus or MPC55xx or MPC56xx or MPC57xx family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-PPCNEXUS also supports these devices with a Multilink LC/FX. NXP S32 Design Studio with a Multilink LC/FX or Cyclone LC/FX supports these devices for debug and development.

PEmicro supports most NXP devices with an mpc5??X or mpc8??X in the part number where the ? signifies a digit and the X signifies any letter, but the customer may want to contact PEmicro to be sure. We refer to this product family as the Power MPC5xx/8xx family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-PPCZ also supports these devices with a Multilink LC/FX.

Pemicro does not support NXP devices which start with dsp56f8 or mc56f8??X in the part number where the ? signifies a digit and the X signifies any letter. These devices are an older DSP family which has the 56800 core which is not supported by pemicro (pemicro does support the newer 56800E/EF/EX cores as described next). PEmicro does supports all NXP devices which contain the 56f8??? or 56f8???? part numbers. We refer to this product family as the DSC family of devices. The Cyclone FX and Cyclone LC support these parts for programming. The "PROG Flash Programming Software" which has the part number PROG-HL-DSC also supports these devices with a Multilink LC/FX/DSC. NXP Codewarrior with a Multilink LC/FX/DSC or Cyclone LC/FX supports these devices for debug and development.

PEmicro supports most NXP devices which have a 68hc16 or 68hc916 in the part number. We refer to this product family as the 68HC16 family of devices or sometimes as the HC16 family. The Multilink FX support these parts for programming when used with the "PROG Flash Programming Software" which has the part number PROG-HL-16Z. The Multilink FX supports debugging these devices when used with the appropriate software.

PEmicro supports most NXP devices which have the MC683?? in the part number. We refer to this product family as the CPU3xx family of devices. The Multilink FX support these parts for programming when used with the "PROG Flash Programming Software" which has the part number PROG-HL-32Z. The Multilink FX supports debugging these devices when used with the appropriate software.

When we refer to the family name we sometimes also refer to it as the architecture. i.e. 68HC16 devices are part of the 68HC16 architect.

Added Support for Silicon Labs EFR32xG26 Microcontrollers

PEmicro Blogger (www.pemicro.com) — Tue, 21 Oct 2025 12:08:42 EST

Source: www.pemicro.com

With the release of Cyclone software v11.66 and PROG v9.91, PEMicro’s development and production tools now include support for Silicon Labs EFR32xG26 High Performance Wireless microcontrollers. The EFR32xG25 MCU is based on the ARM Cortex-M33 and designed for complex IoT solutions. This support includes the EFR32BG26 High-Performance Energy-Efficient Bluetooth LE family, the EFR32MG26 Multiprotocol Wireless SoC for Matter, and the EFM32PG26 Low power high-performance IoT Module with AI/ML Hardware Accelerator.

New device support added for the following part numbers: EFR32BG26B311F1024IL136, EFR32BG26B311F1024IM68, EFR32BG26B311F2048IL136, EFR32BG26B311F2048IM48, EFR32BG26B311F2048IM68, EFR32BG26B321F1024IM68, EFR32BG26B321F2048IM48, EFR32BG26B321F2048IM68, EFR32BG26B410F3200IM48, EFR32BG26B411F3200IM48, EFR32BG26B420F3200IM48, EFR32BG26B421F3200IM48, EFR32BG26B510F3200IL136, EFR32BG26B510F3200IM48, EFR32BG26B510F3200IM68, EFR32BG26B511F3200IL136, EFR32BG26B511F3200IM48, EFR32BG26B511F3200IM68, EFR32MG26B211F2048IM68, EFR32MG26B211F3200IM48, EFR32MG26B221F2048IM68, EFR32MG26B221F3200IM48, EFR32MG26B311F3200IL136, EFR32MG26B410F3200IM48, EFR32MG26B410F3200IM68, EFR32MG26B411F3200IM48, EFR32MG26B411F3200IM68, EFR32MG26B420F3200IM48, EFR32MG26B420F3200IM68, EFR32MG26B421F3200IM48, EFR32MG26B421F3200IM68, EFR32MG26B510F3200IL136, EFR32MG26B510F3200IM48, EFR32MG26B510F3200IM68, EFR32MG26B511F3200IL136, EFR32MG26B511F3200IM48, EFR32MG26B511F3200IM68, EFR32MG26B520F3200IM48, EFR32MG26B520F3200IM68, EFR32MG26B521F3200IM48, EFR32MG26B521F3200IM68, EFM32PG26B101F512IL136, EFM32PG26B101F512IM68, EFM32PG26B301F1024IL136, EFM32PG26B301F1024IM68, EFM32PG26B301F2048IL136, EFM32PG26B301F2048IM68, EFM32PG26B500F3200IL136, EFM32PG26B500F3200IM48, EFM32PG26B500F3200IM68, EFM32PG26B501F3200IL136, EFM32PG26B501F3200IM48, EFM32PG26B501F3200IM68