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: 
Visitor rasjani
Visitor
4,301 Views
Registered: ‎05-22-2017

Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

I have an issue with 2016.4 yocto builds that seems to happen randomly in our jenkins build environment running on ubuntu 16.04.02 LTS.

 

Main build log has following:

 

 

ERROR: fsbl-0.2+xilinx+gitAUTOINC+a931a8d447-r0 do_compile: Function failed: do_compile (log file is located at /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/temp/log.do_compile.23940)
ERROR: Logfile of failure stored in: /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/temp/log.do_compile.23940
Log data follows:
| DEBUG: Executing shell function do_compile
| Starting SDK. This could take few seconds... Eclipse:
| An error has occurred. See the log file
| /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/.metadata/.log.
| XSCTHELPER INFO: Empty WorkSpace
| Starting SDK. This could take few seconds... Eclipse:
| An error has occurred. See the log file
| /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/.metadata/.log.
| timeout while establishing a connection with SDK
|     while executing
| "error "timeout while establishing a connection with SDK""
|     (procedure "getsdkchan" line 108)
|     invoked from within
| "getsdkchan"
|     (procedure "projects" line 35)
|     invoked from within
| "projects -clean -type $type -name $name"
|     (procedure "clean_n_build" line 2)
|     invoked from within
| "clean_n_build bsp $params(bspname)"
|     invoked from within
| "if { $params(ws) ne "" } {
|   #Local Work Space available
|   setws $params(ws)
|   if { [catch {importprojects $params(ws)} result] } {
|     puts "XSCTHELPER IN..."
|     (file "/home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/app.tcl" line 111)
| WARNING: /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/temp/run.do_compile.23940:1 exit 1 from 'eval xsct /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/app.tcl -ws /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0 -pname fsbl -rp /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/git -do_compile 1'

 

 

And most likely the relevant portion of the log file

/home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0/.metadata/.lo

looks something like this:

!ENTRY org.eclipse.cdt.core 4 2 2017-05-22 06:23:29.568
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.cdt.core".
!STACK 0
java.lang.IllegalStateException: Workspace is closed.
  at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:411)
  at org.eclipse.cdt.internal.core.model.CModel.<init>(CModel.java:34)
  at org.eclipse.cdt.internal.core.model.CModelManager.<init>(CModelManager.java:104)
  at org.eclipse.cdt.internal.core.model.CModelManager.getDefault(CModelManager.java:190)
  at org.eclipse.cdt.internal.core.model.CModelOperation.run(CModelOperation.java:602)
  at org.eclipse.cdt.internal.core.model.CModelOperation.runOperation(CModelOperation.java:635)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.setPathEntryContainer(PathEntryManager.java:688)
  at org.eclipse.cdt.core.model.CoreModel.setPathEntryContainer(CoreModel.java:882)
  at org.eclipse.cdt.internal.core.settings.model.ConfigBasedEntriesContainerInitializer.initialize(ConfigBasedEntriesContainerInitializer.java:26)
  at org.eclipse.cdt.internal.core.model.PathEntryManager$1.run(PathEntryManager.java:761)
  at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getPathEntryContainer(PathEntryManager.java:751)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getPathEntryContainer(PathEntryManager.java:711)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:549)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:526)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:510)
  at org.eclipse.cdt.internal.core.model.PathEntryStoreChangedOperation.executeOperation(PathEntryStoreChangedOperation.java:41)
  at org.eclipse.cdt.internal.core.model.CModelOperation.execute(CModelOperation.java:341)
  at org.eclipse.cdt.internal.core.model.CModelOperation.run(CModelOperation.java:607)
  at org.eclipse.cdt.internal.core.model.CModelOperation.runOperation(CModelOperation.java:635)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.pathEntryStoreChanged(PathEntryManager.java:1339)
  at org.eclipse.cdt.internal.core.model.PathEntryStoreProxy.notifyListeners(PathEntryStoreProxy.java:63)
  at org.eclipse.cdt.internal.core.model.PathEntryStoreProxy.fireContentChangedEvent(PathEntryStoreProxy.java:56)
  at org.eclipse.cdt.internal.core.model.PathEntryStoreProxy.postProcessProviderChange(PathEntryStoreProxy.java:141)
  at org.eclipse.cdt.internal.core.settings.model.AbstractCExtensionProxy.checkUpdateProvider(AbstractCExtensionProxy.java:121)
  at org.eclipse.cdt.internal.core.settings.model.AbstractCExtensionProxy.providerRequested(AbstractCExtensionProxy.java:38)
  at org.eclipse.cdt.internal.core.model.PathEntryStoreProxy.getRawPathEntries(PathEntryStoreProxy.java:96)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getRawPathEntries(PathEntryManager.java:647)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:543)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:526)
  at org.eclipse.cdt.internal.core.model.PathEntryManager.getResolvedPathEntries(PathEntryManager.java:510)
  at org.eclipse.cdt.core.model.CoreModel.getResolvedPathEntries(CoreModel.java:948)
  at org.eclipse.cdt.internal.core.model.CProject.getResolvedPathEntries(CProject.java:400)
  at org.eclipse.cdt.internal.core.model.CProject.getOutputEntries(CProject.java:509)
  at org.eclipse.cdt.internal.core.model.CProject.isOnOutputEntry(CProject.java:541)
  at org.eclipse.cdt.internal.core.model.CContainer.computeChild(CContainer.java:215)
  at org.eclipse.cdt.internal.core.model.CContainer.computeChildren(CContainer.java:182)
  at org.eclipse.cdt.internal.core.model.CContainer.buildStructure(CContainer.java:154)
  at org.eclipse.cdt.internal.core.model.Openable.generateInfos(Openable.java:261)
  at org.eclipse.cdt.internal.core.model.CElement.openWhenClosed(CElement.java:427)
  at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:305)
  at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:295)
  at org.eclipse.cdt.internal.core.model.Parent.getChildren(Parent.java:55)
  at org.eclipse.cdt.internal.core.model.CElement.accept(CElement.java:524)
  at org.eclipse.cdt.internal.core.model.CElement.accept(CElement.java:526)
  at org.eclipse.cdt.internal.core.pdom.indexer.PDOMRebuildTask.createDelegate(PDOMRebuildTask.java:118)
  at org.eclipse.cdt.internal.core.pdom.indexer.PDOMRebuildTask.run(PDOMRebuildTask.java:78)
  at org.eclipse.cdt.internal.core.pdom.PDOMIndexerJob.run(PDOMIndexerJob.java:149)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 4 2 2017-05-22 06:23:29.575
!MESSAGE An internal error occurred during: "C/C++ Indexer".
!STACK 0
java.lang.NullPointerException
  at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:349)
  at org.eclipse.core.runtime.Plugin.getLog(Plugin.java:297)
  at org.eclipse.cdt.core.CCorePlugin.log(CCorePlugin.java:1439)
  at org.eclipse.cdt.core.CCorePlugin.log(CCorePlugin.java:1418)
  at org.eclipse.cdt.core.CCorePlugin.log(CCorePlugin.java:1405)
  at org.eclipse.cdt.internal.core.pdom.PDOMIndexerJob.run(PDOMIndexerJob.java:162)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SESSION 2017-05-22 06:38:10.652 -----------------------------------------------
eclipse.buildId=2016.4
java.version=1.8.0_66
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -application com.xilinx.sdk.cmdline.service 41604
Command-line arguments:  -os linux -ws gtk -arch x86_64 -application com.xilinx.sdk.cmdline.service 41604 -data /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0

!ENTRY org.eclipse.core.resources 2 10035 2017-05-22 06:38:17.460
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.osgi 4 0 2017-05-22 06:38:19.673
!MESSAGE Application error
!STACK 1
java.lang.IllegalArgumentException: Argument cannot be null
  at org.eclipse.swt.SWT.error(SWT.java:4472)
  at org.eclipse.swt.SWT.error(SWT.java:4406)
  at org.eclipse.swt.SWT.error(SWT.java:4377)
  at org.eclipse.swt.graphics.Resource.<init>(Resource.java:50)
  at org.eclipse.swt.graphics.Color.<init>(Color.java:80)
  at com.xilinx.sdk.loggers.SdkLogAppender.initializeOutputStreams(SdkLogAppender.java:52)
  at com.xilinx.sdk.loggers.SdkLogAppender.append(SdkLogAppender.java:83)
  at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
  at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
  at org.apache.log4j.Category.callAppenders(Category.java:206)
  at org.apache.log4j.Category.forcedLog(Category.java:391)
  at org.apache.log4j.Category.log(Category.java:856)
  at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:304)
  at com.xilinx.sdk.cmdline.application.SdkServiceStartUp.registerTcfCmdServers(SdkServiceStartUp.java:21)
  at com.xilinx.sdk.cmdline.application.Service.start(Service.java:47)
  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:497)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
