AsRock BIOS Update Procedure

Applies to motherboard models starting with “IMB-…”, “NUC-…” and others. If unsure, please contact OnLogic Tech Support.

Warning: Never interrupt a BIOS update. If the update is interrupted, the system may become irreparable. Damage caused as a result of BIOS updates may not be covered by the system’s warranty.

Booting MS-DOS from a USB drive can be useful for applying BIOS updates and other tasks.

Required Tools

• USB flash drive (32GB or smaller)

• A Windows 7/10 PC

Creating the drive

• Download the Rufus tool from

• Launch Rufus

• Under “Device” select your USB drive

• Under “Boot selection” choose “FreeDOS”

• Click START at the bottom of the window

• Double check you have selected the correct drive and press OK to proceed

• When the status bar says READY, the process is complete

• Copy any files you will need in DOS to the flash drive. If you are applying a BIOS update, copy those files now.

• Eject and unplug the flash drive

• Connect the flash drive to the target PC and power it on. Go into the BIOS (Typically F2/Del/Esc) and set it as the primary boot device.

• On newer systems, it is necessary to enable CSM / legacy boot mode as shown.

• If successful, you will be greeted with the familiar old DOS prompt.

• Use the dir command to confirm what files are on your USB drive.

• Update .bat files can be executed by typing the filename.

OnLogic offers a simple utility for updating the microcontroller firmware on your Karbon 300 or Karbon 700 series computer. You can find versions for both Windows and Linux systems below.

Note: You can also update your system firmware using the ‘s ‘update’ subcommand.

Quickstart

Updating a system BIOS to the latest version from the EFI takes just a few steps: ● Format an empty USB flash drive ● Copy the update files to the drive ● Reboot into the UEFI menu and boot the drive ● Complete the BIOS update

Creating the USB Flash Drive

To update your system BIOS from an EFI shell, you will first need to create a bootable USB drive. Below are the steps to do this using either Windows or Linux as your operating system:

Windows

Attach the USB drive that you are able to erase to the system. You should see it appear in File Explorer:

Configure the options to format the drive as FAT32. When ready, click ‘start’. (WARNING: This will destroy all data on the drive)

Once the operation completes, copy the EFI folder (and any other files) from this update package to your drive.

Format a USB flash drive as FAT32 using the Disks utility, using the gparted application, or from the command line:

1. Determine the correct drive $ lsblk

2. Unmount the device (suppose the device is sdx1) $ sudo umount /dev/sdx1

3. Format the drive as FAT32 (suppose the device is sdx1) $ sudo mkfs.vfat -F 32 /dev/sdx1

Then copy the files from this update folder to the formatted partition using any method.

In order to access the system’s UEFI/BIOS menu, you will need to reboot your system. While it is restarting, press the UEFI hotkey (usually ESC, F2, or DEL), until the UEFI menu appears.

Once the menu is open, select and boot from the newly created USB drive. Refer to the system manual or system bios manual for specific instructions about this step for your system. On some systems, you may need to enable “USB Booting” before you can load the EFI Shell from the drive.

***Please note that having Secure Boot Enabled will prevent the BIOS update from proceeding. Please disable Secure Boot before attempting to boot from the USB drive or the security policy will block the boot device***

After the EFI Shell on the drive has booted, wait five seconds for the system to auto detect the update script. When it completes, you will be prompted to review the update and press any key to continue or ‘q’ to quit.

Confirm the update, and wait for the BIOS update to complete. When it finishes, your system should reboot automatically. If it does not, reboot the system now; the BIOS upgrade is now complete.

Applies to: DI-Series, DS-Series, DX-Series, P2000-Series

• Copy the BIOS files to a FAT32 formatted flash drive

• Insert the flash drive into the Cincoze unit

You can use this process to install updated microcontroller (MCU) firmware on your model system. You will need the updated Microcontroller firmware, which is available on the specific system’s page. Make sure to download the Microcontroller firmware before proceeding.

Download the ZMU utility for deploying the updated microcontroller firmware

1. Download the ZMU utility with the link above and copy zmu-windows-x86_64.exe from it to the desktop.

Some touchscreens require additional drivers to work on Ubuntu and similar OS distributions. This page will guide you through the installation.

Download the driver files from the following link and save to the downloads folder.

Use the tar command to extract the archive. Tip: Type “tar -zxvf eGT” and press tab. The rest of the filename will be autofilled.

CD into the newly created folder.

use chmod to make the setup.sh file executable and then run it with ./

