Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 277 subscribers
  • Views 288 views
  • Users 0 members are here
Related

Using an existing image of Pulsar and changing the PL

Former Member

We are trying to get the MicroZed 7010 board running with a simple custom PL that connects to the processor over an AXI lite bus.  We have tried many times to get an image built of the windriver pulsar following the wr-core guide, wr-core/docs/README-xilinx-zynq.TXT

We have made it partially through the outlined process many times but have yet to successfully get completely through the process.  

Is there a way that we can modify the PL, use an existing build of windriver, and configure Linux to address the PL without going through the entire wr-core linux build process?

  • 0

    Hi Matt,

    We just completed two different example designs with tutorials target to the MicroZed Industrial IoT Starter Kit that do exactly what you are asking for.  Each design uses a custom PL with I2C and SPI peripherals connected to the Zynq PS over the AXI interconnect, and starts with a known-good microSD card image and instructions so you can see it all working before diving into the steps of the tutorial.  Both of these designs will be posted to the reference design section of this site sometime tomorrow.  I will reply back with the links once I know they have been posted.

    Back to your post, though.  Are you saying that the bitbake process fails to build a Pulsar kernel and file system image?  Or that the image fails to boot?  Or the image boots, but you aren't able to access your peripheral in the PL?  Sorry for all the questions, but I am confused about exactly where your failure is.  If the latter, I suspect that would be a device tree mismatch between the hardware that is described in the default device tree (the dtb file in the OVERCBOOT partition) and your actual hardware.  The device tree describes the hardware present for Linux during boot.  If the information for your peripheral in the PL is not included in the device tree, then Linux won't be able to "communicate" with it.  The tutorials I mention deal with this in a constrained manner - what is required for the reference design to work - but for more information about the details of customizing a device tree to your particular hardware other resources will need to be consulted.

    Stay tuned for the links to the tutorials I mentioned.

    --Tom

  • 0

    Two years after the post of mnewell969 I can confirm that nothing changed: both versions 8 and 7 of wr-core cannot be compiled (version 8 because of SSL issue with python, version 7 gives som obscure diagnostic)