Skip to contentSkip to conversation

Can't run HOB

DISCUSSION Gary Thomas 3 participants 5 messages Mar 20, 2012

lore
Share & tools
lore
#0 lore raw

When I try HOB on my tree, it parses the metadata to around 57% and then brings up what I guess is a warning (sadly, it only shows an empty dialogue with an "OK" button). This seems to happen because I have meta-ti in my bblayers.conf. I also have this statement in my local.conf:
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"

Maybe HOB is not honouring the BBMASK?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 9 lines · Gary Thomas

When I try HOB on my tree, it parses the metadata to around 57% and then brings up what I guess is a warning (sadly, it only shows an empty dialogue with an "OK" button). This seems to happen because I have meta-ti in my bblayers.conf. I also have this statement in my local.conf:
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"

Maybe HOB is not honouring the BBMASK?

Variables are still handled in bitbake server side, Hob only acts as a bridge between user and bitbake server.

The phenomenon is strange since the code piece will detect if the error msg is None or not. If it is None, it will not pop up the error dialog.

================================================================
def handler_command_failed_cb(self, handler, msg):
if msg:
lbl = "<b>Error</b>\n"
lbl = lbl + "%s\n\n" % msg
dialog = CrumbsMessageDialog(self, lbl,
gtk.STOCK_DIALOG_WARNING)
dialog.add_button(gtk.STOCK_OK, gtk.RESPONSE_OK) response = dialog.run() dialog.destroy()
================================================================

What's does it do if you click the "OK" button?

Thanks,
Dongxiao

Quoted 1 line
#2 lore raw
Quoted 29 lines · Dongxiao
Quoted 9 lines · Gary Thomas

When I try HOB on my tree, it parses the metadata to around 57% and then brings up what I guess is a warning (sadly, it only shows an empty dialogue with an "OK" button). This seems to happen because I have meta-ti in my bblayers.conf. I also have this statement in my local.conf:
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"

Maybe HOB is not honouring the BBMASK?

Variables are still handled in bitbake server side, Hob only acts as a bridge between user and bitbake server.

The phenomenon is strange since the code piece will detect if the error msg is None or not. If it is None, it will not pop up the error dialog.

================================================================
def handler_command_failed_cb(self, handler, msg):
if msg:
lbl = "<b>Error</b>\n"
lbl = lbl + "%s\n\n" % msg
dialog = CrumbsMessageDialog(self, lbl,
gtk.STOCK_DIALOG_WARNING)
dialog.add_button(gtk.STOCK_OK, gtk.RESPONSE_OK) response = dialog.run() dialog.destroy()
================================================================

Quoted 1 line

What's does it do if you click the "OK" button?

It seems to stop scanning recipes immediately. There is no text along with the warning dialogue.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
In reply to Xu, Dongxiao

I suspect msg = "".

Can you add print(msg) at the beginning of the function? That's:

=========
def handler_command_failed_cb(self, handler, msg):
print(msg)
if msg:
lbl = "<b>Error</b>\n" lbl = lbl + "%s\n\n" % msg dialog =
=========

--
Shane

Xu, Dongxiao wrote on 2012-03-20:

Quoted 38 lines · Gary Thomas
Quoted 8 lines

When I try HOB on my tree, it parses the metadata to around 57% and then brings up what I guess is a warning (sadly, it only shows an empty dialogue with an "OK" button). This seems to happen because I have meta-ti in my bblayers.conf. I also have this statement in my local.conf:
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"
Maybe HOB is not honouring the BBMASK?

Variables are still handled in bitbake server side, Hob only acts as a bridge between user and bitbake server.

The phenomenon is strange since the code piece will detect if the error msg is None or not. If it is None, it will not pop up the error dialog.

===============================================================
=
def handler_command_failed_cb(self, handler, msg):
if msg:
lbl = "<b>Error</b>\n" lbl = lbl + "%s\n\n" % msg dialog = CrumbsMessageDialog(self, lbl, gtk.STOCK_DIALOG_WARNING) dialog.add_button(gtk.STOCK_OK, gtk.RESPONSE_OK) response = dialog.run() dialog.destroy()
=============================================================== =

What's does it do if you click the "OK" button?

Thanks,
Dongxiao

Quoted 1 line

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#4 lore raw
Quoted 10 lines · Shane

I suspect msg = "".

Can you add print(msg) at the beginning of the function? That's:

=========
def handler_command_failed_cb(self, handler, msg):
print(msg)
if msg:
lbl = "<b>Error</b>\n" lbl = lbl + "%s\n\n" % msg dialog =
=========

Message attached (it's big).

Note: this setup (my metadata + meta-ti + yocto core) builds images just fine.

Quoted 41 lines

Xu, Dongxiao wrote on 2012-03-20:

Quoted 38 lines · Gary Thomas
Quoted 8 lines

When I try HOB on my tree, it parses the metadata to around 57% and then brings up what I guess is a warning (sadly, it only shows an empty dialogue with an "OK" button). This seems to happen because I have meta-ti in my bblayers.conf. I also have this statement in my local.conf:
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"
Maybe HOB is not honouring the BBMASK?

Variables are still handled in bitbake server side, Hob only acts as a bridge between user and bitbake server.

The phenomenon is strange since the code piece will detect if the error msg is None or not. If it is None, it will not pop up the error dialog.

===============================================================
=
def handler_command_failed_cb(self, handler, msg):
if msg:
lbl = "<b>Error</b>\n" lbl = lbl + "%s\n\n" % msg dialog = CrumbsMessageDialog(self, lbl, gtk.STOCK_DIALOG_WARNING) dialog.add_button(gtk.STOCK_OK, gtk.RESPONSE_OK) response = dialog.run() dialog.destroy()
=============================================================== =

What's does it do if you click the "OK" button?

Thanks,
Dongxiao

Quoted 1 line

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Failure expanding variable do_compile, expression was # TODO :: KERNEL_CC, should use for kernel module build?

    # TODO :: Check the 'unset's

    unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS

    do_make_scripts

    # Build the gpp (hlos) kernel space
    cd ${SYSLINK_ROOT}/ti/syslink/utils/hlos/knl/Linux && make \
        ARCH="${TARGET_ARCH}" \
        CROSS_COMPILE="${TARGET_PREFIX}" \
        SYSLINK_PLATFORM="${SYSLINKPLATFORM}" \
        SYSLINK_VARIANT="${SYSLINKVARIANT}" \
        SYSLINK_LOADER="${SYSLINKLOADER}" \
        SYSLINK_PKGPATH="${IPC_INSTALL_DIR}/packages" \
        KDIR="${STAGING_KERNEL_DIR}"

# # Build the gpp (hlos) kernel space samples.
# for sample in ${SYSLINKHLOSSAMPLES}; do
# cd ${SYSLINK_ROOT}/ti/syslink/samples/hlos/$sample/knl/Linux && make \

#            ARCH="${TARGET_ARCH}" \
#            CROSS_COMPILE="${TARGET_PREFIX}" \
#            SYSLINK_PLATFORM="${SYSLINKPLATFORM}" \
#            SYSLINK_VARIANT="${SYSLINKVARIANT}" \
#            SYSLINK_LOADER="${SYSLINKLOADER}" \
#            SYSLINK_PKGPATH="${IPC_INSTALL_DIR}/packages" \
#            SYSLINK_SDK=EZSDK \
#            KDIR="${STAGING_KERNEL_DIR}"

# done

    # Build the gpp (hlos) user space
    cd ${SYSLINK_ROOT}/ti/syslink/utils/hlos/usr/Linux && make \
        ARCH="${TARGET_ARCH}" \
        CROSS_COMPILE="${TARGET_PREFIX}" \
        TOOLCHAIN_PREFIX="${TOOLCHAIN_PATH}/${TARGET_PREFIX}" \
        SYSLINK_PLATFORM="${SYSLINKPLATFORM}" \
        SYSLINK_VARIANT="${SYSLINKVARIANT}" \
        SYSLINK_LOADER="${SYSLINKLOADER}" \
        SYSLINK_PKGPATH="${IPC_INSTALL_DIR}/packages"

    # Build the gpp (hlos) user space samples
    # First build the common lib for samples.
    cd ${SYSLINK_ROOT}/ti/syslink/samples/hlos/common/usr/Linux && make \
        ARCH="${TARGET_ARCH}" \
        CROSS_COMPILE="${TARGET_PREFIX}" \
        TOOLCHAIN_PREFIX="${TOOLCHAIN_PATH}/${TARGET_PREFIX}" \
        SYSLINK_PLATFORM="${SYSLINKPLATFORM}" \
        SYSLINK_VARIANT="${SYSLINKVARIANT}" \
        SYSLINK_LOADER="${SYSLINKLOADER}" \
        SYSLINK_SDK=EZSDK \
        SYSLINK_PKGPATH="${IPC_INSTALL_DIR}/packages"

    for sample in ${SYSLINKHLOSSAMPLES}; do
        cd ${SYSLINK_ROOT}/ti/syslink/samples/hlos/$sample/usr/Linux && make \
            ARCH="${TARGET_ARCH}" \
            CROSS_COMPILE="${TARGET_PREFIX}" \
            TOOLCHAIN_PREFIX="${TOOLCHAIN_PATH}/${TARGET_PREFIX}" \
            SYSLINK_PLATFORM="${SYSLINKPLATFORM}" \
            SYSLINK_VARIANT="${SYSLINKVARIANT}" \
            SYSLINK_LOADER="${SYSLINKLOADER}" \
            SYSLINK_SDK=EZSDK \
            SYSLINK_PKGPATH="${IPC_INSTALL_DIR}/packages"
    done

    # Build the dsp/arm (rtos) code (system and samples)
    # cd ${SYSLINK_ROOT}/ti/syslink && \
    #     ${XDC_INSTALL_DIR}/xdc --jobs=${BB_NUMBER_THREADS} -PR .
    export XDCOPTIONS=v
    cd ${SYSLINK_ROOT}/ti/syslink && \
        ${XDC_INSTALL_DIR}/xdc -P \
         `${XDC_INSTALL_DIR}/bin/xdcpkg ${SYSLINK_ROOT}/ti/syslink | grep -v samples`
    export XDCARGS="profile=debug"
    cd ${SYSLINK_ROOT}/ti/syslink && \
        ${XDC_INSTALL_DIR}/xdc --jobs=${BB_NUMBER_THREADS} -P \
         `${XDC_INSTALL_DIR}/bin/xdcpkg ${SYSLINK_ROOT}/ti/syslink | grep samples`

which triggered exception TypeError: sequence item 95: expected string, int found