Vitis include directory error/modified DDR code Eclypse Z7 Zmod 1410

[Xband]

Hi, 

I have what seems to be a working hardware design with the Zmod 1410 scope module (see below).  My thought then was to modify the DDR example code removing all references to "triggering" (I don't care about that at this point) and recycle the multi S2MM_cyclic_transfer_test example.  

I created a new "helloworld" application in Vitis, copied the main.c from the above application and rebuilt the project.  Then added what seemed to be relevant libraries in the main.c file.  

I did this 2 times and am having the same problem with the UserRegister path, I've built and cleaned the project, the cleaned  version looks like it should run but then cannot find a valid platform when I try to launch from the Debug hardware option.  Seems to be the same path issue for both versions, I was worried the "datatrans_" directory path was causing some problem so built the new "axidata" version.  

The scope below shows a 1MHz sine wave with 100MHz ADC sample from the Zmod and the lower sawtooth is a DSP accumulator.  These seem ok before the AXI stuff happens is why I claim the hardware design is ok.  

Any ideas on what could be the problem? 

Thanks, 

 

 

Error:

Error while launching program: 
The platform 'C:/GitHub/WN_Zmod/Vitis_notrig/design_1_wrapper_1/export/design_1_wrapper_1/design_1_wrapper_1.xpfm' used by the system project 'axidata_system' is not valid.
The platform 'C:/GitHub/WN_Zmod/Vitis_notrig/design_1_wrapper_1/export/design_1_wrapper_1/design_1_wrapper_1.xpfm' used by the system project 'axidata_system' is not valid.
 

Description Resource Path Location Type

Invalid project path: Include path not found (C:\..\GitHub\WN_Zmod\Vitis_notrig\datatrans_\Debug\_sdk\bsp\ps7_cortexa9_0\include). datatrans_ pathentry Path Entry Problem

 

Description Resource Path Location Type

Invalid project path: Include path not found (C:\..\GitHub\WN_Zmod\Vitis_notrig\design_1_wrapper_1\export\design_1_wrapper_1\sw\design_1_wrapper_1\standalone_ps7_cortexa9_0\bspinclude\include). axidata pathentry Path Entry Problem

 

 

Edited March 28 by Xband
clarify

[artvvb]

Hey, sorry for the delay.

Unfortunately, whenever I've seen invalid xpfm files, I've needed to recreate a workspace... Speculating, but it's possible that copying or moving a workspace directory from one place on your system to another could cause it.

It's great that the hardware project is working!

Thanks,

Arthur

[Xband]

New issue that a source file is for some reason looking for a version from a USB drive that a previous version of the code was loaded from, I cannot seem to make the new directory stick even though I can navigate and choose what seems to be the proper file. 

This seems to keep the Vivado ILA from triggering so I cannot see what is happening to AXI variables. 

Thanks for any help.

 

[artvvb]

There appears to be an issue with the include directories in the project - that D:/ path matches my filesystem. I think each of the application projects need to have their paths and symbols updated as below, to make sure that Vitis is trying to pull files from the correct relative paths, instead of the absolute ones. I'm not sure if this is the actual cause of the issue, and if it is, how we didn't catch it before - it would have been something you likely would have run into previously, at least if downloading the ZIP archive with the Vitis projects - but it seems to have been an oversight on my part...

Right-click on the application project and select "properties". Open "C/C++ General -> Paths and Symbols". In the Includes tab, edit the include directories that don't exist on your system to point to the corresponding paths in the workspace.

[Xband]

I don't seem to have all these options enabled?

[artvvb]

These settings are for the application project rather than the system project, as it's the part that holds the actual C sources - the system project is a wrapper that can have multiple applications in it, like multiple baremetal applications for multiple processor cores, for example. See the selected stuff below. The Assistant identifies what type of project each of them is, but the properties are only accessible through the Explorer pane.