Difference between revisions of "Armadeus 7.0 Troubleshots"

Latest revision as of 17:00, 31 March 2022

Due to NXP specifications changes, 4.17 kernel seems to have some problems when using CPU frequency scaling and/or i.MX6ULL at full speed (900MHz). Consequences are random kernel crashes with stack overflow/memory problems. For these reasons we recommend everyone using this kernel/release and i.MX6ULL to add a patch in patches/linux/4.17/.

This patch can be found in latest git tree:

   https://sourceforge.net/p/armadeus/code/ci/master/tree/patches/linux/4.17/0112-ARM-dts-imx6ull-update-vdd_soc-voltage-for-900MHz-op.patch

Then we also recommend to de-activate CPU frequency scaling on i.MX6ULL and fix operating frequency (to put somewhere in your app starting script, here frequency is fixed to 900MHz):

   cd /sys/devices/system/cpu/cpu0/cpufreq/
   echo userspace > scaling_governor
   echo 900000 > scaling_setspeed

When trying to build armadeus-7.0 on Ubuntu 18.04, you will encounter a lot of small compilation issues, that can be adressed manually, but we highly recommend to use more recent armadeus BSP versions on Ubuntu 18.04 to avoid these problems. (Or to build armadeus-7.0 with a 16.04 virtual machine).

docker build -t armadeus/ubuntu-16.04 -f ubuntu-16.04/Dockerfile . docker run --rm -it -u 1000:1000 -v ~/armadeus-7.0-opos6ul:/app

@@ Line 8: / Line 8: @@
      echo 900000 > scaling_setspeed
-==Ubuntu 18.04 compilation issues==
+==Ubuntu 18.04+ compilation issues==
 * When trying to build armadeus-7.0 on Ubuntu 18.04, you will encounter a lot of small compilation issues, that can be adressed manually, but we highly recommend to use more recent armadeus BSP versions on Ubuntu 18.04 to avoid these problems. (Or to build armadeus-7.0 with a 16.04 virtual machine).
+== Building Armadeus 7.0 with a Ubuntu 16.04 Docker image ==
+docker build -t armadeus/ubuntu-16.04 -f ubuntu-16.04/Dockerfile .
+docker run --rm -it -u 1000:1000 -v ~/armadeus-7.0-opos6ul:/app