Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 127 subscribers
  • Views 2381 views
  • Users 0 members are here
Related

How to update an existing Vitis platform's hardware specification?

guillengap

If a hardware design is changed after having created a Vitis application project, several steps must be taken in order to update the Vitis workspace with a newly exported XSA file.

This happened to me when I tried to create boot image in Vitis. So, I forgotten to check the "Quad SPI Flash" in Vivado platform. I was guided by common sense but I think it didn't work.

So, How to solve this easily? What are these steps?

  • You might have to start over again for getting Vivado platform updated, so XSA is up to date. Do not hack XAS manfully, since there are so many parameters there and you might not know all deep knowledge behind it. Trust me, you might have to pay tone of time to debug  SW from the hacked XSA file.

    One tip for your SW APIs: after you regenerate XSA, create a new BSP package for the SW APIs, then you can get a proper FSBL for your booting images, you might not need to update all your Vitis APIs for now as far as the APIs did not use QSPI as a dependency.

  • in reply to flyingbean

    Your advice is consistent! I followed the steps in this post and it didn't work for me: https://digilent.com/reference/programmable-logic/guides/vitis-update-hardware-specification

    I looked for a quick and easy solution and it doesn't exist. It's better to do things well and concentrate on what I'm doing.

    Kind regards

  • I checked the link from Digilent HOWTO and understood what you wanted to do. The short answer for this topic is YES and NO. Digitlent HOWTO shew how to update XSA platform info under Vitis GUI. If your API used some features getting significant changed because XSA updating, You will need to start over API flow under Vitis. However, some APIs, such as Hello_world, FSBL, you might just need to regenerate ELF files without modifying the source codes. I think it is a case-by-case solution. No quick answer for that.