PyBBIO GSoC 2014 ideas

There’s been some interest in working with PyBBIO for GSoC 2014, so I’ve created a wiki page for people to put ideas together here: https://github.com/alexanderhiam/PyBBIO/wiki/GSoC-2014-ideas

Thanks! I would encourage you to use the http://elinux.org wiki in the end, but simply getting the info out where you’ll edit it is helpful. You might provide a pointer to your wiki page from the elinux ideas entry.

Doesn’t the Adafruit fork of your code include I2C support?

Tying into some other system-specific services like setting the video resolution is a thought.

There are other subsystems like GPMC, eQEP, CAN, etc. that have gotten less high-level support.

There’s been some interest in working with PyBBIO for GSoC 2014, so I’ve created a wiki page for people to put ideas together here: https://github.com/alexanderhiam/PyBBIO/wiki/GSoC-2014-ideas

Thanks! I would encourage you to use the http://elinux.org wiki in the end, but simply getting the info out where you’ll edit it is helpful. You might provide a pointer to your wiki page from the elinux ideas entry.

Just added a link, and I’ll move the list there when it gets more finalized.

Doesn’t the Adafruit fork of your code include I2C support?

They did at one point start a fork, but then they ended up going from a fork of their Raspberry Pi library instead which already had an I2C smbus wrapper. I’m shooting for something similar (just an smbus wrapper), but that matches PyBBIO’s API a bit more. (It looks like this should be done before GSoC)

Tying into some other system-specific services like setting the video resolution is a thought.

Yeah, more general embedded Linux centric routines would be cool.

There are other subsystems like GPMC, eQEP, CAN, etc. that have gotten less high-level support.

Good ideas, I’ll add them to the list.

There's been some interest in working with PyBBIO for GSoC 2014, so I've
created a wiki page for people to put ideas together here:
https://github.com/alexanderhiam/PyBBIO/wiki/GSoC-2014-ideas

Thanks! I would encourage you to use the http://elinux.org wiki in the
end, but simply getting the info out where you'll edit it is helpful. You
might provide a pointer to your wiki page from the elinux ideas entry.

Just added a link, and I'll move the list there when it gets more
finalized.

Doesn't the Adafruit fork of your code include I2C support?

They did at one point start a fork, but then they ended up going from a

fork of their Raspberry Pi library instead which already had an I2C smbus
wrapper. I'm shooting for something similar (just an smbus wrapper), but
that matches PyBBIO's API a bit more. (It looks like this should be done
before GSoC)

Any hope of working with Justin and Simon to create a single "upstream"?
Right now, because of the work Justin and Simon did on the Adafruit
library, it looks more complete and has more documentation. The result is
that we have it slated for installation in the new Debian image. I just
verified the below works out-of-the-box on the new image (blink.py):

import Adafruit_BBIO.GPIO as GPIO
import time

GPIO.setup("P9_14", GPIO.OUT)

while True:
    GPIO.output("P9_14", GPIO.HIGH)
    time.sleep(0.5)
    GPIO.output("P9_14", GPIO.LOW)
    time.sleep(0.5)

If we need to fix the module name, etc. for the upstream, it would be good
to make the change before it goes into production! (Still weeks out as we
haven't had a good public soak yet.)

I’d definitely be up for joining forces, but the libraries use pretty different approaches at the moment. It might require a fair bit of effort to merge them. I’ll shoot a note their way about it…

The way I see it PyBBIO is more user friendly and simple. Currently it lacks the I2C as compared to the AdafruitBBIO, but has many more libraries for hardware extensions [ from servos to character LCDs and good support for async stuff]. I’m currently working on I2C, which should get done this week.
But having one library for all IO related operations will be great :smiley: [including PRU support :wink: ]

regards,
Deepak

I am interested in this project, however I only just started a software engineering degree and I’m wondering what would be expected of me to gauge whether or not I’ll be able to complete it. Any thoughts of a few things I would be doing?

Thanks,
Derek

I am interested in this project, however I only just started a software engineering degree and I’m wondering what would be expected of me to gauge whether or not I’ll be able to complete it. Any thoughts of a few things I would be doing?

There’s certainly the expectation that you are already comfortable coding in Python and C.

This has reference to my email conversation with Alexander Hiam.
I have certain sensor/peripherals modules that I have been using with the arduino for which I think I can write PyBBIO libraries:-

  1. XBee Radios
  2. HC​ SR 04 Distance Module
  3. Stepper Motor
  4. 128x64 GLCD KS0108
  5. Tones Library (for use with speakers)
  6. MQ gas sensor series
  7. TMP36/LM35 Temperature Sensor
  8. LPY503 Gyro

In case you have any other modules in mind, I can procure them at my end and probably write libraries for them too.

I’ve put a more finalized list of project ideas on elinux.org: http://elinux.org/BeagleBoard/GSoC/Ideas#PyBBIO_library_development

Great! Looks Awesome :smiley:
I’d like to work on on chip peripherals :slight_smile:

Regards,
Deepak

Would love to take up the sensors/displays/radios part :smiley:

I would enjoy working with all of those, especially the sensors.