01-27-2016 01:36 AM
I´m trying to update my project in Vivado 2014.4 to 2015.4.
In this project, I use both ARMs CPUs, using BSP source for SDK 2014.2.
But in XAPP1079 only are available BSP sources for Vivado 2015.2, and I can´t run the second ARM.
Are there any advance about this for Vivado 2015.4??
02-11-2016 03:52 AM
I have the same problem. I have started new project with licenced Vivado and SDK 2015.4 but we have not started the second core with default fsbl project.
thanks your helps.
03-10-2016 08:05 AM
I am interested too in using xapp1079 into Vivado 2015.4, but only the SDK part.
I used the update to Vivado 2015.2 but i see there are problems with the drivers of cdma and vdma: it doesn't recognize xil_types.h
Did you find any solution?
03-14-2016 12:18 AM
03-16-2016 01:11 PM
As balkris suggests:
I've attached a zip file that contains just the above mentioned modified files for standalone_v5_39. Rename the attached to .zip.
03-25-2016 01:07 PM
I'm also still having trouble running the application on CPU1 in 2015.4.
I've done the following:
Only the application on CPU0 is running. Do you see anything that might be wrong?
04-11-2016 06:16 AM
FSBL does not need to be modified anymore. After opening your SDK project and adding the standalone BSP repository, create FSBL. As part of the zip located on the wiki for 2015.2, there is a readme that contains the instructions. The only difference will be the new BSP that you have created.
02-07-2017 11:45 PM
I got it solved.
i used this sdk_repo.zip and unzip it.
copy the "standalone_v5_3" folder from "C:\Xilinx\SDK\2015.4\data\embeddedsw\lib\bsp" to sdk_repo folder(local Project repo".
replace the each files from sdk_repo/bsp/standalone_v5_39 to sdk_repo/standalone_v5_3
delete the bsp folder in sdk_repo and rename the "standalone_v5_3" "standalone_v5_39".
and follow all the steps in XAPP1079. to get the results.
first i tried with running the both cpu app in debug mode.
to run and check in debug mode you need to follow the below steps
1.in app_cpu0.c comment " Reset and start CPU1 code " completely.
2.when you launch the debug config in system debugger bode.
specify the both apps in application. and for for CPU1 check the stop at entry point.
and launch the debug.
3.cpu0 app with stop at entry point and cpu1 at bootfs.S file.
4.put trigger at the entry point of cpu1 and run the cpu1.
5.and also run the cpu0.
6. you must get both the prints on UART.
03-10-2017 03:25 PM
I am trying to recreate XAPP1079 in Vivado 2016.2. I tried to perform the diff and merge solution you proposed with the XAPP for Vivado 2015.2 but I am getting many errors trying to build the bsp in SDK (mostly relating to missing header files, despite using the current standalone bsp as my base... which is apparently standalone v5_5).
Is there a 2016.2 version of XAPP1079 coming out anytime or do you have any knowledge as to why I cannot convert the 2015.2 files up to 2016.2?