This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: I2C and SPI porting help
Gary Thomas wrote:
On Fri, 2005-10-28 at 15:21 +0100, Will Wagner wrote:
Carlos Sobrinho wrote:
Hello there.
I'm working with a AEB-1 board and I implemented the SPI and I2C buses with
bit bang but now I would like to migrate my code to use the cyg_i2c_* and
cyg_spi_* infrastructure.
I read the hardware porting guide but I still need some more info.
Can anyone point me in the right direction? Maybe give a example?
I read that I only need some basic io in some functions and I need to pass the
function pointer to the I2C/SPI struct.
Do I need to add something in the packages/dev/spi... or can I use it in my
own application?
Any information would be gladly appreciated
I can send you my implementation of SPI using an MPC866P if you want an
example.
Could you post it here (so we may all benefit)?
Very happy to post it. Should I be posting it here or the ecos devel
mailing list? I would like to just tidy it up a bit first before
submitting it. I also have a whole load of other changes to support the
866P that I'd like to submit, I thought I'd tidy it all up and then
submit it all at once.
Does it use the cyg_XXX infrastructure?
Yes it uses the cyg SPI infrastructure. It is heavily based on the arm
at91 code checked into anoncvs.
Thanks
--
------------------------------------------------------------------------
Will Wagner will_wagner@carallon.com
Senior Project Engineer Office Tel: 0207 371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss