Altera Blaster Problems

744 views
Skip to first unread message

Graeme Jury

unread,
Mar 18, 2019, 6:02:48 AM3/18/19
to Hermes-Lite
Hello Group,

It's the old blaster problem again. I received a blaster from Steve's link (alicexxx) today and it turned out to be an STM type and again won't go. It's hard to believe that these keep getting churned out by the hundreds and nobody is protesting or complaining that they don't work which makes me suspicious that I have something incorrectly set up. I did have a Blaster that worked but handed it on to Roger zl1ami never dreaming that it would be so hard to get another.

I really tried everything I could today including erasing my ver 13 quartus and installing the latest 18.1 version. To make sure that it is working ok I unpacked my HL1 (it was packed to move house) and ran a verify on it which worked flawlessly so I am pretty sure the jtag chain and programmer software are good. If there was noise on the STM blaster program lead I would not have expected a jtag chain fail straight off. I also get the programmer reporting hardware not found.

Has anybody got one of these STM blasters going and if so what is your magic formula? I have 3 of the little blighters in my attempts to score a pic based one and I am starting to feel that they may be now unobtainable so cheap clones may be a thing of the past.

73, Graeme ZL2APV

Alan Hopper

unread,
Mar 18, 2019, 6:23:47 AM3/18/19
to Hermes-Lite
Hi Graeme,
my slightly older stm blaster is listed in Device Manager as 'Altera USB-Blaster' the driver date is 21/04/2009 and version 2.4.16.0
Sven did mention that his recently purchased blaster had the ribbon cable assembled wrongly.
73 M0NNB

Graeme Jury

unread,
Mar 18, 2019, 6:40:52 AM3/18/19
to Hermes-Lite
Thanks for the response Alan. I take it that your blaster is working ok and I will check the wiring of the programming lead plus will shorten it a bit. Btw SparkSDR works really well for me and was up for 4 days without a hitch.

73, Graeme ZL2APV

Graeme Jury

unread,
Mar 18, 2019, 2:26:41 PM3/18/19
to Hermes-Lite
Hello Group,

I should have said that I am using Linux Mint 18.1 and do not have access to a Windows computer. It seems that this may be a Linux problem as I now believe that some Windows users at least after sorting out the driver issue do have theirs going.

I have shown below the errors that I get while trying to run the programmer and will be grateful if anyone who could would skim through and see if anything causes concern. If I can't get this going I will get a Raspberry Pi and program it with that.

Here I am checking after plugging in the blaster
gvj@gvj-M92p ~ $ dmesg | tail
[29506.331674] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[29506.480765] usb 3-2: New USB device found, idVendor=09fb, idProduct=6001
[29506.480769] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[29506.480771] usb 3-2: Product: USB-Blaster(Altera)
[29506.480773] usb 3-2: Manufacturer: Altera
[29506.480775] usb 3-2: SerialNumber: 6D8250974954

Here I am checking that it is found as a USB device
gvj@gvj-M92p ~ $ lsusb | grep Altera
Bus 003 Device 004: ID 09fb:6001 Altera Blaster

This is my /etc/udev/rules.d so I can run jtagd as root
# For Altera USB-Blaster permissions.
SUBSYSTEM=="usb",\
ENV{DEVTYPE}=="usb_device",\
ATTR{idVendor}=="09fb",\
ATTR{idProduct}=="6001",\
MODE="0666",\
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}",\
RUN+="/bin/chmod 0666 %c"
# "SUBSYSTEM==\"usb\", ATTR{idVendor}==\"09fb\", ATTR{idProduct}==\"6001\", MODE=\"0666\""

Here I start jtagd in the foreground in debug mode so I can follow what is happening there
gvj@gvj-M92p ~ $ ./intelFPGA/18.1/qprogrammer/bin/jtagd --foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster(Altera) [3-2]"

  *** When I run jtagconf it adds the following lines
USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed

The config file reports
gvj@gvj-M92p ~ $ ./intelFPGA/18.1/qprogrammer/bin/jtagconfig
1) USB-Blaster(Altera) [3-2]
  Unable to read device chain - JTAG chain broken

Trying with the programmer ver 18.1

First I start jtagd in debug mode si I can monitor what it is doing

./intelFPGA/18.1/qprogrammer/bin/jtagd --foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster(Altera) [3-2]"

It pauses at this point until I run the programmer

USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster port (/dev/bus/usb/003/004) opened
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster closed

Obviously did some retries. Here is the message screen from the programmer ...
Info (209060): Started Programmer operation at Tue Mar 19 07:02:44 2019
Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F30DD
Info (209007): Configuration succeeded -- 1 device(s) configured
Error (209037): JTAG Server can't access selected programming hardware
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Tue Mar 19 07:03:10 2019

Maybe this information will help someone see where I am going wrong. One thing that I have not followed up yet is the line when I first start jtagd ...
Using config file /etc/jtagd/jtagd.conf
which may be a clue. I have searched the whole intel directory and have not found a config file anywhere.

Nil desperandum, Graeme ZL2APV

Sebastien F4GRX

unread,
Mar 18, 2019, 3:24:45 PM3/18/19
to hermes-lite
Hello,

You got to the exact same point I reached using quartus 18 in Linux.

I don't think we are doing something wrong. This looks like a
straightforward operation. The FPGA is detected, but somewhat can not be
programmed.

More debugging seem to require a deeper knowledge of the internals of
this device.

That's the point where I rm -rf the intel directory and got immediate
success with a raspberry pi.

But I admit, this whole situation with blaster clone is deeply
disappointing. There is no way to understand what is going wrong.

Sebastien
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

Steve Haynal

unread,
Mar 18, 2019, 4:45:17 PM3/18/19
to Hermes-Lite
Hi Graeme,

Thanks for the details. I ordered another USB blaster from a different vendor a couple of week ago, so hopefully that will be the STM version.

Do you have the power on and connected to the HL2 when you are programming? No power to the unit will lead to problems where you can see something on the JTAG but then can't do much.

Did you download the standalone programmer or Quartus lite? If Quartus lite, did you also download and install the support for Cyclone IV devices, or include support for all devices in your download? To program the EEPROM, a special image is loaded on to the FPGA to allow this indirect programming of the EEPROM. You may be missing this special image.

One way to check if you are missing the special image is to try and program the .sof file, which is volatile but doesn't require any extra images. Can you try that? The .sof files are also on the gateware release page.

I just received a $5.00 pi zero. I will set that up for HL2 gateware programming and share the setup. That has some complexity as you use the pi zero in gadget mode, and gadget mode can be tricky for some to setup.

73,

Steve
kf7o

Graeme Jury

unread,
Mar 18, 2019, 5:01:33 PM3/18/19
to Hermes-Lite
Hi Steve,

Thanks for the pointers which have got me another step down the road.

I did have power on and a connection to the HL2.

I download the standalone programmer only and I may be missing the special image.

I have just tried programing the .sof file and it went perfectly.

Looks like I need to figure out how to download and install support for cyclone IV devices and get the special image.

A Raspberry Pi zero will be a big asset to the stable :-)

Many thanks for your help Steve it has taken me forward and I can see hope here.

73, Graeme ZL2APV

Steve Haynal

unread,
Mar 19, 2019, 2:07:53 AM3/19/19
to Hermes-Lite
Hi Graeme,

I have just the Quartus 18.1 programmer installed on 1 machine and the "special" file should be included:
18.1/qprogrammer/common/devinfo/programmer/sfl_enhanced_ep4ce22.sof

I removed that file and Quartus then give an error about it missing, so I no longer think that is your problem.

Attached is a screenshot of my successful programming. Do you see any differences compared to yours?

73,

Steve
kf7o

quartus1.png

Graeme Jury

unread,
Mar 19, 2019, 6:31:28 AM3/19/19
to Hermes-Lite
Hi Steve,

Again thanks for giving me your time. I have done a screenshot of my set-up which still fails so you can see exactly what I get. There is a bug in Quartus where the checkboxes don't show and the filename disappears after the spot where the program checkbox would show is clicked but I think this is a painting bug as I have had it before. Anyway clicking the right spot enables the start button and away I go heading for failure. My procedure was...
Boot from cold.
plug blaster onto HL2
Power up HL2
Plug blaster into USB
From a terminal change to programmer bin directory
Run in terminal ./Quartus_pgmw
Check the blaster is selected in hardware
Load the .jic file
Check program box
Click start.

I also tried setting up for a blaster II as per Intel instructions but that brought on jtag chain broken errors. I tried this because some of the advertisements claimed the cables were blaster II but clearly this one at least is not.

I take it that as I can volatile program the fpga it proves my cable is correct and there are no reversals as found by others and my rate and data throughput are ok?

73, Graeme ZL2APV

Sorry using a tablet which won't let me add my screenshot so will do it in the morning.

Graeme Jury

unread,
Mar 19, 2019, 6:49:07 AM3/19/19
to Hermes-Lite
Finally figured it out 😀

Graeme
quartus1_gj.png

Sebastien F4GRX

unread,
Mar 19, 2019, 6:52:22 AM3/19/19
to Hermes-Lite
I confirm that I hit the exact same error with my own cable.

Sebastien

Steve Haynal

unread,
Mar 19, 2019, 11:57:17 AM3/19/19
to Hermes-Lite
Hi Graeme,

That bug with checkboxes in Quartus on Linux is annoying. There is a workaround of changing your theme. I use Linux Mint, and if I set the Themes->Controls to "Mint-Y" instead of "Mint-X" the problem goes away.

Since you can program .sof but not .jic, let's try changing a few of the settings related to the serial flash loader to see if it fixes your problem or provides us with more information. Attached is a screenshort of Tools->Options->Programmer. By default "Use the enhanced mode Serial Flash Loader (SFL) IP for factory default helper image" is checked. Can you uncheck this and try programming the .jic file. It still works for me, although programming takes a little longer. You may also want to experiment with the compression, CRC settings and adding extra serial flash page program time.

73,

Steve
kf7o

options1.png

in3otd

unread,
Mar 19, 2019, 1:39:26 PM3/19/19
to Hermes-Lite
er, silly question... what happens if you click "Start" again after the first failure? Rarely here, with Windows and a PIC-based programmer, the first attempt at programming the FPGA returns the same failure message, but after pressing "Start" a second time programming always succeeds.

73 de Claudio, IN3OTD / DK1CG

Sid Boyce

unread,
Mar 19, 2019, 6:35:15 PM3/19/19
to herme...@googlegroups.com
Hi Claudio,
In my case fails on any number of tries.
73 ... Sid.

On 19/03/2019 17:39, in3otd wrote:
> er, silly question... what happens if you click "Start" again after
> the first failure? Rarely here, with Windows and a PIC-based
> programmer, the first attempt at programming the FPGA returns the same
> failure message, but after pressing "Start" a second time programming
> always succeeds.
>
> 73 de Claudio, IN3OTD / DK1CG
>
> On Tuesday, March 19, 2019 at 11:49:07 AM UTC+1, Graeme Jury wrote:
>
> Finally figured it out 😀
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.


--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Josh Logan

unread,
Mar 19, 2019, 6:54:17 PM3/19/19
to Sid Boyce, Hermes-Lite

I wanted to send in a link and picture of my USB blaster:

I purchased it about a month ago, and used this to install the updated firmware via Windows 10.
IMG_20190319_154205.jpg

73, Josh KD7HGL
 

To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

Sid Boyce

unread,
Mar 19, 2019, 7:05:56 PM3/19/19
to Josh Logan, Hermes-Lite
Thanks Josh,
I'll check it out.
73 ... Sid.

On 19/03/2019 22:53, Josh Logan wrote:
>
> I wanted to send in a link and picture of my USB blaster:
> https://www.ebay.com/itm/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/332826408783Â
>
>
> I purchased it about a month ago, and used this to install the updated
> firmware via Windows 10.
> IMG_20190319_154205.jpg
>
> 73, Josh KD7HGL
> Â
>
> On Tue, Mar 19, 2019 at 3:35 PM Sid Boyce <boyc...@gmail.com
> <mailto:boyc...@gmail.com>> wrote:
>
> Hi Claudio,
> In my case fails on any number of tries.
> 73 ... Sid.
>
> On 19/03/2019 17:39, in3otd wrote:
> > er, silly question... what happens if you click "Start" again after
> > the first failure? Rarely here, with Windows and a PIC-based
> > programmer, the first attempt at programming the FPGA returns
> the same
> > failure message, but after pressing "Start" a second time
> programming
> > always succeeds.
> >
> > 73 de Claudio, IN3OTD / DK1CG
> >
> > On Tuesday, March 19, 2019 at 11:49:07 AM UTC+1, Graeme Jury wrote:
> >
> >     Finally figured it out 😀
> >
> >     Graeme
> >
> >     On Tuesday, March 19, 2019 at 11:31:28 PM UTC+13, Graeme
> Jury wrote:
> >     > Hi Steve,
> >     >
> >     > Again thanks for giving me your time. I have done a
> screenshot
> >     of my set-up which still fails so you can see exactly
> what I get.
> >     There is a bug in Quartus where the checkboxes don't show
> and the
> >     filename disappears after the spot where the program checkbox
> >     would show is clicked but I think this is a painting bug
> as I have
> >     had it before. Anyway clicking the right spot enables the
> start
> >     button and away I go heading for failure. My procedure was...
> >     > Boot from cold.
> >     > plug blaster onto HL2
> >     > Power up HL2
> >     > Plug blaster into USB
> >     > From a terminal change to programmer bin directory
> >     > Run in terminal ./Quartus_pgmw
> >     > Check the blaster is selected in hardware
> >     > Load the .jic file
> >     > Check program box
> >     > Click start.
> >     >
> >     > I also tried setting up for a blaster II as per Intel
> >     instructions but that brought on jtag chain broken
> errors. I tried
> >     this because some of the advertisements claimed the
> cables were
> >     blaster II but clearly this one at least is not.
> >     >
> >     > I take it that as I can volatile program the fpga it
> proves my
> >     cable is correct and there are no reversals as found by
> others and
> >     my rate and data throughput are ok?
> >     >
> >     > 73, Graeme ZL2APV
> >     >
> >     > Sorry using a tablet which won't let me add my
> screenshot so
> >     will do it in the morning.
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Hermes-Lite" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send
> > an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> > <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>.

Graeme Jury

unread,
Mar 19, 2019, 8:03:44 PM3/19/19
to Hermes-Lite
Hi Steve,

Tried all your suggestions and yes changing to mint-Y fixed the problem and I am no longer flying blind. I tried all combination of programmer settings that you suggested and many more besides but still no luck. I have attached another screen shot which this time shows the screen better. After this I tried again with jtagd running in debug mode and got the following result ...

This is where I started the blaster in debug mode.
gvj@gvj-M92p ~/intelFPGA/18.1/qprogrammer/bin $ ./jtagd --foreground --debug

JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster(Altera) [3-2]"

The output pauses at this point until I run an operation which in this case is the programmer.
The screenshot shows the programmer output while below shows the jtagd debug output.
USB-Blaster port (/dev/bus/usb/003/007) opened

USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster port (/dev/bus/usb/003/007) opened

USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster closed

I attempted to start the programmer a second time but it failed with the message shown on the screenshot.
I again ran the programmer with the .sof file and again it worked everytime leaving on HL2 led1 blinking and led4 steady on.

73, Graeme zl2apv
quartus2_gj.png

Graeme Jury

unread,
Mar 19, 2019, 8:09:04 PM3/19/19
to Hermes-Lite
Hi Claudio,

Yes, sure did try several times but always ...
Info (209060): Started Programmer operation at Wed Mar 20 13:06:14 2019

Error (209037): JTAG Server can't access selected programming hardware
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Wed Mar 20 13:06:34 2019

Keep the suggestions coming we have Sid and Sebastien hanging in there too. The answer to this will make a lot of people happy :-)

73, Graeme zl2apv

Steve Haynal

unread,
Mar 20, 2019, 12:20:49 AM3/20/19
to Hermes-Lite
Hi Graeme,

Just for reference, here is my jtagd output. Mine appears to broadcast and force JTAG version 0. Are your running through a USB hub? Maybe you can try directly to the computer? Do all 3 of your blasters behave the same way?