1. Download and run the firmware update utility from the link above.

2. Download the firmware binary from the link above and click the Browse button to select it to install. The example image is for version 0.3.7, but your version may be different.

3. Select the firmware file and click the Update button.

You can use this process to install updated power sequence microcontroller firmware on your model system. You will need the updated power sequence microcontroller firmware, which is available on the specific system’s page. Make sure to download the power sequence microcontroller firmware before proceeding.

Downloads

Download the power sequence update utility for deploying the updated power sequence microcontroller firmware.

Updating Firmware on Windows

How will the certificates be updated?

Typically this is performed by the Operating System’s update manager (Windows updates, or the respective update manager in a Linux distribution), meaning that systems deployed in the field that receive regular OS updates most likely already have the new certificates enrolled. Alternatively for systems that may not have an internet connection, the new certificates can be enrolled manually

OS Specific Updates

Windows Updates

Microsoft has provided some info on how to audit your Secure Boot status in windows. The recommended update path for Windows users is to leverage Windows Updates to handle the new certificate enrollment.

Linux

Update managers differ between linux distributions but ultimately rely on the fwupd tool to manage system firmware updates. If the fwupd command is not present in a linux OS, then the OS’s package manager can be used to install fwupd.

In Ubuntu, fwupd can be installed via:

sudo snap install fwupd

Note: make sure fwupd is version 2.1.0 or later. Once installed the fwupdmgr can be used to query and initiate the certificate update:

hx500@hx500-CometLake:~$ fwupdmgr get-updates
 Updating lvfs
 Downloading… [***]
 Successfully downloaded new metadata:
<..> 
 ├─UEFI CA:
 │ │ Device ID: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
 │ │ Current version: 2011
 │ │ Vendor: Microsoft (UEFI:Microsoft)
 │ │ GUIDs: 26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
 │ │ c34a7e6a-bd86-5244-8bd0-7db66fd3c073 ← UEFI\CRT_E30CF09DABEAB32A6E3B07A7135245DE05FFB658
 │ │ Device Flags: • Internal device
 │ │ • Updatable
 │ │ • Supported on remote server
 │ │ • Needs a reboot after installation
 │ │ • Signed Payload
 │ │ • Can tag for emulation
 │ │
 │ └─Secure Boot Signature Database Configuration Update:
 │ New version: 2023
 │ Remote ID: lvfs
 │ Release ID: 116503
 │ Summary: UEFI Secure Boot Signature Database
 │ License: Proprietary
<..> 
 │ Description:
 │ This updates the 3rd Party UEFI Signature Database (the "db") to the latest release from Microsoft.It also adds the latest OptionROM UEFI Signature Database update.

Manual updates

Microsoft has made the new certificates . Once downloaded customers will need to convert the x509 certificate (.crt file) into a DER encoded format (.cer file). This can be done with the openssl tool in Windows or Linux

The syntax for conversion is:

openssl x509 -outform DER -in <input_filename>.crt -out <output_filename>.cer

Example using one of the downloaded certificates:

Once converted, the .cer file can be placed on a USB flash drive and manually loaded in to the UEFI by going to the “Administer Secure Boot” menu, choosing the respective certificate repository (KEK, and db) and choosing “enroll”

After choosing the enroll option, navigate to the USB stick that has the DER formatted certificates and select it. You may be prompted for an owner UUID which is provided for each certificate on the .

Once enrolled the new certificate will show in the repository

Manuals and Downloads

Raspberry PI Imager

Raspberry Pi Firmware Tool (for eMMC)

Configuration Files (required when installing an OS):

Bullseye 32bit files- Download Bullseye 64bit files – Download

Bookworm 32bit files- Download Bookworm 64bit files – Download

**If installing to FR202, you will need to add the lines to the config.txt file noted in the section below for Bullseye

• To get started, connect a keyboard, mouse, and monitor before powering up the system.

• If you purchased the standard 60 watt power supply, it will be pre-wired and ready for use.

• For the Din rail power supply, connect the wires as shown below. V+ to the red wire, V- to the black.

• Use a flathead screwdriver to loosen the terminals to accept the wires. Insert the wires and then tighten the terminals back down.

• On the system side, depress the orange tabs and slide the wires in.

This section covers what to expect the first time you power your system on.

If you did not select an operating system when ordering, the system will boot up to a diagnostic splash screen. You can install an operating system using the steps further down on this page.

• Log in to the default pi account with the password “raspberry”

• Enter “raspberry” again (it is asking for the current password to enable changing it.)

