Wizard Import_Error

[tim]

Hi,

there is an error while importing an example-project.

After selecting the *.ewp-File (ans Button “next”) this Message occur: System.ArgumentOutOfRangeException: StartIndex darf nicht kleiner als Null sein.
VGDB-Version is: 5.6  (Beta 4 build 4225)

Is this a common behavior?

Is there a Way to import a True Studio project?

Kind Regards

Tim

 

 

 

 

VisualGDB version: 5.6.4.4225
—————— System.ArgumentOutOfRangeException ——————
System.ArgumentOutOfRangeException: StartIndex darf nicht kleiner als Null sein.
Parametername: startIndex
bei System.String.Remove(Int32 startIndex)
bei IARProjectFileImporter.IARProjectImporter.ExpandRelativePath(String path)
bei IARProjectFileImporter.IARProjectImporter.<ExtractInvariantBuildSettings>b__3_1(XmlElement el)
bei System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
bei System.Linq.Buffer1..ctor(IEnumerable1 source)
bei System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
bei IARProjectFileImporter.IARProjectImporter.ExtractInvariantBuildSettings(XmlNode pNode)
bei IARProjectFileImporter.IARProjectImporter.ParseEWPFile(String pFileEwp, IProjectImportService service)
bei IARProjectFileImporter.IARProjectImporter.ImportProject(ProjectImportParameters parameters, IProjectImportService service)
bei VisualGDB.WPF.Wizards.Embedded.EmbeddedProjectTypePage.ControllerImpl.CommitPage(h1 commitMode)
bei VisualGDB.WPF.Wizards.WPFWizardWindow.ControllerImpl.TryPrepareAndCommitPagesUntil(Int32 pageIndex)
trace=[System.String.Remove:54, IARProjectFileImporter.IARProjectImporter.ExpandRelativePath:34, IARProjectFileImporter.IARProjectImporter.<ExtractInvariantBuildSettings>b__3_1:0, System.Linq.Enumerable+WhereSelectEnumerableIterator2.MoveNext:77, System.Linq.Buffer1..ctor:114, System.Linq.Enumerable.ToArray:14, IARProjectFileImporter.IARProjectImporter.ExtractInvariantBuildSettings:117, IARProjectFileImporter.IARProjectImporter.ParseEWPFile:170, IARProjectFileImporter.IARProjectImporter.ImportProject:0, VisualGDB.WPF.Wizards.Embedded.EmbeddedProjectTypePage+ControllerImpl.CommitPage:264, VisualGDB.WPF.Wizards.WPFWizardWindow+ControllerImpl.TryPrepareAndCommitPagesUntil:122]

 

[support]

Hi,

It looks like the .ewp file structure is slightly different from what VisualGDB expects, so the importing logic fails. If you could attach the .ewp file (please put it into a .zip archive), we can gladly investigate it and fix the importer.

If you do not wish to share the project file, you can also fork and update the IAR importing plugin directly.

The TrueStudio import should work out-of-the-box, as long as you select it in the wizard. If not, please let us know more details and we will look further into it.

[tim]

Hi,

thanks for your answer.
The Project comes straight out from here:

https://github.com/SiliconLabs/wfx-fullMAC-tools

It’s the first time the VGDB-Wizard stumbles….

Kind Regards

Tim

 

 

[tim]

uups, file too large

Location: https://github.com/SiliconLabs/wfx-fullMAC-tools
Path to Example-Project: wfx-fullMAC-tools\Examples\STM32\commissioning\F429ZI_bare_metal\

 

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Thanks, it looks like the .ewp file references some sources and include directories outside its directory, that resulted in some invalid paths when the project file was moved to a shorter path.

We have updated VisualGDB to skip over invalid paths rather than throwing an exception: VisualGDB-5.6.5.4312.msi.

That said, the project will likely not build until the missing files are manually located and added to it.

[tim]

Hi,

thanks for your Investigations.

I’ve cross-checked this behavior.
With the original Projektstructure (above all – references to outside sources) the Import-Wizards runs fine.

From this Point of View: Mea culpa…

to handle that issue:
An Wizard-Error-Massage “not all Paths resolved”, for example, would be fine.

Kind regards

Tim

[support]

Hi,

No problem. In the long term, we will add support for collecting non-critical warnings during the project import, and showing them at the end of the import, however for now, invalid paths will be just ignored.

Placing the project in a correct location should indeed get it imported correctly.

[Author]

Posts