73,

Steve
kf7o

JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster [1-1.1]"
USB-Blaster port (/dev/bus/usb/001/019) opened
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/001/019) opened
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/001/019) opened
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed
USB-Blaster port (/dev/bus/usb/001/019) opened
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster reports JTAG protocol version 0, using version 0
USB-Blaster closed

Graeme Jury

unread,
Mar 20, 2019, 4:46:57 AM3/20/19
to Hermes-Lite
Thanks Steve,

Sure is turning out to be a problem. I have found one of my other blasters and it gives me exactly the same results as my current one. Roger zl1ami is presently in Australia but when he gets back I will ask him to send me the blaster that I gave him as it used to work so I can try it out on quartus 18.1

I have ordered a Raspberry Pi which should be here in a few days and will try programming with that. I am losing hope of ever getting the Blaster to work and I am amazed that it is so much of a problem.

73, Graeme ZL2APV

Wolfram Perrey

unread,
Mar 22, 2019, 11:32:37 PM3/22/19
to Hermes-Lite
Hello Graem, without intention to explain why it worked for me or to stress someone else with this
unforgiving issue, but as reference where I sourced my blaster:


Some observations:
- Yes, its a STM type Blaster - May be there are some with difference firmware versions
inside (Some work? Some not?? may be???) but my blaster from this source definitely works (And work well every time I used!!)
- Please look in the comments from this AE dealer, almost all positive and one buyer very specific that it worked for him also under Win10!
- SW: "Programmer (Quartus Prime 18.1)" and the application of the original drivers from inside the SW package - (Used on Win7 64bit and a Win10 64bit mashine)
- Make sure that the system has manually installed only Quartus driver (Nothing automatic authentic, cryptic and authorized and with stupid windows nobo warnings)
(If you let Win choose to load divers automatically, or You choose the wrong driver set from Quartus you get a lot of troubles inclusive blue screens and so on)
Deal with drivers under Win can be very unforgiving. There are are tons of descriptions in the internet how to deal with that.
For shure, the ribbon cable must be connected right, on the programmer side as on the target site. I simply copied how to connect the ribbon on both
side from Steve instruction video - one by one exactly - to avoid any diference. Yes, and I also double checked that my ribbon showed up exactly as on the video.
May be there are some Chines who are not doing well on there ribbon cable assembly, but If You are unsure, compare to a working reference is good practice.

But anyway, today order two more Blaster from this referenced source, for testing that this source rely works. The parts are cheap enough to do that and
when it worked (I expect that) I make them a giveaway - May be for You or someone else struggling with the same problem.    . 
 

Am Mittwoch, 20. März 2019 05:46:57 UTC-3 schrieb Graeme Jury:
Thanks Steve,

Sure is turning out to be a problem. I have found one of my othugler blasters and it gives me exactly the same results as my current one. Roger zl1ami is presently in Australia but when he gets back I will ask him to send me the blaster that I gave him as it used to work so I can try it out on quartus 18.1

Steve Haynal

unread,
Mar 22, 2019, 11:48:07 PM3/22/19
to Hermes-Lite
Hi Wolfram,

Have you tried your USB Blaster under Linux? Graeme has had trouble under Linux, and I don't think he has access to Windows. He can program a .sof file but not the .jic file. This is interesting as it indicates his setup mostly works, but has trouble when indirectly programming the EEPROM. I think the Quartus programmer switches to some other mode of operation during this indirect programming which his Blaster is not fully supporting. Amogh mentioned that some people are reflashing the STM firmware. I suspect there are some STM blasters with a version of firmware that has timing incompatibilities with the indirect programming. I have ordered a third USB Blaster and hope to receive a STM-based one this time.

Best Regards,

Steve Haynal

Graeme Jury

unread,
Mar 22, 2019, 11:57:33 PM3/22/19
to Steve Haynal, Hermes-Lite
Hi Wolfram, Steve and Group,

As Steve pointed out I am Linux only here and I think my STM based programmer will work with Windows but for Linux it is exactly as Steve explained. The re-flashing is interesting and I will follow that up. Steve if you want one of the blasters I have that don't work for me I would be happy to make you a present of it.

Thanks for persevering with this.

Graeme ZL2APV

--
You received this message because you are subscribed to a topic in the Google Groups "Hermes-Lite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hermes-lite...@googlegroups.com.

Wolfram Perrey

unread,
Mar 23, 2019, 1:57:53 AM3/23/19
to Hermes-Lite
Hello Graem and Steve, sorry, I never tried Linux. I have one machine with a Linux Mint Serena and I will try that even as I'm
not so familiar with the OS

Steve Haynal

unread,
Mar 25, 2019, 12:40:30 AM3/25/19
to Hermes-Lite
Hi Graeme,

Thanks for you offer of a STB-based programmer. My next order should arrive soon. If it is not STM-based, I will take you up on your offer.

73,

Steve
kf7o
To unsubscribe from this group and all its topics, send an email to hermes-lite+unsubscribe@googlegroups.com.

Sid Boyce

unread,
Mar 26, 2019, 8:27:01 AM3/26/19
to herme...@googlegroups.com
Hi Steve,
Results from 4 programmers:-

Today I received a USB Blaster Rev.C that looks just like the one you have.
Results with 18.1 and 15.0.
slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin # ./jtagconfig -d
1) USB-Blaster(Altera) [1-3]
  Unable to read device chain - JTAG chain broken

  Captured DR after reset = ()
  Captured IR after reset = ()
  Captured Bypass after reset = ()
  Captured Bypass chain = ()
  JTAG clock speed 6 MHz

2) Remote server slipstream: Unable to connect

slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
1) USB-Blaster(Altera) [1-3]
  020F30DD   EP3C25/EP4CE22 (IR=10)

  Captured DR after reset = (020F30DD) [32]
  Captured IR after reset = (155) [10]
  Captured Bypass after reset = (0) [1]
  Captured Bypass chain = (0) [1]
  JTAG clock speed 6 MHz

2) Remote server slipstream: Unable to connect

I tried 2 others that also do not work with 18.1 - AOK with 15.0. One is
a large 105mmx53mm Altera USB Blaster Rev.C.
slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
1) USB-Blaster [1-3]
  020F30DD   EP3C25/EP4CE22 (IR=10)

  Captured DR after reset = (020F30DD) [32]
  Captured IR after reset = (155) [10]
  Captured Bypass after reset = (0) [1]
  Captured Bypass chain = (0) [1]
  JTAG clock speed 6 MHz

2) Remote server slipstream: Unable to connect

slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
1) USB-Blaster [1-3]
  020F30DD   EP3C25/EP4CE22 (IR=10)

  Captured DR after reset = (020F30DD) [32]
  Captured IR after reset = (155) [10]
  Captured Bypass after reset = (0) [1]
  Captured Bypass chain = (0) [1]
  JTAG clock speed 6 MHz

2) Remote server slipstream: Unable to connect


73 ... Sid.


On 25/03/2019 04:40, Steve Haynal wrote:
> Hi Graeme,
>
> Thanks for you offer of a STB-based programmer. My next order should
> arrive soon. If it is not STM-based, I will take you up on your offer.
>
> 73,
>
> Steve
> kf7o
>
>
> On Friday, March 22, 2019 at 8:57:33 PM UTC-7, Graeme Jury wrote:
>
> Hi Wolfram, Steve and Group,
>
> As Steve pointed out I am Linux only here and I think my STM based
> programmer will work with Windows but for Linux it is exactly as
> Steve explained. The re-flashing is interesting and I will follow
> that up. Steve if you want one of the blasters I have that don't
> work for me I would be happy to make you a present of it.
>
> Thanks for persevering with this.
>
> Graeme ZL2APV
>
> On Sat., 23 Mar. 2019, 4:48 pm Steve Haynal,
> when it worked _(I expect that)_ I make them a giveaway -
> May be for You or someone else struggling with the same
> problem.    .Â
> Â
>
> Am Mittwoch, 20. März 2019 05:46:57 UTC-3 schrieb Graeme
> Jury:
>
> Thanks Steve,
>
> Sure is turning out to be a problem. I have found one
> of my othugler blasters and it gives me exactly the
> same results as my current one. Roger zl1ami is
> presently in Australia but when he gets back I will
> ask him to send me the blaster that I gave him as it
> used to work so I can try it out on quartus 18.1
>
> I have ordered a Raspberry Pi which should be here in
> a few days and will try programming with that. I am
> losing hope of ever getting the Blaster to work and I
> am amazed that it is so much of a problem.
>
> 73, Graeme ZL2APV
>
> --
> You received this message because you are subscribed to a
> topic in the Google Groups "Hermes-Lite" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>.
> To unsubscribe from this group and all its topics, send an
> email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.


Steve Haynal

unread,
Mar 26, 2019, 11:03:47 AM3/26/19
to Hermes-Lite
Hi Sid,

What do you mean by "looks just like the one you have?" Is it PIC-based or STM32-based inside?

For 18.1, have you tried the following?

In you messages, 3/4 times the JTAG chain is seen, but then you have a message

2) Remote server slipstream: Unable to connect 

Where is this coming from? I don't see it on my Linux machine. This is the remote server for programming. Do you have that running? How did you start it?


There are too many variables in play, and I think for you and others who are having problems, we may need to back up and start with an entirely fresh Linux install. Perhaps a live image we can all agree on.

73,

Steve
kf7o


>         For more options, visit https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send

Sid Boyce

unread,
Mar 26, 2019, 12:29:44 PM3/26/19
to herme...@googlegroups.com
The new one is STM32-based.
openSUSE Tumbleweed
--------------------------------------------
slipstream:~ # l /usr/lib64/libudev.so*
lrwxrwxrwx 1 root root     12 Mar 13 12:19 /usr/lib64/libudev.so ->
libudev.so.1
lrwxrwxrwx 1 root root     17 Mar 13 12:19 /usr/lib64/libudev.so.1 ->
libudev.so.1.6.13
-rwxr-xr-x 1 root root 182536 Mar 13 12:20 /usr/lib64/libudev.so.1.6.13

The message comes from "jtagconfig -d" and that includes the programmer
I used to upload
Hermes-Lite2/gateware/bitfiles/testing/20190223/hl2b5up/hl2b5up.jic
The chips in that Hobby Components one are PIC18FK450 and two LVC125A's.

The chip  in another one is marked SiLabs F321 with the other chip a
74HC244D.
https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf

Same problems on Kubuntu 18.10 as on openSUSE Tumbleweed.
root@sdrbox1:~# ls -l /lib/x86_64-linux-gnu/libudev.so*
lrwxrwxrwx 1 root root     12 Feb 28 19:29
/lib/x86_64-linux-gnu/libudev.so -> libudev.so.1
lrwxrwxrwx 1 root root     17 Feb 28 19:29
/lib/x86_64-linux-gnu/libudev.so.1 -> libudev.so.1.6.11
-rw-r--r-- 1 root root 125128 Feb 28 19:29
/lib/x86_64-linux-gnu/libudev.so.1.6.11
73 ... Sid.

On 26/03/2019 15:03, Steve Haynal wrote:
> Hi Sid,
>
> What do you mean by "looks just like the one you have?" Is it
> PIC-based or STM32-based inside?
>
> For 18.1, have you tried the following?
> https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux
>
> In you messages, 3/4 times the JTAG chain is seen, but then you have a
> message
>
> 2) Remote server slipstream: Unable to connectÂ
>
> Where is this coming from? I don't see it on my Linux machine. This is
> the remote server for programming. Do you have that running? How did
> you start it?
>
>
> There are too many variables in play, and I think for you and others
> who are having problems, we may need to back up and start with an
> entirely fresh Linux install. Perhaps a live image we can all agree on.
>
> 73,
>
> Steve
> kf7o
>
>
>
>
> On Tuesday, March 26, 2019 at 5:27:01 AM UTC-7, Sid Boyce wrote:
>
> Hi Steve,
> Results from 4 programmers:-
>
> Today I received a USB Blaster Rev.C that looks just like the one
> you have.
> Results with 18.1 and 15.0.
> slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin #
> ./jtagconfig -d
> 1) USB-Blaster(Altera) [1-3]
>    Unable to read device chain - JTAG chain broken
>
>    Captured DR after reset = ()
>    Captured IR after reset = ()
>    Captured Bypass after reset = ()
>    Captured Bypass chain = ()
>    JTAG clock speed 6 MHz
>
> 2) Remote server slipstream: Unable to connect
>
> slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
> 1) USB-Blaster(Altera) [1-3]
>    020F30DD   EP3C25/EP4CE22 (IR=10)
>
>    Captured DR after reset = (020F30DD) [32]
>    Captured IR after reset = (155) [10]
>    Captured Bypass after reset = (0) [1]
>    Captured Bypass chain = (0) [1]
>    JTAG clock speed 6 MHz
>
> 2) Remote server slipstream: Unable to connect
>
> I tried 2 others that also do not work with 18.1 - AOK with 15.0.
> One is
> a large 105mmx53mm Altera USB Blaster Rev.C.
> slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
> 1) USB-Blaster [1-3]
>    020F30DD   EP3C25/EP4CE22 (IR=10)
>
>    Captured DR after reset = (020F30DD) [32]
>    Captured IR after reset = (155) [10]
>    Captured Bypass after reset = (0) [1]
>    Captured Bypass chain = (0) [1]
>    JTAG clock speed 6 MHz
>
> 2) Remote server slipstream: Unable to connect
>
> slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagconfig -d
> 1) USB-Blaster [1-3]
>    020F30DD   EP3C25/EP4CE22 (IR=10)
>
>    Captured DR after reset = (020F30DD) [32]
>    Captured IR after reset = (155) [10]
>    Captured Bypass after reset = (0) [1]
>    Captured Bypass chain = (0) [1]
>    JTAG clock speed 6 MHz
>
> 2) Remote server slipstream: Unable to connect
>
>
> 73 ... Sid.
>
>
> On 25/03/2019 04:40, Steve Haynal wrote:
> > Hi Graeme,
> >
> > Thanks for you offer of a STB-based programmer. My next order
> should
> > arrive soon. If it is not STM-based, I will take you up on your
> offer.
> >
> > 73,
> >
> > Steve
> > kf7o
> >
> >
> > On Friday, March 22, 2019 at 8:57:33 PM UTC-7, Graeme Jury wrote:
> >
> >     Hi Wolfram, Steve and Group,
> >
> >     As Steve pointed out I am Linux only here and I think my
> STM based
> >     programmer will work with Windows but for Linux it is
> exactly as
> >     Steve explained. The re-flashing is interesting and I will
> follow
> >     that up. Steve if you want one of the blasters I have that
> don't
> >     work for me I would be happy to make you a present of it.
> >
> >     Thanks for persevering with this.
> >
> >     Graeme ZL2APV
> >
> >     On Sat., 23 Mar. 2019, 4:48 pm Steve Haynal,
> >     <softerh...@gmail.com
> <mailto:softerh...@gmail.com> <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>> wrote:
> >
> >         Hi Wolfram,
> >
> >         Have you tried your USB Blaster under Linux? Graeme
> has had
> >         trouble under Linux, and I don't think he has access to
> >         Windows. He can program a .sof file but not the .jic
> file.
> >         This is interesting as it indicates his setup mostly
> works,
> >         but has trouble when indirectly programming the
> EEPROM. I
> >         think the Quartus programmer switches to some other
> mode of
> >         operation during this indirect programming which his
> Blaster
> >         is not fully supporting. Amogh mentioned that some
> people are
> >         reflashing the STM firmware. I suspect there are
> some STM
> >         blasters with a version of firmware that has timing
> >         incompatibilities with the indirect programming. I have
> >         ordered a third USB Blaster and hope to receive a
> STM-based
> >         one this time.
> >
> >         Best Regards,
> >
> >         Steve Haynal
> >
> >
> >         On Friday, March 22, 2019 at 8:32:37 PM UTC-7,
> Wolfram Perrey
> >         wrote:
> >
> >             Hello Graem, without intention to explain why
> it worked
> >             for me or to stress someone else with this
> >             unforgiving issue, but as reference where I
> sourced my
> >             blaster:
> >
> >           Â
> https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>
>
> >            
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>>
>
> >
> >             Some observations:
> >             - Yes, its a STM type Blaster - May be there
> are some with
> >             difference firmware versions
> >             inside (Some work? Some not?? may be???) but
> my blaster
> >             from this source definitely works (And work
> well every
> >             time I used!!)
> >             - Please look in the comments from this AE
> dealer, almost
> >             all positive and one buyer very specific that
> it worked
> >             for him also under Win10!
> >             - SW: "Programmer (Quartus Prime 18.1)" and the
> >             application of the original drivers from
> inside the SW
> >             package - (Used on Win7 64bit and a Win10
> 64bit mashine)
> >             - Make sure that the system has manually
> installed only
> >             Quartus driver (Nothing automatic authentic,
> cryptic and
> >             authorized and with stupid windows nobo warnings)
> >             (If you let Win choose to load divers
> automatically, or
> >             You choose the wrong driver set from Quartus
> you get a lot
> >             of troubles inclusive blue screens and so on)
> >             Deal with drivers under Win can be very
> unforgiving. There
> >             are are tons of descriptions in the internet
> how to deal
> >             with that.
> >             For shure, the ribbon cable must be connected
> right, on
> >             the programmer side as on the target site. I
> simply copied
> >             how to connect the ribbon on both
> >             side from Steve instruction video - one by one
> exactly -
> >             to avoid any diference. Yes, and I also double
> checked
> >             that my ribbon showed up exactly as on the video.
> >             May be there are some Chines who are not doing
> well on
> >             there ribbon cable assembly, but If You are
> unsure,
> >             compare to a working reference is good practice.
> >
> >             But anyway, today order two more Blaster from
> this
> >             referenced source, for testing that this
> source rely
> >             works. The parts are cheap enough to do that and
> >             when it worked _(I expect that)_ I make them a
> giveaway -
> >             May be for You or someone else struggling with
> the same
> >             problem.    .Â
> >             Â
> >
> >             Am Mittwoch, 20. März 2019 05:46:57 UTC-3
> schrieb Graeme
> >             Jury:
> >
> >                 Thanks Steve,
> >
> >                 Sure is turning out to be a problem. I
> have found one
> >                 of my othugler blasters and it gives me
> exactly the
> >                 same results as my current one. Roger
> zl1ami is
> >                 presently in Australia but when he gets
> back I will
> >                 ask him to send me the blaster that I
> gave him as it
> >                 used to work so I can try it out on
> quartus 18.1
> >
> >                 I have ordered a Raspberry Pi which
> should be here in
> >                 a few days and will try programming with
> that. I am
> >                 losing hope of ever getting the Blaster
> to work and I
> >                 am amazed that it is so much of a problem.
> >
> >                 73, Graeme ZL2APV
> >
> >         --
> >         You received this message because you are subscribed
> to a
> >         topic in the Google Groups "Hermes-Lite" group.
> >         To unsubscribe from this topic, visit
> >       Â
> https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>
>
> >        
> >         To unsubscribe from this group and all its topics,
> send an
> >         email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> >         For more options, visit
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>.
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Hermes-Lite" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
USB-Plaster.png

