Debix Yocto fetch fail

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debix Yocto fetch fail

256 Views
SamuelDo
Contributor I

Hello,

I am currently building a Yocto image for DEBIX Model A (i.MX8M Plus) using the NXP Yocto 6.12-styhead release and the DEBIX meta-layers.
However, the build fails during the fetch stage of the kernel recipe linux-imx_6.12.bb.

I'am using this repo : https://github.com/debix-tech/yocto-nxp-debix

and after cloning and using the .build.sh I get those errors

ERROR: linux-imx-6.12.3+git-r0 do_fetch: Fetcher failure:
Unable to find revision 34099a3c1a8c09693a46ea7ba5370115a733996e
in branch lf_6.12.3-debix_model_ab even from upstream

my guess is that it's trying to reach a private repo

here is the build config


BB_VERSION = 2.9.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = ubuntu-24.04
TARGET_SYS = aarch64-poky-linux
MACHINE = imx8mp-lpddr4-evk
DISTRO = fsl-imx-xwayland
DISTRO_VERSION = 6.12-styhead
TUNE_FEATURES = aarch64 armv8a crc crypto

 

 

0 Kudos
Reply
2 Replies

156 Views
SamuelDo
Contributor I

I will look with the debix support, should I turn back with the answer if anyone needs it ? I have an additional question, does NXP has a distro or yocto project for the imx8 ?

0 Kudos
Reply

221 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

I can identify the problem is occurring during the fetch stage of the linux-imx_6.12.bb kernel recipe.

The error message indicates that the build system is unable to find the specified revision (34099a3c1a8c09693a46ea7ba5370115a733996e) in the "lf_6.12.3-debix_model_ab" branch. This typically happens when the repository URL is correct, but the specific commit or branch name is not accessible.

Since you're using the DEBIX meta-layers from the repository you shared (https://github.com/debix-tech/yocto-nxp-debix), your suspicion that it's trying to reach a private repository is likely correct.

To resolve this issue, I recommend:

1. Check with DEBIX support about access to their private repositories that contain the specific branch/commit mentioned in the error message.

2. Verify if DEBIX has provided any documentation regarding additional repositories that need to be configured when using their meta-layers.

3. As an alternative approach, you could modify the linux-imx recipe to use a publicly available branch/commit instead, though this may not align with DEBIX's specific customizations for their hardware.

4. Examine the linux-imx_6.12.bb recipe file to confirm which repository URL and branch it's trying to access. The recipe file should be located in your meta-layer directories.

This appears to be a configuration issue specific to the DEBIX customization of the NXP Yocto layers, rather than a problem with the core NXP BSP.

