[hpsdr] Operating Configurations

[Christopher T. Day]

Alex,

I need to check a few details - but also need to get to work - but I
think that is essentially right. Two points already:

At step 4), the typical behavior on Windows, anyway, is to load into the
host PC the mini-class/port drivers corresponding to the device
descriptors returned. One thing I want to check is reconciling this with
FX2 firmware loading.

I still have the unresolved question of available room in the 1-Wire
devices. As an example, the default descriptors in the FX2 (which are
intended only for booting) are a ~200 bytes long. Given all the audio
stuff on the Janus board, I'd be happier with something like 2kB. Most
of the 1-Wire EEPROMS I saw were about 265 _bits_. The biggest one is
expensive and has a long lead time.


	Chris - AE6VK


-----Original Message-----
From: Alex [mailto:harvilchuck at yahoo.com] 
Sent: Friday, May 12, 2006 8:16 AM
To: Philip Covington; Lyle Johnson
Cc: Christopher T. Day; hpsdr at hpsdr.org
Subject: Re: [hpsdr] Operating Configurations

At startup time we need to be able to have OZY know what is connected to
ATLAS and report it back to the host computer or to SASQUATCH. 

So would this be a sequencing at HPSDR connection time (host computer,
no SASQUATCH):

(1) Host computer queries OZY via USB for device descriptors
(2) OZY queries the cards via the Dallas 1-wire interface for their
device descriptors (stored on each card)
(3) OZY returns the device descriptors to the host computer
(4) Host computer then transmits via USB the appropriate device control
8051 code to be loaded into OZY's FX2 for operations (based on the
device descriptors returned)
(5) OZY FX2 loads the received code, and activates the reset line for
the ATLAS bus 
(6) All ATLAS cards reset and report ready status to OZY via I2C bus


Alex, N3NP


 
----- Original Message ----
From: Philip Covington <p.covington at gmail.com>
To: Lyle Johnson <kk7p at wavecable.com>
Cc: Christopher T. Day <CTDay at lbl.gov>; hpsdr at hpsdr.org
Sent: Friday, May 12, 2006 9:07:32 AM
Subject: Re: [hpsdr] Operating Configurations

***** High Performance Software Defined Radio Discussion List *****

On 5/11/06, Lyle Johnson <kk7p at wavecable.com> wrote:
<snip>
> What if we dedicate yet another ATLAS tine - X16C0/pin A18 - to a
1-wire
> bus and add a Dallas 1-wire serial number chip with EEPROM (DS2430
> series, for example)?  You can have a gazillion of these - more than
> we'll ever have slots - and each one has a unique electronic serial
> number besides.  The protocol to enumerate the devices is readily
> available and easy to implement.

We use the dallas S/N and temp sensor devices to ID our boards at
OSU-ISL.

For HPSDR OZY we could steal one of the serial ports from the FX2 and
use a DS2480B to interface to the 1-Wire bus.  That way we would not
have to generate the 1-Wire timing in the FX2 or FPGA.  The FX2
firmware would just set up the serial port and read the 1-Wire bus for
configuration.

<http://pdfserv.maxim-ic.com/en/ds/DS2480B.pdf>

73 de Phil N8VB
_______________________________________________
HPSDR Discussion List
To post msg: hpsdr at hpsdr.org
Subscription help: http://lists.hpsdr.org/listinfo.cgi/hpsdr-hpsdr.org
HPSDR web page: http://hpsdr.org
Archives: http://lists.hpsdr.org/pipermail/hpsdr-hpsdr.org/





 1147448939.0