cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
fostercl1
Contributor
Contributor
416 Views
Registered: ‎01-31-2018

Updating driver version when multiple instances are defined causes BSP regeneration to fail

We have several products that have multiple instances of IIC, DMA, etc. 

We keep the system.mss file tracked in our VCS, so the driver versions are retained.

When we update to a newer version, this is done through SDK's Board Support Settings drop down. I can update the Axi IIC driver version here from 3.4 to 3.5:

temp1.PNG

When that is done, all four instances of the axi_iic driver get updated in the UI:

temp2.PNG

However, the regen system.mss file only updates one of the versions:

temp4.PNG

And the regnerate BSP fails due to multiple driver versions:

temp3.PNG

The system.mss file should correctly reflect that all drivers have changed. 

As a result, I have to reopen the dialog multiple times to change the driver version. After doing this several times, the BSP can correctly be regenerated.

0 Kudos
Reply
2 Replies
stephenm
Moderator
Moderator
369 Views
Registered: ‎09-12-2007

What flow are you using?

  • Change the MSS (with all the drivers rev'ed) in the BSP in the GUI
  • Then do a clean in the SDK

Or are you doing this from the command line:

  • updatemss
  • regenbsp
0 Kudos
Reply
fostercl1
Contributor
Contributor
322 Views
Registered: ‎01-31-2018


@stephenm wrote:

What flow are you using?

  • Change the MSS (with all the drivers rev'ed) in the BSP in the GUI
  • Then do a clean in the SDK

Or are you doing this from the command line:

  • updatemss
  • regenbsp

We are changing the BSP driver versions in the GUI. Screenshots are attached in my original post.  The GUI seems to update, but those changes don't properly get set in the MSS.

0 Kudos
Reply