Need pantavisor-appengine-ARM32 binary for i.MX6UL device

Product Support and Help
1

Hi, I have a Light device with:

  • CPU: ARMv7 (i.MX6UL)
  • OS: FSLC X11, Yocto rocko
  • Kernel: 4.9.88

I need the pantavisor-appengine-ARM32.tar.gz pre-built binary. The S3 bucket at pantavisor-ci.s3.amazonaws.com returns AccessDenied. pvr 052 is already installed and working. Can you share a public download link for the ARM32 appengine binary?

Thank you

2

Hi,

The appengine right now is built for x86 because is intended to be use to run pantavisor in your host computer.

Integrate meta-pantavisor into your Yocto Build (Recommended)

Since the device runs Yocto Rocko with FSLC X11, integrating the official Yocto layer is the cleanest way to produce a flashable image or initramfs containing Pantavisor.

  1. Clone the layer:

    cd path/to/yocto/sources
git clone https://github.com/pantavisor/meta-pantavisor.git

  2. Add the layer to your build environment: Edit conf/bblayers.conf to include meta-pantavisor:

    BBLAYERS += " ${TOPDIR}/../sources/meta-pantavisor "

  3. Configure Pantavisor in conf/local.conf: Add Pantavisor to your image dependencies or set it up as your init supervisor:

    IMAGE_INSTALL:append = " pantavisor"

  4. Build the image:

    bitbake core-image-minimal # (or your specific image target)
3

But if you can give us more details about what are you building and how. Maybe we can help you with more information

4

we also have official support for a board using i.MX6ULL - Flashing: Toradex Colibri iMX6ULL | Pantavisor Docs that may be similar of yours.

There is also a guide on how to port Pantavisor to your specific board:

Well keep us posted! We can help you in the way.

Cheers

5

Hi @ibrahim.abbas,

one important thing to get the appengine flavour of pantavisor is to set certain DISTRO_FEATURES and PANTAVISOR_FEATURES flags.

Check out the distro conf/include we have, e.g. conf/distro/panta-appengine.conf conf/distro/panta-appengine.inc as a good starting point.

With that you should get the pv-appengine commands etc that you would need to run in order to start appengine inside your normal system image.

Let us know if that works for you.

6

Thanks for the detailed responses. A bit more context on my situation:

I don’t have access to the original Yocto/BSP source tree that built this device’s current image, I only have SSH/root access to the running device itself (FSLC X11 2.4, Yocto rocko, kernel 4.9.88, armv7l/i.MX6UL). I checked the device’s own package feed (dnf search pantavisor, pv-appengine, appengine, pantahub) and there’s nothing pre-staged there either.

Given that, a couple of questions:

  1. Is there any way to get pv-appengine running on this device without a full custom Yocto build, e.g. a generic armv7 rpm/ipk that could be installed onto an existing rocko-based rootfs?
  2. If a custom Yocto build is unavoidable, is the Toradex Colibri iMX6ULL config (mentioned by @ferlzc) close enough to attempt as a starting point even without knowing my exact board’s original BSP, or would that risk incompatibility with my board’s specific peripherals/bootloader?
  3. Regarding @asac’s note on DISTRO_FEATURES/PANTAVISOR_FEATURES, since I’d be starting a fresh Yocto build from meta-pantavisor’s own reference configs (not adding a layer to an existing vendor tree), are there other flags/configs I’d need to also pull in to get a bootable image for a generic i.MX6UL target?
7

If you don’t have the trees to reproduce the system and you dont have an SDK either to build new stuff for that exact system, it will be quite cumbersome to do any binary compatible builds for your system. Easiest would be if you have enough storage to put a full rootfs in that system and use chroot etc. to then run appengine with all the dependencies from that rootfs.

How much free storage do you have on your system?