[beagleboard-gsoc] Re: Interested participant for GSoC 2013

Google Summer of Code
1

Sounds like you have a good start on thinking about this...

best to refine your ideas a bit and bounce things off of people here on the
list...

Hi Tom, sorry for the late response

now is the time for "discussion on ideas" so if you have specific questions
related to what you are thinking post them here and we can try to help.

I'm currently thinking about the port of the arduino libraries, while using the standard IDE in order to write code for the beagle board.

This means that firstly the core functions, like digitalWrite(), pinMode(), digitalRead().

This means that the code should be cross-compiled for the ARM processor, and loaded to the beagle board.

What I had in mind was to create a small daemon, which will run on the beagle board GNU/Linux OS - let's call it beagleduino-daemon, which will be responsible for listening to the IDE, catching the compiled code from the IDE and running it on the beagle board.

This implies that there should be some method of relaying the compiled binary to the beagle board itself, maybe making an extension to the current arduino IDE, or calling up on some script that will copy the .bin (compiled program) file via scp/ftp/w/e to the beagle board, and tell the daemon to execute the new code.

The daemon will also need to know if the program stops, waits for an interrupt (software interrupts / software pooling?).

How does this sound ?

I don't know that a Beaglebone is a requirement as the xM is still current
too, and it sounds like you have some ideas already to use MSP430 too...

I got confused as to the target of the idea, I though that the arduino port should be targeted to the Beagle Bone only.

Good Luck and let us know if there is anything more we can help you with

Tom

Regards,
Aleks

2

Sounds like you have a good start on thinking about this…

best to refine your ideas a bit and bounce things off of people here on the
list…

Hi Tom, sorry for the late response

now is the time for “discussion on ideas” so if you have specific questions
related to what you are thinking post them here and we can try to help.

I’m currently thinking about the port of the arduino libraries, while
using the standard IDE in order to write code for the beagle board.

This means that firstly the core functions, like digitalWrite(),
pinMode(), digitalRead().

This means that the code should be cross-compiled for the ARM processor,
and loaded to the beagle board.

What I had in mind was to create a small daemon, which will run on the
beagle board GNU/Linux OS - let’s call it beagleduino-daemon, which will
be responsible for listening to the IDE, catching the compiled code from
the IDE and running it on the beagle board.

This implies that there should be some method of relaying the compiled
binary to the beagle board itself, maybe making an extension to the
current arduino IDE, or calling up on some script that will copy the
.bin (compiled program) file via scp/ftp/w/e to the beagle board, and
tell the daemon to execute the new code.

The daemon will also need to know if the program stops, waits for an
interrupt (software interrupts / software pooling?).

How does this sound ?

Start simple and expand. Make sure you can scp/start/stop reliably before trying to do more complicated things like debug. I don’t even know where you’d hook anything like that into the Arduino IDE. I’m not even really sure what you are talking about. A simple ‘exec’ should return upon termination. I would just use existing servers as much as possible, potentially even ‘gdbserver’.

I don’t know that a Beaglebone is a requirement as the xM is still current
too, and it sounds like you have some ideas already to use MSP430 too…

I got confused as to the target of the idea, I though that the arduino
port should be targeted to the Beagle Bone only.

Ideally, you’d cover both BeagleBoard(-xM) and BeagleBone(Black). I’d work closely with whatever mentors you can align with to make sure they are comfortable with your approach (as in which one to start with first).