User Tools

Site Tools

한국어

comfilepi:raspbian:index

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
comfilepi:raspbian:index [2026/07/09 07:14] – [Flashing the eMMC via a USB Cable] mfranklincomfilepi:raspbian:index [2026/07/10 04:23] (current) – [Install an OS by Booting from a USB Drive] mfranklin
Line 5: Line 5:
 The OS is intended to provide a practical starting point for developing and deploying ComfilePi-based industrial solutions, using familiar Windows, Linux, and Raspberry Pi tooling to install packages, configure services, and develop applications. The OS is intended to provide a practical starting point for developing and deploying ComfilePi-based industrial solutions, using familiar Windows, Linux, and Raspberry Pi tooling to install packages, configure services, and develop applications.
  
-**Existing Solutions**: For solutions already deployed on an older OS release, it is recommended to no upgrade to at later OS unless there is a compelling reason to do so. Prior releases are available in the [[comfilepi:raspbian:os_archive:index|OS archive]]. 
  
-**New Solutions**: For new development, using the latest ComfilePi OS release is recommended. 
  
  
Line 14: Line 12:
  
 The ComfilePi Trixie OS contains several improvements and changes over prior releases.  Please see the [[comfilepi:trixie:index|ComfilePi Trixie OS]] for more information. The ComfilePi Trixie OS contains several improvements and changes over prior releases.  Please see the [[comfilepi:trixie:index|ComfilePi Trixie OS]] for more information.
 +
 +**Existing Solutions**: For solutions already deployed on an older OS release, it is recommended to no upgrade to at later OS unless there is a compelling reason to do so. Prior releases are available in the [[comfilepi:raspbian:os_archive:index|OS archive]].
 +
 +**New Solutions**: For new development, using the latest ComfilePi OS release is recommended.
  
 ^  Download Link                                                                                                ^  Release Date  ^  Supported Models                          OS Word Size  ^                                                  ^ ^  Download Link                                                                                                ^  Release Date  ^  Supported Models                          OS Word Size  ^                                                  ^
Line 47: Line 49:
  
  
-==== Booting from a USB Drive to Install an OS Image ====+==== Install an OS by Booting from a USB Drive ====
  
 === CPi-C/G/J/S === === CPi-C/G/J/S ===
  
-The CPi-C/G/J/S panel PCs can boot from a USB drive.  Therefore, it is possible to boot from a ComfilePi OS installed on a USB drive, and from there, flash the SD Card/eMMC/NVME drive locally.  This method is **//much//** faster than writing the OS image to the ComfilePi over a USB cable.   +The CPi-C/G/J/S panel PCs can boot from a USB drive.  Therefore, it is possible to boot from a ComfilePi Trixie OS installed on a USB drive, and from there, flash the SD Card/eMMC/NVME drive locally.  This method is **//much//** faster than writing the OS image to the ComfilePi over a USB cable.  
- +
-<html><center><iframe width="800" height="480" src="https://www.youtube.com/embed/2ooBcTkZjzc" title="ComfilePi emmc install" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe></center></html> +
  
 Procedure: Procedure:
-  - From a workstation PC, use a disk imaging utility to write the ComfilePI OS to a USB drive.  Be sure to update the ///boot/firmware/config.txt// file with the model-specific one in the //bootfs// partition.+  - From a workstation PC, use a disk imaging utility to write the ComfilePi OS to a USB drive.  Be sure to update the ///boot/firmware/config.txt// file with the model-specific one in the //bootfs// partition.
   - If the ComfilePi already has an existing OS installed, make it unbootable using one of the following methods:   - If the ComfilePi already has an existing OS installed, make it unbootable using one of the following methods:
     * If the ComfilePi boots from an SD card, simply eject the SD card.     * If the ComfilePi boots from an SD card, simply eject the SD card.
Line 64: Line 63:
     * For the CPi-C/G/S panel PCs it is also possible [[https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#edit-the-configuration|change the bootloader's configuration]] to try booting from the USB drive first, before booting from the SD Card/eMMC, but it is recommended to keep the default bootloader configuration.     * For the CPi-C/G/S panel PCs it is also possible [[https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#edit-the-configuration|change the bootloader's configuration]] to try booting from the USB drive first, before booting from the SD Card/eMMC, but it is recommended to keep the default bootloader configuration.
   - Boot from the USB drive, and wait for it to fully initialize and boot to the desktop.   - Boot from the USB drive, and wait for it to fully initialize and boot to the desktop.
-  - Once booted from the USB drive, enable SSH. 
   - Copy the OS image you wish to write to the ComfilePi's boot device to a directory on the USB drive using one of the following methods:   - Copy the OS image you wish to write to the ComfilePi's boot device to a directory on the USB drive using one of the following methods:
-    * Use ''scp'' or a utility like FileZilla to copy the OS image from a desktop computer to the ComfilePi.   +    * Enable SSH on the ComfilePi, and use ''scp'' or a utility like FileZilla to copy the OS image from a desktop computer to the ComfilePi.   
-    * If the OS image is stored on a web server, use a utility like ''curl'' or ''wget'' to download the OS to a directory on the USB drive.  +    * If the OS image is stored on a web server, use a utility like [[https://manpages.debian.org/trixie/curl/curl.1.en.html|curl]] or [[https://manpages.debian.org/trixie/wget/wget.1.en.html|wget]] to download the OS to a directory on the USB drive.  
     * Use a second USB drive to store your source OS image(s) and connect it to the ComfilePi after it has been booted from the first USB drive.     * Use a second USB drive to store your source OS image(s) and connect it to the ComfilePi after it has been booted from the first USB drive.
-    * Prior to booting from the first USB drive, you can add a 4th partition to the USB drive to copy OS images to.+    * Prior to booting from the first USB drive, add a 4th partition to the USB drive to copy the source OS images to it.
   - Open the //Backup/Restore// application form the //ComfilePi// menu.   - Open the //Backup/Restore// application form the //ComfilePi// menu.
   - Select the //Restore// option.   - Select the //Restore// option.
Line 83: Line 81:
  
  
-==== Flashing the eMMC via a USB Cable ====+==== Installing an OS Using a USB Cable ====
  
 === CPi-A/B/C/G/S === === CPi-A/B/C/G/S ===
Line 99: Line 97:
 === CPi-J === === CPi-J ===
  
-CPi-J panel PCs do not have a USB device port for programming the eMMC.  Use the method to [[#booting_from_a_usb_drive_to_install_an_os_image|boot from a USB drive]] instead.+CPi-J panel PCs do not have a USB device port for programming the eMMC.  Use the method to [[#install_an_os_by_booting_from_a_usb_drive]] instead.
  
  
Line 113: Line 111:
  
 To configure passwordless SSH authentication, configure the //ssh_authorized_keys// field as described in this [[https://docs.cloud-init.io/en/latest/reference/yaml_examples/ssh.html|cloud-init documentation]]. To configure passwordless SSH authentication, configure the //ssh_authorized_keys// field as described in this [[https://docs.cloud-init.io/en/latest/reference/yaml_examples/ssh.html|cloud-init documentation]].
-==== Bookworm and earlier ==== 
  
-The latest Raspaberry Pi Imager program removed the ability to customize custom OS images, so you will need to use v1.9.6 or earlier to configure first boot initialization.+[[:comfilepi:rpi_imager_replace_userid:index|Bookworm and Earlier]]
  
-To replace the //pi// user and/or password, use the [[https://downloads.raspberrypi.com/imager/imager-1.9.6.exe|Raspberry Pi Imager v1.9.6]], press the gear icon and set a new username and password in the //Advance Options// screen before writing the OS to the SD card or eMMC. 
  
-{{ :comfilepi:raspbian:replace_user_gear.png?500 }} 
  
-{{ :comfilepi:raspbian:replace_user_password.png?500 }} 
  
 ===== Creating an OS Image for Backup and/or Cloning ===== ===== Creating an OS Image for Backup and/or Cloning =====
- 
-==== Win32DiskImager ==== 
- 
-After customizing an OS by changing settings, adding/remove software, etc. you may want to create a clone of the OS to provision additional panel PCs.  If using a Windows PC, consider using [[https://sourceforge.net/projects/win32diskimager/|Win32DiskImager]] to //Read// the SD card or eMMC disk to an image file (.img), and then use that resulting image file to provision additional ComfilePi panel PCs. 
- 
-{{ :comfilepi:raspbian:custom_os_image_backup.png }} 
  
 === The Backup/Restore Application === === The Backup/Restore Application ===
Line 137: Line 125:
 {{  :comfilepi:raspbian:cpi-backup-restore.png }} {{  :comfilepi:raspbian:cpi-backup-restore.png }}
  
-The backup procedure uses [[https://manpages.debian.org/trixie/gdisk/sgdisk.8.en.html|sgdisk]] and [[https://manpages.debian.org/trixie/fsarchiver/fsarchiver.8.en.html|fsarchiver]] to backup the partition table and partitions respectively, and package them into a .tar archive.  One advantage of this method is that it is possible to untar the .tar archive, and manually edit the partition table backup file to change the size or layout of the partitions.+The backup procedure uses [[https://manpages.debian.org/trixie/gdisk/sgdisk.8.en.html|sgdisk]] and [[https://manpages.debian.org/trixie/fsarchiver/fsarchiver.8.en.html|fsarchiver]] to backup the partition table and partitions respectively, and packages them into a .tar archive.  One advantage of this method is that it is possible to untar the .tar archive, and manually edit the partition table backup file to change the size or layout of the partitions.
  
 Using the //Backup/Restore// application to restore the .tar archive also provides the ability change the disk UUIDs, reinitialize the machine ID (e.g. to recreate unique SSH keys), and offer a final dialog to select the appropriate config.txt file (e.g. if clone from one ComfilePi model to another). Using the //Backup/Restore// application to restore the .tar archive also provides the ability change the disk UUIDs, reinitialize the machine ID (e.g. to recreate unique SSH keys), and offer a final dialog to select the appropriate config.txt file (e.g. if clone from one ComfilePi model to another).
  
 +==== Win32DiskImager ====
 +
 +After customizing an OS by changing settings, adding/remove software, etc. you may want to create a clone of the OS to provision additional panel PCs.  If using a Windows PC, consider using [[https://sourceforge.net/projects/win32diskimager/|Win32DiskImager]] to //Read// the SD card or eMMC disk to an image file (.img), and then use that resulting image file to provision additional ComfilePi panel PCs.
 +
 +{{ :comfilepi:raspbian:custom_os_image_backup.png }}
  
 [[comfilepi:index|ComfilePi - Industrial Raspberry Pi Panel PC]] [[comfilepi:index|ComfilePi - Industrial Raspberry Pi Panel PC]]
comfilepi/raspbian/index.1783581260.txt.gz · Last modified: by mfranklin