Updating your ARTIK Board
ARTIK 5 and 7 modules now support Ubuntu! Read below about how to upgrade your board to this operating system and its longer support lifetime.
Throughout these articles, we discuss installing software both on your ARTIK module and, occasionally, on your development PC. If not specified, assume we are referring by default to the ARTIK module and that you must be connected to a network to do so.
Upgrading OS and Packages
If you are starting project development, now is a good time to make sure you have the latest firmware and software available.
Step 1. Upgrade your OS. ARTIK modules come pre-loaded with a specific Linux operating system (OS), depending on module type:
- Ubuntu only (ARTIK 530s and 710s modules)
- Fedora upgradable to Ubuntu (ARTIK 530 and 710 standard modules)
- Fedora 24 only (ARTIK 520)
- Fedora 22 only (ARTIK 1020).
Fedora is more compact than Ubuntu, but its support lifetime is limited compared to Ubuntu (5 yrs). Move to Ubuntu now to avoid reloading all your software and tools later. Click to install the latest ARTIK image and choose the newest image for your module.
Step 2. Connect to a Network. To load software, you'll need to either connect an Ethernet cable or set up your Wi-Fi® network and password.
Try out "on-boarding." You'll have a chance in the Connect to the World article to see how your eventual end-user product could connect to the Internet and to ARTIK Cloud using a simple smart phone app.
Step 3. Upgrade installed packages. Start by reading a primer on package management systems. Now you're ready for the latest software updates.
In the version of Ubuntu we use,
apt are nearly interchangeable. We use
apt but you can feel free to use either.
apt-key add /var/lib/apt/keyrings/artik-platform-keyring.gpg
apt install build-essential
Verify your repository first as noted below, then type
Note: A patch is available in the repositories for the KRACK vulnerability of
wpa_supplicant. Simply run the normal update/upgrade process to implement the fix. You can also patch just the affected package as follows.
apt install --only-upgrade wpasupplicant
dnf upgrade wpa_supplicant
Step 4. Install a development environment on your PC. If you loaded the ARTIK IDE earlier, you're nearly done – go to the Update SDK article to check for updates. If not, go to Software Tools to get an overview of what's available.
Step 5. Verify API access. ARTIK API support is included automatically when you install the ARTIK IDE. You just need to enable repository access on your ARTIK board. For an Ubuntu system, this typically means running:
1 2 3 4
echo "deb http://repo.artik.cloud/artik/bin/pub/artik/ubuntu xenial main" > /etc/apt/sources.list.d/artik-e2e-sources.list apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 55955AEB apt update apt install libartik-sdk
Step 6. Add additional packages. You'll eventually want to add other software, typically using a package installer. We've included instructions throughout the articles about what packages you'd need for a specific feature (like adding Node-RED as we describe in the Tutorials).
Verifying Fedora repository
At the conclusion of active development for a given Fedora release, Fedora repositories may be phased out and moved to a permanent archive. If you are having any problems with
dnf update or package downloads, make sure the repository URLs point to the right locations.
You'll find the information in
/etc/yum.repos.d/ in various files. You can either change them manually or use a command like the one below to make the substitution.
sed -i 's|archive\.fedoraproject\.org\/pub|archives\.fedoraproject\.org\/pub\/archive|g' /etc/yum.repos.d/*
Ubuntu Differences from Fedora
You'll find it quite easy to move to Ubuntu. We've provided a short comparison list showing command differences between Ubuntu and Fedora. We've also included installation differences within our articles.
Another consideration is the Ubuntu
vi editor, which defaults to a less user-friendly mode than in Fedora. Just create a file
~/.vimrc with contents
set nocp to make it work as it did under Fedora.