DT5560 Production Image

Complete set of files used in production to install the software of a DT5560 desktop digitizer (Zynq 7030): boot image, OS installer, operating system, installation script and the data partition with applications, x5560 web dashboard, SDK bridge, Resource Explorer, display logo and FPGA firmware. The installation runs over Ethernet from a TFTP server and erases the SD card of the instrument. Instruments already in the field are updated with dt5560-update-packet instead.

Compatibility

The image does not program the Intel MAX10 FPGA of the DT5560 base board: its firmware is in dt5560-max10-base-firmware.

What's in this package

dt5560-image.tar.gz contains six files:

dt5560-image-overlay.tar.gz is the default content of the data partition (network, settings and USB setup files listed below) published on its own; dt5560-update-packet takes usb.sh from it.

BOOT.BIN

Data partition (dt5560se_sdcard.tar.gz)

Empty folders software/user, etc, firmware, fwupgrade and www are also created.

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 instrument is erased.

1. Download dt5560-image.tar.gz from NI Packages and extract it.

2. Put image.ub, os_install.sh, os_image.ub and dt5560se_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. BOOT.BIN must already be programmed in the boot flash of the board (the programming method is not part of this package).

4. Connect the Ethernet port of the DT5560 to the same network (192.168.60.0/24) and power it on.

5. On a board without a saved U-Boot environment, U-Boot uses its default settings (board address 192.168.60.2, server 192.168.60.15) and default command: it saves its environment, downloads image.ub (the OS installer) from 192.168.60.15 over TFTP and starts it.

6. 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.

7. 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 dt5560se_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=dt5560se_sdcard.tar.gz, installed= date and time); a failure here is only a warning;
   7. deletes the downloaded dt5560se_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.

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

First boot of the installed instrument

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) and runs a staged update, if any;
2. loads /mnt/sdcard/etc and runs the firmware manager, which checks the MAX10 base FPGA and applies a pending MAX10 update;
3. programs firmware.fpga into the Zynq FPGA, loads the network configuration, brings up Ethernet and the USB network gadget and starts the x5560 web dashboard;
4. if the FPGA is programmed, starts adcinit, the display application and nibridge; otherwise it stays in recovery mode, where the dashboard is still available to install a firmware.

Open the dashboard at http://<dt5560-ip>/ or https://<dt5560-ip>/. 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

• A DT5560 with BOOT.BIN of this package in its boot flash and an SD card (all its content is erased).
• A TFTP server at 192.168.60.15 on the same Ethernet network as the instrument, with read and write access.
• Credentials: the factory default password of the root and user accounts, to be changed at the first login.

Versioning and releases

• Releases are tagged with the date format YYYY.MM.DD.NN, for example 2026.10.11.00.
• The release version is written into os_install.sh and stored on the instrument in /mnt/boot/factory/VERSION.
• The changelog (CHANGELOG.md) is shown on NI Packages with each release.
• Release channel on this portal: stable.

Related packages

Known limitations and notes

• The installation erases the whole SD card, including settings and user firmware.
• The TFTP server address 192.168.60.15 and the board address 192.168.60.2 are fixed.
• The MAX10 base board firmware is not part of this image.
• The Software version shown on the Device Status page of the dashboard is read from sys_version.json and does not show the release number of this image; the release is recorded in /mnt/boot/factory/VERSION.

Source and support

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