UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor phherzog
Visitor
566 Views
Registered: ‎07-16-2012

Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

Hi everybody,

I'm trying to migrate a pretty simple standalone project from Vivado 2016.2 to 2018.2. I'm failing because the bsp contains much less include files:

2018.2

~/bldc_bsp/bldc_block_i_bldc_i_bldc_one_clock_domain_i_microblaze_bldc_microblaze_bldc/include$ ls
xbram.h xbram_hw.h xio.h xparameters.h

2016.2

~/bldc_bsp/bldc_block_i_bldc_i_bldc_one_clock_domain_i_microblaze_bldc_microblaze_bldc/include$ ls
bspconfig.h microblaze_sleep.h xdebug.h xil_hal.h xil_testmem.h
fsl.h profile.h xenv.h xil_io.h xil_types.h
mb_interface.h _profile_timer_hw.h xenv_standalone.h xil_macroback.h xio.h
mblaze_nt_types.h pvr.h xil_assert.h xil_misc_psreset_api.h xparameters.h
microblaze_exceptions_g.h xbasic_types.h xil_cache.h xil_printf.h xplatform_info.h
microblaze_exceptions_i.h xbram.h xil_cache_vxworks.h xil_testcache.h xstatus.h
microblaze_interrupts_i.h xbram_hw.h xil_exception.h xil_testio.h


Now some of the missing files, i.e. xbasic_types.h, I can find in ~/bldc_bsp/bldc_block_i_bldc_i_bldc_one_clock_domain_i_microblaze_bldc_microblaze_bldc/libsrc/standalone_v6_7/src
while others remain missing, i.e. mb_interface.h, which contains microblaze_enable_interrupts() (this function can not be found anywhere in the whole bsp)

Where did these files and the function go?

Thanks,

- Philip

0 Kudos
1 Solution

Accepted Solutions
Observer ttyler777
Observer
344 Views
Registered: ‎03-05-2019

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

So, googling "::sw_libmetal_v1_4::generate line 84" brought me to this post, so I'm going to go ahead and describe how I fixed this issue here, incase anyone else needs help with this.  I don't know if this fixes the original issue described by OP, but it probably fixes his second issue.

Long story short, the file path to the bsp was too long (>255 characters), which was causing errors when I tried to add libmetal to the BSP. 

I figured this out by first tracking down the tcl script that is used (C:\Xilinx\SDK\2018.2\data\embeddedsw\ThirdParty\sw_services\libmetal_v1_4\data) and then finding line 144 (84 of the "generate" function), as indicated in the error.  Then, I inserted this line:

error "${msg}"

instead of this line:

error "Failed to generate cmake files."

Which allowed me to see a more detailed output.  And in that output were multiple warnings about the path length.  Ta-da!

This was all done using XSDK 2018.2 fyi

 

5 Replies
Moderator
Moderator
540 Views
Registered: ‎09-12-2007

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

I would recommend ramping to Vivado 2018.2 and allow the tools to ramp the design. Generate Block Design, Generate Bitstream, and export to SDK.

Then in SDK use this updated HDF to create the BSP, and port your application project to this BSP

0 Kudos
Visitor phherzog
Visitor
520 Views
Registered: ‎07-16-2012

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

Hi Stephen,

that's exactly what I did, and what I tried, but since the new 2018.2-generated BSP is missing so many files I couldn't.

Where did all those header files and the missing function go?

- Philip

0 Kudos
Visitor phherzog
Visitor
489 Views
Registered: ‎07-16-2012

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

Since there is still no help from Xilinx I tried "Modify BSP" and adding libmetal, guessing this might be the missing part. But that gives me an error:

11:11:03 INFO : Processing command line option -hwspec E:/Systems/Kentledge/FPGA/Core/microblaze/bldc/software/FlexKent.hdf.
11:12:19 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_libmetal_v1_4::
11:12:19 ERROR : (XSDB Server)generate : Failed to generate cmake files.
while executing
"error "Failed to generate cmake files.""
(procedure "::sw_libmetal_v1_4::generate" line 84)
invoked from within
"::sw_libmetal_v1_4::generate libmetal"
ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()

11:12:19 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running g
11:12:19 ERROR : (XSDB Server)enerate_bsp.

11:12:19 ERROR : Error generating bsp sources: Failed in generating sources
11:12:19 ERROR : Failed to regenerate sources for BSP project bldc_bsp
org.eclipse.core.runtime.CoreException: Internal error occurred while generating bsp sources. Please check the SDK Log view for further details.
at com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler.internalGenerateBsp(RegenBspSourcesHandler.java:178)
at com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler.access$2(RegenBspSourcesHandler.java:163)
at com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler$1$1.run(RegenBspSourcesHandler.java:131)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
at com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler$1.run(RegenBspSourcesHandler.java:135)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
11:12:22 INFO : Refreshed build settings on project bldc

0 Kudos
Observer ttyler777
Observer
345 Views
Registered: ‎03-05-2019

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution

So, googling "::sw_libmetal_v1_4::generate line 84" brought me to this post, so I'm going to go ahead and describe how I fixed this issue here, incase anyone else needs help with this.  I don't know if this fixes the original issue described by OP, but it probably fixes his second issue.

Long story short, the file path to the bsp was too long (>255 characters), which was causing errors when I tried to add libmetal to the BSP. 

I figured this out by first tracking down the tcl script that is used (C:\Xilinx\SDK\2018.2\data\embeddedsw\ThirdParty\sw_services\libmetal_v1_4\data) and then finding line 144 (84 of the "generate" function), as indicated in the error.  Then, I inserted this line:

error "${msg}"

instead of this line:

error "Failed to generate cmake files."

Which allowed me to see a more detailed output.  And in that output were multiple warnings about the path length.  Ta-da!

This was all done using XSDK 2018.2 fyi

 

Visitor phherzog
Visitor
324 Views
Registered: ‎07-16-2012

Re: Migrating from Vivado 2016.2 to 2018.2, many missing includes

Jump to solution
Great job, thanks. I had solved my problem by removing the paths to the ARM Designstart stuff from Vivado. Might have been the same problem.

Why the *** does Xilinx (1) produce error messages like this and (2) doesn't help fixing the problem?
0 Kudos