Will you be supporting the Intel Apollo-Lake Atom?

If so, when do you think you will have support? Thanks!

Hi, can you link to a product page, what kind of device are you trying to use?

We have some changes coming that will address general devices with X86 processors like that, shouldn’t be too much in the future, will keep you posted!

This is the product page:


It looks pretty cool… For good measure we’ve added that device to the support request list in this repo:

Great, thank you! The other device we’re looking at is an industrial variant of the Pi3 here. Will your existing Pi3 support work for this device?

Yeah, believe it should. That looks interesting as well, for many reasons :slight_smile:

Any further update on support for this device? For my work, this would be the most suitable device to deliver our product. We need the higher processing power and ram wrapped in a fan-less rugged case that is provided.

Would an Intel NUC or UP2 resin.io image work? I don’t see a general amd64 image?

Experimenting using the Intel NUC image on fitlet2. Will report back my observations.

We’ve been testing with the fitlet2 and found that the Intel NUC image works out of the box for the device. Compulab classifies their device as comparable to the NUC.

Have you had to modify your application’s code base to run on the fitlet2?

I’m getting “illegal instruction” errors when attempting to run OpenSfM code on the fitlet2 w/ J3455 processor. Application code works well in Docker container on amd64 workstation. Using Intel NUC resin.io image.

Runs the initial sh script to upload images, then borks on OpenSfM call:

[DEBUG] running PYTHONPATH=/usr/local/lib/python2.7/dist-packages /usr/local/src/OpenSfM/bin/opensfm extract_metadata /var/www/data/4b8732b5-327d-4e7b-ad58-f873ad8cbf81/opensfm
Illegal instruction (core dumped)
Traceback (most recent call last):
File “/code/run.py”, line 47, in
File “/code/scripts/run_opensfm.py”, line 113, in process
(context.pyopencv_path, context.opensfm_path, tree.opensfm))
File “/code/opendm/system.py”, line 34, in run
raise Exception(“Child returned {}”.format(retcode))
Exception: Child returned 132

Been through the application on both fitlet2 container and workstation container, all seems to be the same; BIOS is set to Linux; Graphics drivers are installed

Our code is all node.js and C# for the most part. We haven’t had to make any changes yet.

Kicked the resin.io to the curb for now. Testing with Debian Stretch + Docker install to debug code issue. Will reinstall resin image once application code is running on fitlet2