Firstly, could you elaborate on what you are trying to achieve, please?
Secondly, the image did work, didn’t it?
rpi-update is not really applicable to the customized distro we provide. It can break things.
4.1.6-v7+, had upgraded to 4.1.18-v7+
Correct me if I’m wrong but I guess the problem is indeed in the raspi-update tool. The kernel we ship is not the same as the Foundation’s one. The tool on the other hand doesn’t know anything about that and wipes the device tree blobs and kernel we’d been making away.
After adding modules to boot config.txt file
Why? The Device Tree mechanism saves the hustle of configuring these things yourself.
The kernel module names seem to be “spi-bcm2835” “i2c-dev” “spidev” and a few other modules, but the documentation lists incorrect names on the EMLID site (2708 rather than 2835)
Thanks for the information. We’ll fix it right away. But I do not really understand what is the problem you’re trying to solve. So I’m in the dark. Is the upstream driver (spi-bcm2835) is not applicable in any way spi-bcm2708 is?
Either way, you can look into this post which can be of help.