Repo sync error

Hello Team,
I am trying to build image for Aster Carrier Board from this link guide .
i am getting error in repo sync command

error: Cannot fetch openembedded-core.git from https://github.com/openembedded/openembedded-core.git
Fetching: 100% (5/5), done in 19m10.719s
error: Unable to fully sync the tree
error: Downloading network changes failed.
Try re-running with "-j1 --fail-fast" to exit at the first error.
================================================================================
Repo command failed due to the following `SyncError` errors:
GitCommandError: 'fetch --quiet --progress repo --prune --recurse-submodules=no --tags +refs/heads/*:refs/remotes/repo/* +refs/heads/kirkstone:refs/remotes/repo/kirkstone +refs/tags/*:refs/tags/*' on meta-openembedded.git failed
stdout: remote: Enumerating objects: 244549, done.        
GitCommandError: 'fetch --quiet --progress repo --prune --recurse-submodules=no --tags +refs/heads/*:refs/remotes/repo/* +refs/heads/kirkstone:refs/remotes/repo/kirkstone +refs/tags/*:refs/tags/*' on meta-freescale.git failed
stdout: remote: Enumerating objects: 51157, done.        
GitCommandError: 'fetch --quiet --progress repo --prune --recurse-submodules=no --tags +refs/heads/*:refs/remotes/repo/* +refs/heads/kirkstone:refs/remotes/repo/kirkstone +refs/tags/*:refs/tags/*' on meta-freescale-distro.git failed
stdout: remote: Enumerating objects: 2431, done.        
GitCommandError: 'fetch --quiet --progress repo --prune --recurse-submodules=no --tags +refs/heads/*:refs/remotes/repo/* +refs/heads/kirkstone:refs/remotes/repo/kirkstone +refs/tags/*:refs/tags/*' on openembedded-core.git failed
stdout: remote: Enumerating objects: 526161, done.        
GitCommandError: 'fetch --quiet --progress repo --prune --recurse-submodules=no --tags +refs/heads/*:refs/remotes/repo/* +refs/heads/2.0:refs/remotes/repo/2.0 +refs/tags/*:refs/tags/*' on bitbake.git failed
stdout: remote: Enumerating objects: 65944, done.        
+5 additional errors...

Can you suggest me how can i resolve it

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

The errors you’re encountering during the repo sync operation suggest there might be network-related issues or specific problems with accessing the repositories. Here are several steps you can take to resolve these issues:

  1. Retry with Limited Parallel Downloads: Sometimes, network issues can be mitigated by reducing the number of parallel downloads. Use the -j1 option with the repo sync command to limit the sync to one repository at a time, as suggested:

    repo sync -j1 --fail-fast
    

    This can help identify if the problem is with a specific repository and also reduce the likelihood of network errors.

  2. Check Network Configuration: Ensure that your network configuration allows access to the repositories mentioned in the errors. This includes checking firewall settings, proxy configurations, and whether your internet connection is stable and not blocking git or https connections to GitHub or other repository hosts.

  3. Clear Local Repo Cache: If the problem persists, there might be an issue with the local cache of the repositories. You can clear the local repo cache by removing the problematic repositories’ directories from the .repo/projects and .repo/project-objects directories, as mentioned in the context provided. For example:

    rm -rf .repo/projects/openembedded-core.git
    rm -rf .repo/project-objects/openembedded-core.git
    

    After clearing the cache, try running the repo sync command again.

  4. Use Git Protocol: If your network allows it, switching to the git protocol might provide a more reliable connection for fetching the repositories. Modify your .repo/manifest.xml file to use the git protocol for the failing repositories. For example, change the fetch URL for the OpenEmbedded repository to:

    <remote fetch="git://github.com/openembedded/openembedded-core.git" name="oe"/>
    

    Note: This step requires that your network and firewall settings allow git protocol traffic, which is not always the case.

  5. Check for Git LFS Issues: If any of the repositories use Git Large File Storage (LFS), ensure that Git LFS is correctly installed and configured on your system. Sometimes, errors can occur if large files are not properly fetched with Git LFS.

  6. Update Git and Repo Tool: Ensure that you are using the latest versions of Git and the repo tool. Older versions might have bugs or incompatibilities that have been resolved in newer releases.

If after trying these steps you continue to experience issues, it might be helpful to isolate whether the

Please, also check if these links can help you solve your problem:

Secure Boot on Torizon OS | Toradex Developer Center.