• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 269 views
  • Users 0 members are here
Options
Related

What is the relationship between Vela versions and Ethos‑U software versions?

fjpmbb

I would like to understand the relationship between Vela compiler versions and Arm Ethos‑U software components.

  1. What is the version relationship between Vela and Ethos‑U?

    • Is there an officially recommended or validated mapping between:
      • Vela versions
      • Ethos‑U IP versions (e.g. Ethos‑U55)
      • Ethos‑U Core Driver
      • Ethos‑U Core Software
      • Ethos‑U Core Platform
    • If such a relationship exists, is there a compatibility or version mapping table that can be shared?

  2. Specific question for the latest Vela release

    • The current latest Vela version is Vela 5.0.0.
    • For a system based on Ethos‑U55, which versions of the following components are recommended or required to be used together with Vela 5.0.0?
      • Ethos‑U Core Driver
      • Ethos‑U Core Software
      • Ethos‑U Core Platform

Any official guidance, documentation, or best‑practice recommendations would be greatly appreciated.

Parents
  • 0 Arm Employee Badge in reply to fjpmbb

    Hi,

    I've managed to track down an answer -

    The vela.ini file format has not changed between 4.2.0 and 5.0.0.
    To verify, run this command using each vela version and then diff the files:
    cat "$(vela --list-configs Arm/vela.ini | sed -n '1s/^Configurations defined in \(.*\):$/\1/p')" > vela-$(vela --version).ini
    The main difference between v4.x.x and v5.0.0 is the default compilation core chosen (regor vs legacy). I suspect that the custom config contains something that the new compilation core doesn’t like and you could test this by forcing the new (regor) compilation core in vela 4.2.0 by adding the additional option “--debug-force-regor”.
    Having verified that, you will presumably still have the issue, so then could you please file an issue on https://gitlab.arm.com/artificial-intelligence/ethos-u/ethos-u-vela/-/issues including steps for us to be able to recreate the failure.
Reply
  • 0 Arm Employee Badge in reply to fjpmbb

    Hi,

    I've managed to track down an answer -

    The vela.ini file format has not changed between 4.2.0 and 5.0.0.
    To verify, run this command using each vela version and then diff the files:
    cat "$(vela --list-configs Arm/vela.ini | sed -n '1s/^Configurations defined in \(.*\):$/\1/p')" > vela-$(vela --version).ini
    The main difference between v4.x.x and v5.0.0 is the default compilation core chosen (regor vs legacy). I suspect that the custom config contains something that the new compilation core doesn’t like and you could test this by forcing the new (regor) compilation core in vela 4.2.0 by adding the additional option “--debug-force-regor”.
    Having verified that, you will presumably still have the issue, so then could you please file an issue on https://gitlab.arm.com/artificial-intelligence/ethos-u/ethos-u-vela/-/issues including steps for us to be able to recreate the failure.
Children
No data