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 ,
Just an update rebuilding on max10_bmc_v3_15_0 also fails on the same location.
Thanks
Regards
Kian
- KianHinT_altera2 years ago
Frequent Contributor
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_FPGA2 years ago
Contributor
Hey @khtan,
It cleared the screc_cat issues, but there are still a lot more critical warnings with the build. Also not to mention the Timing Constraints are not met.
The build is completed after this but when programming the board with the binaries generated from the build and then running the tcl script as given in the guide. The 2nd tcl script - max10_syscon_flash fails stating -Apr 04, 2024 7:18:35 PM com.altera.debug.core
SEVERE: master_read_32: com.altera.systemconsole.internal.plugin.jtag.oci.Nios2DebugException: Target is broken and needs to be reseterror: master_read_32: com.altera.systemconsole.internal.plugin.jtag.oci.Nios2DebugException: Target is broken and needs to be reset
while executing
"master_read_32 $mp $flash_cmd_read_data_0 1"
(procedure "read_memory_id" line 5)
invoked from within
"read_memory_id"
(procedure "detect_flash_vendor" line 4)
invoked from within
"detect_flash_vendor"
(file "max10_syscon_flash.tcl" line 814)
invoked from within
"source max10_syscon_flash.tcl"Any ideas as to resolve this would be deeply appreciated.
Thank you,
Best Regards.