Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 329 subscribers
  • Views 412 views
  • Users 0 members are here
Related

Error while creating a UC/OS III BSP

Former Member

Hi everyone

I'm trying to install the UC/OS III v1.30 on my Zedboard, but everytime I try to generate a BSP, the following error mesg pops out:

01:29:10 ERRORt:  [Hsm 55-1545] Problem running tcl command namespace eval sw_ucos_v1_30 source ucos.tcl :
    while executing
"source ucos.tcl"
    (in namespace eval "::sw_ucos_v1_30" script line 1)
    invoked from within
"namespace eval sw_ucos_v1_30 source ucos.tcl"
[Hsm 55-1440] Error(s) while running DRCs.
01:29:10 ERRORt: Error generating bsp sources: Failed to generate BSP.
01:29:10 ERRORt: Failed to generate sources for BSP project ucos_bsp_0
org.eclipse.core.runtime.CoreException: Internal error occurred while generating bsp sources. Please check the SDK Log view for further details.
tat com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler.internalGenerateBsp(RegenBspSourcesHandler.java:178)
tat com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler.access$2(RegenBspSourcesHandler.java:163)
tat com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler$1$1.run(RegenBspSourcesHandler.java:131)
tat org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
tat com.xilinx.sdk.sw.ui.handlers.RegenBspSourcesHandler$1.run(RegenBspSourcesHandler.java:135)
tat org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

It seems to me that something is wrong with the namespace line in .tcl files, but I don't know how to fix this.

I'm doing this on SDK 2014.2 and Vivado 2014.2
My OS is Windows 7

Please advise me how to fix this.
Thank you

  • 0

    Hello Sijie,

    I have found that third party BSP releases are usually very heavily dependent upon the TCL command support, namespace conventions, and SDK feature availability found within the version of SDK under which those BSPs were developed and released.

    Looking at the u00B5C/OS Xilinx SDK Repository Release Notes page, I see that Vivado 2015.1 is required for v1.30 so your best bet is to migrate to this later version of Vivado to meet the BSP requirements.

    https://doc.micrium.com/pages/viewpage.action?pageId=15710044

    If you need to stay with Vivado 2014.2, another option which may work is to try an older version of the BSP.  I see that v1.00 requires Vivado 2014.3 which has fewer feature changes from 2014.2 SDK than does the 2015.1 SDK release.  So it is possible that you may find some success with the older version of the BSP.

    However, it is recommended to migrate to the latest version of the Vivado tools to get the most up to date features and support.

    Regards,

    -Kevin

  • 0 in reply to zedhed

    Ha~Thank you for your advice, I installed the new version of vivado and sdk, everything works fine now.

    Sincerely
    Sijie