Steve Haynal

unread,
Mar 26, 2019, 12:48:05 PM3/26/19
to Hermes-Lite
Hi Sid,

I do not see the "2) Remote server slipstream: Unable to connect"  message when doing the same on my setup. You say you see this even with your working probe? Are you certain you haven't started some Quartus server process?

73,

Steve
kf7o
 
>     >         email to hermes-lite+unsubscribe@googlegroups.com
>     <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>     >         <mailto:hermes-lite+unsub...@googlegroups.com
>     <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
>     >         For more options, visit
>     https://groups.google.com/d/optout
>     <https://groups.google.com/d/optout>
>     >         <https://groups.google.com/d/optout
>     <https://groups.google.com/d/optout>>.
>     >
>     > --
>     > You received this message because you are subscribed to the Google
>     > Groups "Hermes-Lite" group.
>     > To unsubscribe from this group and stop receiving emails from
>     it, send
>     <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
>     > For more options, visit https://groups.google.com/d/optout
>     <https://groups.google.com/d/optout>.
>
>
>     --
>     Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
>     Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
>     Senior Staff Specialist, Cricket Coach
>     Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send

Steve Haynal

unread,
Mar 26, 2019, 1:13:13 PM3/26/19
to Hermes-Lite
Hi Sid,

From your last e-mail then I am assuming your answer is yes to the question below.

I do not see this message. This may be a clue to what is different with your setup. Do you have any other nontypical jtag or usb-related process on your machine? This could be from something entirely different than Quartus. It could be some automatic script you installed with Quartus to launch a daemon.

73,

Steve
kf7o

Sid Boyce

unread,
Mar 26, 2019, 4:31:46 PM3/26/19
to herme...@googlegroups.com
Only this afternoon I did a BIOS upgrade and rebooted so no quaruts was
started, only "jtagconfig -d" which fails completely with 18.1 and works
with 15.0.
73 ... Sid.

On 26/03/2019 16:48, Steve Haynal wrote:
> Hi Sid,
>
> I do not see the "2) Remote server slipstream: Unable to connect" 
> message when doing the same on my setup. You say you see this even
> with your working probe? Are you certain you haven't started some
> Quartus server process?
>
> 73,
>
> Steve
> kf7o
> Â
>
> On Tuesday, March 26, 2019 at 9:29:44 AM UTC-7, Sid Boyce wrote:
>
> The new one is STM32-based.
> openSUSE Tumbleweed
> --------------------------------------------
> slipstream:~ # l /usr/lib64/libudev.so*
> lrwxrwxrwx 1 root root     12 Mar 13 12:19
> /usr/lib64/libudev.so ->
> libudev.so.1
> lrwxrwxrwx 1 root root     17 Mar 13 12:19
> /usr/lib64/libudev.so.1 ->
> libudev.so.1.6.13
> -rwxr-xr-x 1 root root 182536 Mar 13 12:20
> /usr/lib64/libudev.so.1.6.13
>
> The message comes from "jtagconfig -d" and that includes the
> programmer
> I used to upload
> Hermes-Lite2/gateware/bitfiles/testing/20190223/hl2b5up/hl2b5up.jic
> The chips in that Hobby Components one are PIC18FK450 and two
> LVC125A's.
>
> The chip  in another one is marked SiLabs F321 with the other chip a
> 74HC244D.
> https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf
> <https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf>
>
> Same problems on Kubuntu 18.10 as on openSUSE Tumbleweed.
> root@sdrbox1:~# ls -l /lib/x86_64-linux-gnu/libudev.so*
> lrwxrwxrwx 1 root root     12 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so -> libudev.so.1
> lrwxrwxrwx 1 root root     17 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so.1 -> libudev.so.1.6.11
> -rw-r--r-- 1 root root 125128 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so.1.6.11
> 73 ... Sid.
>
> On 26/03/2019 15:03, Steve Haynal wrote:
> > Hi Sid,
> >
> > What do you mean by "looks just like the one you have?" Is it
> > PIC-based or STM32-based inside?
> >
> > For 18.1, have you tried the following?
> >
> https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux
> <https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux>
>
> >
> > In you messages, 3/4 times the JTAG chain is seen, but then you
> have a
> > message
> >
> > 2) Remote server slipstream: Unable to connectÂ
> >
> > Where is this coming from? I don't see it on my Linux machine.
> This is
> > the remote server for programming. Do you have that running? How
> did
> > you start it?
> >
> >
> > There are too many variables in play, and I think for you and
> others
> > who are having problems, we may need to back up and start with an
> > entirely fresh Linux install. Perhaps a live image we can all
> agree on.
> >
> > 73,
> >
> > Steve
> > kf7o
> >
> >
> >
> >
> > On Tuesday, March 26, 2019 at 5:27:01 AM UTC-7, Sid Boyce wrote:
> >
> >     Hi Steve,
> >     Results from 4 programmers:-
> >
> >     Today I received a USB Blaster Rev.C that looks just like
> the one
> >     you have.
> >     Results with 18.1 and 15.0.
> >     slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin #
> >     ./jtagconfig -d
> >     1) USB-Blaster(Altera) [1-3]
> >        Unable to read device chain - JTAG chain broken
> >
> >        Captured DR after reset = ()
> >        Captured IR after reset = ()
> >        Captured Bypass after reset = ()
> >        Captured Bypass chain = ()
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster(Altera) [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     I tried 2 others that also do not work with 18.1 - AOK
> with 15.0.
> >     One is
> >     a large 105mmx53mm Altera USB Blaster Rev.C.
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >
> >     73 ... Sid.
> >
> >
> >     On 25/03/2019 04:40, Steve Haynal wrote:
> >     > Hi Graeme,
> >     >
> >     > Thanks for you offer of a STB-based programmer. My next
> order
> >     should
> >     > arrive soon. If it is not STM-based, I will take you up
> on your
> >     offer.
> >     >
> >     > 73,
> >     >
> >     > Steve
> >     > kf7o
> >     >
> >     >
> >     > On Friday, March 22, 2019 at 8:57:33 PM UTC-7, Graeme
> Jury wrote:
> >     >
> >     >     Hi Wolfram, Steve and Group,
> >     >
> >     >     As Steve pointed out I am Linux only here and
> I think my
> >     STM based
> >     >     programmer will work with Windows but for
> Linux it is
> >     exactly as
> >     >     Steve explained. The re-flashing is
> interesting and I will
> >     follow
> >     >     that up. Steve if you want one of the blasters
> I have that
> >     don't
> >     >     work for me I would be happy to make you a
> present of it.
> >     >
> >     >     Thanks for persevering with this.
> >     >
> >     >     Graeme ZL2APV
> >     >
> >     >     On Sat., 23 Mar. 2019, 4:48 pm Steve Haynal,
> >     >     <softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>
> <mailto:softerh...@gmail.com <mailto:softerh...@gmail.com>
> >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>>> wrote:
> >     >
> >     >         Hi Wolfram,
> >     >
> >     >         Have you tried your USB Blaster
> under Linux? Graeme
> >     has had
> >     >         trouble under Linux, and I don't
> think he has access to
> >     >         Windows. He can program a .sof file
> but not the .jic
> >     file.
> >     >         This is interesting as it indicates
> his setup mostly
> >     works,
> >     >         but has trouble when indirectly
> programming the
> >     EEPROM. I
> >     >         think the Quartus programmer
> switches to some other
> >     mode of
> >     >         operation during this indirect
> programming which his
> >     Blaster
> >     >         is not fully supporting. Amogh
> mentioned that some
> >     people are
> >     >         reflashing the STM firmware. I
> suspect there are
> >     some STM
> >     >         blasters with a version of firmware
> that has timing
> >     >         incompatibilities with the indirect
> programming. I have
> >     >         ordered a third USB Blaster and hope
> to receive a
> >     STM-based
> >     >         one this time.
> >     >
> >     >         Best Regards,
> >     >
> >     >         Steve Haynal
> >     >
> >     >
> >     >         On Friday, March 22, 2019 at 8:32:37
> PM UTC-7,
> >     Wolfram Perrey
> >     >         wrote:
> >     >
> >     >             Hello Graem, without
> intention to explain why
> >     it worked
> >     >             for me or to stress
> someone else with this
> >     >             unforgiving issue, but as
> reference where I
> >     sourced my
> >     >             blaster:
> >     >
> >     >           Â
> >     >           ÂÂ
> >    
> >     >             Some observations:
> >     >             - Yes, its a STM type
> Blaster - May be there
> >     are some with
> >     >             difference firmware versions
> >     >             inside (Some work? Some
> not?? may be???) but
> >     my blaster
> >     >             from this source
> definitely works (And work
> >     well every
> >     >             time I used!!)
> >     >             - Please look in the
> comments from this AE
> >     dealer, almost
> >     >             all positive and one buyer
> very specific that
> >     it worked
> >     >             for him also under Win10!
> >     >             - SW: "Programmer (Quartus
> Prime 18.1)" and the
> >     >             application of the
> original drivers from
> >     inside the SW
> >     >             package - (Used on Win7
> 64bit and a Win10
> >     64bit mashine)
> >     >             - Make sure that the
> system has manually
> >     installed only
> >     >             Quartus driver (Nothing
> automatic authentic,
> >     cryptic and
> >     >             authorized and with stupid
> windows nobo warnings)
> >     >             (If you let Win choose to
> load divers
> >     automatically, or
> >     >             You choose the wrong
> driver set from Quartus
> >     you get a lot
> >     >             of troubles inclusive blue
> screens and so on)
> >     >             Deal with drivers under
> Win can be very
> >     unforgiving. There
> >     >             are are tons of
> descriptions in the internet
> >     how to deal
> >     >             with that.
> >     >             For shure, the ribbon
> cable must be connected
> >     right, on
> >     >             the programmer side as on
> the target site. I
> >     simply copied
> >     >             how to connect the ribbon
> on both
> >     >             side from Steve
> instruction video - one by one
> >     exactly -
> >     >             to avoid any diference.
> Yes, and I also double
> >     checked
> >     >             that my ribbon showed up
> exactly as on the video.
> >     >             May be there are some
> Chines who are not doing
> >     well on
> >     >             there ribbon cable
> assembly, but If You are
> >     unsure,
> >     >             compare to a working
> reference is good practice.
> >     >
> >     >             But anyway, today order
> two more Blaster from
> >     this
> >     >             referenced source, for
> testing that this
> >     source rely
> >     >             works. The parts are cheap
> enough to do that and
> >     >             when it worked _(I expect
> that)_ I make them a
> >     giveaway -
> >     >             May be for You or someone
> else struggling with
> >     the same
> >     >            problem.   
> .Â
> >     >             Â
> >     >
> >     >             Am Mittwoch, 20.
> März 2019 05:46:57 UTC-3
> >     schrieb Graeme
> >     >             Jury:
> >     >
> >     >                Thanks Steve,
> >     >
> >     >                 Sure is turning
> out to be a problem. I
> >     have found one
> >     >                 of my othugler
> blasters and it gives me
> >     exactly the
> >     >                 same results as
> my current one. Roger
> >     zl1ami is
> >     >                presently in
> Australia but when he gets
> >     back I will
> >     >                 ask him to send
> me the blaster that I
> >     gave him as it
> >     >                 used to work so
> I can try it out on
> >     quartus 18.1
> >     >
> >     >                 I have ordered a
> Raspberry Pi which
> >     should be here in
> >     >                 a few days and
> will try programming with
> >     that. I am
> >     >                losing hope of
> ever getting the Blaster
> >     to work and I
> >     >                 am amazed that
> it is so much of a problem.
> >     >
> >     >                 73, Graeme ZL2APV
> >     >
> >     >         --
> >     >         You received this message because
> you are subscribed
> >     to a
> >     >         topic in the Google Groups
> "Hermes-Lite" group.
> >     >         To unsubscribe from this topic, visit
> >     >       Â
> >     >       ÂÂ
> >    
> >     >         To unsubscribe from this group and
> all its topics,
> >     send an
> >     >         email to
> hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >     >        
> <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>>.
> >     >         For more options, visit
> >     >         <https://groups.google.com/d/optout
> >     >
> >     > --
> >     > You received this message because you are subscribed to
> the Google
> >     > Groups "Hermes-Lite" group.
> >     > To unsubscribe from this group and stop receiving emails
> from
> >     it, send
> >     > an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>>.
> >     --
> >     Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> >     Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers
> Tech Support
> >     Senior Staff Specialist, Cricket Coach
> >     Microsoft Windows Free Zone - Linux used for all Computing
> Tasks
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Hermes-Lite" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.

Graeme Jury

unread,
Mar 26, 2019, 4:43:57 PM3/26/19
to herme...@googlegroups.com
Hi Sid,

Have you installed the whole of Quartus 15.0 or just the programmer? I
am going to install it here and will wait until I see what you have done
and see if I can get the same result. Also do you have Quartus 18.1
installed on the same machine as Quartus 15.0 i.e. is there an 18.1 and
a 15.0 directory under the intelFPGA directory?

73, Graeme ZL2APV

Sid Boyce

