Forum Discussion

RRomano001's avatar
RRomano001
Icon for Contributor rankContributor
6 years ago
Solved

Quartus18.x,19.1 issue1: Programmer

Hi platform Linux:

target MAX10SC 04 08 16 25 50 EQFP 144 (custom board)

target MAX10SC 08 and 50 BGA484 Terasic DE10Lite, RoketBoard Arrow/terasic DECA

Quartus II lite 18.1 (programmer from 19.1 same)

Programmer: USB blaster, Terasic embedded programmer on DE10 Lite.

I don't use winxx platform, try'd on VM win 7 Pro where I use Terasic tools thru linux USB Blaster server, programmer 18/19 same issue.

Failed to setup USB blaster native driver on that platform...

Try'd on a stand alone Win7 only, same issue on device drivers, so again I cannot test native winzz USB blaster drivers. (install Quartus on win7 require a huge amount of time compared to few minutes on Linux/MAC so I am not interested test more on.)

**************************************************************************************

*** Test bench programmers 18.1 19.1:

**************************************************************************************

Programmer of latest version (18.x,19.1) fail reporting failure 0% after a while.

Unsuccessful operation: program, verify, blank check flash with .pof files.

After one of that operation Fpga remain in a limbo state, programmer never work again and require a power cycle.

Erase flash (.pof) work.

Verify leave board in an unknown state, old image never load at end of operation.

After power cycle of USB Blaster and regaining control of USB Blaster then a .sof can be loaded in ram also without power cycle of my custom board.

(NA on Terasic due to integrated programmer).

This is spread on all my board and Terasic too.

**************************************************************************************

*** TEST 2 Using programmer version 15.0 same hardware same platform:

**************************************************************************************

Blank check proceed to 100% so 18.x 19.1 erasure work for sure.

Program .pof proceed to 100% verify ok

verify .pof work

Load .sof work

Erase work

console output:

Info (209060): Started Programmer operation at Thu May 2 10:42:02 2019

Info (209016): Configuring device index 1

Info (209017): Device 1 contains JTAG ID code 0x0318A0DD

Info (209007): Configuration succeeded -- 1 device(s) configured

Info (209011): Successfully performed operation(s)

Info (209061): Ended Programmer operation at Thu May 2 10:42:04 2019

Leaving both 18.x (19.x too) 15.0 Quartus running at same time don't change behavior.

Failure on 18.x block hardware so try on 15.0 result in failure:

Console output:

Info (209060): Started Programmer operation at Thu May 2 10:58:44 2019

Error (209053): Unexpected error in JTAG server -- error code 35

Error (209012): Operation failed

Info (209061): Ended Programmer operation at Thu May 2 10:59:05 2019

power cycle USB blaster then verify on 15.0:

Info (209060): Started Programmer operation at Thu May 2 11:00:34 2019

Info (209017): Device 1 contains JTAG ID code 0x0318A0DD

Info (209021): Performing verification on device(s)

Info (209011): Successfully performed operation(s)

Info (209061): Ended Programmer operation at Thu May 2 11:01:09 2019

Edit:

After verify image reload and restart, also power cycling board reload from flash as it was.

18.x seems has broken pipe to console and no messages appear on.

  • ShafiqY_Intel's avatar
    ShafiqY_Intel
    6 years ago

    Hi,

    I think it might be your flash is not fully erase. (the reason you not able to verify)

    The Programmer Engine supposed to NOT touch other flash partition except those defined with bitstream and user data.

    Kindly follow the attachment pdf for step to fully erase.

    (Since you are using MAX 10, use .pof file instead of .jic)

    I hope this will help.

    Thanks

