Homebrew, open source, repurposed, hacked, software defined, open hardware

Sunday, 16 December 2012

JTAG firmware updates on the HPSDR

This guide is really just a set of cheat notes to go along with

http://openhpsdr.org/wiki/index.php?title=Quick_Startup_Guide_%28Windows%29

First of all, a clean installation of Windows XP SP2

Windows XP also needs:

Windows Imaging Components
Windows Installer 3.1
.NET Framework 1.1

.NET 2.0 SP1
.NET 4.0

for the PowerSDR 2.2.5 (W5WC) installer to be able to proceed

USBIO.exe is also needed


The first time an HPSDR is upgraded, the JTAG programming firmware is loaded into the Ozy board. This only needs to be done once.

After this, Ozy is put in the 2nd slot from the power connector, and the Mercury and Penelope boards are upgraded one after the other in the slot between the power connector and Ozy.

This picture shows where the JTAG jumper (a tan colour) goes on the Mercury-EU receiver:


This photo shows where the jumper goes on Penelope, the 0.5watt exciter:


The batch files for programming need modifying as follows, to accommodate the new version of the Quartus software, which is v12.1

For Program-Penelope-EPCS4.bat the following three blocks of text need to be added:

ECHO  C. Quartus v12.1

IF /I '%Choice%'=='C' GOTO Q121

:Q121
SET DIRECTORY=c:\altera\12.1\qprogrammer\bin\quartus_pgm
GOTO LOOP


Similarly, for the Program-Mercury-EPCS16.bat the following six additions are needed:

ECHO  C. Quartus v12.1

IF /I '%Choice%'=='C' GOTO Q121

:Q121
SET DIRECTORY=c:\altera\12.1\qprogrammer\bin\quartus_pgm
GOTO LOOP

ECHO Oeu. Program using Mercury_eu_v3.3

IF /I '%Choice%'=='Oeu' GOTO ItemOEU

:ItemOEU
%DIRECTORY% -c USB-Blaster mercury_EU_v3.3.cdf
GOTO CONTINUE


Finally, the Mercury programming batch file expects a .cdf file for the Mercury EU board, and this can be easily created by modifying the TAPR Mercury .cdf file in a text editor to contain the file name for the Mercury EU firmware.

These files should be updated in due course on the svn, eliminating the need for modifications.

No comments:

Post a Comment