unread,
Mar 26, 2019, 4:53:05 PM3/26/19
to herme...@googlegroups.com
Hi Steve,
I do not. This was after doing a motheboard BIOS upgrade and rebooting
and no SDR software running.
I had tried 18.1 just before, powered off HL2, swtched to 15.0, powered
up HL2 and ran ./jtagconfig -d

As you can see, with 15.0 I got the same message and immediately after
was able to start the programmer and successfully program the HL2.
slipstream:~ # ps fax|grep jtag
 8792 pts/0    S+     0:00  |   |           \_ grep --color=auto jtag
slipstream:~ #
73 ... Sid.

On 26/03/2019 17:13, Steve Haynal wrote:
> Hi Sid,
>
> From your last e-mail then I am assuming your answer is yes to the
> question below.
>
> I do not see this message. This may be a clue to what is different
> with your setup. Do you have any other nontypical jtag or usb-related
> process on your machine? This could be from something entirely
> different than Quartus. It could be some automatic script you
> installed with Quartus to launch a daemon.
>
> 73,
>
> Steve
> kf7o
>
>
>
> On Tuesday, March 26, 2019 at 9:48:05 AM UTC-7, Steve Haynal wrote:
>
> Hi Sid,
>
> I do not see the "2) Remote server slipstream: Unable to
> connect"  message when doing the same on my setup. You say you
> see this even with your working probe? Are you certain you haven't
> started some Quartus server process?
>
> 73,
>
> Steve
> kf7o
> Â
>
> On Tuesday, March 26, 2019 at 9:29:44 AM UTC-7, Sid Boyce wrote:
>
> The new one is STM32-based.
> openSUSE Tumbleweed
> --------------------------------------------
> slipstream:~ # l /usr/lib64/libudev.so*
> lrwxrwxrwx 1 root root     12 Mar 13 12:19
> /usr/lib64/libudev.so ->
> libudev.so.1
> lrwxrwxrwx 1 root root     17 Mar 13 12:19
> /usr/lib64/libudev.so.1 ->
> libudev.so.1.6.13
> -rwxr-xr-x 1 root root 182536 Mar 13 12:20
> /usr/lib64/libudev.so.1.6.13
>
> The message comes from "jtagconfig -d" and that includes the
> programmer
> I used to upload
> Hermes-Lite2/gateware/bitfiles/testing/20190223/hl2b5up/hl2b5up.jic
>
> The chips in that Hobby Components one are PIC18FK450 and two
> LVC125A's.
>
> The chip  in another one is marked SiLabs F321 with the other
> chip a
> 74HC244D.
> https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf
> <https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf>
>
>
> Same problems on Kubuntu 18.10 as on openSUSE Tumbleweed.
> root@sdrbox1:~# ls -l /lib/x86_64-linux-gnu/libudev.so*
> lrwxrwxrwx 1 root root     12 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so -> libudev.so.1
> lrwxrwxrwx 1 root root     17 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so.1 -> libudev.so.1.6.11
> -rw-r--r-- 1 root root 125128 Feb 28 19:29
> /lib/x86_64-linux-gnu/libudev.so.1.6.11
> 73 ... Sid.
>
> On 26/03/2019 15:03, Steve Haynal wrote:
> > Hi Sid,
> >
> > What do you mean by "looks just like the one you have?" Is it
> > PIC-based or STM32-based inside?
> >
> > For 18.1, have you tried the following?
> >
> https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux
> <https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux>
>
> >
> > In you messages, 3/4 times the JTAG chain is seen, but then
> you have a
> > message
> >
> > 2) Remote server slipstream: Unable to connectÂ
> >
> > Where is this coming from? I don't see it on my Linux
> machine. This is
> > the remote server for programming. Do you have that running?
> How did
> > you start it?
> >
> >
> > There are too many variables in play, and I think for you
> and others
> > who are having problems, we may need to back up and start
> with an
> > entirely fresh Linux install. Perhaps a live image we can
> all agree on.
> >
> > 73,
> >
> > Steve
> > kf7o
> >
> >
> >
> >
> > On Tuesday, March 26, 2019 at 5:27:01 AM UTC-7, Sid Boyce
> wrote:
> >
> >     Hi Steve,
> >     Results from 4 programmers:-
> >
> >     Today I received a USB Blaster Rev.C that looks just
> like the one
> >     you have.
> >     Results with 18.1 and 15.0.
> >    
> slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin #
> >     ./jtagconfig -d
> >     1) USB-Blaster(Altera) [1-3]
> >        Unable to read device chain - JTAG chain broken
> >
> >        Captured DR after reset = ()
> >        Captured IR after reset = ()
> >        Captured Bypass after reset = ()
> >        Captured Bypass chain = ()
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster(Altera) [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     I tried 2 others that also do not work with 18.1 - AOK
> with 15.0.
> >     One is
> >     a large 105mmx53mm Altera USB Blaster Rev.C.
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >     slipstream:/home/lancelot/altera/15.0/quartus/bin #
> ./jtagconfig -d
> >     1) USB-Blaster [1-3]
> >        020F30DD   EP3C25/EP4CE22 (IR=10)
> >
> >        Captured DR after reset = (020F30DD) [32]
> >        Captured IR after reset = (155) [10]
> >        Captured Bypass after reset = (0) [1]
> >        Captured Bypass chain = (0) [1]
> >        JTAG clock speed 6 MHz
> >
> >     2) Remote server slipstream: Unable to connect
> >
> >
> >     73 ... Sid.
> >
> >
> >     On 25/03/2019 04:40, Steve Haynal wrote:
> >     > Hi Graeme,
> >     >
> >     > Thanks for you offer of a STB-based programmer. My
> next order
> >     should
> >     > arrive soon. If it is not STM-based, I will take you
> up on your
> >     offer.
> >     >
> >     > 73,
> >     >
> >     > Steve
> >     > kf7o
> >     >
> >     >
> >     > On Friday, March 22, 2019 at 8:57:33 PM UTC-7,
> Graeme Jury wrote:
> >     >
> >     >     Hi Wolfram, Steve and Group,
> >     >
> >     >     As Steve pointed out I am Linux only here
> and I think my
> >     STM based
> >     >     programmer will work with Windows but for
> Linux it is
> >     exactly as
> >     >     Steve explained. The re-flashing is
> interesting and I will
> >     follow
> >     >     that up. Steve if you want one of the
> blasters I have that
> >     don't
> >     >     work for me I would be happy to make you a
> present of it.
> >     >
> >     >     Thanks for persevering with this.
> >     >
> >     >     Graeme ZL2APV
> >     >
> >     >     On Sat., 23 Mar. 2019, 4:48 pm Steve Haynal,
> >     >     <softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>
> <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>>> wrote:
> >     >
> >     >         Hi Wolfram,
> >     >
> >     >         Have you tried your USB Blaster
> under Linux? Graeme
> >     has had
> >     >         trouble under Linux, and I don't
> think he has access to
> >     >         Windows. He can program a .sof
> file but not the .jic
> >     file.
> >     >         This is interesting as it
> indicates his setup mostly
> >     works,
> >     >         but has trouble when indirectly
> programming the
> >     EEPROM. I
> >     >         think the Quartus programmer
> switches to some other
> >     mode of
> >     >         operation during this indirect
> programming which his
> >     Blaster
> >     >         is not fully supporting. Amogh
> mentioned that some
> >     people are
> >     >         reflashing the STM firmware. I
> suspect there are
> >     some STM
> >     >         blasters with a version of
> firmware that has timing
> >     >         incompatibilities with the
> indirect programming. I have
> >     >         ordered a third USB Blaster and
> hope to receive a
> >     STM-based
> >     >         one this time.
> >     >
> >     >         Best Regards,
> >     >
> >     >         Steve Haynal
> >     >
> >     >
> >     >         On Friday, March 22, 2019 at
> 8:32:37 PM UTC-7,
> >     Wolfram Perrey
> >     >         wrote:
> >     >
> >     >             Hello Graem, without
> intention to explain why
> >     it worked
> >     >             for me or to stress
> someone else with this
> >     >            unforgiving issue, but
> as reference where I
> >     sourced my
> >     >             blaster:
> >     >
> >     >           Â
> >     >           ÂÂ
> >    
> >     >             Some observations:
> >     >             - Yes, its a STM type
> Blaster - May be there
> >     are some with
> >     >            difference firmware
> versions
> >     >             inside (Some work?
> Some not?? may be???) but
> >     my blaster
> >     >             from this source
> definitely works (And work
> >     well every
> >     >             time I used!!)
> >     >             - Please look in the
> comments from this AE
> >     dealer, almost
> >     >             all positive and one
> buyer very specific that
> >     it worked
> >     >             for him also under Win10!
> >     >             - SW: "Programmer
> (Quartus Prime 18.1)" and the
> >     >            application of the
> original drivers from
> >     inside the SW
> >     >             package - (Used on
> Win7 64bit and a Win10
> >     64bit mashine)
> >     >             - Make sure that the
> system has manually
> >     installed only
> >     >             Quartus driver
> (Nothing automatic authentic,
> >     cryptic and
> >     >            authorized and with
> stupid windows nobo warnings)
> >     >             (If you let Win choose
> to load divers
> >     automatically, or
> >     >             You choose the wrong
> driver set from Quartus
> >     you get a lot
> >     >             of troubles inclusive
> blue screens and so on)
> >     >             Deal with drivers
> under Win can be very
> >     unforgiving. There
> >     >             are are tons of
> descriptions in the internet
> >     how to deal
> >     >             with that.
> >     >             For shure, the ribbon
> cable must be connected
> >     right, on
> >     >             the programmer side as
> on the target site. I
> >     simply copied
> >     >             how to connect the
> ribbon on both
> >     >             side from Steve
> instruction video - one by one
> >     exactly -
> >     >             to avoid any
> diference. Yes, and I also double
> >     checked
> >     >             that my ribbon showed
> up exactly as on the video.
> >     >             May be there are some
> Chines who are not doing
> >     well on
> >     >             there ribbon cable
> assembly, but If You are
> >     unsure,
> >     >             compare to a working
> reference is good practice.
> >     >
> >     >             But anyway, today
> order two more Blaster from
> >     this
> >     >            referenced source, for
> testing that this
> >     source rely
> >     >             works. The parts are
> cheap enough to do that and
> >     >             when it worked _(I
> expect that)_ I make them a
> >     giveaway -
> >     >             May be for You or
> someone else struggling with
> >     the same
> >     >            problem. 
>   .Â
> >     >             Â
> >     >
> >     >             Am Mittwoch, 20.
> März 2019 05:46:57 UTC-3
> >     schrieb Graeme
> >     >             Jury:
> >     >
> >     >                Thanks Steve,
> >     >
> >     >                Sure is
> turning out to be a problem. I
> >     have found one
> >     >                of my
> othugler blasters and it gives me
> >     exactly the
> >     >                same results
> as my current one. Roger
> >     zl1ami is
> >     >                presently in
> Australia but when he gets
> >     back I will
> >     >                ask him to
> send me the blaster that I
> >     gave him as it
> >     >                used to work
> so I can try it out on
> >     quartus 18.1
> >     >
> >     >                I have
> ordered a Raspberry Pi which
> >     should be here in
> >     >                a few days
> and will try programming with
> >     that. I am
> >     >                losing hope
> of ever getting the Blaster
> >     to work and I
> >     >                am amazed
> that it is so much of a problem.
> >     >
> >     >                73, Graeme
> ZL2APV
> >     >
> >     >         --
> >     >         You received this message
> because you are subscribed
> >     to a
> >     >         topic in the Google Groups
> "Hermes-Lite" group.
> >     >         To unsubscribe from this topic,
> visit
> >     >       Â
> >     >       ÂÂ
> >    
> >     >         To unsubscribe from this group
> and all its topics,
> >     send an
> >     >         email to
> hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >     >        
> <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     >         For more options, visit
> >     >        
> >     >
> >     > --
> >     > You received this message because you are subscribed
> to the Google
> >     > Groups "Hermes-Lite" group.
> >     > To unsubscribe from this group and stop receiving
> emails from
> >     it, send
> >     > an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >     --
> >     Sid Boyce ... Hamradio License G3VBV, Licensed Private
> Pilot
> >     Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers
> Tech Support
> >     Senior Staff Specialist, Cricket Coach
> >     Microsoft Windows Free Zone - Linux used for all
> Computing Tasks
> >
> > --
> > You received this message because you are subscribed to the
> Google
> > Groups "Hermes-Lite" group.
> > To unsubscribe from this group and stop receiving emails
> from it, send
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech
> Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.

Steve Haynal

unread,
Mar 26, 2019, 11:13:05 PM3/26/19
to Hermes-Lite
Hi Sid,

Okay. Your problem appears to be different from Graeme as he can program a .sof. You also see the extra message, even when programming succeeds. Was anything installed in your /etc/init.d which may automatically start some jtag or USB related process? Any unusual software on your machine that required special libusb or related installs?

I'd like to be systematic about these problems, so here is a checklist for people, with what I think are the correct answers for you:

1. Blaster Microcontroller of failing USB probe: STM
2. Operating System: Linux openSUSE Tumbleweed
3. Power applied to HL2 during programming, and what type of powersupply? : Yes, please specify type as I am wondering about noise/levels between host and HL2
4. Version and type of Quartus install: 18.1 Full
5. udev USB blaster rules installed an udev restarted or system rebooted. Below is my /etc/udev/rules/d/51-usbblaster.rules

# USB-Blaster
SUBSYSTEM=="usb",\
ENV{DEVTYPE}=="usb_device",\
ATTR{idVendor}=="09fb",\
ATTR{idProduct}=="6001",\
MODE="0666",\
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}",\
RUN+="/bin/chmod 0666 %c" 

6. Does programming of .sof work:  No
7. Messages from jtagconfig -d
8. Messages from jtagd --foreground --debug 
9. Does the link  /lib/x86_64-linux-gnu/libudev.so -> libudev.so.1 exist
10. Anything unusual about the USB connection (cable length, hubs, etc.)
11. Try multiple USB sockets (EHCI, OHCI UHCI drivers), try with and without a hub, 
12. Output from lsusb -vvv

Bus 001 Device 007: ID 09fb:6001 Altera Blaster
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x09fb Altera
  idProduct          0x6001 Blaster
  bcdDevice            4.00
  iManufacturer           1 Altera
  iProduct                2 USB-Blaster
  iSerial                 3 00000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               80mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
Device Status:     0x0001
  Self Powered







>         <mailto:softerhardware@gmail.com>
>         >     <mailto:softerhardware@gmail.com
>         <mailto:softerhardware@gmail.com>>
>         <mailto:softerhardware@gmail.com
>         <mailto:softerhardware@gmail.com>
>         >     <mailto:softerhardware@gmail.com
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>         >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
>         >     >        
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>         >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
>         >     >         For more options, visit
>         >    https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>
>         >     <https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>>
>         >     >        
>         <https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>
>         >     <https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>>>.
>         >     >
>         >     > --
>         >     > You received this message because you are subscribed
>         to the Google
>         >     > Groups "Hermes-Lite" group.
>         >     > To unsubscribe from this group and stop receiving
>         emails from
>         >     it, send
>         >     > an email to hermes-lite+unsubscribe@googlegroups.com
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>         >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
>         <mailto:hermes-lite%252Bunsubscribe@googlegroups.com>>
>         >     > <mailto:hermes-lite+unsub...@googlegroups.com
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>         >     <mailto:hermes-lite%2Bunsu...@googlegroups.com
>         >     > For more options, visit
>         https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>
>         >     <https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>>.
>         >
>         >
>         >     --
>         >     Sid Boyce ... Hamradio License G3VBV, Licensed Private
>         Pilot
>         >     Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers
>         Tech Support
>         >     Senior Staff Specialist, Cricket Coach
>         >     Microsoft Windows Free Zone - Linux used for all
>         Computing Tasks
>         >
>         > --
>         > You received this message because you are subscribed to the
>         Google
>         > Groups "Hermes-Lite" group.
>         > To unsubscribe from this group and stop receiving emails
>         from it, send
>         > an email to hermes-lite+unsubscribe@googlegroups.com
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>
>         > <mailto:hermes-lite+unsub...@googlegroups.com
>         <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
>         > For more options, visit https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>.
>
>
>         --
>         Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
>         Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech
>         Support
>         Senior Staff Specialist, Cricket Coach
>         Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send

