Forum Discussion

amildm's avatar
amildm
Icon for Contributor rankContributor
4 years ago
Solved

seed -> how to get same SOF for each compilation run?

Hi All, Each time when I compile the design, I'm getting the different SOF files even I don't change anything neither in my Design nor in QSF... the resulting SOF will be different... Sho...
  • ak6dn's avatar
    ak6dn
    4 years ago

    The source files drive the logic generation / mapping phases.

    So if you compile with the exact same sources, the logic produced will be exactly the same.

    The SEED value only drives the fitter.

    Different SEED values will produce different placements of the exact same logic.

    So if you don't change the source files, the logic will be the same.

    If you don't change the seed, the placement will be the same.

amildm's avatar
amildm
Icon for Contributor rankContributor
4 years ago

1) I'm not using the POF files (they are manly for the MAX devices). For Cyclone 10 devices I'm using the JIC files, which are generated from the SOF files.

So, do the JIC files contain be the same timestamps as SOF? Will be the JIC files the same while using the same SEED.

2) As for the System Console, I'd wonder to know how I can check the timestamp if it's a part of JIC.

3) Anyway, I'd like to receive a response from an Intel's employee whether I'm guaranteedthat the compiled logic be exactly the same when using the SAME SEED for the DIFFERENT COMPILATIONS. I mean exactly the same LOGIC used, SAME ROUTE and SAME TIMING REPORTS.

Thank you!

ak6dn's avatar
ak6dn
Icon for Regular Contributor rankRegular Contributor
4 years ago

The source files drive the logic generation / mapping phases.

So if you compile with the exact same sources, the logic produced will be exactly the same.

The SEED value only drives the fitter.

Different SEED values will produce different placements of the exact same logic.

So if you don't change the source files, the logic will be the same.

If you don't change the seed, the placement will be the same.

  • amildm's avatar
    amildm
    Icon for Contributor rankContributor
    4 years ago

    So what are the "pseudo_seed", which a see in the *.syn.rpt ?

    -----------------------------------------------------------------------------------

    hssi_10g_tx_pcs_pseudo_seed_a ; 288230376151711743 ; String ;
    hssi_10g_tx_pcs_pseudo_seed_b ; 288230376151711743 ; String ;

    hssi_10g_tx_pcs_pseudo_seed_a ; 1111111111111111111111111111111111111111111111111111111111 ; Unsigned Binary ;
    hssi_10g_tx_pcs_pseudo_seed_b ; 1111111111111111111111111111111111111111111111111111111111 ; Unsigned Binary ;
    -----------------------------------------------------------------------------------

    • ak6dn's avatar
      ak6dn
      Icon for Regular Contributor rankRegular Contributor
      4 years ago

      Well, that is just a string seed that is part of the name of a variable in some source code.

      Nothing to do with the quartus parameter named SEED.

  • amildm's avatar
    amildm
    Icon for Contributor rankContributor
    4 years ago

    If I don't constrain SEED, it always set to '1' - default value...

    What cases the Fitter changes the SEED value or this never happens?

    In case of the fitting problems (e.g. Timing Closure), is there a sense to randomize the SEED? What values (range of values) could it be set to?

    When Fitter changes its SEED (if ever)?