Actions
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 354 subscribers
  • Views 712 views
  • Users 0 members are here
Related

Having problems running apps out of DRAM on the 7EV SOM

wchase

My app runs in OCM, but not out of DDR.  Are there any known problems with the DDR settings in the current Board File for the 7EV SOM?   Are there any recent/penidng board file updates?  FYI: I'm running the SOM on a custom carrier board.  Thanks

  • 0

    Hi Chase,

    Just to confirm, are you seeing the same issues when used on the provided UltraZed EV Carrier Card?

    -Josh

  • 0 in reply to jafoste4

    I have NOT used the carrier card.  I can do that if necessary.

  • 0

    Hello Chase,

    If you could do that to rule out an unknown factor, and so your system also matches the one we are testing on, that would be great.

    Thank you,

    Josh

  • 0

    I'll give it a try.  Whle I'm doing that - could you tell me if anyone else has reported issues with the board files or DDR on these modules?  I doubt this is a hardware issue with the SOM.  I have two modules doing exactly the same thing.  I can run out of OCM - but not DDR.  So I think its a tool-flow problem.  Thanks.

  • 0

    Hi Chase,

    As of now, I am not aware of any similar issues. However I will continue to ask around.

    -Josh

  • 0

    Hi Chase,

    It sounds like you are developing a standalone application?  I ask because I have seen incorrect linker scripts cause the sorts of problems you are describing.  If you have a EV Carrier I would suggest starting with a known-good hardware platform that you can build from our HDL git repository:

    https://github.com/Avnet/hdl

    You will also need the Vivado Board Description File repo:

    https://github.com/Avnet/bdf

    The Vivado build script can be found in the Scripts folder and you run the script by doing the following:

    1.   Open Vivado
    2.   Navigate to the HDL repo Scripts folder in the TCL command window
        cd /path/to/HDL/repo/Scripts
    3.   Start the script
        source ./make_uz_petalinux.tcl

    The script will also build the hardware platforms for the UltraZed-EG SOM and carriers.  You can prevent this by commenting out these lines near the end of the build script.

    This hardware platform is also used to create the PetaLinux BSPs we have posted on this website. 

    http://zedboard.org/support/design/22581/166

    In fact, if you are developing on a Linux host, you can download and install the PetaLinux BSP for the UltraZed-EV and use the Vivado hardware platform that is included in there.  installation instructions for the BSP can be found in Xilinx UG #1144.  The command goes something like this:

    petalinux-create -t project -s ./uz7ev_evcc_2018_2.bsp

    The Vivado project will be found in the extracted uz7ev_evcc_2018_2/hardware/UZ7EV_EVCC folder.

    I hope this helps.

    --Tom

  • 0

    Thanks Tom,

    Yes - this is stand-alone.  No- OS.  I'm running the built-in "SDK Hello World" app and my custom app.  The linker script is virtually unmodified from what is generated by SDK.  The only change I'm making is to select where the app runs (OCM/DDR).  Both apps work in OCM, but not DDR.  Don't see how the linker script could be wrong. 

    FYI: I've also successfully run these same apps on the Xilinx ZCU102 Dev Board - with an unmodified SDK linker script.

    I'm currently working on the theory that the ZED board-file parameters are not actually being applied to the generated BD (or they are just wrong - your input suggest that they are ok).  I had a problem on the ZCU102 because I did not run the "board automation" step in Vivado prior to saving/generating the BD.  Executing this step fixed my issues on the ZCU102.  I'm trying to do the same on the ZED hardware.

     

    I do not have the option of modifying my Vivado Installation, so my BD build process is as follows:

    My bd-build script does the following

    •   start the Vivado GUI
    •   set_param board. repoPaths "<path>/ultrazed_7ev_som/1.1/"
    •   create_project ...
    •   set_property BOARD_PART em.avnet.com:ultrazed_ev_som:part:0:1.1 (current_project]
    •   read_bd <bd name>
    •   generate_target <bd name>.bd
    •   stop

    The rest of the process is:

    •   use the Vivado GUI to modify the bd with a few user changes.
    •   save bd and quit Vivado
    •   Run an implementation script that does the read_bd and generate_target steps, then proceeds with PAR.

     

    There is no "board automation" step in this flow - so I'm trying to add it.

    Please advise!

    Thanks,

    Warren