Azure SDK on Yocto Thud IMX8M Mini

cancel
Showing results for 
Search instead for 
Did you mean: 

Azure SDK on Yocto Thud IMX8M Mini

725 Views
dave_nugent
Contributor II

Hi,

I am having a problem adding Azure iot SDK  Recipe meta-iot-cloud (OpenEmbedded Layer Index - meta-iot-cloud ) to my build (IMX8M Mini Yocto Thud). I am able to add the layer to my source directory, and add the layer to my bblayers.conf, but when I try to add azure-iot-sdk-c ( OpenEmbedded Layer Index - azure-iot-sdk-c ) to my IMAGE_INSTALL_append in local.conf and run bitbake I get the errors:

ERROR: azure-uamqp-c-1.2.4-r0 do_unpack: gitsm: submodule unpack failed: UnpackError Unpack failure for URL: 'gitsm://www.github.com/Azure/azure-c-shared-utility;protocol=https;name=deps/azure-c-shared-utility;subpath=deps/azure-c-shared-utility;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /home/dnugent/workspace/thud-imx-yocto-bsp/downloads//git2/www.github.com.Azure.azure-c-shared-utility; shallow clone not enabled
ERROR: azure-uamqp-c-1.2.4-r0 do_unpack: Unpack failure for URL: 'gitsm://www.github.com/Azure/azure-c-shared-utility;protocol=https;name=deps/azure-c-shared-utility;subpath=deps/azure-c-shared-utility;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /home/dnugent/workspace/thud-imx-yocto-bsp/downloads//git2/www.github.com.Azure.azure-c-shared-utility; shallow clone not enabled
ERROR: azure-uamqp-c-1.2.4-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: /home/dnugent/workspace/thud-imx-yocto-bsp/build-dir/tmp/work/aarch64-poky-linux/azure-uamqp-c/1.2.4-r0/temp/log.do_unpack.23085
ERROR: Task (/home/dnugent/workspace/thud-imx-yocto-bsp/sources/meta-iot-cloud/recipes-azure/azure-uamqp-c/azure-uamqp-c_1.2.4.bb:do_unpack) failed with exit code '1'
ERROR: azure-umqtt-c-1.1.4-r0 do_unpack: gitsm: submodule unpack failed: UnpackError Unpack failure for URL: 'gitsm://github.com/Azure/azure-ctest.git;protocol=https;name=testtools/ctest;subpath=testtools/ctest;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /home/dnugent/workspace/thud-imx-yocto-bsp/downloads//git2/github.com.Azure.azure-ctest.git; shallow clone not enabled
ERROR: azure-umqtt-c-1.1.4-r0 do_unpack: gitsm: submodule unpack failed: UnpackError Unpack failure for URL: 'gitsm://github.com/Azure/azure-ctest.git;protocol=https;name=testtools/ctest;subpath=testtools/ctest;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /home/dnugent/workspace/thud-imx-yocto-bsp/downloads//git2/github.com.Azure.azure-ctest.git; shallow clone not enabled
ERROR: azure-umqtt-c-1.1.4-r0 do_unpack: Unpack failure for URL: 'gitsm://github.com/Azure/azure-ctest.git;protocol=https;name=testtools/ctest;subpath=testtools/ctest;bareclone=1;nobranch=1'. No up to date source found: clone directory not available or not up to date: /home/dnugent/workspace/thud-imx-yocto-bsp/downloads//git2/github.com.Azure.azure-ctest.git; shallow clone not enabled
ERROR: azure-umqtt-c-1.1.4-r0 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: /home/dnugent/workspace/thud-imx-yocto-bsp/build-dir/tmp/work/aarch64-poky-linux/azure-umqtt-c/1.1.4-r0/temp/log.do_unpack.23084
ERROR: Task (/home/dnugent/workspace/thud-imx-yocto-bsp/sources/meta-iot-cloud/recipes-azure/azure-umqtt-c/azure-umqtt-c_1.1.4.bb:do_unpack) failed with exit code '1'

Does anybody know what the issue could be?

Thanks so much!

Tags (2)
2 Replies

289 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Dave Nugent,

Are you using the Thud branch from the Community BSP? I’m just double checking as you should ideally use the same poky version for all layers.

This problem seems to be related to the meta-iot-cloud layer itself. I couldn’t find what could cause the “No up to date source found” but have you tried syncing the layer again to see if there was a problem with the metadata?

Another alternative could be trying an older more mature branch like sumo as this could be a yet to be fixed issue on the thud branch of this layer.

Regards,

0 Kudos

289 Views
dave_nugent
Contributor II

Thanks Gusarambula,

Yeah I was using the Thud branch from the community BSP and I was using the same verison for all layers. I am not sure what the issue was but I was able to resolve the issue by switching everything to the Sumo branch.

Thanks for the help!