!SESSION 2017-05-22 06:40:10.623 -----------------------------------------------
eclipse.buildId=2016.4
java.version=1.8.0_66
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -application com.xilinx.sdk.cmdline.service 45753
Command-line arguments:  -os linux -ws gtk -arch x86_64 -application com.xilinx.sdk.cmdline.service 45753 -data /home/jenkins/slave/workspace/our_product_iofpga_clean_build/build_iofpga/tmp/work/aarch64-company-linux/fsbl/0.2+xilinx+gitAUTOINC+a931a8d447-r0

!ENTRY org.eclipse.core.resources 2 10035 2017-05-22 06:40:17.752
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.osgi 4 0 2017-05-22 06:40:19.842
!MESSAGE Application error
!STACK 1
java.lang.IllegalArgumentException: Argument cannot be null
  at org.eclipse.swt.SWT.error(SWT.java:4472)
  at org.eclipse.swt.SWT.error(SWT.java:4406)
  at org.eclipse.swt.SWT.error(SWT.java:4377)
  at org.eclipse.swt.graphics.Resource.<init>(Resource.java:50)
  at org.eclipse.swt.graphics.Color.<init>(Color.java:80)
  at com.xilinx.sdk.loggers.SdkLogAppender.initializeOutputStreams(SdkLogAppender.java:52)
  at com.xilinx.sdk.loggers.SdkLogAppender.append(SdkLogAppender.java:83)
  at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
  at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
  at org.apache.log4j.Category.callAppenders(Category.java:206)
  at org.apache.log4j.Category.forcedLog(Category.java:391)
  at org.apache.log4j.Category.log(Category.java:856)
  at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:304)
  at com.xilinx.sdk.cmdline.application.SdkServiceStartUp.registerTcfCmdServers(SdkServiceStartUp.java:21)
  at com.xilinx.sdk.cmdline.application.Service.start(Service.java:47)
  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:497)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

I've went through all of the related posts here and it seems there has been few reports of similar cases that have been marked as solved:

 

  1. Missing "localhost" from /etc/hosts - verified, its there.
  2. Knowledge base pointed that in same cases, one should have environment varible SWT_GTK3 with value 0 ..  I added this to xilinx.sh in /etc/profile.d and have verified that the env is present in the jenkins slave running the yocto build.
  3. There where some suggestions to increase the size of timeout from 30 seconds to 60 seconds (pre 2016.3) in xsdb.tcl .. It seems the default value there was already 60 seconds. Just to be on the safe side, I increased the timeout from 60 to 120 seconds.

 

Im pretty noob with yocto tools and xilinx even more so i don't know how to debug this issue further.

 

The issue happens randomly - which makes it even harder to debug but so far, its always either fsbl or pmu-firmware recipes.

 

Stacktrace logs look like the issues is happening in Eclipse CDT (and c/c++ indexer?) .. I spotted few similar bug reports in eclipse bug tracker reported for CDT 8.8.0 - which is also the version in Xilinx 2016.4 if im not mistaken. Possible a bug in upstream products ?

 

Any suggestions ?

 

 

0 Kudos
11 Replies
Visitor rasjani
Visitor
4,293 Views
Registered: ‎05-22-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

I forgot to mention that if i run bitbake in the loop, checking for exit code and finish if succes or after few tries, the build actually does succesfully finish. So the issue does not seem to be about hitting some hard error that cannot be recovered from.

0 Kudos
Moderator
Moderator
4,220 Views
Registered: ‎09-12-2007

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

The bitbake will breakup the job into tasks. So, this might be causing the issue. If you breakup the job into its individual tasks

for example bitbake virtual/bootloader, and bitbake virtual/pmufw does this work? 

 

If this does, then you could try reduce the BB_NUMBER_THREADS and PARALLEL_MAKE in your local.conf

http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#var-PARALLEL_MAKE

https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#var-BB_NUMBER_THREADS

0 Kudos
Visitor rasjani
Visitor
4,166 Views
Registered: ‎05-22-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

Limiting parallel building would increase buildtimes. Same suggestion (splitting build into multiple phases) came via other routes also. I did try it out but initially failed. If i do clean build, building firware still has quite a few packages and steps to do get all the dependencies build.

 

I did essentially fix the issue by bruteforcing build by doing iterations:

 

iterations=5
for i in $(seq 1 $iterations); do
  echo -e "\n*** building: main-image ($i/$iterations)"
  set +e
  bitbake $MIRROR_OPTION io-image ${BITBAKE_DEBUG}
  RET=$?
  set -e
  if [ $RET == 0 ]; then
    echo "Build Success"
    break
  fi
  if [ $i == $iterations ]; then
    echo "Build Failed even after $iterations iterations"
    exit $RET
  fi
done

Essentially this is as effective as breaking the build into smaller steps..

 

But anyway, either this or building separate  steps are only workarounds for the real issue - why the timeout in the first place ? It seems the issue is because eclipse fails to start. I did crawl throught eclipse bug tracker and googled around and while not being able to pinpoint the issue, i did find few occurances where similar behaviour in standalone eclipse produced similar results with cdt 8.8.0..

 

 

0 Kudos
Moderator
Moderator
4,156 Views
Registered: ‎09-12-2007

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

In yocto flow, the timeout errors in XSCT are because eclipse fails to start on time. Yocto build flow is spawning of multiple threads because of which there is not enough memory for SDK to start. Plx team is using a large timeout value, so that SDK has enough time to start. I not aware of any other solution, other than the one you are using.

0 Kudos
Visitor rasjani
Visitor
4,111 Views
Registered: ‎05-22-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

> the timeout errors in XSCT are because eclipse fails to start on time.

 

indeed - and the scenarios where this happens on plain eclipse (with same error messages and somewhat similar backtrace) is when the workspace is corrupted or with unsaved data.  When checking the log details (as shown in the initial post) - it indeed looks like something might be going wrong first:

 

!ENTRY org.eclipse.cdt.core 4 2 2017-05-22 06:23:29.568
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.cdt.core".
!STACK 0
java.lang.IllegalStateException: Workspace is closed.

Then restart or new invocation of xsct:

 

!ENTRY org.eclipse.core.resources 2 10035 2017-05-22 06:38:17.460
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

And this gets repeated few times and then finally the whole build fails to xsct timeout ..

 

Ofcourse i cant say my assumption here is 100% true because i didn't have timestamps on console build log at the time enable.

 

So, what im trying to ask: this looks like a bug in the sdk or components used by it. Similar issues have been reported in cdt 8.8.0 which is still also used w/ 2017.1 - can those be ruled out for not being the cause for this ?

 

 

0 Kudos
Moderator
Moderator
4,079 Views
Registered: ‎09-12-2007

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

This is a known issue that the xilinx developers are looking into addressing in 2017.2. 

0 Kudos
Visitor martindreher
Visitor
3,297 Views
Registered: ‎10-15-2015

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

I have the same behavior also with version 2017.2.

