ZimaBoard Quick Start
Overview
This section provides Eclipse Kura™ quick installation procedures for the ZimaBoard and the Kura development environment.
Warning
This quickstart will install the version of Kura with the administrative web UI and network configuration support but not CAN bus support. For more information on this please visit the Eclipse Kura download page
This quickstart has been tested using the latest Ubuntu 24.04.3 LTS Live Server for amd64 architecture flashed on the SD card with balenaEtcher.
Eclipse Kura™ Installation
To install Eclipse Kura with its dependencies on the ZimaBoard, perform the following steps:
-
Boot the ZimaBoard with the latest Ubuntu 24.04 LTS Server image.
-
Make sure your device is connected to internet.
-
Upgrade the system:
-
Download the Kura package with:
wget http://download.eclipse.org/kura/releases/<version>/kura-<kura-version>_generic-<arch>_installer.debNote: replace
<version>in the URL above with the version number of the latest release (e.g. 5.6.0) and<arch>with your device architecture (i.e.x86_64in this case) -
Install Kura with:
All the required dependencies will be downloaded and installed.
Known Issues
dhclient apparmor profile
On Ubuntu 24.04 with NetworkManager and DHCP (IPv4), a network interface fails to obtain an IPv4 address automatically. The issue is due to this bug.
To fix it, the AppArmor configuration has to be updated as follows:
- edit the
/etc/apparmor.d/sbin.dhclientfile and add the following lines in the main section: - add the following at the end of the file:
# Added to fix dhclient /usr/libexec/nm-dhcp-helper { #include <abstractions/base> #include <abstractions/dbus> /usr/libexec/nm-dhcp-helper mr, /run/NetworkManager/private-dhcp rw, signal (send) peer=/sbin/dhclient, /var/lib/NetworkManager/*lease r, signal (receive) peer=/usr/sbin/NetworkManager, ptrace (readby) peer=/usr/sbin/NetworkManager, network inet dgram, network inet6 dgram, }
named failing to start
On Ubuntu 24.04 with NetworkManager and DHCP (IPv4) you might see the following error in the Kura logs:
2026-06-19T10:00:09,741 [DnsMonitorServiceImpl] WARN o.e.k.n.c.m.DnsServerMonitor - Command 'Failed to start named' exited with code {1}.
org.eclipse.kura.KuraException: Command 'Failed to start named' exited with code {1}.
at org.eclipse.kura.linux.net.dns.LinuxDnsServer.start(LinuxDnsServer.java:181)
at org.eclipse.kura.nm.configuration.monitor.DnsServerMonitor.reconfigureDNSProxy(DnsServerMonitor.java:254)
at org.eclipse.kura.nm.configuration.monitor.DnsServerMonitor.manageDnsProxies(DnsServerMonitor.java:229)
at org.eclipse.kura.nm.configuration.monitor.DnsServerMonitor.monitorDnsServerStatus(DnsServerMonitor.java:133)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
To fix it, the AppArmor configuration has to be updated as follows:
- edit the
/etc/apparmor.d/local/usr.sbin.namedfile and add the following lines in the main section:# Site-local additions for /usr/sbin/named. # This file is included by /etc/apparmor.d/usr.sbin.named. # Allow BIND/named worker threads to set/read their thread names. owner /proc/*/task/*/comm rw, # Allow BIND/named to read the kernel ephemeral port range. @{PROC}/sys/net/ipv4/ip_local_port_range r, # Allow BIND/named to notify systemd that it is ready / running. @{run}/systemd/notify w, # Allow BIND/named to read Ubuntu kernel version metadata. @{PROC}/version_signature r, # Only enable this if named still fails to start/run without it. # capability sys_admin,