{"id":2569,"date":"2023-03-10T18:20:44","date_gmt":"2023-03-10T17:20:44","guid":{"rendered":"https:\/\/www.nico-maas.de\/?p=2569"},"modified":"2023-03-10T18:20:46","modified_gmt":"2023-03-10T17:20:46","slug":"balenaos-on-the-advantech-air-020x","status":"publish","type":"post","link":"https:\/\/www.nico-maas.de\/?p=2569","title":{"rendered":"balenaOS on the Advantech AIR-020X"},"content":{"rendered":"\n

Last week I posted the review of the Advantech AIR-020X<\/a> with which I used to create the labSentinel 2 system<\/a>.<\/p>\n\n\n\n

I remarked that the hardware was great, however the software support and update capability of the system was severly lagging behind for an \"industrial floor, always on\" type of machine. Luckily, thats exactly what balena <\/a>has been created for.<\/p>\n\n\n\n

Even better, their environment already support Nvidia Jetson devices - also Nvidia Jetson Xavier NX modules. With the AIR-020X being a really nice carrierboard (and housing) for this module, I went to work.<\/p>\n\n\n

\n
\"\"<\/a>
Spoiler Alert - it works!<\/figcaption><\/figure>\n<\/div>\n\n\n

Installing balenaOS on the AIR-020X<\/h2>\n\n\n\n

1.) I setup an Ubuntu 20.04 LTS machine, installed npm and setup jetson-flash<\/a><\/p>\n\n\n\n

2.) I went to https:\/\/www.balena.io\/os<\/a> and downloaded the latest NVIDIA JETSON XAVIER NX DEVKIT EMMC image (2.107.10) in the development version. <\/p>\n\n\n\n

3.) Unzip the file after setting up jetson-flash and getting your AIR-020X into recovery mode. This means opening the bottom of the case by unscrewing the 4 philipps head screws, connecting the Micro USB port of the AIR-020X with your Ubuntu host computer, applying power to the AIR-020X, but do not yet press the power switch.<\/p>\n\n\n\n

4.) There is foil\/recovery switch next to the Micro USB connector and LAN port. You need to press and hold this switch and at the same time press the power on button of the unit for about 4 seconds.<\/p>\n\n\n

\n
\"\"<\/a><\/figure>\n<\/div>\n\n\n

5.) On Ubuntu, run lsusb | grep Nvidia<\/code> - this should return a similar line to this<\/p>\n\n\n\n