Currently I have also no solution for that problem :-(

 

Is there someone who has a solution or a workaround?

0 Kudos
Xilinx Employee
Xilinx Employee
3,282 Views
Registered: ‎01-03-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

hi @martindreher,

 

Can you run below command just after launching XSCT.

configparams sdk-launch-timeout 3600

Then then run all your commands.

 

Thanks & Regards,

Praveen Kumar. V

0 Kudos
Xilinx Employee
Xilinx Employee
3,277 Views
Registered: ‎06-29-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

The reason for failure is xsct uses a locking mechanism which is by default set to /home/user/

 

you have to change this 

 

in fsbl and pmufw recipes add this two lines 

 

export _JAVA_OPTIONS
_JAVA_OPTIONS = "-Duser.home=${TMPDIR}/xsctenv"

 

Visitor martindreher
Visitor
1,855 Views
Registered: ‎10-15-2015

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

Thanks vineethc. The timeout error is gone now...

But now I get the next failure :-(

 

Because of the error "Eclipse: Cannot open display:" I have to start "Xvfb :1" and set <export DISPLAY = ":1.0">

 

| Picked up _JAVA_OPTIONS: -Duser.home=/home/office/myproject/poky/build/tmp/xsctenv
| done
| 'fsbl_bsp' will not be imported... [ALREADY EXIST]
| 'fsbl_hwproj' will not be imported... [ALREADY EXIST]
| 'fsbl' will not be imported... [ALREADY EXIST]
| Building '/fsbl_bsp'
| 11:25:56 **** Clean-only build of project fsbl_bsp ****
| make -k clean
| make -C psu_cortexa53_0/libsrc/ddrcpsu_v1_1/src -s clean
| make -C psu_cortexa53_0/libsrc/ipipsu_v2_3/src -s clean
| make -C psu_cortexa53_0/libsrc/gpiops_v3_3/src -s clean
| make -C psu_cortexa53_0/libsrc/myTestIp_v1_0/src -s clean
| make -C psu_cortexa53_0/libsrc/standalone_v6_3/src -s clean
| make -C psu_cortexa53_0/libsrc/scugic_v3_7/src -s clean
| make -C psu_cortexa53_0/libsrc/sysmonpsu_v2_2/src -s clean
| make -C psu_cortexa53_0/libsrc/emacps_v3_4/src -s clean
| make -C psu_cortexa53_0/libsrc/zdma_v1_2/src -s clean
| make -C psu_cortexa53_0/libsrc/rtcpsu_v1_4/src -s clean
| make -C psu_cortexa53_0/libsrc/cpu_cortexa53_v1_3/src -s clean
| make -C psu_cortexa53_0/libsrc/axipmon_v6_5/src -s clean
| make -C psu_cortexa53_0/libsrc/csudma_v1_1/src -s clean
| make -C psu_cortexa53_0/libsrc/sdps_v3_2/src -s clean
| make -C psu_cortexa53_0/libsrc/iicps_v3_5/src -s clean
| make -C psu_cortexa53_0/libsrc/usbpsu_v1_2/src -s clean
| make -C psu_cortexa53_0/libsrc/uartps_v3_4/src -s clean
| make -C psu_cortexa53_0/libsrc/qspipsu_v1_4/src -s clean
| make -C psu_cortexa53_0/libsrc/coresightps_dcc_v1_4/src -s clean
| rm -f psu_cortexa53_0/lib/libxil.a
| 
| 11:25:56 Build Finished (took 136ms)
| 
| Building '/fsbl'
| Building '/fsbl_bsp'
| Invoking Make Builder...fsbl_bsp
| 11:25:57 **** Build of project fsbl_bsp ****
| make -k all
[...]

 

But now I get the error ".../Release/fsbl.elf': No such file or directory"

 

I'm not sure if I should use the meta-xilinx-tools because it looks a bit buggy.

0 Kudos
Xilinx Employee
Xilinx Employee
1,831 Views
Registered: ‎06-29-2017

Re: Xilinx 2016.4 - xsct - Timeout while building fsbl and pmu-firmware

I think you are missing some pre-reuisites,

 

can you do this small exercise,  are you able to run xsct directly on console and able to generate fsbl.elf 

0 Kudos