Yocto build failures due to offline repositories

Technical Support
, ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I understand your frustration with the sporadic build failures when git.toradex.com repositories become unavailable. This is indeed a known issue that affects Yocto builds when the primary repository sources are unreachable, even when local caches exist.

Current Repository Structure

Toradex maintains several BSP layers and repositories that are essential for building custom images (1). The main repositories include:

  • toradex-manifest: Contains all layers used by Torizon OS and Reference Images
  • meta-toradex-bsp-common: BSP layer common to all Toradex modules
  • meta-toradex-nxp: BSP layer for NXP SoC-based modules
  • meta-toradex-ti: BSP layer for Texas Instruments SoC-based modules

Workarounds for Repository Availability Issues

Based on community experiences, here are some approaches to mitigate this issue:

1. Alternative Repository Access Methods

Some users have found success using different protocols when the HTTPS access fails (2). You can try modifying your repository access to use:

git clone git://git.toradex.com/meta-toradex-bsp-common.git

Instead of the HTTPS variant that may be experiencing issues.

2. Local Repository Mirroring

While you mentioned maintaining internal mirrors, this remains one of the most robust solutions for production environments. You can:

  • Clone the essential repositories locally during stable periods
  • Modify your local.conf to point to your internal mirrors
  • Set up automated synchronization during maintenance windows

3. Yocto Build Configuration

Ensure your Yocto build configuration includes proper fallback mechanisms. The Yocto Project documentation suggests configuring multiple source URIs where possible (1).

Repository Status and Alternatives

The issue you’re experiencing appears to be related to temporary server availability problems (3). While there isn’t currently an official GitHub mirror for u-boot-toradex, the community has noted that such infrastructure improvements would benefit all users.

Recommendations

  1. Immediate Solution: Use the git:// protocol instead of HTTPS when accessing Toradex repositories
  2. Medium-term: Implement local mirroring for critical repositories in your build infrastructure
  3. Build Resilience: Configure your build system to retry failed downloads after a delay

Your suggestions for adding repository mirrors and improving the robustness of the build system are valuable feedback that would benefit the entire Toradex community. The current single point of failure does create unnecessary build interruptions for development teams.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.