Bus 003 Device 005: ID 0955:7023 NVIDIA Corp. APX<\/code><\/pre>\n\n\n\n
Import is the ending \"APX\", which means it is in recovery mode.<\/p>\n\n\n\n
6.) Now you can start the flash process<\/p>\n\n\n\n
user@balenaTest:~\/jetson-flash$ .\/bin\/cmd.js -f .\/jetson-xavier-nx-devkit-emmc-2.107.10-v14.4.4.img -m jetson-xavier-nx-devkit-emmc\r<\/code><\/pre>\n\n\n\n
The .img value points to the unzipped image file, the -m tells the jetson-flash tool that we are running a Xavier NX system and want to install balenaOS on the internal eMMC module.<\/p>\n\n\n\n
7.) This will now start the process which will take some minutes and also ask you for your sudo password. At the end you should see something like this:<\/p>\n\n\n\n
[ 255.8670 ] Flashing completed\r\n\r\n[ 255.8670 ] Coldbooting the device\r\n[ 255.8696 ] tegrarcm_v2 --ismb2\r\n[ 255.9454 ]\r\n[ 255.9502 ] tegradevflash_v2 --reboot coldboot\r\n[ 255.9530 ] Bootloader version 01.00.0000\r\n[ 255.9984 ]\r\n*** The target t186ref has been flashed successfully. ***\r\nReset the board to boot from internal eMMC.<\/code><\/pre>\n\n\n\n
8.) As soon as you reboot the device, you will be greeted with the balenaOS logo and can use it as any other balenaOS device.<\/p>\n\n\n\n
Adding the AIR-020X to a fleet<\/h2>\n\n\n\n
If you want to use it e.g. in a fleet, I would recommend creating a new one with the device type Nvidia Jetson Xavier. This is important to allow sample projects to correctly work, as its basically the same thing as the more specialized version \"jetson-xavier-nx-devkit-emmc\" - but most demo projects just implement the former one :).<\/p>\n\n\n\n
To now join the installed device onto your new fleet, download and install balenaCLI<\/a> - login to your balena Cloud account and do a balena scan<\/code> using balenaCLI to find your AIR-020X on the network.<\/p>\n\n\n\n
-\n  host:          56e1ef3.local\n  address:       192.168.178.112\n  osVariant:     development\n  dockerInfo:\n    Containers:        1\n    ContainersRunning: 1\n    ContainersPaused:  0\n    ContainersStopped: 0\n    Images:            1\n    Driver:            overlay2\n    SystemTime:        2023-03-10T14:05:52.568438957Z\n    KernelVersion:     4.9.253-l4t-r32.7\n    OperatingSystem:   balenaOS 2.107.10\n    Architecture:      aarch64\n  dockerVersion:\n    Version:    20.10.17\n    ApiVersion: 1.41<\/code><\/pre>\n\n\n\n
After that, you can easily join this device with<\/p>\n\n\n\n
.\\balena join 192.168.178.112\r\n? Select fleet <yourFleetNameToSelect>\r\n? Check for updates every X minutes 10\r\n[Success] Device successfully joined balena-cloud.com!<\/code><\/pre>\n\n\n\n
... and voila, its online!<\/p>\n\n\n\n
What does work?<\/h2>\n\n\n\n
\"\"<\/a>
Testing GPIO pins with a multimeter<\/figcaption><\/figure>\n\n\n\n
The AIR-020X has a lot of custom GPIO chips, 2x RS485\/RS232 interface, 1x CANbus interface, a second network interface and even a NVMe. Luckily, everything just works out of the box.<\/p>\n\n\n\n
- HDMI works\n- USB works<\/code><\/pre>\n\n\n\n
- onboard network card (dmesg + dhcp test, gets ip \/ works)\r\n[   29.231807] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps\/Full - flow control rx\/tx\n\n- 2nd network card (dmesg + dhcp test, get ip \/ works)\r\n[  104.307175] igb 0004:05:00.0 enP4p5s0: igb: enP4p5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow <\/code><\/pre>\n\n\n\n
- NVMe is recognized (lsblk)\r\nnvme0n1      259:0    0 119.2G  0 disk\r\n|-nvme0n1p1  259:1    0    96G  0 part\r\n|-nvme0n1p2  259:2    0    64M  0 part\r\n|-nvme0n1p3  259:3    0    64M  0 part\r\n|-nvme0n1p4  259:4    0   448K  0 part\r\n|-nvme0n1p5  259:5    0   448K  0 part\r\n|-nvme0n1p6  259:6    0    63M  0 part\r\n|-nvme0n1p7  259:7    0   512K  0 part\r\n|-nvme0n1p8  259:8    0   256K  0 part\r\n|-nvme0n1p9  259:9    0   256K  0 part\r\n|-nvme0n1p10 259:10   0   300M  0 part\r\n`-nvme0n1p11 259:11   0  22.8G  0 part<\/code><\/pre>\n\n\n\n
- can bus interface is auto loaded on boot (see ifconfig -a)\r\ncan0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00\r\n          NOARP  MTU:16  Metric:1\r\n          RX packets:0 errors:0 dropped:0 overruns:0 frame:0\r\n          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0\r\n          collisions:0 txqueuelen:10\r\n          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)\r\n          Interrupt:63<\/code><\/pre>\n\n\n\n
- gpio\/dio, works, but bit3 does sadly not work\n( more info: http:\/\/ess-wiki.advantech.com.tw\/view\/File:AIR-020-nVidia_GPIO.docx )\nPin Number AIR-020X AIR-020T AIR-020N\nGPIO bit1 \t393 \t269 \t\t38\nGPIO bit2 \t421 \t425 \t\t149\nGPIO bit3 \t265 \t411 \t\t65\nGPIO bit4 \t424 \t264 \t\t168\nGPIO bit5 \t418 \t476 \t\t202\nGPIO bit6 \t436 \t396 \t\t246\nGPIO bit7 \t417 \t337 \t\t169\nGPIO bit8 \t268 \t338 \t\t194\n\n# set bit 1 as GPIO pin\necho 393 > \/sys\/class\/gpio\/export\n# get value 0=low, 1=high\ncat \/sys\/class\/gpio\/gpio393\/value\n# set direction out or in\necho out > \/sys\/class\/gpio\/gpio393\/direction\n# get direction\ncat \/sys\/class\/gpio\/gpio393\/direction\nout\n# set value on out pin\necho 1 > \/sys\/class\/gpio\/gpio393\/value\n\ntest:\n# 265, bit3 did not work on export\necho 393 > \/sys\/class\/gpio\/export\necho 421 > \/sys\/class\/gpio\/export\necho 265 > \/sys\/class\/gpio\/export\necho 424 > \/sys\/class\/gpio\/export\necho 418 > \/sys\/class\/gpio\/export\necho 436 > \/sys\/class\/gpio\/export\necho 417 > \/sys\/class\/gpio\/export\necho 268 > \/sys\/class\/gpio\/export\n\necho out > \/sys\/class\/gpio\/gpio393\/direction\necho out > \/sys\/class\/gpio\/gpio421\/direction\necho out > \/sys\/class\/gpio\/gpio265\/direction\necho out > \/sys\/class\/gpio\/gpio424\/direction\necho out > \/sys\/class\/gpio\/gpio418\/direction\necho out > \/sys\/class\/gpio\/gpio436\/direction\necho out > \/sys\/class\/gpio\/gpio417\/direction\necho out > \/sys\/class\/gpio\/gpio268\/direction\n\necho 1 > \/sys\/class\/gpio\/gpio393\/value\necho 1 > \/sys\/class\/gpio\/gpio421\/value\necho 1 > \/sys\/class\/gpio\/gpio265\/value\necho 1 > \/sys\/class\/gpio\/gpio424\/value\necho 1 > \/sys\/class\/gpio\/gpio418\/value\necho 1 > \/sys\/class\/gpio\/gpio436\/value\necho 1 > \/sys\/class\/gpio\/gpio417\/value\necho 1 > \/sys\/class\/gpio\/gpio268\/value<\/code><\/pre>\n\n\n\n
- com ports, running as RS-232 or RS-485 (not tested, but recognized)\r\n( more info: http:\/\/ess-wiki.advantech.com.tw\/view\/AIR-020-RS-485 )\r\nroot@56e8bf3:\/# ls \/dev\/ | grep ttyTH\r\nttyTHS0 <- COM1\r\nttyTHS1 <- COM2\r\nttyTHS4<\/code><\/pre>\n\n\n\n
More info to the hardware can be found in the Advantech Wiki<\/a>.<\/p>\n\n\n\n
GPU Demos<\/h2>\n\n\n\n
Last but not least I want to point you towards the nice balena Jetson tutorial which can be found here<\/a>.<\/p>\n\n\n\n
It will help you getting started with Jetson samples that are hosted here<\/a>.<\/p>\n\n\n\n
In the end I was able to also get CUDA acceleration to work and see this smoke demo:<\/p>\n\n\n
\n
\"\"<\/a>
Nothing like some GPU accelerated smoke<\/figcaption><\/figure>\n<\/div>\n\n\n
With that I am closing this post. It was surprisingly easy to get this device to work - the only thing left would be to get it to boot and to work from its internal NVMe storage, but other than that its a nice tool for working with GPU workloads like Edge Impulse<\/a>.<\/p>\n