• Enter a new password. Note that it must be different from the default or it will error out.

• Enter the new password again to confirm

• You will be greeted with the Raspbian welcome screen.

• Configure localization information

• Click next to skip the redundant password change dialog. It will keep the password you set earlier.

• Compete the setup wizard and the unit is ready for use.

The Lite version of Raspberry PI OS (Raspbian) boots straight to a login prompt.

• Log in with the following credentials:

• username: pi

• password: raspberry

• You will be prompted to change the default password on first login. re-enter “raspberry” as the current password, and then set your new password.

• Click on the “Ubuntu” user

• Enter the default password – “ubuntu”

• Enter the default password again – “ubuntu”

• Create a new password

• Click next and complete the setup wizard.

• Your system is now ready for use.

Ubuntu server boots straight to a login prompt.

• Log in with the following credentials:

• username: ubuntu

• password: ubuntu

• You will be prompted to change the default password on first login. re-enter “ubuntu” as the current password, and then set your new password.

• Remove the 3 M3x4mm screws from the bottom of the system.

• Lift up the bottom lid starting from the side with the OnLogic label

• You now have access to the FR200 motherboard. Components such as the TPM, storage drives, and wireless modules

• It is recommended not to disassemble the unit any further unless absolutely necessary. Further disassembly has greater potential to cause warranty voiding damage. Use caution.

• Remove the 3 5mm standoffs from the system.

• Gently pop the bottom plate off and gently remove the WiFi pigtail (if equipped)

• The CM4 module is held in by x2 M2 screws.

• To remove the module, remove the x2 screws and lift straight up.

• Use caution as the connector is fragile.

• Re-install the module by lining up the screw holes. Gently pop it down into the sockets.

• Ensure the thermal pads and EMI gasket are still attached and in the shown locations.

• Set the system onto the bottom plate, aligning the screw holes.

• Re-install the x3 brass standoffs. Hand tighten and do not over torque. They can sheer off if too much force is applied.

• Line up the two pegs of the bottom plate first, then hinge it into place.

• Re-install the M3 screws into the bottom of the chassis.

• Remove the 7 M3x4mm screws from the bottom of the system.

• Remove the bottom bottom lid by lifting straight up.

• Remove the internal storage cooler. Note that it “hooks” around the I/O board.

• You will now have access to the I/O board. This connects to the FR202 motherboard via the Raspberry Pi GPIO connector (shown below on the LEFT). Note that models with LCD screens will have the x2 additional connectors (shown below on the RIGHT). Remove the x4 5mm hex standoffs to loosen the I/O board. You can now disconnect the GPIO connector to get access to the FR202 motherboard. &#xNAN;*Note: If your system has an LCD, be careful of the x2 additional connectors on the right.

• You now have access to the FR200 motherboard. Components such as the TPM, storage drives, and wireless modules

Factor series systems currently support Ubuntu 20.04, Ubuntu 22.04, Ubuntu 24.04, and Raspberry Pi OS (Bullseye and Bookworm) OSes. Other OSes or versions may not install or function properly.

Follow the steps below to install one of these operating systems. Make sure to verify if your system has eMMC storage or not. Many systems shipped from OnLogic have the OS installed onto the M.2 SATA drive.

A USB flash drive smaller than the system’s storage is required for this method. Example: The Factor system has 32GB storage. The flash drive must be 16GB or smaller.

• Begin by downloading the .

• Click on “CHOOSE OS”

• Select your desired image. In most cases, you will want the default “Raspberry Pi OS

• Click on “CHOOSE STORAGE”

• Select your flash drive from the list

• Click “WRITE”

• Double check that this is the correct drive and choose “YES”

• If an error occurs, try using the erase function from the imager’s “operating system” menu

• Erase function shown

• The image writing process will begin. This takes some time.

• Success!

• Access the “boot” partition in your file browser and locate the config.txt file. You will need to replace the config.txt with the OnLogic one, and add usercfg.txt to the “boot” directory. Note that there are differences between 32 bit and 64 bit, so download your preferred file from here:

Bullseye 32bit files- Bullseye 64bit files –

Bookworm 32bit files- Bookworm 64bit files –

• Unplug the flash drive from the computer and plug it into the single blue USB 3 port on the Factor unit.

• Plug in the factor unit and it should boot up to the flash drive. It may restart automatically once or twice to configure everything.

• Complete the setup wizard with the desired settings.

• Configure localization information

• Click next if you wish to keep the current password (default: raspberry)

• Launch terminal from the panel in the top left

