element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development MicroZed AMP (Baremetal/Baremetal) Configuration Issue
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 328 subscribers
  • Views 215 views
  • Users 0 members are here
Related

MicroZed AMP (Baremetal/Baremetal) Configuration Issue

Former Member
Former Member over 9 years ago

Hi everybody,

I followed Developing Zynq Software with Xilinx SDK Lab 9 Dual Processor Software Development.  When I tried to generate app_cpu1 (standalone_amp application project) for amp,  The New project Templates page not showing any available Templates, there is a message says that there is no supported application for selected processor and OS. I am running SDK 2015.4.  
Please let me know what is happening here!  thank you for your help!

  • Sign in to reply
  • Cancel
Parents
  • zedhed
    0 zedhed over 9 years ago

    Hi liang.zhu,

    That Lab 9 required us to create a custom Standalone BSP template called "standalone_amp" according to the information found in Xilinx XAPP1079:

    http://www.wiki.xilinx.com/XAPP1079+Latest+Information

    The latest SpeedWay release we have supports Vivado Design Suite 2014.4 tools and that BSP that is included is likely not supported by 2015.4 tools.

    I am guessing that it should be possible for you to create a new "standalone_amp" which is derived from the standalone BSP template sources found in the SDK install folder data/embeddedsw/lib/bsp/ sub-directory.

    I did this for 2014.4 tools by copying the latest standalone BSP template folder "standalone_v4_2" over to a new one called "standalone_amp_v4_2" and then renamed the standalone.mld, standalone.mss, and standalone.tcl files in the data folder to standalone_amp.* names.

    I edited the standalone_amp.mld file to change the OS parameter from "standalone" to "standalone_amp" and also the OPTION NAME from "standalone" to "standalone_amp" and saved those changes.

    I then edited the standalone_amp.mss file to change the PARAMETER OS_NAME from from "standalone" to "standalone_amp" and saved those changes.

    I ran a diff on all of the files under the src/ folder against a previous version of the from "standalone_amp" template and merged the code changes which relate to initializing only certain hardware resources once by CPU0 and not reinitialize them by CPU1.  You might be wondering "Where those code changes came from originally if they were copied from an older version of BSP?" and the answer for that is that they were derived from the files included with the original XAPP1079 release.

    The final step is to make sure that the local folder containing your new "standalone_amp" BSP template is specified as a local repository under SDK so that it becomes visible to you in the new project wizard.

    If running standalone AMP in your product is not a requirement and you are just doing the SpeedWay to learn more about Zynq-7000 All Programmable SoC, then it might be easier for you to try all of this with 2014.4 tools since we know that the files we include for Lab 9 will work with those tools just fine.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • zedhed
    0 zedhed over 9 years ago

    Hi liang.zhu,

    That Lab 9 required us to create a custom Standalone BSP template called "standalone_amp" according to the information found in Xilinx XAPP1079:

    http://www.wiki.xilinx.com/XAPP1079+Latest+Information

    The latest SpeedWay release we have supports Vivado Design Suite 2014.4 tools and that BSP that is included is likely not supported by 2015.4 tools.

    I am guessing that it should be possible for you to create a new "standalone_amp" which is derived from the standalone BSP template sources found in the SDK install folder data/embeddedsw/lib/bsp/ sub-directory.

    I did this for 2014.4 tools by copying the latest standalone BSP template folder "standalone_v4_2" over to a new one called "standalone_amp_v4_2" and then renamed the standalone.mld, standalone.mss, and standalone.tcl files in the data folder to standalone_amp.* names.

    I edited the standalone_amp.mld file to change the OS parameter from "standalone" to "standalone_amp" and also the OPTION NAME from "standalone" to "standalone_amp" and saved those changes.

    I then edited the standalone_amp.mss file to change the PARAMETER OS_NAME from from "standalone" to "standalone_amp" and saved those changes.

    I ran a diff on all of the files under the src/ folder against a previous version of the from "standalone_amp" template and merged the code changes which relate to initializing only certain hardware resources once by CPU0 and not reinitialize them by CPU1.  You might be wondering "Where those code changes came from originally if they were copied from an older version of BSP?" and the answer for that is that they were derived from the files included with the original XAPP1079 release.

    The final step is to make sure that the local folder containing your new "standalone_amp" BSP template is specified as a local repository under SDK so that it becomes visible to you in the new project wizard.

    If running standalone AMP in your product is not a requirement and you are just doing the SpeedWay to learn more about Zynq-7000 All Programmable SoC, then it might be easier for you to try all of this with 2014.4 tools since we know that the files we include for Lab 9 will work with those tools just fine.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube