[hpsdr] Universal synth bus and stuff

[Lyle Johnson]

 >> Also we are looking to be compatible with HPSDR at the socket
 >> level so we can interchange hardware, but unless someone
 >> defines a pin standard soon, we will have to go our own way.

> A PDF document describing ATLAS and the but definitions is available at (http://www.hamsdr.com/dnld.aspx?id=217) and some additional information at (http://www.needles.de/pics/Atlas_Bus_Def.pdf)

After looking at this document, are there any specific signals that your 
project requires that are not already defined or suggested?  If so, 
having a list of them might result in some further suggested uses of 
backplane signals.

***

Regarding an abstraction layer for standardizing your RF control signals...

You might want to consider making this an SPI interface.  Most 
microcontrollers have at least one SPI interface, and if you choose to 
use one with two SPI interfaces as well as one I2C interface, you should 
be able to handle almost anything.  Or, you might make it an I2C 
interface if you can obtain a microcontroller with two I2C and one SPI 
interface on it.  However, SPI can typically be clocked much faster than 
I2C.  I am not sure if this capability would directly translate into 
benefits or greater flexibility for your projects.


73,

Lyle KK7P


 1149000118.0