• Run the “lsblk” command

• In this example, our flash drive is SDA M.2 drive is SDB, and onboard eMMC storage is mmcblk0.

• We will now clone the flash drive onto the desired storage drives. Following the example above, run a DD command:

• Install to SATA M.2: sudo dd if=/dev/sda of=/dev/sdb status=progress

• Install to eMMC: sudo dd if=/dev/sda of=/dev/mmcblk0 status=progress

• An error saying “no space left on device” means that your flash drive was too big. It needs to be smaller than the drive you are installing to.

• Success!

• The terminal will show the amount of data copied and then drop to a prompt.

• Shut down the system and unplug your flash drive.

• Power the system back on and it will boot up into the operating system. The installation is now complete.

Follow this method if your Factor unit is equipped with onboard eMMC storage.

• Remove the 3 M3x4mm screws from the bottom of the system.

• Lift up the bottom lid starting from the side with the OnLogic label

• Locate the 6 pin jumper block.

• It should already have a jumper installed on it.

• Move the jumper from its default position onto the “Boot DIS” pins as shown.

• This tells the CM4 module to go into bootloader mode and allows flashing of the internal storage over USB-C.

• Connect the USB-C port to another computer.

• Connect power to the unit.

• Download and install the from the links at the top of this page.

• Type rpiboot into the start menu and launch the rpiboot program

• A terminal window will appear. It will automatically run a few commands and then close.

• If the terminal stays at this stage, that means the PI was not detected. Double check jumper placement. Confirm power is connected to the unit and try a different USB cable.

• If successful, the eMMC storage will be given a drive letter. Windows can not read it as it contains a Linux filesystem. Do not format it. The Raspberry PI imaging tool will be used instead.

• Download the Raspberry Pi imager using the link at the top of this page.

• Launch it from the start menu

• Click on “CHOOSE OS”

• Select your desired image. In most cases, you will want the default “Raspberry Pi OS”

• Click on “CHOOSE STORAGE”

• Select the RPI-MSD disk from the list. This is the Pi’s internal eMMC storage.

• Click “WRITE”

• Double check that this is the correct drive and choose “YES”

• If an error occurs, try using the erase function from the imager’s “operating system” menu

• Erase function shown

• The image writing process will begin. This takes some time.

• Success!

• Unplug the USB-C cable and then plug it back in.

Access the “boot” partition in your file browser and locate the config.txt file. You will need to replace the config.txt with the OnLogic one, and add usercfg.txt to the “boot” directory. Note that there are differences between 32 bit and 64 bit, so download your preferred file from here:

Bullseye 32bit files- Bullseye 64bit files –

Bookworm 32bit files- Bookworm 64bit files –

• Restore the jumper to its original position.

• Line up the two pegs of the bottom plate first, then hinge it into place.

• Re-install the M3 screws into the bottom of the chassis.

• Boot up the Factor unit. It will reboot once or twice to configure itself.

• You will be greeted with the Raspbian welcome screen.

• Configure localization information

• Click next if you wish to keep the current password (default: raspberry)

• Compete the setup wizard and the unit is ready for use.

A USB flash drive smaller than the system’s storage is required for this method. Example: The Factor system has 32GB storage. The flash drive must be 16GB or smaller. The Factor series systems are compatible with Ubuntu versions 20.04, 22.04, and 24.04 (both Desktop and Server). Other versions are not supported and may present errors during installation or general use. You can review the supported OS in the .

• Download the Raspberry Pi imager using the link at the top of this page.

• Launch it from the start menu

• Select the “Other general-purpose OS” category

• Click On Ubuntu and select a supported version (more information above on supported versions).

• Click Skip Customization

• Select your flash drive from the list and write to it. Click “WRITE”

• Double check that this is the correct drive and choose “YES”

• Note: If error occurs, use the erase function to format drive and start again.

• The image writing process will begin. This takes some time.

• Success! but the configuration needs to be modified to boot properly.

• Unplug the flash drive and then plug it back in.

• The boot partition should show up with a drive letter.

• If it doesn’t, you may need to assign one manually via Disk Management or Diskpart.

Ubuntu Config Files:

• Eject the boot partition

• Unplug the flash drive from the computer and plug it into the single blue USB 3 port on the Factor unit.

• Power on the Factor unit and wait for the login prompt.

Log in to the newly installed OS. See default credentials referenced in section above (typically ubuntu/ubuntu)

• Open a terminal

• Run the “lsblk” command

• In this example, our flash drive is SDA, the M.2 drive is SDB, and onboard eMMC storage is mmcblk0.

• We will now clone the flash drive onto the desired storage drives. Following the example above, run a DD command:

• Install to M.2: sudo dd if=/dev/sda of=/dev/sdb status=progress

• Install to eMMC: sudo dd if=/dev/sda of=/dev/mmcblk0 status=progress

• An error saying “no space left on device” means that your flash drive was too big. It needs to be smaller than the drive you are installing to. Use a different flash drive and set it up again.

• If completed successfully, the terminal will show the amount of data copied and then drop to a prompt.

• Shut down the system and unplug your flash drive.

Installing Ubuntu is a bit more involved than Raspberry Pi OS. Configuration files need to be edited manually or the operating system will not boot properly.

The Factor series systems are compatible with Ubuntu versions 20.04 and 22.04 (both Desktop and Server). Other versions are not supported and may present errors during installation or general use. You can review the supported OS in the .

Follow this method if your Factor unit is equipped with onboard eMMC storage.

• Remove the 3 M3x4mm screws from the bottom of the system.

• Lift up the bottom lid starting from the side with the OnLogic label

• Locate the 6 pin jumper block.

• It should already have a jumper installed on it.

• Move the jumper from its default position onto the “Boot DIS” pins as shown.

• This tells the CM4 module to go into bootloader mode and allows flashing of the internal storage over USB-C.

• Connect the USB-C port to another computer.

• Connect power to the unit.

• Download and install the “Firmware Tool” from the links at the top of this page.

• Type rpiboot into the start menu and launch the rpiboot program

• A terminal window will appear. It will automatically run a few commands and then close.

• If the terminal stays at this stage, that means the PI was not detected. Double check jumper placement. Confirm power is connected to the unit and try a different USB cable.

• If successful, the eMMC storage will be given a drive letter. Windows can not read it as it contains a Linux filesystem. Do not format it. The Raspberry PI imaging tool will be used instead.

• Download the Raspberry Pi imager using the link at the top of this page.

• Launch it from the start menu

• Select the “Other general-purpose OS” category

• Click On Ubuntu

• Scroll down to and select a of Ubuntu

• For 32-bit Ubuntu installations, select Server even if you want Ubuntu Desktop. The desktop will be installed later.

• Select the RPI-MSD disk from the list. This is the Pi’s internal eMMC storage.

• Select your RPI-MSD disk from the list and write to it. Click “WRITE”

• Double check that this is the correct drive and choose “YES”

• Note: If error occurs, use the erase function to format drive and start again.

• Success! but the configuration needs to be modified to boot properly.

• Unplug the USB-C cable and then plug it back in.

• The boot partition should show up with a drive letter. If it doesn’t, you may need to assign one manually via Disk Management or Diskpart.

Ubuntu Config Files:

• Eject the boot partition

• Unplug the power and USB cable from the Factor unit

• Restore the jumper to its original position.

• Line up the two pegs of the bottom plate first, then hinge it into place.

• Re-install the M3 screws into the bottom of the chassis.

• Power up the unit and it will boot into Ubuntu. Log in with the following credentials:

• username: ubuntu

• password: ubuntu

You will be prompted to change the password. Enter a new password. Your system is now set up and ready to use.

32bit Ubuntu Desktop can not be installed directly. You must first install Ubuntu Server using one of the methods above. Once server is up and running, the following procedure will install the desktop environment.

• Log in to the system

• Run ‘sudo apt update’

• Run ‘sudo apt install ubuntu-desktop’

• Type Y and press enter at the prompt.

The CM4 module has a hardcoded boot order of eMMC > SATA M.2 > USB. This can be problematic if the image on the eMMC or SATA M.2 becomes corrupted or needs to be erased for other reasons. The simple solution is to erase the boot partition. This can be done one of two ways.

Note that this method can only by used to wipe eMMC storage, not a SATA M.2

• Remove the 3 M3x4mm screws from the bottom of the system.

• Lift up the bottom lid starting from the side with the OnLogic label

• Locate the 6 pin jumper block.

• It should already have a jumper installed on it.

• Move the jumper from its default position onto the “Boot DIS” pins as shown.

• This tells the CM4 module to go into bootloader mode and allows flashing of the internal storage over USB-C.

• Connect the USB-C port to another computer.

• Connect power to the unit.

• Download and install the “Firmware Tool” from the links at the top of this page.

• Type rpiboot into the start menu and launch the rpiboot program

• A terminal window will appear. It will automatically run a few commands and then close.

