- Who will be the mentor? (project: Documentation for BeagleBone and BeagleBone Black)
For updating bone101, I’m likely to be the primary mentor. When the mentors meet to discuss the projects, we might identify a different primary mentor and will certainly be identifying backup mentors.
In general, I will answer with respect to this project idea: http://elinux.org/BeagleBoard/GSoC/Ideas#BoneScript_web_pages_with_live-running_examples_and_documentation
Matt and Hunyue have a rather different but useful proposal at http://elinux.org/BeagleBoard/GSoC/Ideas#Documentation_for_BeagleBone_and_BeagleBone_Black, but I have concerns it is overly focused on documentation and not open source coding. Hopefully they will reply, perhaps taking a leadership role that sends you in a completely different direction—and that is fine.
- I think, I am going to write a stimulus generator that simulate the real joint hardware (like thermometer, accelerometer and other recommended devices). I am document the ideal, typical and maybe wrong signal shape that can help other development.
Sounds like it might get a bit complicated. What type of hardware would you design for this? Does indeed sound like it’d be useful.
- My ideas, I’m curious about your opinion:
- I would like to make an UART test example (I have a lot of experience with DMX and Modbus communication, but there will be other communication protocol), and a PC program, that can communicate and can modelling the signal shape. If I will receive devices, then I will make a test program too.
You will certainly get a BeagleBone Black, but we won’t be providing any other hardware than that.
- I2C: a basic thermometer and EEPROM communicate preview
- SPI: accelerometer or an ADC device
- PWM: typical LED brightness control, and motor controlling.
- ADC: compare the joint ADC (SPI compatible) device.
Also need to show using the on-board ADC as we have done with TMP36 devices and potentiometers.
You’ve seen BeagleBoard.org - BoneScript and http://github.com/beagleboard/bone101 and reviewed them, right? I’d expect you to be looking at all those existing tutorials forward, but cleaning up the presentation, content and functionality.
- USB: if I have enough time, then I would like to connect to a Kinect sensor. If you recommend an easier task, then will be e.g.: mouse or keyboard communicate example.
Kinect would be great. A first step would be integrating webcam frame grabbing into presenting the captured images on a web page.
- Am I on the right way? Are these enough or to less?
I think more consideration needs to go into the UI and I’ve had quite a bit of discussion with Diego in particular about how we’d want to make creating these tutorials something anyone can contribute to using gists.
- Can this example use up the PRU or I should choose another examples?
Not sure what you mean here. I think you can load PRU firmware for the tutorials.
- What does it mean “optimization” in the project description? Using the PRU if it is possible.
k, now I know you are talking about Matt and Hunyue’s idea. It means taking code and moving it to a dedicated processor such that it would run faster.
Especially the comments.