Navio+ and RPi2 image

[george.staroselskiy]

@ThoSc

Sorry for the fuzzy topic, but I get the feeling my questions are somehow related to each other and I wish to have a better understanding of what’s happening.

Sure, they are all connected! I’ll try to answer them the best as I can.

@ThoSc

new RPi2 image (emlid-raspbian-20160718.img).

It’s not the newest. Take a look at the beta.

@ThoSc

Is my RPI2 image compatible with Navio+ “out of the box” ?

Yes.

@ThoSc

Are the examples in the Navio repo of any relevance for my hardware setup ?

Yes, of course.

Let’s get to the meaty stuff.

@ThoSc

What does the rcio_worker process exactly do ? Is it necessary to run it with Navio + ? I assumed it would be bound to the presence of the RC-coprocessor on Navio2…

Yes, it’s Navio 2 specific. It doesn’t do anything on Navio. You can blacklist rcio_spi or remove dtoverlay=rcio from /boot/config.txt if you want to.

@ThoSc

What makes the RT patch unnecessary in the newest images ? Is it related to the different RCI/O management of Navio2 ?

We run PREEMPT kernels. They can deal with the necessary load quite alright.

@ThoSc

echo 27 > export in the directory /sys/class/gpio

Thanks for asking. That is indeed a minor bug on Navio+. It doesn’t really stop you from using with ArduPilot, though. You can also edit /boot/config.txt end remove dtoverlay=navio-rgb. This will stop Device busy errors from showing up and hence make it possible to run the examples.

I hope I made it clear.