Forum Discussion
N6000-PL MAX10 Build
- 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
Hi,
I tried version max10_bmc_v3_14_0 and max10_bmc_v3_15_0 today , seems I'm getting different error on v15, passes ufm_onchip_flash.hex error but fail at another place which is strange, rerunning the build again to confirm. Anyway looks like didn't have any issues reported in the system for BMC generation that I could pull from out.
For the srec_cat question, I will have to revert to the development team that does the ofs-bmc for this issue , tried different approaches to try resolve it but didnt seems to work or having the same warnings as yours.
Thanks
Regards
Kian