[C.CC USERS] Ethernet shield

[Andy Man Of Mystery]

SPI and SD, definitely.  Ethernet could be useful.  Is there already support
for I2C?  If not, that should be added too.

External EEPROM via I2C is quite easy to do, and inherently fairly slow, so
doesn't necessarily need inbuilt support beyond supporting I2C itself, but
is something I'd probably want to use.  I2C and SPI are both typically used
for displays on Arduinos and AVRs in general, among other things.  The 4 bit
LCD library should be supported too, if it isn't already.

How about supporting the Qtouch library?  A lot of AVRs can be used with
touch sensitive buttons, and Qtouch.

Sorry, I have no idea which things are already supported.  Libraries that
are linked in if used, rather than built into the runtime, would definitely
be preferable.

Regards,

Andy

----- Original Message -----
From: "Matt Jadud" <matt at jadud.com>
To: "Hachi" <hemanzur at gmail.com>
Cc: <users at concurrency.cc>
Sent: Tuesday, September 04, 2012 6:24 PM
Subject: Re: [C.CC USERS] Ethernet shield


> Hi Hachi,
>
> On Tue, Sep 4, 2012 at 1:16 PM, Hachi <hemanzur at gmail.com> wrote:
> > The only problem is that for this project I need to use the ethernet
port,
> > and the SD card reader/writer on the ethernet shield.
> > Is there any way to use this shield with occam-pi ? Is it possible to
use
> > arduino libraries embedded in occam-pi to use the shield ?
>
> There are not, yet, probably because none of us own an ethernet shield.
>
> (I think that's true.)
>
> It is certainly *possible*. Within just a few small limitations
> (mostly limited to speed), we can do anything in occam-pi that can be
> done in C.
>
> Reading this page:
>
> http://arduino.cc/en/Main/ArduinoEthernetShield
>
> and assuming you are working with that ethernet shield, the answer is
> that we have some work to do. Specifically, I don't think we (yet)
> have a SPI implementation written. This could be a good opportunity to
> work on one, however, which would give us library support for 1) SPI
> devices, and 2) specifically, this device.
>
> The other answer is "yes," we can embed C code into our runtime. This
> grows the size of the runtime for everyone (generally bad), and to
> embed "arduino" code specifically, we have to roll everything over to
> C++... which is messy, and has other problems associated with it.
> (And, again, it grows the VM.) So we could, but it is a rather bad
> path for us to go down at this point.
>
> As a dev group, we haven't been working very consistently of late,
> primarily due to moves between jobs, etc. Would there be interest in
> picking up some ethernet shields and putting together:
>
> 1. A SPI library,
> 2. An SD library, and
> 3. An Ethernet library?
>
> The SD and Ethernet libraries would be very useful to me, certainly.
> And Hachi, you would (of course) be encouraged to join in that effort
> as well, if you were so inclined.
>
> Cheers,
> Matt
>
> _______________________________________________
> users mailing list
> users at concurrency.cc
> http://lists.concurrency.cc/mailman/listinfo/users