Generating bit file for boot up using debugger about riscv_vhdl

[sergeykhbr]

Just several comments because in your question actually several questions:

• You can freely change json-configuration files it cannot affect the build process.

• examples/dhrystone/makefiles/binarm folder contains the pre-built hex-image + elf (with debug symbols) for ARM processor (not a RISC-V). These files are used by target functional_arm_gui.json or with the custom ARM-R5 system that not in the repository. You shouldn't rename it.

• FPU is disabled by default for boot/ example. See the parameter FPU_ENABLED=0 in the make_boot. Total size of the boot image 3 KB it is much less than available 'bootrom' space.

• I am using own utility 'examples/elf2rawx' to generate hex-file. So you can try to build it and copy the binary file 'elf2rawx' into the folder with your gcc compiler:

     $ cd examples/elf2rawx/makefiles
     $ make
     $ cp elf/elf2rawx $(YOUR_CUSTOM_RISCV_GCC_FOLDER)
     $ cd ../../dhrystone21/makefiles
     $ make
  

• What version of gcc you are using (or actually where I can get the same to reproduce your result)?

• Are you going to port freertos yourself?

[taniyagarg4]

i have actually followed your steps and sorry we are booting zephyr the way you have done. i was to change the folder name because it is giving an error while generating bit file. So if i should not rename then what is to be done

…

On Thu, Sep 5, 2019 at 2:05 PM Sergey ***@***.***> wrote: Just several comments because in your question actually several questions: - You can freely change json-configuration files it cannot affect the build process. - *examples/dhrystone/makefiles/binarm* folder contains the *pre-built* hex-image + elf (with debug symbols) for ARM processor (not a RISC-V). These files are used by target *functional_arm_gui.json* or with the custom ARM-R5 system that not in the repository. You shouldn't rename it. - FPU is disabled by default for *boot/* example. See the parameter *FPU_ENABLED=0* in the *make_boot*. Total size of the boot image 3 KB it is much less than available 'bootrom' space. - I am using own utility *'examples/elf2rawx'* to generate hex-file. So you can try to build it and copy the binary file 'elf2rawx' into the folder with your gcc compiler: $ cd examples/elf2rawx/makefiles $ make $ cp elf/elf2rawx $(YOUR_CUSTOM_RISCV_GCC_FOLDER) $ cd ../../dhrystone21/makefiles $ make - What version of gcc you are using (or actually where I can get the same to reproduce your result)? - Are you going to port freertos yourself? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30?email_source=notifications&email_token=ANDB7TBGGARXKOQG6DOTTPTQIDAEPA5CNFSM4ITZPIT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD56J6UQ#issuecomment-528260946>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANDB7TAHMCPONJFLIV7UZBTQIDAEPANCNFSM4ITZPITQ> .

-- *Thanks and Regards* Taniya Garg Mail: [email protected] Mob: [phone]

[sergeykhbr]

I think I've understood. There're special *.vhd configuration file for each project:

• rtl/prj/kc705/config_k7.vhd for the KC705 board
• rtl/prj/ml605/config_v6.vhd for the ML605 board
• rtl/prj/modelsim/config_msim.vhd for the simulation in QuestaSim
• etc

All these files have the following constants definition:

constant CFG_SIM_BOOTROM_HEX : string := 
            CFG_TOPDIR & "examples/boot/linuxbuild/bin/bootimage.hex";

constant CFG_SIM_FWIMAGE_HEX : string := 
            CFG_TOPDIR & "examples/zephyr/gcc711/zephyr.hex";

Make sure that these constants are the same as shown above to run zephyr. It possible to change them to run bare-metal Dhrystone benchmark or bootrom_tests for CPU verification or redefine CFG_TOPDIR parameter.

[taniyagarg4]

Ok sir I will try this but if I want to use the hex image I generated using your specified method, then what should I do because that is the one that's giving error?

…

On Fri, 6 Sep, 2019, 1:42 AM Sergey, ***@***.***> wrote: I think I've understood. There're special *.vhd configuration file for each project: - *rtl/prj/kc705/config_k7.vhd* for the KC705 board - *rtl/prj/ml605/config_v6.vhd* for the ML605 board - *rtl/prj/modelsim/config_msim.vhd* for the simulation in QuestaSim - etc All these files have the following constants definition: constant CFG_SIM_BOOTROM_HEX : string := CFG_TOPDIR & "examples/boot/linuxbuild/bin/bootimage.hex"; constant CFG_SIM_FWIMAGE_HEX : string := CFG_TOPDIR & "examples/zephyr/gcc711/zephyr.hex"; Make sure that these constants are the same as shown above to run zephyr. It possible to change them to run bare-metal Dhrystone benchmark or *bootrom_tests* for CPU verification or redefine *CFG_TOPDIR* parameter. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30?email_source=notifications&email_token=ANDB7TBTDDHVAMKE3CCHZHDQIFR23A5CNFSM4ITZPIT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6ATNFI#issuecomment-528561813>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANDB7TAMXOWNHIYIPLEFYXLQIFR23ANCNFSM4ITZPITQ> .

[sergeykhbr]

In that case please share information about gcc version and build log.