• If the terminal stays at this stage, that means the PI was not detected. Double check jumper placement. Confirm power is connected to the unit and try a different USB cable.

• If successful, the eMMC storage will be given a drive letter. Windows can not read it as it contains a Linux filesystem. Do not format it. The Raspberry PI imaging tool will be used instead.

• Download the Raspberry Pi imager using the link at the top of this page.

• Launch it from the start menu

• Click on “CHOOSE OS”

• Scroll down and click on “erase”

• Click on “CHOOSE STORAGE”

• Select the RPI-MSD disk from the list. This is the Pi’s internal eMMC storage.

• click “WRITE”

• Double check that this is the correct drive and choose “YES”

• The storage has now been erased.

• Proceed to one of the operating system installation guides on this page.

If the Linux image on the Factor unit is still bootable, you can use the terminal to erase the boot partition.

• Run the lsblk command to list the storage devices

• In this example, the boot partition is stored on /dev/mmcblk0p1

• The following command will copy zeroes over that partition, effectively wiping it and preventing the Pi from booting to it.

sudo dd if=/dev/zero of=/dev/mmcblk0 status=progress

A SATA M.2 storage drive will likely show up as sdb, so this command will wipe the M.2’s boot partition:

sudo dd if=/dev/zero of=/dev/sdb status=progress

Once the drive wipe has completed, proceed to one of the operating system installation guides on this page.

The FR200 series serial mode can be controlled by configuring the embedded FTDI EEPROM. You will need to install the utility before updating the serial mode.

• Install required libraries: sudo apt install libconfuse-dev libusb-1.0-0-dev and build tools: sudo apt install cmake build-essential

• Download the latest libFTDI Source .tar.bz2 from the Intra2Net page here: | Example: wget https://www.intra2net.com/en/developer/libftdi/download/libftdi1-1.5.tar.bz2

• Download the configuration file for your required mode:

  • – wget static.onlogic.com/resources/firmware/documentation/configs/FR200_RS232.conf

  • – wget static.onlogic.com/resources/firmware/documentation/configs/FR200_RS422.conf

With the serial port configuration enabled, the port will now enumerate as /dev/ttyUSB[x], where [x] is the port number. This is typically /dev/ttyUSB0, but may be enumerated differently depending on other USB devices connected. You can also identify the serial port chip via the hardware ID, which is F81439A.

The TPM is an optional Nuvoton-based hardware add-on for the FR200 series systems.

You can download the required Device Tree files and Readme installation instructions from here:

Important notes about Factor PoE (Power Over Ethernet) PD setup and the various revisions of the module.

• Do not connect both power inputs at the same time. Only connect x1 power connection (either PoE OR terminal block).

• Review specific details in the specific models below\

The ADP125 is an isolated PoE PD (powered device) modules. Factor series systems configured and shipped in August 2024 or later have this version of the module. This offers isolation/protection from transient voltage of up to 100KV.

Factor Series systems configured with PoE PD modules and shipped before August 2024 will use the ADP122. Important notes about Factor PoE (Power Over Ethernet) setup when using the ADP122 addon module:

• Do not connect both power inputs at the same time. Only connect x1 power connection (either PoE OR terminal block).\

The ADP122 is a non-isolated PoE PD (powered device) module. The FR200 product family provides a ground scheme that isolates digital and chassis ground. Downstream equipment may modify this ground scheme by shorting chassis and digital ground together within the cabling or attached circuitry. Downstream or upstream devices that depend on isolated digital and shield/chassis grounds may experience performance degradation as a result of this equipment.

In the event of a break in ground scheme due to installation environment and connected equipment, there is no safety concern. However, equipment that depends on ground isolation for protection or measurement may experience loss of performance including, but not limited to, inaccuracy of power measurement or power delivery or equipment damage.

You can review additional details in the Errata document below:

If you are having issues accessing the RTC, especially after installing a new operating system, you will need to add these lines to your config.txt file:

You can also refer to the Raspberry PI CM4 documentation for more info. Section 2.13 under "Real time clock (RTC)" at this link:

Functions listed in this FR202 Features section are in addition to the Factor Series Features section above, and for the FR202 system only. The below features and not available on the FR201 platform.

Note: For the best experience, always update to the latest firmware version before testing these commands.

The FR202 Digital IO is connected to the CM4 via a virtual USB-CDC-ACM serial port; you can see that the USB device is detected using lsusb and OnLogic’s USB Vendor ID:

lsusb -d 353f:

Data can be sent to the device over its virtual serial port, which will be available in /dev :

