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,

Resolved the issue with .elf files not being able to be converted into .hex.

Now the sre_cat is not able to concatenate dev_img_info.hex and max10_onchip_flash.hex to output ufm_onchip_flash.hex. It is giving this warning message -

srec_cat: mem_init/max10_onchip_flash.hex: 2: multiple 0x00000000 values
(previous = 0x27, this one = 0x00)
srec_cat: mem_init/max10_onchip_flash.hex: 2: multiple 0x00000000 values
(previous = 0x28, this one = 0x00)

Any ideas to resolve this are greatly welcomed.

Thank you,
Best Regards.