Actions
Forum Thread Details
  • State Verified Answer
  • Replies 2 replies
  • Subscribers 365 subscribers
  • Views 697 views
  • Users 0 members are here
Related

UltraZed-EG custom images problems

okarin 
I have an UltraZed-EG SOM on an UltraZed IO Carrier Card, don't have a voucher for Vivado-use, not sure if my board is production/es1, and whether it matters.
The prebuilt images work fine (only eth0 issue in 2017.2, no issues with 2016.2)
Downloaded uz3eg_iocc_2017_2.bsp and used it as a base for the project. I'm using Petalinux 2017.4 sdk.
When I tried to build the images, I got the following critical warning:
CRITICAL WARNING: [Board 49-71] The board_part definition was not found for em.avnet.com:ultrazed_eg_iocc_production:part0:1.0. The project's board_part property was not set, but the project's part property was set to xczu3eg-sfva625-1-i. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command. Check if board.repoPaths parameter is set and the board_part is installed from the tcl app store.
I'm handling errors and issues as I move ahead slowly. However, I'm sure that it shouldn't be this problematic to bring this board up with custom images.
So I'm wondering what am I missing?
  • 0

    Hi there,

    It sounds like you are missing the board definitions.
    http://zedboard.org/support/documentation/14201

    Take a peek there at the bottom of the page.  Install the board definitions for the version of the tools you are using and see how that works out for you!

    --Dan

  • 0

    Beside not haivng the Board Definition Files (BDF) installed, there are a couple of other things going on here.  From what you describe "The prebuilt images work fine (only eth0 issue in 2017.2, no issues with 2016.2)" it sounds like you have a SOM with ES1 silicon.  That would explain why eth0 works with PetaLinux 2016.2, but not 2017.2.  The 2016.2 Ethernet works only with ES1 silicon SOMs (red soldermask).  The remedy is to either a)buy a production SOM (black soldermask) or b)stick with using the 2016.2 Vivado and PetaLinux tools.If you stick with the 2016.2 tools and need/want to rebuild/customize the hardware platform you will need a Vivado license voucher to unlock the ES1 devices in the tools.  Painful as it may sound, purchasing a production silicon UltraZed-EG SOM will provide the path of least resistance to future development and will allow you to use the no-cost WebPack edition of Vivado.

    You also mentioned attempting to use the 2017.2 BSP with PetaLinux 2017.4.  In general I would advise against this.  The BSPs are always targeted to a specific Vivado and PetaLinux tools release, and things are known to break (and sometimes in mysterious ways) if the BSP version doesn't match the tools version.  The same goes for matching Vivado and PetaLinux versions.  Bad and strange things often happen if the Vivado and PetaLinux tools versions you are developing with don't match.

    I hope this helps.

    --Tom