ls /dev | grep ACM

The serial port can operate either as an interactive UART terminal, or as an endpoint for raw byte commands.

The FR202’s UART shell supports line editing, history, and TAB completion. Digital inputs and outputs are collected into groups, and dio commands are performed on those groups.

For instance, DO_G0 is “Digital Output Group 0”. A complete list of devices can be produced by running device list. Once you have selected a device, dio commands may be run:

To exit the interactive terminal and enter byte-processing mode, run the byte_mode command.

For information about other terminal commands, see:

When using byte mode, DIO commands are sent in the form of command packets, and each command will receive a status (and optional data) as a response.

The command header is eight bytes in length:

All command headers must indicate the type of data to follow, by setting the command kind:

Each command sent will recieve a response from the microcontroller. This response may contain data, but can always be examined to determine if the command succeeded.

The DIO command format is as follows:

The digital IO command supports the following actions:

A sample application demonstrating some simple features of the display is provided for each of the supported Operating systems here:

On systems pre-installed with an OS from OnLogic, the display demo files are located under /usr/sbin/demo-display and /etc/systemd/system/demo-display.service

Pieces of this sample package are referenced in the display sections following. It also ships on all OnLogic-provided Pi OS and Ubuntu software images, enabled by default. To disable it, run sudo systemctl disable demo-display from a terminal window.

If you have deployed Bookworm onto your Factor unit since receiving it you may see the demo program not work right away. If you see this behavior please type `raspi-config` in the Linux terminal, select `Interface Options` then select `I2C` and enable it.

Display Controller:

Controlling the Backlight

Touch Controller:

Display backlight is controlled by an i2c expander at 0x3C on I2C1.

The OnLogic-provided utility “fr202-i2c” can control the backlight with the commands:

Enable: fr202-i2c set p7v6_shdn 0

Disable: fr202-i2c set p7v6_shdn 1

A list of other controllable signals is available in the help text for the tool. It is provided with the display code samples as well as

The backlight can also be enabled using the i2ctools utilities as follows:

Configure GPIO IC: i2cset -y 1 0x3c 0x03 0x81

Enable: i2cset -y 1 0x3c 0x01 0xbf

Disable: i2cset -y 1 0x3c 0x01 0xff

pip install st7789

apt install python3-rpi.gpio python3-spidev python3-pil python3-numpy

The provided python example “demo-display” demonstrates the use of Python’s PIL and the ST7789 display library to display static images and text. It runs as a service in OnLogic-provided Pi OS and Ubuntu installations as well.

pip install opencv-python

apt install libatlas-base-dev

pip install -U numpy

The separately provided “st7789-video” demonstrates the use of opencv’s video library to show a video on-screen. By default, the sample is configured to read and display a video called “test.avi” in the same folder as the application. A video is not provided.

The ADC is attached to SPI 4 CS0. Look for this device name in your OS hardware list. Example:

/dev/spidev4.0

The ADC part number is LTC2448; a description of the SPI protocol can be found in the device manual .

An example of accessing the ADC can be found in the FR202-demo program as well. You can download it from . Search for “adc” in the demo-display file for examples.

All ADC channels are differential and configured as follows: ANALOG IN 0: Channel 0+1

ANALOG IN 1: Channel 2+3

ANALOG IN 2: Channel 4+5

ANALOG IN 3: Channel 6+7

TEMPERATURE 0: SENSOR Channel 8+9, REFERENCE Channel 10+11

TEMPERATURE 0: SENSOR Channel 12+13, REFERENCE Channel 14+15

***This has been resolved with a new image deployment as of Mid-August 2025 but systems from January-August 2025 may still experience this issue and will require the workaround below or a reimage***

Starting in the beginning of 2025, our Raspberry Pi OS image files had an automatic service included to help manage the FR202 display. Services are programs that automatically launch and run in the background in Linux operating systems. This service is included in both the FR201 and FR202 as they utilize the same motherboard/processing units, and therefore have the same image files. We had found that this specific service can lead to error messages on the FR201 as it is searching for hardware that is not present in the system. This can lead to larger than necessary log files, which can consume storage space unnecessarily.

On the FR202 this service makes the LCD screen show the screen-test outputs, and the demo-display files can be modified to match the specific use case. This service identifies the FR202 hardware and runs properly, but on FR201s it fails since that hardware is not present. When it fails, this results in repeated lines of errors captured in the OS error logs. Essentially, it can consume storage space, and may cause concerns for those who are unaware.

