Hello Matt,
Let us talk here about SPI, and not in the RF12 discussion.
I saw your code, and you are right about the mode.
The mode is not only about speed, but also about clock polarity.
About my other remark:
It would be nice if in the labels of the procedures and functions
no “_sw” or “_hw” appears for the ones who are compatible.
I  know that changing labels in the lib for the hardware driver
can cause confusion. But still ...
Perhaps this is the solution: Identical routines with old and new
names in
the same module, and old names marked with “outdated, not compatible”.
The compiler will remove unused ones.
Background:
I had SPI working with the hardware, when I the interface-hardware
became
needed for I2C (in a project with Joep Suijs).
So to use Standard I/O pins I not only had to write a
SPI_sw_master.jal
but also change all the code that used the old routines (or have “_hw”
in the
calls in SPI_sw...). In the hw -sw driver pair for I2C, I saw that
there was
no need.

By the way: are you interested in a driver for the 24lc256 SPI-RAM?
If so: mail [email protected] and you get it. I have no time to check
for JALLIB style
as I am very busy with a radio-link using a RFM70. The RF12B did not
pass for
the project with Joep.
-------------------------------------------------------------------

On 15 mrt, 08:24, [email protected] wrote:
> Revision: 2520
> Author: [email protected]
> Date: Tue Mar 15 00:23:45 2011
> Log: SPI software libraryhttp://code.google.com/p/jallib/source/detail?r=2520
>
> Added:
>   /trunk/include/peripheral/spi/spi_master_sw.jal

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to