Forum Discussion

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

[NIOS] New CPU Memory HEX file -> should all NIOS system be regenerated?

Hello, When the NIOS Memory HEX file is replaced with a new one -> should all NIOS subsystem be regenerated (new RTL file will be created)? Can not I leave the whole NIOS system untouched and jus...
  • RProesel's avatar
    RProesel
    3 years ago

    You do not have to regenerate the NIOS sub-system if you change the .hex file that you are using to initialize the memory.

    You only have to do 2 steps in Quartus:

    1) Run 'Update Memory Initialization File' in the Processing menu.

    2) Run 'Start Assembler' under 'Start' in the Processing menu.

    This will create a new SOF file using the new .HEX file.

EBERLAZARE_I_Intel's avatar
EBERLAZARE_I_Intel
Icon for Regular Contributor rankRegular Contributor
3 years ago

Helo,


Yes, if you have any changes in the hardware system, you must recreate, update or regenerate the BSP project to keep the library header files up-to-date.


The BSP editor will generate the .elf based of your design, which will be used by the .HEX.


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

The question was a bit different ....

I already have a new .HEX file - received it from out SW group.

But, when I replace the "old" .HEX with the "new" .HEX (shown in the GUI screenshot in my previous post), QSYS wants to re-generate the whole NIOS subsystem (RTL generation).

Why? The .HEX, which I received, is based on the same NIOS configuration. The only thing, that has been changed, is the Memory (ROM/RAM) contents, which NIOS works with... I mean no logic has been changed, only memory contents have been changed - so why the whole NIOS subsystem RTL should be re-generated?

Thank you in advance