The OS images this affects are our Raspberry Pi OS images (full/lite, and 32/64 bit). The original revision images were used through the end of December 2024, with the new revision that includes this service starting to be used at the beginning of January 2025. Ubuntu does not have the service included.

Because of our OS file management, FR201s and FR202s use the same image files. This means that the demo-display and service setup always happen, regardless of the system model. We recommend disabling the service in the following cases:

• User has an FR201

• User has an FR202 and doesn't have/want to use the LCD

For those that want to see if the service is running, they can run the following command:

systemctl list-units --type=service --state=running

If the service is running, and it needs to be disabled, the following two commands should be run:

sudo systemctl stop demo-display.service sudo systemctl disable demo-display.service

To check if the demo-display file is installed, it is located under the /usr/sbin directory.

If you are encountering general issues with your FR200 series system, such as the Real-Time-Clock (RTC) disconnecting, various ports not being detected, or features not working as expected, make sure you’re using the OnLogic provided config.txt and usercfg.txt files. These add additional functionality to the system, and allow the Raspberry Pi CM4 module to properly interface with the OnLogic designed FR200 series daughterboards. You can download the files from the section above.

You should make sure that any Factor (FR201 and FR202) units have the following lines in the config.txt file:

For the FR202 specifically, you will also need to ensure the config.txt file includes:

CPU Panic error messages may be see during/after an OS installation due to using an older or malfunctioning USB drive. Please make sure to use a USB 3.0 drive or newer, installed into the USB 3.0 slot on the Factor system. A different USB drive may also need to be used.

If one of the Ethernet ports is not detected or shows as Disabled in Ubuntu, you can follow these steps to add it into Netplan and enable it.

1. Run the following command:

1. Look for the Logical name, which is required in the next step, and run the following commands

1. Add the logical name (found in Step 2) to the 50-cloud-init.yaml file. See an example below:

1. Close and save, then run the following commands

If the TPM modules is not working properly, refer to the section above for installing and configuring the necessary files.

Booting Ubuntu via USB may result in a black screen if the eMMC has an OS image on it. Wiping the eMMC and/or M.2 drive is recommended if that is encountered.

Some operating system versions require different config.txt settings to make the power indicator light function. If your Factor unit is otherwise functional, but the power indicator light is not lighting up, this is likely an issue with the config.txt file. Look for the following lines in the file:

Replace those lines with

If you’re seeing issues using the FR202 LCD display, or seeing errors when running the FR202-demo scripts, make the following changes to your config.txt file:

Delete/comment out:

dtparam=spi=on

Add:

dtoverlay=spi4-1cs dtoverlay=spi3-1cs,cs0_pin=24 dtoverlay=i2c5,pins12_13=on,baudrate=40000

After making any changes, save and restart the operating system.

The Factor’s CM4 compute module has a built-in Wi-Fi antenna that it uses by default instead of the attached external antenna. The config file /boot/firmware/config.txt (or /boot/config.txt depending on your OS) may need to be updated for the CM4 to use the external antenna to connect to Wi-Fi instead of its internal one. To do this, open the specified config file and add the line ‘dtparam=ant2’, save, and then reboot your system. This should provide a noticeable improvement in Wi-Fi speeds.

In a Factor with 4G LTE and Wi-Fi, there can be an issue where the devices “compete” for priority over each other, preventing them from connecting properly to the internet. To resolve this, you will need to set the priorities for the devices in the ‘/etc/dhcpcd.conf’ file for the Raspberry Pi OS and in the netplan configuration for the Ubuntu OS. You can do this by entering the following into the configuration file:

interface wlan0 metric 100 interface eth0 metric 200

The lower the metric, the higher priority. So in this example, the WIFI device (wlan0) will take priority over the ethernet. What that is doing is ensuring that the WIFI device’s default route is being used to route network traffic. The customer may need to set priorities for each network device, which for Factor is eth0, eth1, wlan0, and usb0, where usb0 is the AMIT card.

The Out-of-Box version of the following operating systems on the FR200 systems can encounter issues with the NWK300 modem where you may not be able to set up the modem properly:

• Raspberry Pi (Bullseye)

• Raspberry Pi Lite (Bullseye)

• Ubuntu Desktop/Server 20.04 - 32 Bit

• Ubuntu Desktop/Server 22.04

The issue can be resolved by running an OS update. Run the command:

'sudo apt update && sudo apt upgrade'

And the system should be able to use the modem normally. This issue is not present in the Bookworm or Ubuntu 24.04 operating systems.