Build Linux IMAGE for IMX.6 -- 2 on Yocto

Finish a distribution for a solid run imx6 SOM on a custom board that is inspired by the humming board. ## Yocto Requirements We need an image that automatically starts X and our own software. All the hardware should be usable (Display, Touch, NFC, Serial Devices, RTC, USB, Sound). The image should be resilient (e.g. disconnecting the power should not be able to corrupt the filesystem). We have a ubuntu machine on AWS where we have a basic yocto build running, that produces a morty image we can boot on our device. It is the cubox-i config from [login to view URL] With the solidrun kernel from [login to view URL] Our own board is based on the humminboard and uses an IMX6 MicroSom from solidrun. ### What needs to be done #### The Basics * use our own device tree * add nxp NFC PN7120 driver (see [login to view URL]) * add linux_libnfc-nci [login to view URL] (produces a shared library and two configuration files that are required in /etc) * add small custom C command line tool from us that links against linux_libnfc-nci * add audio (pulseaudio with paplay) * add java (openjdk-7 jre) * add our software (java software with gui, basically be able to start a jar) and autostart it on boot * document all the steps taken, so we could reproduce the results easily on a new machine #### The Advanced * add a user and ssh for maintainance access * add security (iptables, maybe SELinux, open for your suggestions) * discuss with us and implement a resilience and update strategy Maybe having an image with 3 partitions, 2 root (2GB each), 1 data (4GB) would be beneficial. Where the active root partition would be mounted read only and the data partition would hold our application data (and var and tmp). Updates could be applied to the inactive partition and that partition could only be activated if the update is successful. But we are very open for suggestions to this differently, this is just an idea. We already take care of updates for our own software, but also need a strategy how updates to the root system could be handled (e.g. to update the kernel or apply security updates for ssh). The terminals may don't have internet access (everything required must be provided by LAN internal server). Things like Mender and OSTree are maybe overkill to setup and maintain for our usecase. Current idea: When we update our server, our software on the terminal knows that an update is available. Our software downloads a script with update instructions and executes it. The script downloads the required files from our on premis server, installs them into the inactive root partition (if we use 2) and if successful switches marks the updated partition as active and reboots. But again, we would appreciate better suggestions.