tioubxancur | # 1331 | 2016-05-10, 13:37 | Report

I followed that, but it seems a lot of work.
I was wondering if someone uses that or who knows it can point me to the .cpio file responsible. Perhaps someone still has it handy.

juiceme | # 1332 | 2016-05-10, 20:16 | Report

Well, it is not that difficult.

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!

marmistrz | # 1333 | 2017-08-16, 18:47 | Report

I'm trying once again to boot Debian with mainline kernel on my N950.

My Ubiboot configuration is: https://pastebin.com/dByXqphq
ubiboot.log: https://pastebin.com/HCV6y0kA
ubiboot.dmesg: https://pastebin.com/T9W6HeT6

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?

juiceme | # 1334 | 2017-08-16, 20:34 | Report

So you have Debian on slot #5

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?

juiceme | # 1335 | 2017-08-17, 03:56 | Report

One thing I thought about; have you turned off the watchdogs?
Debian of course doesn't know how to feed the dogs unless you added a script for that in initialization yourself...

marmistrz | # 1336 | 2017-08-17, 17:54 | Report

Of course I did not.

Are the R&D flags explained anywhere? I see in 0xFFFF:
what are the different watchdogs on the N950? what is software lifeguard? dsme?

juiceme | # 1337 | 2017-08-17, 19:08 | Report

I just turn 'em all off

marmistrz | # 1338 | 2017-08-17, 19:23 | Report

I disabled them all, unfortunately, the device reboots after a while.

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

---

Last edited by marmistrz; 2017-08-17 at 19:56.

juiceme | # 1339 | 2017-08-17, 19:45 | Report

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?


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.

marmistrz | # 1340 | 2017-08-17, 19:58 | Report

That was installed from the repo. 4.9 should have the most needed patches
http://elinux.org/N950

The patches for display were not merged yet, though.

of course, to

and without unscrewing the device? I'm a little afraid I'll break my N950.