Forum Discussion

RRomano001's avatar
RRomano001
Icon for Contributor rankContributor
7 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...
  • ShafiqY_Intel's avatar
    ShafiqY_Intel
    7 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

ShafiqY_Intel's avatar
ShafiqY_Intel
Icon for Frequent Contributor rankFrequent Contributor
7 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
7 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
    7 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

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

    Ok after this ***USELESS*** answer I feel the pain of remain on Altera (now intel) platform.

    Programmer versionless erase the flash, 18.x 19.x report error but it is fully erased as reported from 15.0 progremmer version it do all operation on .sof or .pof versionless.

    Every version erase flash.. 18,.x 19.x Presumably after 16.x . New version erase but report error.

    Version 18.x 19.x just program .sof file. .POF report error on program verify blank check.

    Version 15.0 has no issue, it can program .pof .sof from every version is generated from. (verify and blank check work fine)

    I am using a max10 not cyclone 10.

    This resemble a M$ish answer and all answer are same value.... :(

    I remember a long long time ago:

    I was both unix and Dbase administrator on a large organization.

    I was happy managing Oracle and Unix on a multiprocessor MOtorola (now frescale) SMP 4x 68030 and some networked backup same processor kind.

    One of insane commercial people decided was time to enter M$ domain...

    So dismantled mainframes , network was based on a modem bank and over 1000 terminal and data concentrator all around county where on service.

    Answer to terminal where under 1 second on huge load.

    So I told company people to hire a so called M$ admin, I don't like that platform, I assist on migration then I quit.

    NT + SQL server, ( 2GB very expensive that time vs 256MB smp snooped cache on unix mainframe) they pay'd like a large flat and a supercar.

    So starting migration of large dbase, all proceed till a point we forever got an error... M$ error...

    Called assistance the kid answered with standard reply, then screaming due it was not able to understand technical language quitted...

    After a week I told people to buy Oracle on NT, still remember I quit from this platform....

    New admin (oh how much it was an arrogant and low skilled person.... ) installed Oracle but screamed a lot this is not a M$ product... I was proud manager told him this is a company need work not use what you want that doesn't work....

    So migrated dbase, ( a lot slower than on mainframe ).. I quitted and company started his choice of bad service... minutes for query than under second.... They bought other cluster and so on... Intel was happy ... Administrative when realized mainframe was a lot less expensive not!

    After this story I was just called another time from finance administrative.. They told me M$ answered, 6 mount later our question, answer was:

    "Yes doing migration SQL server really emit that error....."

    This service was so expensive like a supercar.... (or large flat if you prefer)

    Is Altera now Intel this way of M$ized answer?

    Sorry JonSnow, I flagged your answer as the best one in memory of this old episode...

    I am sure no other solution exists than migrate away from Ex Altera now Intel and I fear M$ too...

    Sorry I cannot accept answer say what it work must be done on another family...

    I am waiting for Xilinx development tools to try migrate away.

    Best regards

    Roberto