R5560-B DAQ Production Image

Production image of the R5560-B DAQ board (Zynq 7035). It contains everything needed to program a new or fully re-initialised DAQ board: the boot image (BOOT.BIN), the OS installer, the operating system (PetaLinux 2019.2) and the content of the data partition with the DAQ applications, the x5560 web dashboard, the Resource Explorer, the FPGA test firmware of the variant and its default MCA firmware.

It is intended for production and service. Boards already in the field are updated with the update packet r5560-b-daq-update-packet instead (see Related packages).

Compatibility

Not for: R5560-A (Zynq 7030, use r5560-a-daq-image), R5560-D (Zynq 7045, use r5560-d-daq-image); the R5560 base (controller) board (use r5560-base-image); R5560SE DAQ boards (use r5560se-a-daq-image / r5560se-b-daq-image). A complete R5560 rack also needs the base board image r5560-base-image: every Zynq has its own image.

What's in this package

r5560-b-daq-image.tar.gz is a gzip-compressed tar archive with six files at the top level:

Note the two image.ub: in this archive image.ub is the installer; on the programmed board image.ub on the boot partition is the operating system (os_image.ub renamed by the installer).

BOOT.BIN

Built with bootgen from bootgen.bif, in this order:

The bitstream in BOOT.BIN is the test firmware; the MCA firmware is never part of BOOT.BIN.

Data partition (r5560_sdcard.tar.gz)

Extracted at the root of the data partition, mounted as /mnt/sdcard on the running board (owner root, numeric ids):

How to install (production)

The installation runs over Ethernet from a TFTP server with the fixed address 192.168.60.15. All content of the SD card of the board is erased.

1. Download r5560-b-daq-image.tar.gz from NI Packages and extract it.

2. Put os_install.sh, os_image.ub and r5560_sdcard.tar.gz in the root directory of the TFTP server at 192.168.60.15. The server must also accept uploads: the installer sends its log files back.

3. Connect the Ethernet port of the DAQ board to the same network (192.168.60.0/24).

4. Boot the board with BOOT.BIN and the OS installer image.ub of this package (the loading method depends on the factory programming setup and is not part of this package).

5. The OS installer sets eth0 to 192.168.60.2, downloads os_install.sh from 192.168.60.15 and runs it, logging to /tmp/logsetup.log.

6. os_install.sh then:

   1. unmounts and deletes all partitions of the SD card (/dev/mmcblk0);
   2. creates partition 1 (512 MB, bootable) and partition 2 (rest of the card) and formats both as ext4;
   3. mounts partition 1 on /mnt/boot and partition 2 on /mnt/sdcard;
   4. downloads os_image.ub into the boot partition and renames it image.ub;
   5. downloads r5560_sdcard.tar.gz into the data partition and extracts it there;
   6. saves a factory copy of the data partition on the boot partition: /mnt/boot/factory/sdcard-factory.tar.gz plus /mnt/boot/factory/VERSION (version= the release of this image, source=r5560_sdcard.tar.gz, installed= date and time); a failure here is only a warning;
   7. deletes the downloaded r5560_sdcard.tar.gz;
   8. writes the U-Boot environment in flash (/dev/mtd1, offset 0x0, size 0x20000): bootargs = console=ttyPS0,115200 root=/dev/ram0 rw earlyprintk mem=768M, mmcboot = load mmc 0 ${netstart} image.ub;bootm ${netstart}, bootcmd = run mmcboot, and ethaddr;
   9. unlocks the boot flash partition (flash_unlock /dev/mtd0);
   10. prints ##NI_OS-Installation-Completed## and uploads logsetup.log and setup_completed.log to the TFTP server.

   After each phase the script writes a step code to an I2C port expander (bus 1, address 0x20), ending with 0x00. If a step fails it writes the reason to setup_error.log, uploads logsetup.log and setup_error.log to the TFTP server and stops.

7. Check on the TFTP server that setup_completed.log arrived (otherwise read setup_error.log). os_install.sh does not reboot the board: restart it. U-Boot then runs mmcboot and starts the operating system from the SD card.

First boot of the installed board

At every boot the start script of the operating system:

1. checks and mounts the data partition on /mnt/sdcard (if it cannot be repaired, it is reformatted and restored from the factory copy);
2. loads /mnt/sdcard/etc and programs firmware.fpga into the FPGA;
3. brings up Ethernet and the USB network gadget and starts the x5560 web dashboard;
4. if the FPGA is programmed, opens the PPP link to the base (192.0.0.<slot+2>) and starts adcinit.elf, the system manager and nibridge; otherwise it stays in recovery mode, where the dashboard is still available to install a firmware.

Open the dashboard of the board at http://<daq-ip>/ or https://<daq-ip>/, or from the Rack page of the R5560 base dashboard. The accounts user and root ship with the factory default password; the dashboard forces a password change at the first login. The first root login on the console or SSH also asks for a new root password.

Requirements

• An R5560 DAQ board of variant B (Zynq 7035) with an SD card; all data on the card is erased.
• A TFTP server at 192.168.60.15 that serves the files of this package and accepts uploads, reachable from the board Ethernet port (the installer uses 192.168.60.2).
• The means to load BOOT.BIN and the OS installer on the board (factory programming setup).

Versioning and releases

• Version format: YYYY.MM.DD.NN, for example 2026.10.11.00.
• The changelog (CHANGELOG.md) is shown with each release on this portal.
• Release channel on this portal: stable.
• On the board the release of the image is recorded in /mnt/boot/factory/VERSION; the dashboard reports it as the factory version in its storage status (GET /api/v1/system/storage). The Device Status page shows the versions of the dashboard, software, operating system and device daemon.

Related packages

Known limitations and notes

• The installation erases and repartitions the whole SD card of the board.
• os_install.sh does not write BOOT.BIN to the boot flash: BOOT.BIN is programmed as part of the factory setup.
• The TFTP server address 192.168.60.15 and the board address 192.168.60.2 are fixed in the installer.
• The factory copy on the boot partition is written only by this image. Update packets do not refresh it: if the data partition is ever rebuilt from it, the board returns to the software of the production image and the latest update packet has to be installed again.
• The FPGA starts with the test firmware; the MCA firmware in user_firmware/ is installed and activated from the dashboard Firmware page.
• zynq_fsbl.elf at the top of the archive is the boot loader built with the operating system; BOOT.BIN contains the USB-capable boot loader of r5560x-daq-fsbl-usb instead.

Source and support

• Development repository: https://gitlab.lanni/nuclear-instruments/prodotti/x5560/fw-sw/r5560/r5560-b-daq-image
• For support contact Nuclear Instruments / CAEN support.