Reflash v1.2.0

From iagent
Jump to: navigation, search

Release candidate - Reflash v1.2.0 is not final

Reflash v1.2.0-RC1 is a pre-release for testing, and installs Rebuild v1.2.0 (also at release candidate stage). It may still change before v1.2.0. For the current release, see Reflash v1.1.0.

Reflash header.png

Reflash is a Linux image for downloading and installing Rebuild and Refactor images on Recore. You can also create an image from the contents of the eMMC.

Reflash v1.2.0 is the release where Reflash also sets the printer up: the Wi-Fi, the hostname, the password and the configuration are chosen in Reflash, and the installed system carries them out.

For the previous release, see Reflash v1.1.0, which has the instructions for entering FEL mode and for writing Reflash to a USB drive. They are the same for v1.2.0, except for the image's name, reflash-v1.2.0-RC1.img.xz, which is on the release page.

What is new in v1.2.0

Set up printer

A Set up printer bar under the install flow opens one panel for everything Reflash can set:

  • Network: Wi-Fi mode (automatic, client or hotspot), the network, and the hotspot's name and password. A new image's Wi-Fi can be copied from Reflash, copied from the eMMC, or typed in.
  • Location: country and time zone.
  • Accounts: the debian login password, SSH on or off, and the hostname (the .local name).
  • Display: screen rotation.
  • Config archive: save, upload, download, delete and install, with a file tree to choose which files go in or out.
  • Optional software: LED effects, installed on the new image when there is an internet connection.

Every option has a Default box, and an option that is left alone sends nothing. For an installed system, hostname, SSH, country, time zone and display rotation can be read from the eMMC and written to it.

Wi-Fi

  • Wi-Fi, SSH and screen rotation are one set of settings, held by Reflash and by the installed system and kept the same. When Reflash starts it reads the installed system's, so there is nothing to carry over.
  • A Manage Wi-Fi dialog scans live and handles the switch from hotspot to client. When Reflash is opened by an IP address, Connect now warns that the address may change and offers the board's .local name instead, keeping the chosen network.
  • The info panel's Network rows follow Wi-Fi changes without a reload, and the Options slider has a button for Reflash's own Wi-Fi again.

Config backups

  • Backups of the configuration files are on the main screen: the eMMC heading chooses between the whole eMMC and Config files, and the install side chooses Default config or an archive from the USB drive. A configuration can be installed alone, into the system that is already installed.
  • A Rebuild v1.0 or v1.1 system can be backed up from Reflash, so its configuration can move to a new release.
  • A Files window shows what is on the USB drive. Long names are shortened in the middle, and the integrity mark and Delete have their own place.
  • Installing a configuration while the USB drive is changing mode no longer fails with "the backup is not on the USB drive": an already mounted drive is remounted in place.

Boards

  • Reflash picks the board's device tree with fdtfile= in armbianEnv.txt, not a link that a kernel update puts back. This keeps A6 boards' STM32 reachable after Rebuild's kernel updates.
  • The STM32's serial line is available under Reflash on every board (UART2 for A7 and A8, UART4 for A5 and A6), so the new image can flash the STM32 while it is being installed, instead of on its first boot.
  • The thermal limits match Rebuild's (throttling from 75 °C and harder at 85 °C), and the GPU runs at 180 MHz.
  • The installer is the one the image ships, so a new image is installed the way that image wants to be installed.

Known issues

A USB drive that is not detected

On some boards the USB drive is not enumerated at boot. Reflash waits for the drive and counts the wait on screen, and names a drive that never appears as broken. If it never appears, power the board off completely - a reset is not always enough - and try again, or try a different drive. This is tracked as Reflash issue #88.

Kossel-A7 (A7 0374)

One A7 has not come up after being flashed until it was power cycled, see Rebuild issue #166. Other boards have not shown it.

Contributing

Bug reports and pull requests are welcome at GitHub. If you use an AI assistant to write the patch, see AI-assisted contributions.