Graeme Jury

unread,
Mar 27, 2019, 12:22:29 AM3/27/19
to herme...@googlegroups.com
As requested

1. Blaster Microcontroller of failing USB probe: STM
2. Operating System: LinuxMint 19.1
3. Power applied to HL2 during programming, and what type of
powersupply? : Yes, 12 volt gel cell
4. Version and type of Quartus install: both 18.1 & 15.0 programmer only.
5. udev USB blaster rules installed an udev restarted or system rebooted.
# For Altera USB-Blaster permissions.
#SUBSYSTEM=="usb",\
#ENV{DEVTYPE}=="usb_device",\
#ATTR{idVendor}=="09fb",\
#ATTR{idProduct}=="6001",\
#MODE="0666",\
#NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}",\
#RUN+="/bin/chmod 0666 %c"
#
# Intel FPGA Download Cable
SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6001",
MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6002",
MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6003",
MODE="0666"

# Intel FPGA Download Cable II
SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6010",
MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6810",
MODE="0666"

6. Does programming of .sof work:  Yes both on 18.1 and 15.0
7. Messages from jtagconfig -d
~/intelFPGA/18.1/qprogrammer/bin $ ./jtagconfig -d
1) USB-Blaster(Altera) [3-2]
  020F30DD   10CL025(Y|Z)/EP3C25/EP4CE22 (IR=10)
    Node 18206E00  Serial Flash loader #0
    Design hash    EFCF2328D450FA627C5D

  Captured DR after reset = (020F30DD) [32]
  Captured IR after reset = (155) [10]
  Captured Bypass after reset = (0) [1]
  Captured Bypass chain = (0) [1]
  JTAG clock speed 6 MHz

/altera/15.0/qprogrammer/bin $ ./jtagconfig -d
1) USB-Blaster(Altera) [3-2]
  020F30DD   EP3C25/EP4CE22 (IR=10)
    Node 18206E00  Serial Flash loader #0
    Design hash    EFCF2328D450FA627C5D

  Captured DR after reset = (020F30DD) [32]
  Captured IR after reset = (155) [10]
  Captured Bypass after reset = (0) [1]
  Captured Bypass chain = (0) [1]
  JTAG clock speed 6 MHz

8. Messages from jtagd --foreground --debug
~/intelFPGA/18.1/qprogrammer/bin $ ./jtagd --foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster(Altera) [3-2]"

9. Does the link  /lib/x86_64-linux-gnu/libudev.so -> libudev.so.1 exist
= YES
10. Anything unusual about the USB connection (cable length, hubs, etc.)
= NO
11. Try multiple USB sockets (EHCI, OHCI UHCI drivers), try with and
without a hub, = Sorry, not sure what to do here.

12. Output from lsusb -vvv
Bus 003 Device 005: ID 09fb:6001 Altera Blaster
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x09fb Altera
  idProduct          0x6001 Blaster
  bcdDevice            4.00
  iManufacturer           1 Altera
  iProduct                2 USB-Blaster(Altera)
  iSerial                 3 8D73357C5748
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              150mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 USB-Blaster(Altera)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

73, Graeme ZL2APV

Steve Haynal

unread,
Mar 27, 2019, 1:18:22 AM3/27/19
to Hermes-Lite
Hi Graeme,

There are differences in the lsusb descriptor output. For example, your has a serial number and mine does not, yours is bus powered but mine is self powered. I don't understand if any of these differences matter. I'll check when my next USB blaster arrives.

73,

Steve
kf7o

Sid Boyce

unread,
Mar 27, 2019, 8:00:23 PM3/27/19
to herme...@googlegroups.com
On 27/03/2019 03:13, Steve Haynal wrote:
> Hi Sid,
>
> Okay. Your problem appears to be different from Graeme as he can
> program a .sof. You also see the extra message, even when programming
> succeeds. Was anything installed in your /etc/init.d which may
> automatically start some jtag or USB related process? Any unusual
> software on your machine that required special libusb or related installs?
>
> I'd like to be systematic about these problems, so here is a checklist
> for people, with what I think are the correct answers for you:
>
> 1. Blaster Microcontroller of failing USB probe: STM
Bus 001 Device 008: ID 09fb:6001 Altera Blaster
> 2. Operating System: Linux openSUSE Tumbleweed
Correct.
> 3. Power applied to HL2 during programming, and what type of
> powersupply? : Yes, please specify type as I am wondering about
> noise/levels between host and HL2
Powered from the station +13.8V DC power supply. I shall have to scope
the HL2 P.S.
> 4. Version and type of Quartus install: 18.1 Full
Full Quartus 18.1
> 5. udev USB blaster rules installed an udev restarted or system
> rebooted. Below is my /etc/udev/rules/d/51-usbblaster.rules

I'll check with yours to see if it makes a difference

slipstream:~ # cat /etc/udev/rules.d/51-usbblaster.rules
USB-Blaster SUBSYSTEM=="usb", ATTRS{idVendor}=="09fb",
ATTRS{idProduct}=="6001", MODE="0666"
USB-Blaster SUBSYSTEM=="usb", ATTR{idVendor}=="09fb",
ATTR{idProduct}=="6002", MODE="0666"
USB-Blaster SUBSYSTEM=="usb", ATTR{idVendor}=="09fb",
ATTR{idProduct}=="6003", MODE="0666"
USB-Blaster SUBSYSTEM=="usb", ATTR{idVendor}=="09fb",
ATTR{idProduct}=="6010", MODE="0666"
USB-Blaster SUBSYSTEM=="usb", ATTR{idVendor}=="09fb",
ATTR{idProduct}=="6810", MODE="0666"


