Forum Discussion

Beginner_in_FPGA's avatar
Beginner_in_FPGA
Icon for Contributor rankContributor
2 years ago
Solved

N6000-PL MAX10 Build

Hi, I am currently building the N6000 MAX10 BMC provided in this guide, when running the script as mentioned in the guide "./build.sh" the script throws errors. I am not able to clear this error and...
Acceleration
Ofs
  • KianHinT_altera's avatar
    KianHinT_altera
    2 years ago

    Hi,

    I had a discussion with one of our OFS-BMC team on the build issue and the srec_cat command and they are aware of the issue and due to release a new build script enhancement to resolve it.

    Issue cause : new Quartus version added additional padding zeroes in .hex file compared to the older versions.

    As the new build script is undergoing corporate release process, we could try this first by manually changing the ./build.sh script first to solve the padding issue on the hex file.

    Change the command from this :

    elf2hex -v bmc_bootloader.elf 0x00000000 0x0001ffff --width=32 --record=4 --little-endian-mem --no-zero-fill --create-lanes=0 bmc_bootloader.hex

    To this in build.sh:

    elf2hex -v bmc_bootloader.elf 0x00000000 0x0001ffff --width=8 --little-endian-mem --no-zero-fill --create-lanes=0 mem_init/max10_onchip_flash.hex

    I haven't confirmed on the fix yet as I'm still currently building it on BMC v14 although they mentioned the new script is targeted for BMC v15 (max10_bmc_v3_15_0). Will let you know the result later as it will take take some time to build

    Thanks

    Regards

    Kian

Beginner_in_FPGA's avatar
Beginner_in_FPGA
Icon for Contributor rankContributor
2 years ago

Hi @khtan,

I am currently building the max10_bmc_v3_15_0. I will try with the max10_bmc_v3_14_0 right now, since you already got the same error as mine.

For the sre_cat there is a simple workaround by using the flag "-multiple" but I don't think it solves the issue since it basically writes two different values to the same address. This could change the Boot loader. When building using the "-multiple" it shows this critical warning and I don't know how this would affect the boot loader if the values would be truncated -

line 10980 - Critical Warning (18093): Memory depth (1048576) in the Memory Initialization File "../../../fw/max10/max10_bootloader/design/bmc_bootloader/mem_init/ufm_onchip_flash.hex" is larger than the flash memory depth (65536). Truncated remaining initial content value to fit flash memory. If you do not want the remaining initial content value to be truncated, make sure the Memory Initialization File contains the same memory depth values for the flash memory.

The cause for these might be the below mentioned critical warning since ufm_onchip_flash.hex is a cat of max10_onchip_flash.hexThere is a critical warning with the max10_onchip_flash.hex-

line 3686 - Critical Warning (127003): Can't find Memory Initialization File or Hexadecimal (Intel-Format) File /home/admin/otc/ofs-bmc/rtl/max10/build/max10_onchip_flash.hex -- setting all initial values to 0

Any ideas as to how to resolve these issues would be deeply appreciated.

Thank you,
Best Regards.