[hpsdr] Sasquatch II

[Philip Covington]

On Wed, Dec 10, 2008 at 1:48 PM, Lyle Johnson <kk7p at wavecable.com> wrote:

> The way I read things, the development path for Sasquatch may be:
>
> 1) Port dttsp to the Beagleboard.
>
> 2) Interface the Beagleboard to ATLAS via OZY (USB).
>
> 3) Create a small carrier board (Son of Sasquatch) for the Beagleboard to
> allow its GPIO to interface to ATLAS.  This is very dependent on there being
> sufficient bandwidth, etc., for the FPGAs downstream to be loaded and
> interfaced (Penelope, Mercury, Phoenix/Janus).
>
> 4) Evaluate creating an OMAPL137-based board with the bus bandwidth for
> ATLAS, etc.  If this looks like a reasonable thing to do then...
>
> 5) Port dttsp to the OMAPL137.
>
> 6) Create the hardware OMAPL137 board (Sasquatch II).
>
> ?
>
> 73,
>
> Lyle KK7P

Looks like the only reasonable custom board route to go down might be
the -L137 with the BGA256 package.   The cost of doing a board like
the Beagle Board with the OMAP3530 is going to be very very expensive
unless you do 1000+, I think.  The cost of prototypes might be just
horrible.  There was a discussion on the Beagle Board forum about
doing custom OMAP3530 boards and the quotes they were getting were
hair raising.  Looks like the Beagle Board is 6 layers, .4mm, with
blind vias, etc... not cheap stuff!

Phil N8VB

 1228948810.0