Become a fan of Slashdot on Facebook


Forgot your password?
Cloud Operating Systems Ubuntu Build Linux

Ubuntu Core Gets Support For Raspberry Pi 2 GPIO and I2C 59

An anonymous reader writes: Ubuntu Core is a tiny Ubuntu distribution aimed at the Internet of Things, using a new transactional packaging format called Snappy rather than the venerable Debian packaging format. It recently gained support for I2C and GPIO on the Raspberry Pi 2, and a quick demo is given here. Ubuntu's Core support site says that the support for Raspberry Pi 2 isn't yet official, but provides some handy tips for anyone who wants to try it out.
This discussion has been archived. No new comments can be posted.

Ubuntu Core Gets Support For Raspberry Pi 2 GPIO and I2C

Comments Filter:
  • by stooo ( 2202012 ) on Saturday August 22, 2015 @06:37PM (#50371827)

    The raspberry hardware i2c implementation is broken. Don't try to communicate with microcontrollers, it will fail due to the broken clock stretching....
    I had to do SW bitbang i2c, what a mess !!

    • SPI works great in raspbian, no problems.

    • We ran into this on another vendor's hardware as well, and also ended up with a bitbanged solution (the wikipedia I2C page pseudocode, actually). I wonder if our vendor is also using Broadcom internally.

      • by gweihir ( 88907 )

        I really think that Broadcom is designing hardware with cheaper than possible personnel. They have so much stupidity and brokeness in their chips, it is staggering.

        • You should see Atmel's bootloader process, and what a mess it is to make it work for a custom board with eg. a different type of RAM or flash. The only hardware vendor (in the embedded space) that I actually trust to make stuff that 'just works' these days is TI.

    • by gweihir ( 88907 )

      And more indication that the RPi Team has no clue what they do hardware-wise....
      I bet the BananaPi does not have this problem either (in addition to a host of other problems of the RPi it does not have).

  • by Anonymous Coward

    It's slow on my new 24-core Xeon servers. I can't imagine how bad it is on a Pi.

    At least with a Pi, you're not going to be running as many services, which systemd makes very difficult to troubleshoot since it swallows stederr, ignores exit statuses, and discards a lot of syslog messages.

    • by Anonymous Coward

      Hurd doesn't use systemd. Just saying.....

  • by Required Snark ( 1702878 ) on Saturday August 22, 2015 @11:11PM (#50372617)
    At least that is what I saw the first time I glanced at the post.
    • by gweihir ( 88907 )

      That is what will follow immediately. Just look at all the stupidity currently going on security-wise on mobile phones. Add all the state-sponsored and -employed thugs to that, and a big mess is sure to ensure.

  • Unless they improved on the historically dodgy USB sw/hw, there's little to be done.

    I'll stick to my cubieboard2... which also has sata.

  • by Charles Werbick ( 4135297 ) on Sunday August 23, 2015 @11:01AM (#50374179)

    Snappy is Cannical's attempt to get rid of apt because it doesn't work for paid apps. They've abandoned the Ubuntu Software Center (and the developers there) and are now pushing this crap. Whatever claim they make about 'sandboxing' and 'security', the end goal is to monetize apps to phone and tablet users. This might not even be so bad if it worked. But Snappy is not ready for primetime. It is cumbersome and buggy.

    I also question the usefulness of an 'app-store' style package management system to a platform that is geared to education. The Raspberry Pi Platform's strength is in its openness and community support. It's gonna suck to see step 4 in EVERY pi project article be 'Go install Core on your pi, then buy my app'.

    So really who cares if Core/Snappy has GPIO. So does Windows 10 IOT. Having tried both images out, WIndows IOT might actually be more useful than Ubuntu Core on the Pi right now. (At least is runs Node.js)

    I'll take apt or pip (or mercurial or Github for that matter) over Snappy any day.

    • Snappy is Cannical's attempt to get rid of apt because it doesn't work for paid apps.

      It seemed to work fine on Maemo 5 Fremantle on my N900 almost six years ago. The Ovi Store used apt.

      • I guess it depends on how you define "work" in this context. Seeing the words "Maemo" and "Fremantle" and "N900" and "Ovi" still makes my blood boil. We wasted a lot of time and money betting on a horse with no legs. It was a damn fine app that was a pleasure to develop too, which is the hell of it. That stuff was great, but commercially successful? Not on your life!

        • Was it apt that burned you, or Nokia? Was packaging really your biggest problem?

          • We never got far enough to deal with apt. Just as we were getting into the home stretch with our app, the Maemo universe exploded into chaos. Harmattan? MeeGo? Where is this going? We decided to wait and see, and it's just as well we did. That code wasn't going anywhere unless we rewrote both the frontend and the backend from scratch.

            That's what I meant by the whole ecosystem not working for paid apps. Maybe if we had made a desperate sprint to try to cash in on a sinking ship at the last minute.

APL hackers do it in the quad.