Regards

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2254314%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EDebix%20Yocto%20fetch%20fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2254314%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20currently%20building%20a%20Yocto%20image%20for%20DEBIX%20Model%20A%20(i.MX8M%20Plus)%20using%20the%20NXP%20Yocto%206.12-styhead%20release%20and%20the%20DEBIX%20meta-layers.%3CBR%20%2F%3EHowever%2C%20the%20build%20fails%20during%20the%20fetch%20stage%20of%20the%20kernel%20recipe%20linux-imx_6.12.bb.%3C%2FP%3E%3CP%3EI'am%20using%20this%20repo%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fdebix-tech%2Fyocto-nxp-debix%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fdebix-tech%2Fyocto-nxp-debix%3C%2FA%3E%3C%2FP%3E%3CP%3Eand%20after%20cloning%20and%20using%20the%20.build.sh%20I%20get%20those%20errors%3C%2FP%3E%3CP%3EERROR%3A%20linux-imx-6.12.3%2Bgit-r0%20do_fetch%3A%20Fetcher%20failure%3A%3CBR%20%2F%3EUnable%20to%20find%20revision%2034099a3c1a8c09693a46ea7ba5370115a733996e%3CBR%20%2F%3Ein%20branch%20lf_6.12.3-debix_model_ab%20even%20from%20upstream%3CBR%20%2F%3E%3CBR%20%2F%3Emy%20guess%20is%20that%20it's%20trying%20to%20reach%20a%20private%20repo%3C%2FP%3E%3CP%3Ehere%20is%20the%20build%20config%3C%2FP%3E%3CPRE%3E%3CBR%20%2F%3EBB_VERSION%20%3D%202.9.1%3CBR%20%2F%3EBUILD_SYS%20%3D%20x86_64-linux%3CBR%20%2F%3ENATIVELSBSTRING%20%3D%20ubuntu-24.04%3CBR%20%2F%3ETARGET_SYS%20%3D%20aarch64-poky-linux%3CBR%20%2F%3EMACHINE%20%3D%20imx8mp-lpddr4-evk%3CBR%20%2F%3EDISTRO%20%3D%20fsl-imx-xwayland%3CBR%20%2F%3EDISTRO_VERSION%20%3D%206.12-styhead%3CBR%20%2F%3ETUNE_FEATURES%20%3D%20aarch64%20armv8a%20crc%20crypto%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%3C%2FPRE%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2255335%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Debix%20Yocto%20fetch%20fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2255335%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20can%20identify%20the%20problem%20is%20occurring%20during%20the%20fetch%20stage%20of%20the%20linux-imx_6.12.bb%20kernel%20recipe.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20error%20message%20indicates%20that%20the%20build%20system%20is%20unable%20to%20find%20the%20specified%20revision%20(34099a3c1a8c09693a46ea7ba5370115a733996e)%20in%20the%20%22lf_6.12.3-debix_model_ab%22%20branch.%20This%20typically%20happens%20when%20the%20repository%20URL%20is%20correct%2C%20but%20the%20specific%20commit%20or%20branch%20name%20is%20not%20accessible.%3CBR%20%2F%3E%3CBR%20%2F%3ESince%20you're%20using%20the%20DEBIX%20meta-layers%20from%20the%20repository%20you%20shared%20(%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fdebix-tech%2Fyocto-nxp-debix%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fdebix-tech%2Fyocto-nxp-debix%3C%2FA%3E)%2C%20your%20suspicion%20that%20it's%20trying%20to%20reach%20a%20private%20repository%20is%20likely%20correct.%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20resolve%20this%20issue%2C%20I%20recommend%3A%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20Check%20with%20DEBIX%20support%20about%20access%20to%20their%20private%20repositories%20that%20contain%20the%20specific%20branch%2Fcommit%20mentioned%20in%20the%20error%20message.%3CBR%20%2F%3E%3CBR%20%2F%3E2.%20Verify%20if%20DEBIX%20has%20provided%20any%20documentation%20regarding%20additional%20repositories%20that%20need%20to%20be%20configured%20when%20using%20their%20meta-layers.%3CBR%20%2F%3E%3CBR%20%2F%3E3.%20As%20an%20alternative%20approach%2C%20you%20could%20modify%20the%20linux-imx%20recipe%20to%20use%20a%20publicly%20available%20branch%2Fcommit%20instead%2C%20though%20this%20may%20not%20align%20with%20DEBIX's%20specific%20customizations%20for%20their%20hardware.%3CBR%20%2F%3E%3CBR%20%2F%3E4.%20Examine%20the%20linux-imx_6.12.bb%20recipe%20file%20to%20confirm%20which%20repository%20URL%20and%20branch%20it's%20trying%20to%20access.%20The%20recipe%20file%20should%20be%20located%20in%20your%20meta-layer%20directories.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20appears%20to%20be%20a%20configuration%20issue%20specific%20to%20the%20DEBIX%20customization%20of%20the%20NXP%20Yocto%20layers%2C%20rather%20than%20a%20problem%20with%20the%20core%20NXP%20BSP.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256425%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Debix%20Yocto%20fetch%20fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256425%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20will%20look%20with%20the%20debix%20support%2C%20should%20I%20turn%20back%20with%20the%20answer%20if%20anyone%20needs%20it%20%3F%20I%20have%20an%20additional%20question%2C%20does%20NXP%20has%20a%20distro%20or%20yocto%20project%20for%20the%20imx8%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E