Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 268 subscribers
  • Views 357 views
  • Users 0 members are here
Related

How to re-create .bin and .elf file?

hs15

Hello everyone,

I've re-created the "Python Web Server on MiniZed" hardware project by sourcing the "make_minized_petalinux.tcl" in Vivado. Now, I'm trying change a few things in the hardware block design and re-create the corresponding .bin and .elf and program the board through xsct. 

Can someone please help me with this?

  • 0

    Your question indicates that you may have been able to run the Python web server on MiniZed.  For the "FPGA" (PL) side you have been able to re-create the block diagram and I assume you are able to modify it in Vivado.  Once you have been able to export the .HDF file to the sdk directory, your efforts on the Vivado side will be over and you have to move to PetaLinux.  You will have to follow the guides on the Reference Designs page in terms of creating a VM on which you can build your PetaLinux project.  Typically you would create your PetaLinux project using a BSP such as the "minized_qspi" BSP that is also on teh Reference Designs page.  That projject has an HDF from Vivado in it.  To replace the HDF with your own, you would use
    petalinux-config --get-hw-description <location-of-your-new-HDF-file>

    On the Reference Designs page there is also a document that may be of interest:

    Prebuilt Platforms Using Hardware Definition Files (HDFs)

  • 0

    Thank you for your response. Yes, I've done all of those. Is HDF the only file that I should replace compared to the previous project? How about .bit and .dtb?

  • 0 in reply to hs15

    The HDF file is like a special zip file and it includes the .bit file that Vivado generated.  When you import the HDF with the command given above, PetaLinux takes it as part of the dts/dti file inputs for the device tree.  As part of the build process, a dts file is compiled to be a dtb file.

  • 0 in reply to stefanrousseau

    Thanks for your response. So, I don't need to recreate the device tree in sdk, the new device tree containing new modified physical addresses and etc will be included by importing HDF file? 

    I have another question: When I build the new Petalinux (including new hardware architecture) and run it on the board, how can I check in Petalinux's terminal whether the defined AXI master/slave ports are included or not (whether the new hardware design is reflected in Petalinux)? How to check the corresponding physical addresses too? For example, if I add two more GPIO via AXI_GP.

     

    Thanks!

  • 0

    Yes when you import the .hdf, the device tree will be re-created an when compiles, a new dtb will be generated.  I am no expert on this, but this is what I understand: After running petalinux-build, you could look in the <your project>/components/plnx/device-tree directory.  There are the various device tree inputs (dtsi files - I miss-wrote "dti" above) and created dts files that finally result in the .dtb file.  The system-user.dtsi file in <your project>/project-spec/meta-user/recipes-bsp/device-tree/files/ is one of these inputs.  You can analyze these files to see whether your hardware is structured as you expect.  Physical addresses are shown and should correspond with what you see in the Vivado address editor.