Bus 001 Device 008: ID 09fb:6001 Altera Blaster
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0
> # USB-Blaster
> SUBSYSTEM=="usb",\
> ENV{DEVTYPE}=="usb_device",\
> ATTR{idVendor}=="09fb",\
> ATTR{idProduct}=="6001",\
> MODE="0666",\
> NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}",\
> RUN+="/bin/chmod 0666 %c"Â
>
> 6. Does programming of .sof work:  No
> 7. Messages from jtagconfig -d
> 8. Messages from jtagd --foreground --debugÂ
> 9. Does the link  /lib/x86_64-linux-gnu/libudev.so ->
> libudev.so.1 exist
> 10. Anything unusual about the USB connection (cable length, hubs, etc.)
> 11. Try multiple USB sockets (EHCI, OHCI UHCI drivers), try with and
> without a hub,Â
> 12. Output from lsusb -vvv
>
> Bus 001 Device 007: ID 09fb:6001 Altera Blaster
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0Â
>   bDeviceProtocol         0Â
>   bMaxPacketSize0         8
>   idVendor           0x09fb Altera
>   idProduct          0x6001 Blaster
>   bcdDevice            4.00
>   iManufacturer           1 Altera
>   iProduct                2 USB-Blaster
>   iSerial                 3 00000000
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           32
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          0Â
>     bmAttributes         0x80
>       (Bus Powered)
>     MaxPower               80mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass    255 Vendor Specific Subclass
>       bInterfaceProtocol    255 Vendor Specific Protocol
>       iInterface              0Â
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x81  EP 1 IN
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               1
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x02  EP 2 OUT
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               1
> Device Status:     0x0001
>   Self Powered
>
>
>
>
>
>
>
>
> On Tuesday, March 26, 2019 at 1:53:05 PM UTC-7, Sid Boyce wrote:
>
> Hi Steve,
> I do not. This was after doing a motheboard BIOS upgrade and
> rebooting
> and no SDR software running.
> I had tried 18.1 just before, powered off HL2, swtched to 15.0,
> powered
> up HL2 and ran ./jtagconfig -d
>
> As you can see, with 15.0 I got the same message and immediately
> after
> was able to start the programmer and successfully program the HL2.
> slipstream:~ # ps fax|grep jtag
>   8792 pts/0    S+     0:00  |  |          
> \_ grep --color=auto jtag
> slipstream:~ #
> 73 ... Sid.
>
> On 26/03/2019 17:13, Steve Haynal wrote:
> > Hi Sid,
> >
> > From your last e-mail then I am assuming your answer is yes to the
> > question below.
> >
> > I do not see this message. This may be a clue to what is different
> > with your setup. Do you have any other nontypical jtag or
> usb-related
> > process on your machine? This could be from something entirely
> > different than Quartus. It could be some automatic script you
> > installed with Quartus to launch a daemon.
> >
> > 73,
> >
> > Steve
> > kf7o
> >
> >
> >
> > On Tuesday, March 26, 2019 at 9:48:05 AM UTC-7, Steve Haynal wrote:
> >
> >     Hi Sid,
> >
> >     I do not see the "2) Remote server slipstream: Unable to
> >     connect"  message when doing the same on my setup. You
> say you
> >     see this even with your working probe? Are you certain you
> haven't
> >     started some Quartus server process?
> >
> >     73,
> >
> >     Steve
> >     kf7o
> >     Â
> >
> >     On Tuesday, March 26, 2019 at 9:29:44 AM UTC-7, Sid Boyce
> wrote:
> >
> >         The new one is STM32-based.
> >         openSUSE Tumbleweed
> >         --------------------------------------------
> >         slipstream:~ # l /usr/lib64/libudev.so*
> >         lrwxrwxrwx 1 root root     12 Mar 13 12:19
> >         /usr/lib64/libudev.so ->
> >         libudev.so.1
> >         lrwxrwxrwx 1 root root     17 Mar 13 12:19
> >         /usr/lib64/libudev.so.1 ->
> >         libudev.so.1.6.13
> >         -rwxr-xr-x 1 root root 182536 Mar 13 12:20
> >         /usr/lib64/libudev.so.1.6.13
> >
> >         The message comes from "jtagconfig -d" and that
> includes the
> >         programmer
> >         I used to upload
> >        
> Hermes-Lite2/gateware/bitfiles/testing/20190223/hl2b5up/hl2b5up.jic
> >
> >         The chips in that Hobby Components one are
> PIC18FK450 and two
> >         LVC125A's.
> >
> >         The chip  in another one is marked SiLabs F321
> with the other
> >         chip a
> >         74HC244D.
> >       Â
> https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf
> <https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf>
> >        
> <https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf
> <https://www.silabs.com/documents/public/data-sheets/C8051F32x.pdf>>
> >
> >
> >         Same problems on Kubuntu 18.10 as on openSUSE
> Tumbleweed.
> >         root@sdrbox1:~# ls -l /lib/x86_64-linux-gnu/libudev.so*
> >         lrwxrwxrwx 1 root root     12 Feb 28 19:29
> >         /lib/x86_64-linux-gnu/libudev.so -> libudev.so.1
> >         lrwxrwxrwx 1 root root     17 Feb 28 19:29
> >         /lib/x86_64-linux-gnu/libudev.so.1 -> libudev.so.1.6.11
> >         -rw-r--r-- 1 root root 125128 Feb 28 19:29
> >         /lib/x86_64-linux-gnu/libudev.so.1.6.11
> >         73 ... Sid.
> >
> >         On 26/03/2019 15:03, Steve Haynal wrote:
> >         > Hi Sid,
> >         >
> >         > What do you mean by "looks just like the one you
> have?" Is it
> >         > PIC-based or STM32-based inside?
> >         >
> >         > For 18.1, have you tried the following?
> >         >
> >       Â
> https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux
> <https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux>
>
> >        
> <https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux
> <https://hackaday.io/project/123606-clone-buino-dual/log/145420-beware-of-quartus-jtag-programmer-on-linux>>
>
> >
> >         >
> >         > In you messages, 3/4 times the JTAG chain is seen,
> but then
> >         you have a
> >         > message
> >         >
> >         > 2) Remote server slipstream: Unable to
> connectÂ
> >         >
> >         > Where is this coming from? I don't see it on my Linux
> >         machine. This is
> >         > the remote server for programming. Do you have
> that running?
> >         How did
> >         > you start it?
> >         >
> >         >
> >         > There are too many variables in play, and I think
> for you
> >         and others
> >         > who are having problems, we may need to back up
> and start
> >         with an
> >         > entirely fresh Linux install. Perhaps a live image
> we can
> >         all agree on.
> >         >
> >         > 73,
> >         >
> >         > Steve
> >         > kf7o
> >         >
> >         >
> >         >
> >         >
> >         > On Tuesday, March 26, 2019 at 5:27:01 AM UTC-7,
> Sid Boyce
> >         wrote:
> >         >
> >         >     Hi Steve,
> >         >     Results from 4 programmers:-
> >         >
> >         >     Today I received a USB Blaster Rev.C
> that looks just
> >         like the one
> >         >     you have.
> >         >     Results with 18.1 and 15.0.
> >         >   ÂÂ
> >        
> slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin #
> >         >     ./jtagconfig -d
> >         >     1) USB-Blaster(Altera) [1-3]
> >         >        Unable to read device
> chain - JTAG chain broken
> >         >
> >         >        Captured DR after
> reset = ()
> >         >        Captured IR after
> reset = ()
> >         >        Captured Bypass after
> reset = ()
> >         >        Captured Bypass chain
> = ()
> >         >        JTAG clock speed 6 MHz
> >         >
> >         >     2) Remote server slipstream: Unable to
> connect
> >         >
> >         >    
> slipstream:/home/lancelot/altera/15.0/quartus/bin #
> >         ./jtagconfig -d
> >         >     1) USB-Blaster(Altera) [1-3]
> >         >      ÂÂÂ
> 020F30DD   EP3C25/EP4CE22 (IR=10)
> >         >
> >         >        Captured DR after
> reset = (020F30DD) [32]
> >         >        Captured IR after
> reset = (155) [10]
> >         >        Captured Bypass after
> reset = (0) [1]
> >         >        Captured Bypass chain
> = (0) [1]
> >         >        JTAG clock speed 6 MHz
> >         >
> >         >     2) Remote server slipstream: Unable to
> connect
> >         >
> >         >     I tried 2 others that also do not work
> with 18.1 - AOK
> >         with 15.0.
> >         >     One is
> >         >     a large 105mmx53mm Altera USB Blaster
> Rev.C.
> >         >    
> slipstream:/home/lancelot/altera/15.0/quartus/bin #
> >         ./jtagconfig -d
> >         >     1) USB-Blaster [1-3]
> >         >      ÂÂÂ
> 020F30DD   EP3C25/EP4CE22 (IR=10)
> >         >
> >         >        Captured DR after
> reset = (020F30DD) [32]
> >         >        Captured IR after
> reset = (155) [10]
> >         >        Captured Bypass after
> reset = (0) [1]
> >         >        Captured Bypass chain
> = (0) [1]
> >         >        JTAG clock speed 6 MHz
> >         >
> >         >     2) Remote server slipstream: Unable to
> connect
> >         >
> >         >    
> slipstream:/home/lancelot/altera/15.0/quartus/bin #
> >         ./jtagconfig -d
> >         >     1) USB-Blaster [1-3]
> >         >      ÂÂÂ
> 020F30DD   EP3C25/EP4CE22 (IR=10)
> >         >
> >         >        Captured DR after
> reset = (020F30DD) [32]
> >         >        Captured IR after
> reset = (155) [10]
> >         >        Captured Bypass after
> reset = (0) [1]
> >         >        Captured Bypass chain
> = (0) [1]
> >         >        JTAG clock speed 6 MHz
> >         >
> >         >     2) Remote server slipstream: Unable to
> connect
> >         >
> >         >
> >         >     73 ... Sid.
> >         >
> >         >
> >         >     On 25/03/2019 04:40, Steve Haynal wrote:
> >         >     > Hi Graeme,
> >         >     >
> >         >     > Thanks for you offer of a STB-based
> programmer. My
> >         next order
> >         >     should
> >         >     > arrive soon. If it is not STM-based, I
> will take you
> >         up on your
> >         >     offer.
> >         >     >
> >         >     > 73,
> >         >     >
> >         >     > Steve
> >         >     > kf7o
> >         >     >
> >         >     >
> >         >     > On Friday, March 22, 2019 at 8:57:33
> PM UTC-7,
> >         Graeme Jury wrote:
> >         >     >
> >         >     >     Hi Wolfram, Steve
> and Group,
> >         >     >
> >         >     >     As Steve pointed
> out I am Linux only here
> >         and I think my
> >         >     STM based
> >         >     >    programmer will
> work with Windows but for
> >         Linux it is
> >         >     exactly as
> >         >     >    Steve explained.
> The re-flashing is
> >         interesting and I will
> >         >     follow
> >         >     >    that up. Steve if
> you want one of the
> >         blasters I have that
> >         >     don't
> >         >     >    work for me I would
> be happy to make you a
> >         present of it.
> >         >     >
> >         >     >    Thanks for
> persevering with this.
> >         >     >
> >         >     >    Graeme ZL2APV
> >         >     >
> >         >     >     On Sat., 23 Mar.
> 2019, 4:48 pm Steve Haynal,
> >         >     >   ÂÂÂ
> <softerh...@gmail.com <mailto:softerh...@gmail.com>
> >         <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>
> >         >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >         <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>>
> >         <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >         <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>
> >         >     <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>
> >         <mailto:softerh...@gmail.com
> <mailto:softerh...@gmail.com>>>>> wrote:
> >         >     >
> >         >     >       
> Hi Wolfram,
> >         >     >
> >         >     >       
> Have you tried your USB Blaster
> >         under Linux? Graeme
> >         >     has had
> >         >     >       
> trouble under Linux, and I don't
> >         think he has access to
> >         >     >       
> Windows. He can program a .sof
> >         file but not the .jic
> >         >     file.
> >         >     >       
> This is interesting as it
> >         indicates his setup mostly
> >         >     works,
> >         >     >       
> but has trouble when indirectly
> >         programming the
> >         >     EEPROM. I
> >         >     >       
> think the Quartus programmer
> >         switches to some other
> >         >     mode of
> >         >     >       
> operation during this indirect
> >         programming which his
> >         >     Blaster
> >         >     >       
> is not fully supporting. Amogh
> >         mentioned that some
> >         >     people are
> >         >     >       
> reflashing the STM firmware. I
> >         suspect there are
> >         >     some STM
> >         >     >       
> blasters with a version of
> >         firmware that has timing
> >         >     >       
> incompatibilities with the
> >         indirect programming. I have
> >         >     >       
> ordered a third USB Blaster and
> >         hope to receive a
> >         >     STM-based
> >         >     >       
> one this time.
> >         >     >
> >         >     >       
> Best Regards,
> >         >     >
> >         >     >       
> Steve Haynal
> >         >     >
> >         >     >
> >         >     >       
> On Friday, March 22, 2019 at
> >         8:32:37 PM UTC-7,
> >         >     Wolfram Perrey
> >         >     >       
> wrote:
> >         >     >
> >         >     >       
>     Hello Graem, without
> >         intention to explain why
> >         >     it worked
> >         >     >       
>     for me or to stress
> >         someone else with this
> >         >     >       
>    unforgiving issue, but
> >         as reference where I
> >         >     sourced my
> >         >     >       
>     blaster:
> >         >     >
> >         >     >       
>   Â
> >         >   Â
> >       Â
> https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>
>
> >        
> >        
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>
>
> >        
> >         >     >       
>   ÂÂ
> >         >   ÂÂ
> >        
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>
>
> >        
> >        
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy
> <https://pt.aliexpress.com/item/altera-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer/2038559613.html?spm=a2g0s.9042311.0.0.2742b90aOQYPcy>
>
> >        
> >         >     >
> >         >     >       
>     Some observations:
> >         >     >       
>     - Yes, its a STM type
> >         Blaster - May be there
> >         >     are some with
> >         >     >       
>    difference firmware
> >         versions
> >         >     >       
>     inside (Some work?
> >         Some not?? may be???) but
> >         >     my blaster
> >         >     >       
>     from this source
> >         definitely works (And work
> >         >     well every
> >         >     >       
>     time I used!!)
> >         >     >       
>     - Please look in the
> >         comments from this AE
> >         >     dealer, almost
> >         >     >       
>     all positive and one
> >         buyer very specific that
> >         >     it worked
> >         >     >       
>     for him also under Win10!
> >         >     >       
>     - SW: "Programmer
> >         (Quartus Prime 18.1)" and the
> >         >     >       
>    application of the
> >         original drivers from
> >         >     inside the SW
> >         >     >       
>     package - (Used on
> >         Win7 64bit and a Win10
> >         >     64bit mashine)
> >         >     >       
>     - Make sure that the
> >         system has manually
> >         >     installed only
> >         >     >       
>     Quartus driver
> >         (Nothing automatic authentic,
> >         >     cryptic and
> >         >     >       
>    authorized and with
> >         stupid windows nobo warnings)
> >         >     >       
>     (If you let Win choose
> >         to load divers
> >         >     automatically, or
> >         >     >       
>     You choose the wrong
> >         driver set from Quartus
> >         >     you get a lot
> >         >     >       
>     of troubles inclusive
> >         blue screens and so on)
> >         >     >       
>     Deal with drivers
> >         under Win can be very
> >         >     unforgiving. There
> >         >     >       
>     are are tons of
> >         descriptions in the internet
> >         >     how to deal
> >         >     >       
>     with that.
> >         >     >       
>     For shure, the ribbon
> >         cable must be connected
> >         >     right, on
> >         >     >       
>     the programmer side as
> >         on the target site. I
> >         >     simply copied
> >         >     >       
>     how to connect the
> >         ribbon on both
> >         >     >       
>     side from Steve
> >         instruction video - one by one
> >         >     exactly -
> >         >     >       
>     to avoid any
> >         diference. Yes, and I also double
> >         >     checked
> >         >     >       
>     that my ribbon showed
> >         up exactly as on the video.
> >         >     >       
>     May be there are some
> >         Chines who are not doing
> >         >     well on
> >         >     >       
>     there ribbon cable
> >         assembly, but If You are
> >         >     unsure,
> >         >     >       
>     compare to a working
> >         reference is good practice.
> >         >     >
> >         >     >       
>     But anyway, today
> >         order two more Blaster from
> >         >     this
> >         >     >       
>    referenced source, for
> >         testing that this
> >         >     source rely
> >         >     >       
>     works. The parts are
> >         cheap enough to do that and
> >         >     >       
>     when it worked _(I
> >         expect that)_ I make them a
> >         >     giveaway -
> >         >     >       
>     May be for You or
> >         someone else struggling with
> >         >     the same
> >         >     >       
>   ÂÂ problem.ÂÂÂÂ
> >           .Â
> >         >     >       
>     Â
> >         >     >
> >         >     >       
>     Am Mittwoch, 20.
> >         März 2019 05:46:57 UTC-3
> >         >     schrieb Graeme
> >         >     >       
>     Jury:
> >         >     >
> >         >     >       
>       Thanks Steve,
> >         >     >
> >         >     >       
>       Sure is
> >         turning out to be a problem. I
> >         >     have found one
> >         >     >       
>        of my
> >         othugler blasters and it gives me
> >         >     exactly the
> >         >     >       
>       same results
> >         as my current one. Roger
> >         >     zl1ami is
> >         >     >       
>       presently in
> >         Australia but when he gets
> >         >     back I will
> >         >     >       
>       ask him to
> >         send me the blaster that I
> >         >     gave him as it
> >         >     >       
>       used to work
> >         so I can try it out on
> >         >     quartus 18.1
> >         >     >
> >         >     >       
>        I have
> >         ordered a Raspberry Pi which
> >         >     should be here in
> >         >     >       
>        a few days
> >         and will try programming with
> >         >     that. I am
> >         >     >       
>       losing hope
> >         of ever getting the Blaster
> >         >     to work and I
> >         >     >       
>        am amazed
> >         that it is so much of a problem.
> >         >     >
> >         >     >       
>       73, Graeme
> >         ZL2APV
> >         >     >
> >         >     >        --
> >         >     >       
> You received this message
> >         because you are subscribed
> >         >     to a
> >         >     >       
> topic in the Google Groups
> >         "Hermes-Lite" group.
> >         >     >       
> To unsubscribe from this topic,
> >         visit
> >         >     >      Â
> >         >   Â
> >       Â
> https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>
>
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>>
>
> >
> >         >   ÂÂ
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>
>
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>>>
>
> >
> >         >
> >         >     >      ÂÂ
> >         >   ÂÂ
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>
>
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>>
>
> >
> >         >   ÂÂ
> >        
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe
> <https://groups.google.com/d/topic/hermes-lite/g9vzzf84PGQ/unsubscribe>
>
> >        
> >         >
> >         >     >       
> To unsubscribe from this group
> >         and all its topics,
> >         >     send an
> >         >     >       
> email to
> >        hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >         >    
> <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>
> >         <mailto:hermes-lite%252Buns...@googlegroups.com
> <mailto:hermes-lite%25252Bun...@googlegroups.com>>>
> >         >     >      ÂÂÂ
> >         <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >         >    
> <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>
> >         <mailto:hermes-lite%252Buns...@googlegroups.com
> <mailto:hermes-lite%25252Bun...@googlegroups.com>>>>.
> >         >     >       
> For more options, visit
> >         >    https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>
> >         >     <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>>
> >         >     >      ÂÂÂ
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>
> >         >     <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>>>.
> >         >     >
> >         >     > --
> >         >     > You received this message because you
> are subscribed
> >         to the Google
> >         >     > Groups "Hermes-Lite" group.
> >         >     > To unsubscribe from this group and
> stop receiving
> >         emails from
> >         >     it, send
> >         >     > an email to
> hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >         >    
> <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>
> >         <mailto:hermes-lite%252Buns...@googlegroups.com
> <mailto:hermes-lite%25252Bun...@googlegroups.com>>>
> >         >     >
> <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >         >    
> <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>
> >         <mailto:hermes-lite%252Buns...@googlegroups.com
> <mailto:hermes-lite%25252Bun...@googlegroups.com>>>>.
> >         >     > For more options, visit
> >        https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>
> >         >     <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>>.
> >         >
> >         >
> >         >     --
> >         >     Sid Boyce ... Hamradio License G3VBV,
> Licensed Private
> >         Pilot
> >         >     Emeritus IBM/Amdahl Mainframes and
> Sun/Fujitsu Servers
> >         Tech Support
> >         >     Senior Staff Specialist, Cricket Coach
> >         >     Microsoft Windows Free Zone - Linux used
> for all
> >         Computing Tasks
> >         >
> >         > --
> >         > You received this message because you are
> subscribed to the
> >         Google
> >         > Groups "Hermes-Lite" group.
> >         > To unsubscribe from this group and stop receiving
> emails
> >         from it, send
> >         > an email to
> hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>
> >         > <mailto:hermes-lite...@googlegroups.com
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>
> >         <mailto:hermes-lite%2Bunsu...@googlegroups.com
> <mailto:hermes-lite%252Buns...@googlegroups.com>>>.
> >         > For more options, visit
> https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>
> >         <https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>>.
> >
> >
> >         --
> >         Sid Boyce ... Hamradio License G3VBV, Licensed
> Private Pilot
> >         Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu
> Servers Tech
> >         Support
> >         Senior Staff Specialist, Cricket Coach
> >         Microsoft Windows Free Zone - Linux used for all
> Computing Tasks
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Hermes-Lite" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send
> <mailto:hermes-lite%2Bunsu...@googlegroups.com>>.
> > For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
>
> --
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

73 ... Sid.

Graeme Jury

unread,
Mar 28, 2019, 8:38:22 PM3/28/19
to Hermes-Lite
My new USB Blaster arrived this morning SUCCESS!! I bought it from this supplier and was drawn to them by feedback from a USA purchaser who said "Works well with Quartus II 18.1 on Linux." It sure proved to be the case and at NZ$3.58 I suggest that people having problems simply dump their troublesome blasters and get one of these.

My thanks to all who have helped with this problem. Programmer output and lsusb details below

73, Graeme ZL2APV

This is the output from my working USB Blaster

Info (209060): Started Programmer operation at Fri Mar 29 13:14:27 2019
Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F30DD
Info (209007): Configuration succeeded -- 1 device(s) configured
Info (209018): Device 1 silicon ID is 0x14
Info (209044): Erasing ASP configuration device(s)
Info (209023): Programming device(s)
Info (209011): Successfully performed operation(s)
Info (209061): Ended Programmer operation at Fri Mar 29 13:14:39 2019


lsusb -vvv
Bus 003 Device 003: ID 09fb:6001 Altera Blaster

Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8

  idVendor           0x09fb Altera
  idProduct          0x6001 Blaster
  bcdDevice            4.00
  iManufacturer           1 Altera
  iProduct                2 USB-Blaster
  iSerial                 3 00000000

  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               80mA

    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1

      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
Device Status:     0x0001
  Self Powered

Graeme Jury

unread,
Mar 28, 2019, 9:02:11 PM3/28/19
to Hermes-Lite
I should have mentioned that the Blaster was based on the PIC18F14K50

Graeme

Sid Boyce

unread,
Mar 29, 2019, 11:58:15 AM3/29/19
to herme...@googlegroups.com
The Hobby Components programmer is based on the PIC18F14K50.

Looks like my problem is to do with LIBRARY_PATH as quartus ships it's
own libraries - libudev.so etc.  so does not use system libraries.
I get the same errors from both x86_64 openSUSE Tumbleweed and Kubuntu
18.10.

slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/bin # ./jtagd
--foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
No USB device change detection because libudev.so.0 not found
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster [1-11]"

slipstream:/home/lancelot/altera/15.0/quartus/bin # ./jtagd --foreground
--debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
No USB device change detection because libudev.so.0 not found
Can't bind to TCP port 1309 - exiting

Moving this over from the openSUSE Tumbleweed box to the Kubuntu 18.10 box.
--------------------------------------------------------------------------------------------------------------------------------------------------
root@sdrbox1:/home/lancelot/intelFPGA_lite/18.1/quartus/bin# ./jtagconfig -d
1) USB-Blaster [2-1]
  Unable to read device chain - JTAG chain broken

  Captured DR after reset = ()
  Captured IR after reset = ()
  Captured Bypass after reset = ()
  Captured Bypass chain = ()
  JTAG clock speed 6 MHz

root@sdrbox1:/home/lancelot/intelFPGA_lite/18.1/quartus/bin# ./jtagd
--foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
No USB device change detection because libudev.so.0 not found
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster [2-1]"
73 ... Sid.

