If I correctly understand what you have in mind, it is just the picture-icons react to tapping, and the texts next to them only describe the actions, right?

To achieve that, all you need is to create the right-hand texts as png images just like described in the animatronics README, and modify the top level touchmap so that their area does not trigger any events... and that's all there is to it!

The system lives for awhile and then reboots. I have no logs in /var/log/journal even though `Storage=persistent` is in /etc/systemd/journald.conf. On the Debian filesystem, /boot/bzImage is a symlink to /boot/vmlinuz-4.9.0-3-armmp (neither of them works)

Does it look like an error in ubiboot configuration?

__________________If you want to support my work, you can donate by PayPal or Flattr

Rootfs for it is on /dev/mmcblk0p4, and you have the kernel correctly placed in /boot/vmlinuz-4.9.0-3-armmp of the said partition.

According to the logs your setup is pretty much OK. The only thing that's not checked in your ubiboot version is the availability/executability of the init fie of the booting OS. (that is checked in the latest version, 0.3.6-tiny...)

So, according to ubiboot everything goes well until it hands execution to the newly loaded kernel. The new kernel then tries to execute /sbin/init.

How doe the boot continue, exactly?
You mention it goes OK first, then reboots?

How far do you get, I assume debian starts to at least some extent?
The kernel you are using, did you compile it yourself with all the patches needed to make it work on N9?

Originally Posted by marmistrz

Is there any way to easily set up a telnet/ssh session from the device, like Nemo does? They're using their own `init-debug` script, though.

Sure you mean to the device, not from?
Easiest is to enable serial console and connect to N9's serial port with minicom; that is pretty much foolproof. Same way you will get kernel logs visible while the device is booting.