R5560 Base Update Packet

Software update for the base (controller) board of an R5560 rack digitizer that is already installed. It updates the base display and control application and the x5560 web dashboard without touching the operating system or the settings of the board. The packet is uploaded from the web dashboard (manually or with the online update) and is applied at the next reboot. The DAQ boards of the rack have their own update packets.

Compatibility

ProductBoardVariantDeviceOperating system
R5560base (controller) board, Enclustra Mars ZX2all (A, B, D)Zynq 7010PetaLinux 2020.1 base image (r5560-base-image)

Not for: the R5560SE base board (use r5560se-base-update-packet) and the DAQ boards (use r5560-a-daq-update-packet or r5560-b-daq-update-packet according to the variant).

What's in this package

ArtifactFileOS / architecture
r5560-base-update-packetR5560_Base_Update.BSUlinux-zynq / armhf

The .BSU file is a gzip-compressed tar archive with an installation script, run_update.sh, and an update/ folder. At the next boot the base board extracts it into /ni and the script installs:

Content of update/Installed toPurpose
r5560se_displayapp.elf/ni/software/base display and control application (touch display, rack I/O, clock, sync, pulser, DAQ management over PPP)
dashboard/ni-dashboard, ni-dashboard-loop.sh, config.example.json, VERSION, keys//ni/software/x5560 web dashboard server and the public keys used to verify signed update packets
ni-dashboard-www//ni/software/ni-dashboard-www/x5560 web dashboard user interface
legacy_web.json/ni/settings/legacy_web.jsonmoves the internal web server of the display application to 127.0.0.1:8080, behind the dashboard (only on an operating system that starts the dashboard, see below)

The script then sets the permissions of /ni and deletes update/ and itself. Network, routing, pulser, analog and dashboard settings in /ni/settings and /ni/ni-dashboard are kept.

On boards whose operating system does not yet start the x5560 dashboard, the packet installs it but the existing web interface stays in use on port 80; the full dashboard becomes active with an operating system image that includes it (r5560-base-image).

How to install

From the web dashboard (manual upload)

  1. Download R5560_Base_Update.BSU from NI Packages to the PC.
  2. Open the dashboard of the base board at http://<base-ip>/ or https://<base-ip>/ and log in. At the first login with the factory default password the dashboard asks for a new password.
  3. Open Device Update and, under Manual update, choose or drop the .BSU file.
  4. The board reads the file header and shows format, product, board, version and whether the packet is compatible. A .BSU packet is shown as "Legacy update (unsigned)": install it only if it comes from NI Packages or another trusted source.
  5. Click Upload and stage. The packet is verified and staged; the page shows the staged update, which can still be discarded.
  6. Reboot the base board with the Reboot button (administrator) or by a power cycle. The update is applied during the next start-up. Do not turn off the device until the procedure ends.

Online update (FOTA)

The online update uses the Internet connection of the PC running the browser; the base board itself does not need Internet access.

  1. Open Device Update on the base dashboard and click Check for updates. The browser asks https://downloads.nuclearinstruments.eu for the latest release of r5560-base-update-packet and shows its version and changelog.
  2. Click Download and install: the browser downloads the packet, verifies its SHA-256 checksum and uploads it to the board, as in a manual upload.
  3. Reboot the base board to apply it.

Without the dashboard

On a base board whose operating system does not yet start the x5560 dashboard, upload the .BSU file with the update function of the existing web interface. The installation at the next boot is the same.

Check the result

  1. After the reboot open Device Update again: Last result shows time, version and success or failure of the update.
  2. On Device Status check the dashboard version.
  3. On the Rack page check that the DAQ boards are listed and reachable.

Requirements

  • An R5560 base board running the base operating system image (PetaLinux 2020.1).
  • A PC with a browser that reaches the base board over Ethernet.
  • A dashboard account. By default the upload works for any logged-in user; the reboot from the dashboard needs the administrator (root). An administrator can also copy an update token from the Security page for update tools that work without login.
  • For the online update: Internet access on the PC running the browser.

Versioning and releases

  • Versions use the date format YYYY.MM.DD.NN (for example 2026.10.11.00).
  • Every release lists its changes in the changelog shown with the release on this portal and in the online update.
  • Release channel on this portal: stable.

Related packages

PackageRelation
r5560x-base-display-appdisplay and control application contained in the packet
x5560-dashboard-backendweb dashboard server contained in the packet
x5560-dashboard-frontendweb dashboard user interface contained in the packet
r5560-base-imagecomplete SD card image of the base board (factory programming, recovery)
r5560-a-daq-update-packet, r5560-b-daq-update-packetupdate packets of the DAQ boards of the rack

Known limitations and notes

  • The packet does not update the operating system, the FPGA bitstream or the boot loader of the base board: these change only with a new r5560-base-image.
  • The packet uses the legacy unsigned format; when the board is configured to accept only signed updates it is refused.
  • The factory copy of /ni stored in the operating system image is not changed by the packet. If the board ever restores /ni from the factory copy, apply the update packet again.
  • The update is applied at the next start-up: a staged packet has no effect until the board is rebooted.

Source and support