1. Think twice

Please have a look at the PCR2 Firmware Changelog to find out if a new firmware does add any functionality you want.

Never update a system that is running perfectly. 

NOTE: Hardware Revisions 03, 04, 05 is needed. Please find 1714-PCB0000-03 or 1714-PCB0000-04 or 1714-PCB0000-05 printed on the electronic board of your PCR2.

2. Firmware Update using Batch-Script

Contact your reseller for getting the latest DFU archive for your device. Your reseller will support you with the update process.

If you have purchased the device directly from Parametric, please write to and specify the serial number of the device.

Put device into DFU mode

  1. Connect a USB-MicroUSB to CONFIG port of your PCR2
  2. Press and hold the BOOT Button 
  3. While holding the BOOT button plug the other end to your Windows 10 PC
  4. The device will enter DFU mode.

    No LEDs blinking and you should find either "STM Device in DFU Mode" or "STM BOOTLOADER" in Windows Device Manager under USB Devices.

Start Device Firmware Update

Unpack the firmware archive and execute Update.bat

DFU will start with erasing the device...

... and then programming the new firmware


3. Extra steps when updating from V3.x to V4.x 

If you are updating the firmware from a V3 firmware such as V3.12.0 to V4.x.x you need to execute following additional steps. Otherwise ignore this chapter

Connect to PCR2 using RealTerm

Connect the cable to PCR2 and PC and open a terminal emulation tool such as RealTerm.

Open Windows Device Manager and look for the Serialport number of your PCR2.

Select the port and open it in RealTerm

Tick 'Half Duplex' to see also the commands you send.

Set DeviceType  

Choose the command sequence for your device from the table below.
Type the commands into the input fields and then click 'Send ASCII". Enable +CR+LF. 


If you own a......execute
set type 0
set type 1
set type 4
set type 5
set type 6
set type 7
set type 8


Set LoRaWAN Region

All LoRaWAN regions are included in the same firmware now and can be switched on request.

You need to set the region once when updating from a firmware prior V4.0.0

If you own a......execute
set conntype 1
set conntype 2
set conntype 3
set conntype 4

Check device type string

After unplug/replugging the device you may check the device type string by sending a get typestr command.


Windows USB Driver Issues

If you plug in a device, for the vast majority of Windows users the driver installation just works fine. 

However, for some of our customers the automatic driver installation does not work or an old driver is still installed and needs to be removed. It is definitely not fun to fumble around in the driver hell of Windows. Therefore we recommend using the Zadig Tool to clean up.

Install WinUSB Driver with Zadig

Zadig is a Windows application that installs generic USB drivers, such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices. It is also useful to uninstall broken drivers.

  • Download Zadig from here:
  • Open Zadig and choose Options>List All Devices to show all USB devices
  • Connect your device while holding the BOOT button
  • Select "STM32 BOOTLOADER" or "STM32 Device in DFU Mode"
  • Select "WinUSB" and press the "Replace Driver" button
  • Try again with the update procedure above

Further Issues

Our updaters use the DFU mechanism integrated in all STM32 microcontrollers.

DFU mode is started by holding the "BOOT" button while powering the device. 

When device is in DFU mode you should see  "STM Device in DFU Mode" or "STM32 BOOTLOADER" under USB-Controller when opening Windows Device Manager.

If this is not the case please follow all steps below before contacting Parametric's Support.

  • Use Windows 10
    Our tools are developed and tested with Windows 10 (64Bit) only.

  • Admin Rights
    Make sure your account does have the rights to install device drivers. Check with your PC Admin.

  • Connect USB cable directly
    Do not use an USB extension cable or USB hub between your PC and the device.

  • Use another USB cable
    Retry with another USB-to-MicroUSB cable as your cable could be broken or of bad quality or does not have the data lines at all.

  • Use another PC
    Please try the same procedure with another PC or notebook.

  • Try with another device
    If you do have another device handy, try the same procedure