On 29/03/2019 00:38, Graeme Jury wrote:
> My new USB Blaster arrived this morning SUCCESS!! I bought it from
> this
> supplier<https://www.aliexpress.com/item/USB-Blaster-ALTERA-CPLD-FPGA-Programmer-for-arduino/32831280653.html?spm=a2g0s.9042311.0.0.71884c4dldZyVe>
> and was drawn to them by feedback from a USA purchaser who said "Works
> well with Quartus II 18.1 on Linux." It sure proved to be the case and
> at NZ$3.58 I suggest that people having problems simply dump their
> troublesome blasters and get one of these.
>
> My thanks to all who have helped with this problem. Programmer output
> and lsusb details below
>
> 73, Graeme ZL2APV
>
> This is the output from my working USB Blaster
>
> Info (209060): Started Programmer operation at Fri Mar 29 13:14:27 2019
> Info (209016): Configuring device index 1
> Info (209017): Device 1 contains JTAG ID code 0x020F30DD
> Info (209007): Configuration succeeded -- 1 device(s) configured
> Info (209018): Device 1 silicon ID is 0x14
> Info (209044): Erasing ASP configuration device(s)
> Info (209023): Programming device(s)
> Info (209011): Successfully performed operation(s)
> Info (209061): Ended Programmer operation at Fri Mar 29 13:14:39 2019
>
>
> lsusb -vvv
> Bus 003 Device 003: ID 09fb:6001 Altera Blaster
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0         8
>   idVendor           0x09fb Altera
>   idProduct          0x6001 Blaster
>   bcdDevice            4.00
>   iManufacturer           1 Altera
>   iProduct                2 USB-Blaster
>   iSerial                 3 00000000
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           32
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          0
>     bmAttributes         0x80
>       (Bus Powered)
>     MaxPower               80mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass    255 Vendor Specific Subclass
>       bInterfaceProtocol    255 Vendor Specific Protocol
>       iInterface              0
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x81  EP 1 IN
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               1
>       Endpoint Descriptor:
>         bLength                 7
>         bDescriptorType         5
>         bEndpointAddress     0x02  EP 2 OUT
>         bmAttributes            2
>           Transfer Type            Bulk
>           Synch Type               None
>           Usage Type               Data
>         wMaxPacketSize     0x0040  1x 64 bytes
>         bInterval               1
> Device Status:     0x0001
>   Self Powered
> 6. Does programming of .sof work:  Yes both on 18.1 and 15.0
> 7. Messages from jtagconfig -d
> ~/intelFPGA/18.1/qprogrammer/bin $ ./jtagconfig -d
> 1) USB-Blaster(Altera) [3-2]
>    020F30DD   10CL025(Y|Z)/EP3C25/EP4CE22 (IR=10)
>      Node 18206E00  Serial Flash loader #0
>      Design hash    EFCF2328D450FA627C5D
>
>    Captured DR after reset = (020F30DD) [32]
>    Captured IR after reset = (155) [10]
>    Captured Bypass after reset = (0) [1]
>    Captured Bypass chain = (0) [1]
>    JTAG clock speed 6 MHz
>
> /altera/15.0/qprogrammer/bin $ ./jtagconfig -d
> 1) USB-Blaster(Altera) [3-2]
>    020F30DD   EP3C25/EP4CE22 (IR=10)
>      Node 18206E00  Serial Flash loader #0
>      Design hash    EFCF2328D450FA627C5D
>
>    Captured DR after reset = (020F30DD) [32]
>    Captured IR after reset = (155) [10]
>    Captured Bypass after reset = (0) [1]
>    Captured Bypass chain = (0) [1]
>    JTAG clock speed 6 MHz
>
> 8. Messages from jtagd --foreground --debug
> ~/intelFPGA/18.1/qprogrammer/bin $ ./jtagd --foreground --debug
> JTAG daemon started
> Using config file /etc/jtagd/jtagd.conf
> Remote JTAG permitted when password set
> USB-Blaster "USB-Blaster(Altera)" firmware version 4.00
> USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
> USB-Blaster added "USB-Blaster(Altera) [3-2]"
>
> 9. Does the link  /lib/x86_64-linux-gnu/libudev.so ->
> libudev.so.1 exist
> = YES
> 10. Anything unusual about the USB connection (cable length,
> hubs, etc.)
> = NO
> 11. Try multiple USB sockets (EHCI, OHCI UHCI drivers), try
> with and
> without a hub, = Sorry, not sure what to do here.
>
> 12. Output from lsusb -vvv
> Bus 003 Device 005: ID 09fb:6001 Altera Blaster
> Device Descriptor:
>    bLength                18
>    bDescriptorType         1
>    bcdUSB               1.10
>    bDeviceClass            0 (Defined at
> Interface level)
>    bDeviceSubClass         0
>    bDeviceProtocol         0
>    bMaxPacketSize0        64
>    idVendor           0x09fb Altera
>    idProduct          0x6001 Blaster
>    bcdDevice            4.00
>    iManufacturer           1 Altera
>    iProduct                2 USB-Blaster(Altera)
>    iSerial                 3 8D73357C5748
>    bNumConfigurations      1
>    Configuration Descriptor:
>      bLength                 9
>      bDescriptorType         2
>      wTotalLength           32
>      bNumInterfaces          1
>      bConfigurationValue     1
>      iConfiguration          0
>      bmAttributes         0x80
>        (Bus Powered)
>      MaxPower              150mA
>      Interface Descriptor:
>        bLength                 9
>        bDescriptorType         4
>        bInterfaceNumber        0
>        bAlternateSetting       0
>        bNumEndpoints           2
>        bInterfaceClass       255 Vendor Specific
> Class
>        bInterfaceSubClass    255 Vendor Specific
> Subclass
>        bInterfaceProtocol    255 Vendor Specific
> Protocol
>        iInterface              2
> USB-Blaster(Altera)
>        Endpoint Descriptor:
>          bLength                7
>          bDescriptorType         5
>          bEndpointAddress     0x81  EP 1 IN
>          bmAttributes            2
>            Transfer Type           Bulk
>            Synch Type               None
>            Usage Type               Data
>          wMaxPacketSize     0x0040  1x 64 bytes
>          bInterval               0
>        Endpoint Descriptor:
>          bLength                7
>          bDescriptorType         5
>          bEndpointAddress     0x02  EP 2 OUT
>          bmAttributes            2
>            Transfer Type           Bulk
>            Synch Type               None
>            Usage Type               Data
>          wMaxPacketSize     0x0040  1x 64 bytes
>          bInterval               0
> Device Status:     0x0000
>    (Bus Powered)
>
> 73, Graeme ZL2APV
>
> On 27/03/19 4:13 PM, Steve Haynal wrote:
> > Try multiple USB sockets (EHCI, OHCI UHCI drivers), try with
> and
> > without a hub,
>
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.

Graeme Jury

unread,
Mar 29, 2019, 4:02:24 PM3/29/19
to herme...@googlegroups.com
Hello Sid,

export
LD_LIBRARY_PATH=/home/lancelot/intelFPGA/18.1/qprogrammer/linux64:$LD_LIBRARY_PATH

should do it (or wherever your libudev.so.0 is located). I have not
tried it but a symlink to your lib might work too.

73, Graeme zl2apv

Sid Boyce

unread,
Mar 29, 2019, 7:06:44 PM3/29/19
to herme...@googlegroups.com
slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/linux64 # export
LD_LIBRARY_PATH=/home/lancelot/intelFPGA/18.1/quartus/linux64:$LD_LIBRARY_PATH
slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/linux64 #
./jtagconfig -d
1) Remote server slipstream: Unable to connect

slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/linux64 # ./jtagd
--foreground --debug
JTAG daemon started
Using config file /etc/jtagd/jtagd.conf
Remote JTAG permitted when password set
No USB device change detection because libudev.so.0 not found
USB-Blaster "USB-Blaster" firmware version 4.00
USB-Blaster endpoints out=02(64), in=81(64); urb size=1024
USB-Blaster added "USB-Blaster [1-11]"
Segmentation fault (core dumped)
slipstream:/home/lancelot/intelFPGA_lite/18.1/quartus/linux64 # l
/etc/jtagd/jtagd.conf
ls: cannot access '/etc/jtagd/jtagd.conf': No such file or direct
libudev.so is the system library.
I am now downloading just the Programmer.
73 ... Sid.

On 29/03/2019 20:02, Graeme Jury wrote:
> export
> LD_LIBRARY_PATH=/home/lancelot/intelFPGA/18.1/qprogrammer/linux64:$LD_LIBRARY_PATH

Graeme Jury

unread,
Mar 29, 2019, 7:55:37 PM3/29/19
to herme...@googlegroups.com
OK Sid,

Starting to clutch at straws but from your home directory try
sudo chown -R lancelot:lancelot *
also try echo $LD_LIBRARY_PATH to see if it really did get the path.

Once I got a good programmer, all the stuff I did to get the other
programmers to go were not necessary and I simply from a cold boot
plugged the blaster into my Hermes-Lite, plugged the blaster into my usb
port, ran up the programmer, the blaster was detected and selected
automatically, loaded the .jic file, hit the start button and after
several seconds, job done.

I wish you luck, Graeme

Steve Haynal

unread,
Mar 30, 2019, 1:38:53 PM3/30/19
to Hermes-Lite
Hi Graeme,

That is great to hear that you have a working USB blaster now. Your lsusb -vvv for this blaster matches mine now, which may be an indicator of what will work. The other STM-based blaster may require firmware upgrade as Amogh found, but I am not sure how to do that.

Sid's lsusb -vvv also matches mine, but my understanding is it only works for Quartus 15.0. This is expected as Quartus 18.1 does not support the Suse he is using:


Unless people enjoy trying to figure out all the missing library dependencies, I don't think it is worth the effort to try and make it work on the latest Suse. Just switch to a supported OS. Linux Mint 19.1 is based on Ubuntu 18.04 and hence is supported.

73,

Steve
kf7o

Sid Boyce

unread,
Mar 30, 2019, 4:16:20 PM3/30/19
to herme...@googlegroups.com
Hi Graeme,
Found the problem using strace, it's looking in PATH does not exist ...
As a matter of fact it's looking in the wrong places for other libraries
also.
The correct PATH to libudev.so is /usr/lib64. I'll pass this on to Intel
to fix.