9 Replies

    • RRomano001's avatar
      RRomano001
      Icon for Contributor rankContributor
      6 years ago

      Hi, I browsed forum and known issue, no solution found.

      Programmer 19.1 was installed on win7pro, same issue.

      checked full quartus19.1 on Linux, no solution to none of issue, removed after a while to free up hdd space.

      just to test plugged out then in USB Blaster, dmesg:

      [170212.789879] usb 3-3.4.3: USB disconnect, device number 20

      [170215.827861] usb 3-3.4.3: new full-speed USB device number 21 using xhci_hcd

      [170215.941054] usb 3-3.4.3: New USB device found, idVendor=09fb, idProduct=6001

      [170215.941061] usb 3-3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

      [170215.941064] usb 3-3.4.3: Product: USB-Blaster(Altera)

      [170215.941068] usb 3-3.4.3: Manufacturer: Altera

      [170215.941071] usb 3-3.4.3: SerialNumber: 8D792F7A5454

      so device is enumerated and in working order, it work from 15.0, fail on more recent version. Not sure if from 15.1 or 16.x, removed all release from 18.0 downto 15.1

      lsusb:

      Bus 003 Device 016: ID 0483:3748 STMicroelectronics ST-LINK/V2

      Bus 003 Device 021: ID 09fb:6001 Altera Blaster

      both device are on active debug over MAX10 board. Same issue is present if jtag server is accessed from Win7PROEN VM (Terasic toolkit) or real machine where it was win10 (Bleah) now dual boot win7proIT , ubuntu 18.4 (fresh new clean, prepared to parallel test quartus issue).

      Edit:

      Test after .pof action verify, required restart JTAGD too, dmesg report nothing, lsusb is same, just erase work on new version but not verify blank check nor program, this issue is stable from the past, just realized now is a software issue not hardware after 4 different adapter buy.

      Original (old cyclone II kit), clone and Terasic on board suffer same way.

      15.0 is retained due more recent version forbid use pin near pll clock input and old board need to be maintained.

      Best regards

      Roberto

    • RRomano001's avatar
      RRomano001
      Icon for Contributor rankContributor
      6 years ago

      NOPE NOPE NOPE NOOOOOOOPEEEEEEE!!!!!

      PLEASE READ THOROUGH:

      Your link report this issue:

      USB BLASTER NOT WORKING.

      THIS IS NOT NOT ****NOT**** my case!

      Device drivers right are ok, Cable is working, I am using on regular basis.

      USB Blaster is perfectly working as you can read from device enumerated and IN WORKING ORDER.

      Programmer 19.1 fail EXACTLY SAME WAY of 18.1 and probably 17.x 18.0.

      ****************************************************************************************************************************************************

      ***********************************-----------------------------------------------------------------------------------******************************

      ============>>>>>>>>>>>>>_____ SOFTWARE Programmer of release 15.0 work hassle FREE. _____<<<<<<===============

      ***********************************-----------------------------------------------------------------------------------******************************

      ****************************************************************************************************************************************************

      --->>>--- QUARTUS PROGRAMMER ---<<< <<not usb Blaster cable>>.

      Issue to USB Blaster came from SOftware 18.x 19.x not from drivers.

      Regards

  • ShafiqY_Intel's avatar
    ShafiqY_Intel
    Icon for Frequent Contributor rankFrequent Contributor
    6 years ago

    Hi,

    I'm apologize for misunderstanding to previous reply.

    Is there any improvement to this issue?

    If not, could you please send the screenshot for the error?

    When you program using Quartus v18.1/19.1, did you compiled your design using Quartus v18.1/19.1 OR you just used old pof file (compiled in Quartus 15.1)?

    Have you tried program it in Quartus Standard version?

    Thanks

    • RRomano001's avatar
      RRomano001
      Icon for Contributor rankContributor
      6 years ago

      Hi, about heaven and hells.....

      .sof or .pof compiled on different version has no impact on issue. 15.0 header or 18.1 header process same way on version so:

      .pof .sof versionless:+

      Programmer version 18.1 Lite, 19.1 (exist just one version). doesn't work, remember this appeared from 17.x (now removed).

      Programmer version 15.0 Work forever.

      Programming .pof with 15.0 version

      just after .pof loaded .sof with 18.1 version

      .pof erase on 18.1 as written work for sure.

      .pof on 18.1 version verify, programming fail after a while.

      • ShafiqY_Intel's avatar
        ShafiqY_Intel
        Icon for Frequent Contributor rankFrequent Contributor
        6 years ago

        Hi,

        I think it might be your flash is not fully erase. (the reason you not able to verify)

        The Programmer Engine supposed to NOT touch other flash partition except those defined with bitstream and user data.

        Kindly follow the attachment pdf for step to fully erase.

        (Since you are using MAX 10, use .pof file instead of .jic)

        I hope this will help.

        Thanks