stat("/lib64/x86_64/x86_64", 0x7ffd721bec30) = -1 ENOENT (No such file
or directory)
openat(AT_FDCWD, "/lib64/x86_64/libudev.so.0", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
stat("/lib64/x86_64", 0x7ffd721bec30)   = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib64/x86_64/libudev.so.0", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
stat("/lib64/x86_64", 0x7ffd721bec30)   = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib64/libudev.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT
(No such file or directory)
stat("/lib64", {st_mode=S_IFDIR|0755, st_size=3574, ...}) = 0
openat(AT_FDCWD, "/usr/lib64/tls/x86_64/x86_64/libudev.so.0",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/tls/x86_64/x86_64", 0x7ffd721bec30) = -1 ENOENT (No
such file or directory)
openat(AT_FDCWD, "/usr/lib64/tls/x86_64/libudev.so.0",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
73 ... Sid.

Sid Boyce

unread,
Mar 30, 2019, 4:40:47 PM3/30/19
to herme...@googlegroups.com
Hi Steve,
Interesting that it says SUSE, obviously they didn't verify this as
openSUSE uses the same LIBRARY_PATH's as openSUSE.
73 ... Sid.
> --
> You received this message because you are subscribed to the Google
> Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to hermes-lite...@googlegroups.com
> <mailto:hermes-lite...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.


Graeme Jury

unread,
Mar 31, 2019, 5:46:37 AM3/31/19
to Hermes-Lite
Hello Steve and Sid,

I would be very interested in where to get the firmware upgrade for the STM based blaster. I think it can be re-flashed from the Arduino environment and there would be nothing to lose by trying.

Sid, good to know that you have found the path problems. They don't exist on my Mint 19.1 setup but you are just the guy to get onto this for Suse.

73, Graeme ZL2APV

Amogh Desai

unread,
Apr 1, 2019, 12:29:37 AM4/1/19
to Hermes-Lite
Hi Graeme,

The upgrade firmware for STM based blaster was reported by me earlier.  I saw it on Aliexpress here under Feedback tab check the 5th comment.  I have attached a picture for your reference.

I got this programmer. Windows 10 received bsod. The drivers were from quartus 16.1. I did not look for other drivers and decided to eliminate this problem radically: replace the firmware. The scheme found, another project found. I got a programmer with mk stm32f103c8t6, which will further simplify the task. While this programmer was driving, i adapted an alternative project to run on the breadboard. The project was successful and everything worked well. Now i adapt the firmware to this programmer. Who understands the programming of stm32 microcontrollers, he can search on github project widso. There is a normal implementation of the usb-blaster firmware, which does not require beaches with drivers in win10. The only thing will need to choose gpio ports according to the programmer scheme and rule the troika of these ports.

Hope this helps.

Amogh
VU3DES

Steve Haynal

unread,
Apr 1, 2019, 12:37:44 AM4/1/19
to Hermes-Lite
Hi Amogh and Graeme,

Here are the links I found. It would be interesting if there is an easy way to reprogram these blasters.


73,

Steve
kf7o

Graeme Jury

unread,
Apr 1, 2019, 1:58:35 PM4/1/19
to Hermes-Lite
Hi Amogh and Steve,

Thanks for the links and I will follow this up as best I can but I am in the middle of moving house and so much of my stuff is now packed ready for the move. The current large property is getting a bit too much for us as we approach 80 so we are moving to suburbia with the resultant downsizing catastrophe, noise and antenna issues. Will be several weeks before I am properly set up but I will follow up on the STM32F103C8T6 reprogramming and see if I can get a system to easily do this - if the upgraded firmware works.

Interesting that the link to the supplier that you provided Amogh is the same supplier that I bought my working PIC18F14K50 based board from so it appears that you can't be sure what you will get and it depends on what is in stock. Marc F6ITU has ordered from there and I ordered a couple of spares as well so it will be interesting to see what we get and if they are STM32F103C8T6 based and whether the firmware in them works on Linux.

73, Graeme ZL2APV

Steve Haynal

unread,
Apr 7, 2019, 1:56:29 AM4/7/19
to Hermes-Lite
Hi Group,

My third USB Blaster arrived and it is finally STM-based. On one of my Linux machines, I see the reported problem where I can program .sof but not .jic files. On another Linux machine, I can program both .sof and .jic files provided I start quartus or quartus_pgmw with --64bit. Quartus tools do not always default to 64 bit and sometimes but be told.

On two Windows machines, I see the blue screen of death. I haven't tried to find and follow the driver install instructions from Wolfram. I did install a VirtualBox Linux machine, and if I pass through the USB to the VirtualBox, I can program both .sof and .jic from a VirtualBox.

The next gateware will have ethernet-based openhpsdr programmer support. Build8 buyers will be able to update the gateware without a USB blaster. Those with older Hermes-Lites can program the .sof on Linux or VirtualBox Linux, then program over ethernet once, and then can always update over ethernet.

73,

Steve
kf7o

Alan Hopper

unread,
Apr 7, 2019, 2:07:00 AM4/7/19
to Hermes-Lite
Steve,
great to hear you've put the ethernet update code in. I have some code to do the programming already and shall put it in Spark soon.
73 Alan M0NNB

Sebastien F4GRX

unread,
Apr 10, 2019, 3:44:21 AM4/10/19
to Hermes-Lite
Great news, and good info with the 64-bit mode stuff. Thanks!

Sebastien
> <https://github.com/Icenowy/USB-Blaster-GCC>
> https://github.com/eleqian/WiDSO/tree/master/MCU/USB-Blaster
> <https://github.com/eleqian/WiDSO/tree/master/MCU/USB-Blaster>
>
> 73,
>
> Steve
> kf7o
>
>
> On Sunday, March 31, 2019 at 9:29:37 PM UTC-7, Amogh Desai wrote:
>
> Hi Graeme,
>
> The upgrade firmware for STM based blaster was reported by me
> earlier.  I saw it on Aliexpress here
> <https://www.aliexpress.com/item/USB-Blaster-ALTERA-CPLD-FPGA-Programmer-for-arduino/32831280653.html?spm=2114.search0104.3.1.19134f40kF5VlS&ws_ab_test=searchweb0_0,searchweb201602_4_10065_10068_319_10059_10884_317_10887_10696_321_322_10084_453_10083_454_10103_10618_10307_537_536_10902,searchweb201603_6,ppcSwitch_0&algo_expid=ac7d4626-1d97-4615-8344-b766d2bca04f-0&algo_pvid=ac7d4626-1d97-4615-8344-b766d2bca04f>under
> Feedback tab check the 5th comment.  I have attached a picture for
> your reference.
>
> I got this programmer. Windows 10 received bsod. The drivers
> were from quartus 16.1. I did not look for other drivers and
> decided to eliminate this problem radically: replace the
> firmware. The scheme found, another project found. I got a
> programmer with mk stm32f103c8t6, which will further simplify
> the task. While this programmer was driving, i adapted an
> alternative project to run on the breadboard. The project was
> successful and everything worked well. Now i adapt the
> firmware to this programmer. *Who understands the programming
> of stm32 microcontrollers, he can search on github project
> widso. *There is a normal implementation of the usb-blaster

rentwist

unread,
Sep 16, 2019, 7:05:42 PM9/16/19
to Hermes-Lite
Hello All,

Solved!

I have the dreaded USB Blaster II clone with the ID 09fb:6001.  Initially, on a W10 machine it installed without a hitch and works. It appears in Device Manager under JTAG Cables > Altera Blaster II.  I got a new super slick ASUS laptop with 1TB SSD, 16GB ram, hot processor, etc. and BAM!  I get the BSOD when I select the drivers folder of Quartus (18.1) as one is supposed to.  Interestingly, in this case, the programmer installs under USB Controllers > USB Blaster (not II).  This appears to be the crux of the matter (at least for Windows machines).  BSOD multiple times until I removed it and the driver files as well.

So after trying unsigned drivers, disabling secure boot (which are a trick on W10) and trying various other things, I searched how to force a desired driver installation under W10.  Follow this (to the T!) and viola!  Installs as JTAG Cables > USB Blaster II and it works just as on the first machine! (which did not require this)

Here is the procedure:

Device manager,
right-click on the existing entry,
Update driver,
Browse my computer ...,
Let me pick ...,
Have disk,
Browse to the driver's folder, (in this case, browse to c: > intelFPGA_lite > 18.1 > quartus > drivers > usb-blaster-ii)
Select its inf file, (in this case, select usbblasterii.inf)
Open,
OK,
select the correct hardware from the list if there are multiple entries shown,
Next,
then it will install even if it older or less suitable.

Hope this helps!  It sure helped me (after some banging my head against the wall for a while)!

73,

Robert, WA2T

Steve Haynal

unread,
Sep 18, 2019, 12:08:01 PM9/18/19
to Hermes-Lite
Hi Robert,

This sounds like a piece of the puzzle. I think Wolfram also recommended something similar. I think there are still other issues too. For example, the STM-based blaster will not program .jic on Linux, even when the drivers are exactly the same.

It would be helpful and appreciated if you add your learnings to the wiki:

73,

Steve
kf7o

dick_...@hotmail.com

unread,
Sep 18, 2019, 2:02:12 PM9/18/19
to Hermes-Lite
Hi All
I had a very old [cira 2006] USB Blaster and it gave me problems with Quartus 18 - said only good up to XP in the instructions and continued to give me blue screens.  Bought a new USBBlaster from Amazon  [not a Blaster II] and it worked fine.  The instructions mentioned by Robert appear in the Intel documentation.  Links below for Blaster and Blaster II.

These instructions cover the method of installation for a clean install or a new device.  The Blaster II also has an install option as an option in Quatrus 18 and it does not work with the original Blaster [not II]

If there is a driver already installed it is best to bring this up in Device manager and uninstalling the driver and removing from the system before trying to update software or drivers.

Dick K9IVB

Bob A. Booey

unread,
Sep 18, 2019, 2:18:29 PM9/18/19
to dick_...@hotmail.com, Hermes-Lite
The key is not following Quartus (18.1 in my case) instructions to only go as deep as the “drivers” folder.  When that is done the clone installs as a USB Blaster (and under USB Controllers) rather than a USB Blaster II (under JTAG Cables), this results in the BSOD’s.  So In the end, avoiding the problem boiled down to drilling down one level lower to the USB Blaster II folder under Drivers.

73,

Robert, WA2T 

Sent from my iPhone
--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/1289e65c-acf8-44b9-a819-38ebb67068aa%40googlegroups.com.

Josh Logan

unread,
Oct 16, 2019, 4:29:38 AM10/16/19
to Bob A. Booey, dick_...@hotmail.com, Hermes-Lite

Coming back to this thread to see is there is any new information.
I have a .jic loaded from February, before Ethernet loading was support.  I did that via Windows 10 and STM32 based programmer.  This week I tried to use the same hardware to upload a gateware file from 20191013.

Under Windows 10, 2 different machines, I get instant BSOF.
Linux....  I did not have a x86 machine handy so I am using a Ubuntu 18.04 live image, and that is able to load a .sof file, but none of the .jic files.

If I load the .sof file I am not able to use SparkSDR to upload firmware.

Is there a way to make the hardware work correctly on Linux or Windows?
Can a .sof file be be created that would allow Ethernet programming?
Should I try to wire up a Pi to do the programming?

Thanks, Josh KD7HGL


Alan Hopper

unread,
Oct 16, 2019, 5:30:51 AM10/16/19
to Hermes-Lite
Josh,
I would have thought the sof would allow programming with spark, how did it fail?
73 Alan M0NNB
Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to herme...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to herme...@googlegroups.com.

ROBERT ENTWISTLE

unread,
Oct 16, 2019, 11:29:09 AM10/16/19
to Josh Logan, Hermes-Lite

Hi Josh,


Under W10 device manager, what is the blaster showing up as?  If not under JTAG Devices > USB Blaster II (good) but under USB Devices >  USB Blaster (bad), this is your problem and you should follow the steps I posted to correct this once you remove the bad entry and the associated driver files.


Hope this helps.


73,


Robert, WA2T

rentwist

unread,
Oct 16, 2019, 11:32:16 AM10/16/19
to Hermes-Lite
Sorry, JTAG Cables (not JTAG Devices) and USB Controllers (not USB Devices) I meant to say.
Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

 

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Steve Haynal

unread,
Oct 17, 2019, 12:41:51 AM10/17/19
to Hermes-Lite
Hi Josh,

If you can program .sof, that should work for then programming over network. Did you program a .sof gateware version that supports network programming?

73,

Steve
kf7o
Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Josh Logan

unread,
Oct 17, 2019, 1:08:01 AM10/17/19
to Steve Haynal, Hermes-Lite

I tried again tonight.  I loaded the 6rx version via .sof.  I rebooted my desktop, and I get farther.  I connect with SparkSDR and I'm able to program .rbf, then when it reboots the LEDs next to the Ethernet Jack are all off.  If I disconnect and reconnect power nothing happens.  I tried both the 6rc, and the stable 20190915 files.

This is a Build7 board.

Is there a different Ethernet programmer I should try?

73, Josh KD7HGL


Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/7f56f267-0c29-4792-b363-54f2dc13a9f6%40googlegroups.com.

Steve Haynal

unread,
Oct 17, 2019, 1:27:11 AM10/17/19
to Hermes-Lite
Hi Josh,

I just tried with a HL2b5 board and I did run into one problem. The network programming would not work if the USB blaster was still connected. I think a connected USB blaster prevents the internal programming from functioning. The steps I followed are:

1. Programmed with latest 6rx gateware .sof
2. Removed USB blaster
3. Programmed latest 6rx gateware .rbf with SparkSDR 2.0.0.7. Spark has to detect the radio but don power the radio on in SparkSDR. Right click on the detected radio to program the .rbf. You should see erase and then programming. It should not take more than about 1 minute.

73,

Steve
kf7o
Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Josh Logan

unread,
Oct 17, 2019, 1:39:55 AM10/17/19
to Steve Haynal, Hermes-Lite

I just tried these steps.  I left the ribbon cable on, but disconnected the USB blaster.
No change.  I get "Programming Complete", and then LEDs turn off, and if I power cycle the board, the LEDs stay off.

Here is my steps to program the .sof file:
ubuntu@ubuntu:~/intel/19.1/qprogrammer/bin$ ./quartus_pgm -c 'USB-Blaster(Altera)' -m JTAG -initcfg -erase_all -o "p;/tmp/hl2b5up.sof"
Info: *******************************************************************
Info: Running Quartus Prime Programmer
    Info: Version 19.1.0 Build 670 09/22/2019 SJ Standard Edition
    Info: Copyright (C) 2019  Intel Corporation. All rights reserved.
    Info: Your use of Intel Corporation's design tools, logic functions
    Info: and other software and tools, and any partner logic
    Info: functions, and any output files from any of the foregoing
    Info: (including device programming or simulation files), and any
    Info: associated documentation or information are expressly subject
    Info: to the terms and conditions of the Intel Program License
    Info: Subscription Agreement, the Intel Quartus Prime License Agreement,
    Info: the Intel FPGA IP License Agreement, or other applicable license
    Info: agreement, including, without limitation, that your use is for
    Info: the sole purpose of programming logic devices manufactured by
    Info: Intel and sold by Intel or its authorized distributors.  Please
    Info: refer to the applicable agreement for further details, at
    Info: https://fpgasoftware.intel.com/eula.
    Info: Processing started: Thu Oct 17 05:02:29 2019
Info: Command: quartus_pgm -c USB-Blaster(Altera) -m JTAG --initcfg --erase_all -o p;/tmp/hl2b5up.sof
Info (213045): Using programming cable "USB-Blaster(Altera) [3-2.4]"
Info (213011): Using programming file /tmp/hl2b5up.sof with checksum 0x00E09542 for device EP4CE22E22@1
Info (209060): Started Programmer operation at Thu Oct 17 05:02:30 2019

Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F30DD
Info (209007): Configuration succeeded -- 1 device(s) configured
Info (209011): Successfully performed operation(s)
Info (209061): Ended Programmer operation at Thu Oct 17 05:02:36 2019
Info: Quartus Prime Programmer was successful. 0 errors, 0 warnings
    Info: Peak virtual memory: 469 megabytes
    Info: Processing ended: Thu Oct 17 05:02:36 2019
    Info: Elapsed time: 00:00:07
    Info: Total CPU time (on all processors): 00:00:01

73, Josh KD7HGL



Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/a65584ec-8177-45c5-bef5-32b6d2919f7a%40googlegroups.com.

Josh Logan

unread,
Oct 17, 2019, 1:43:36 AM10/17/19
to Steve Haynal, Hermes-Lite

I tried pulling the ribbon cable, no change.
I also wanted to add my configuration is USB -> Ethernet and directly cabled to the radio.

Steve Haynal

unread,
Oct 17, 2019, 1:55:09 AM10/17/19
to Hermes-Lite
Hi Josh,

After programming the .sof, can you connect and operate with SparkSDR? That should be the case, and should establish that the connection is good. The ethernet programming is not using anything beyond that connection. Maybe there are timing/jitter issues due to the USB->Ethernet? Can you try on a more standard LAN? You can also try the openhpsdr programmer. See: https://github.com/softerhardware/Hermes-Lite2/wiki/Updating-Gateware#ethernet

73,

Steve
kf7o


Robert, WA2T 
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Steve Haynal

unread,
Oct 18, 2019, 12:21:08 AM10/18/19
to Hermes-Lite
Hi Josh,

On a few rare occasions I have seen the eeprom become so badly corrupted that it can't be programmed. Maybe this has happened to you. If you can get your USB blaster working (the USB Blaster II/Blaster trick may work for you), then you can try to do a full erase and also verify what you write.

73,

Steve
kf7o

Alan Hopper

unread,
Oct 18, 2019, 1:49:28 PM10/18/19
to Hermes-Lite
Hi Josh,
not sure what is going on here, if the programming appears to work and you see erasing then a % programming it would indicate it is all working as there is a handshake at each stage.  If the network is unreliable or swapping packets maybe something can go wrong that isn't trapped but I'm not sure how.  Protocol 2 now has a final checksum sent back which might be worth us considering, I'm not sure if there is a programmer that uses it and on the HL2 I don't think the final ack gets sent before the radio resets anyway.  As a sanity check it might be worth checking your rbf file is the correct size, on the hpsdr group some people seem to manage to download the wrong thing from github (I suspect you are not, just covering all bases).  I've reprogrammed my HL2 a few 100 times in testing the programmer in Spark so believe it is fairly sound.
73 Alan M0NNB

Josh Logan

unread,
Nov 4, 2019, 12:43:36 AM11/4/19
to Alan Hopper, Hermes-Lite


I'm back to looking at this.

I tried HPSDRProgrammer, here is that output:
image.png

I have Quartus working again under Windows.  I was able to pick JTAG cable, then USB-Blaster II.  Thanks for the suggestions.
I can program a .sof or .jic file, but the .jic file does not work on boot/reboot.  Same with the .rbf files via either program.  I tried _main and _rc6.

I also moved it back to the wired Ethernet network with DHCP.  None of those changes made a difference.

I have verified SparkSDR is working when the file is loaded via .sof.
I also removed the USB Blaster from the device when trying to load firmware via Ethernet.

Any other suggestions?

73, Josh KD7HGL




--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/8903b892-0b02-4396-8d4f-154f334aa23a%40googlegroups.com.

Steve Haynal

unread,
Nov 4, 2019, 1:07:15 AM11/4/19
to Hermes-Lite
Hi Josh,

Are you programming the FPGA or attached EEPROM when using the .jic? See the video around time 4:26:

If you are programming the attached EEPROM, do the blank check and verify operations succeed?

I suspect your EEPROM may be bad. This is U1. You may need to replace it. Fortunately they are inexpensive and relatively easy to solder.

73,

Steve
kf7o


To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Josh Logan

unread,
Nov 4, 2019, 1:35:59 AM11/4/19
to Steve Haynal, Hermes-Lite

Yes, I'm following those instructions.  Is there a good way to test U1, or is this programming the best test?

image.png

Both verify and blank-check fail.
I'm also currently seeing only 1 RX work.  I have tried multiple .sof files, and restarting SparkSDR along with the radio a couple of times.

73, Josh KD7HGL


To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/c7a20b93-a408-4587-bd6d-1f43ab42364f%40googlegroups.com.

Steve Haynal

unread,
Nov 4, 2019, 1:48:14 AM11/4/19
to Hermes-Lite
Hi Josh,

You may need to run erase first, and then try blank check. I'd have to check with Quartus.

There is a known issue of finding just 1 RX with the latest gateware and Spark 2.0.0.7. Alan says this will be fixed with Spark 2.0.0.8.

73,

Steve
kf7o
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Josh Logan

unread,
Nov 4, 2019, 1:57:29 AM11/4/19
to Steve Haynal, Hermes-Lite

image.png

73, Josh KD7HGL


To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/10ae7117-5623-4f0d-811b-35536e104d52%40googlegroups.com.

Steve Haynal

unread,
Nov 4, 2019, 12:24:30 PM11/4/19
to Hermes-Lite
Hi Josh,

With the problematic USB blaster clones, we found that on Linux we could only program the volitile .sof image and not the nonvolitile .jic to EEPROM. The cable was incompatible with the programming mode that uses the FPGA as a bridge to the EEPROM. I haven't tried the "USB Blaster II" workaround on Windows, but am wondering if it just bypasses the crash and then has the same behavior we saw on Linux.

I think you have tried programming the volitile .sof, and then programming the EEPROM over ethernet and that also didn't work? If that is true, then I strongly suspect your EEPROM is bad or in a bad state. I've seen this maybe 3 times. I think these are your options:

** Replace the EEPROM U1. The part number is in the BOM. If you do this, I'd appreciate it if you send me the bad EEPROM. I'd like to try and understand this problem better.
** Send me your HL2 board. I will try to figure out what is going on and replace U1 if required. You live just a few hundred miles away so the least expensive post should still be fast.

73,

Steve
kf7o


To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

rentwist

unread,
Nov 4, 2019, 12:59:41 PM11/4/19
to Hermes-Lite
"but am wondering if it just bypasses the crash and then has the same behavior we saw on Linux."

Not sure what the above means, but (for WIndows) if the UB II driver is installed rather than the UB dirver, .jic files program just fine.
To unsubscribe from this group and stop receiving emails from it, send an email to herme...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to herme...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to herme...@googlegroups.com.

Josh Logan

unread,
Nov 6, 2019, 6:46:33 PM11/6/19
to Steve Haynal, Hermes-Lite

I tried programming via Ethernet with both SparkSDR and HPSDRProgrammer_V2_nopcap_2.0.4.10, removing the blaster form the ribbon cable, but neither one worked.
I'll contact you off-list for sending you the whole unit.  That way we can try a 2nd programmer and have you investigate the whole system more.

73, Josh KD7HGL

To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/f10daaa1-ac4f-4363-9b7a-4d1f3a3a5fef%40googlegroups.com.

Steve Haynal

unread,
Nov 7, 2019, 1:29:03 AM11/7/19
to Hermes-Lite
Hi Josh,

Sounds good. I'd like to see this case where the EEPROM can't be programmed.

73,

Steve
kf7o
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite+unsubscribe@googlegroups.com.

Steve Haynal

unread,
Nov 12, 2019, 1:48:12 AM11/12/19
to Hermes-Lite
Hi Josh,

I received your HL2. I couldn't resurrect the EEPROM and don't know why it went bad. I replaced it and all is fine. Your HL2 will be shipped back to you tomorrow.

73,

Steve
kf7o
Reply all
Reply to author
Forward
0 new messages