Showing results for 
Search instead for 
Did you mean: down

Jump to solution
Contributor I

We noticed this morning our builds started failing. Looks like attempting to clone firmware-imx is failing.

When I try to clone the repo independent of a yocto build I see the following output:

git clone git://
Cloning into 'imx-firmware'...
fatal: unable to connect to[0:]: errno=Connection refused

Are there mirrors we could using for this repo?

Labels (1)
1 Solution
NXP TechSupport
NXP TechSupport

Hello Adam Bader, Diego Perez, and Alex Movitz, 

The git:// repository was replaced by git://

Some recipes may still refer to the old repository so please replace them on the recipes where you are experiencing issues.


View solution in original post

0 Kudos
27 Replies
Contributor III

I ran into this issue trying to sync for an Android 8 build.  I was able to get around it with the following.

git config --global url."git://".insteadOf git://


The repo sync completed but the imx-firmware directory was empty.  I had to manually clone to continue the build.

Contributor II

I'm disappointed at this situation.

Your documentation for old revision something like YOCTO 3.14.38 still advise to use

I thought this momentary trouble in git repo. and I cannot found any announcement about new repository, and I almost drop my project.

this is not good.

0 Kudos
Contributor III

Even we at Power Progress Community we are confused...

As 3 years ago we have forked git:// repository in our

that contain our patches to make working the Video Card with T2080RDB, our question is now from which repository we need to re-base our fork ?

0 Kudos
Contributor I

We are also encountering a failed build for cl-som-imx7, would appreciate your assistance locating: 

searched the 3 repos you have suggested, no luck there.

0 Kudos
Contributor III

We have searched the old repository git:// under new NXP git repositories  NXP · GitHub  but it dosen't exists. We have even searched under Code Aurora git repositories  .

Where are now NXP forks of Open Source u-boot ?  They should be Open Source. In particular we need for our NXP T2080 Power Architecture Open Hardware Notebook Design


0 Kudos
Contributor I

You've moved one minor repo, master branch and no sdk branches to github, and deleted an actively used server.

It might be better if you restored, removed your linux-firmware repo, and duplicated it on github NXP.

There are literally hundreds of repos on

We are in the middle of going to production, and this reflects days of work recreating for just our needs.

Many other products and SDK's are broken with no way to recover the correct content. Multiple versions are buried in tar files, and extracting the complete version history is at best a guess.

For c293 we need these 93 repos, along with recipe updates. Safe to say all of qoriq is broken.

Could you please move these to github NXP and update the recipe files?

meta-cyphre-c29x/scripts/fsl-setup-env:SOURCE_MIRROR_URL ?= ""
meta-cgl/meta-cgl-fsl-ppc/recipes-kernel/linux/ += "git://;nobranch=1 \
meta-nxp-npi-1703/recipes-bsp/rcw/ls2-rcw_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-bsp/rcw/rcw_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-bsp/u-boot/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-bsp/pkc-firmware/pkc-firmware_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-bsp/ppa/ppa_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-bsp/ppfe-firmware/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa/fm-ucode/fm-ucode_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa/usdpaa-apps/usdpaa-apps_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa/fmc/fmc_git.bbappend:SRC_URI = "git://;branch=sdk-v2.0.x"
meta-nxp-npi-1703/recipes-dpaa/usdpaa/usdpaa_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-binary/satrace/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-kernel/scatter-gather/scatter-gather_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-kernel/linux/linux-qoriq_4.1.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-kernel/pkc-host/pkc-host_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/.git/config:    url = git://
meta-nxp-npi-1703/recipes-devtools/qemu/qemu_qoriq.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-devtools/cst/cst_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-extended/dpdk/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-extended/dpdk/ = "git://;nobranch=1 \
meta-nxp-npi-1703/recipes-extended/odp/;nobranch=1 \
meta-nxp-npi-1703/recipes-extended/odp/;nobranch=1;name=qbman;destsuffix=git/platform/linux-dpaa2/flib/qbman \
meta-nxp-npi-1703/recipes-extended/odp/;nobranch=1;name=rta;destsuffix=git/platform/linux-dpaa2/flib/rta \
meta-nxp-npi-1703/recipes-extended/skmm-ep/ = "git://;nobranch=1 \
meta-nxp-npi-1703/recipes-extended/skmm-ep/skmm-ep_git.bbappend:SRC_URI = "git://;nobranch=1 \
meta-nxp-npi-1703/recipes-extended/ovs-dpdk/ = "git://;nobranch=1"
meta-nxp-npi-1703/README:4. $ git clone git:// -b jethro-sdk-v2.0-ga-1703 meta-nxp-npi-ga
meta-nxp-npi-1703/recipes-dpaa2/gpp-aioptool/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa2/dpl-examples/dpl-examples_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa2/aiopsl/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa2/restool/restool_git.bbappend:SRC_URI = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa2/mc/ = "git://;nobranch=1"
meta-nxp-npi-1703/recipes-dpaa2/dce/ = "git://;nobranch=1"
meta-freescale/recipes-bsp/apptrk/ = "git://;branch=sdk-v2.0.x \
meta-freescale/recipes-bsp/flash-image/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/qe-ucode/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/rcw/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/rcw/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/u-boot/ = "git://;branch=${SRCBRANCH}"
meta-freescale/recipes-bsp/u-boot/ = "git://;protocol=git;branch=${SRCBRANCH}"
meta-freescale/recipes-bsp/u-boot/ = "git://;branch=${SRCBRANCH} \
meta-freescale/recipes-bsp/ls2-phy/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/pkc-firmware/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-bsp/ppa/ = "git://;branch=sdk-v2.0.x \
meta-freescale/recipes-bsp/fsl-tlu/ = "git://;branch=master"
meta-freescale/recipes-bsp/boot-format/ = "git://;nobranch=1 \
meta-freescale/scripts/fsl-setup-env:SOURCE_MIRROR_URL ?= ""
meta-freescale/recipes-dpaa/flib/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/fm-ucode/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/eth-config/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/dpa-offload/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/usdpaa-apps/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/fmc/ = "git://;branch=sdk-v1.9.x"
meta-freescale/recipes-dpaa/usdpaa/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa/fmlib/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/scatter-gather/ = "git://;branch=master"
meta-freescale/recipes-kernel/ceetm/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/ls-debug/ = "git://;branch=master"
meta-freescale/recipes-kernel/ar/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/uio-seville/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/skmm-host/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/linux/ = "git://;branch=${SRCBRANCH} \
meta-freescale/recipes-kernel/linux/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/asf/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-kernel/perf-qoriq/ = "git://;branch=master"
meta-freescale/recipes-kernel/pkc-host/ = "git://;branch=sdk-v2.0.x"
meta-freescale/conf/layer.conf:QORIQ_MIRROR ?= ""
meta-freescale/.git/config:    url = git://
meta-freescale/recipes-virtualization/hypervisor/    git://;name=hypervisor;branch=sdk-v2.0.x \
meta-freescale/recipes-virtualization/hypervisor/    git://;name=kconfig;destsuffix=git/kconfig;branch=sdk-v2.0.x \
meta-freescale/recipes-virtualization/hypervisor/    git://;name=libos;destsuffix=git/libos;branch=sdk-v2.0.x \
meta-freescale/recipes-virtualization/hypervisor/    git://;name=hypertrk;destsuffix=git/hypertrk;branch=sdk-v2.0.x \
meta-freescale/recipes-virtualization/hv-cfg/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-virtualization/mux-server/ = "git://;branch=master"
meta-freescale/SCR/imx/SCR-3.14.38-6QP_ga.txt:Release Location: branch imx_3.14.38_6qp_ga
meta-freescale/SCR/imx/SCR-3.14.38-6QP_ga.txt:Release Location: branch imx_v2015.04_3.14.38_6qp_ga
meta-freescale/SCR/imx/SCR-3.14.38-6UL_ga.txt:Release Location: branch imx_3.14.38_6ul_ga
meta-freescale/SCR/imx/SCR-3.14.38-6UL_ga.txt:Release Location: branch imx_v2015.04_3.14.38_6ul_ga
meta-freescale/recipes-devtools/gdb/ = ""
meta-freescale/recipes-devtools/qemu/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-devtools/cst/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/hyperrelay/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/ipc-ust/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/web-sysmon/ = "git://;nobranch=1"
meta-freescale/recipes-extended/cantest/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/skmm-ep/ = "git://;branch=sdk-v2.0.x \
meta-freescale/recipes-extended/fsl-pme/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/libppc/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-extended/pme-tools/ = "git://;branch=sdk-v2.0.x \
meta-freescale/recipes-dpaa2/dpl-examples/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa2/restool/ = "git://;branch=sdk-v2.0.x"
meta-freescale/recipes-dpaa2/mc/ = "git://;branch=sdk-v2.0.x"

0 Kudos
Contributor I

Is this ever going to come back online?

Why would a major corporation alienate their current and potential future customers by shutting down a simple git repository?

If you have to ask, I'm essentially looking for the same repository as the previous poster, which I don't see a response to, but, I assume you have the original set of repositories, so I don't understand why you can't just bring them all back online, even if it's at another URL.

0 Kudos
NXP TechSupport
NXP TechSupport

Hello Brian Webb,

My apologies for the inconveniences caused by this change.

There are no plans to bring back online, all content was migrated to either one of these repositories:

It’s cumbersome, but please try changing the repositories as George Refseth to work around this issue.


Contributor IV

Hi gusarambula

It has some fail to download  (base on krogoth_4.1.y")  (4.1.15_2.1.0 BSP)

I had build code in Y2018.

I upload to GDriver

firmware-imx.tar.bz2 - Google Drive 

firmware-imx include more bin file.

BRCM , VPU , EPD , SDMA bin file

You can see firmware-imx/1_5.4-r0/deploy-rpms/cortexa7hf_neon_mx6ul file name list


0 Kudos
Contributor I

Could you at least replace the page with something that informs people of the new locations of the repositories?

Like it or not, your git repository is used all over the place, even in printed literature. Unless you're going out of business I just can't imagine why you would shut it down.

0 Kudos
Contributor II

In our case, we needed to migrate the meta-fsl-bsp-release repository within our submodule. Once we replaced this, all recursive submodules also worked.

[submodule "meta-fsl-bsp-release"]
 path = sources/meta-fsl-bsp-release
- url = git://
+ url =

As an aside, this was a forced migration that we and our partners/customers are not happy about. 

0 Kudos
Contributor II

Even after migrating the submodule repository, we still have a major issue. There are a lot of recipes which still rely entirely on the repository to function. All of these recipes will need to change in the new repositories to reflect that is no longer up.

user@facb926d01b2:~/src/fsl-release-bsp$ grep -rin '' --include=*.bb
sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-bsp/firmware-imx/ ?= "git://;protocol=git"
sources/meta-freescale/recipes-kernel/kernel-modules/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-kernel/kernel-modules/ = "git://;branch=master"
sources/meta-freescale/recipes-kernel/kernel-modules/ = "git://;branch=master"
sources/meta-freescale/recipes-kernel/kernel-modules/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-kernel/kernel-modules/ = "git://;branch=master"
sources/meta-freescale/recipes-kernel/ceetm/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-kernel/pkc-host/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-kernel/linux/ = "git://;nobranch=1 \
sources/meta-freescale/recipes-kernel/skmm-host/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/dynamic-layers/networking-layer/recipes-kernel/asf/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/dynamic-layers/openembedded-layer/recipes-support/web-sysmon/ = "git://;nobranch=1"
sources/meta-freescale/dynamic-layers/openembedded-layer/recipes-dpaa/fmc/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/dynamic-layers/openembedded-layer/recipes-dpaa/usdpaa-apps/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-devtools/qemu/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-devtools/cst/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-extended/pme-tools/ = "git://;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-extended/fsl-pme/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-extended/skmm-ep/ = "git://;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-extended/hyperrelay/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-extended/ipc-ust/ = "git://;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-extended/cantest/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa2/management-complex/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa2/restool/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa2/dpl-examples/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/pkc-firmware/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/fsl-tlu/ = "git://;branch=master"
sources/meta-freescale/recipes-bsp/ppa/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/u-boot/ = "git://;nobranch=1 \
sources/meta-freescale/recipes-bsp/u-boot/ = "git://;protocol=git;branch=${SRCBRANCH}"
sources/meta-freescale/recipes-bsp/boot-format/ = "git://;nobranch=1 \
sources/meta-freescale/recipes-bsp/ls2-phy/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/qe-ucode/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/apptrk/ = "git://;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-bsp/rcw/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-bsp/rcw/ = "git://;nobranch=1"
sources/meta-freescale/recipes-virtualization/hypervisor/ git://;name=hypervisor;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-virtualization/hypervisor/ git://;name=kconfig;destsuffix=git/kconfig;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-virtualization/hypervisor/ git://;name=libos;destsuffix=git/libos;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-virtualization/hypervisor/ git://;name=hypertrk;destsuffix=git/hypertrk;branch=sdk-v2.0.x \
sources/meta-freescale/recipes-virtualization/hv-cfg/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-virtualization/mux-server/ = "git://;branch=master \
sources/meta-freescale/recipes-dpaa/eth-config/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa/fm-ucode/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa/dpa-offload/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa/fmlib/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa/flib/ = "git://;branch=sdk-v2.0.x"
sources/meta-freescale/recipes-dpaa/usdpaa/ = "git://;branch=sdk-v2.0.x"

gusarambula At this point, we are very frustrated with this forced migration and need to come back up so we and our partners can continue operating. This is affecting every NXP customer using i.MX chips. This is completely unacceptable business practices.

Contributor I

Having a similar problem while building a release for Compulab CL-SOM-iMX6:

repo init -u git:// -b imx-morty -m imx-4.1.33-7ulp_beta.xml


Downloading manifest from git://
fatal: unable to connect to[0:]: errno=Connection refused

- Dave


0 Kudos
Contributor I

We are using git://, and can't see that it can be replaced by git://, please elaborate.

<project remote="fsl-release" name="meta-fsl-bsp-release" path="sources/meta-fsl-bsp-release" revision="jethro_4.1.15-1.0.0_ga" >

0 Kudos
Contributor I


<remote fetch="git://" name="fsl-release" />

to this

 <remote fetch="" name="fsl-release" />

In our repo manifest and using the codeaurora mirror fixed our problems.

Best regards,

NXP TechSupport
NXP TechSupport

Hello George,

Thank you for posting this workaround. I'm sure it will help many Community Users.

As reference, the content from the freescale.git repository were moved to the following repositories:

So it may happen that a specific recipe requires one of the two first repositories as well.


0 Kudos
NXP TechSupport
NXP TechSupport

Hello Adam Bader, Diego Perez, and Alex Movitz, 

The git:// repository was replaced by git://

Some recipes may still refer to the old repository so please replace them on the recipes where you are experiencing issues.


View solution in original post

0 Kudos
Contributor II

Hi gusarambula,

Could you pls get the updated link for this from NXP.

IMX_MIRROR ?=      <- Obsolete link


0 Kudos
Contributor I

It does not appear that everything from the git:// repository was properly migrated to git:// (or any other repo I see under user NXP), as now I'm getting the following build errors:

ERROR: linux-compulab-4.1.15-r0 do_fetch: Fetcher failure: Unable to resolve 'rel_imx_4.1.15_1.2.0_ga' in upstream git repository in git ls-remote output for
ERROR: linux-compulab-4.1.15-r0 do_fetch: Function failed: base_do_fetch

The original repo, now unavailable, I believe was pulled from git://
The current failure, however, is failing to pull what was previously housed in git://

Can you assist? This is blocking all new builds, which means new releases for our customers.



0 Kudos
NXP TechSupport
NXP TechSupport

Hello Whitaker,

My apologies. Most of what was on should be now on have you tried with this repository (instead of the imx-firmware)?

And also, which BSP Release are you using? That would help us see which recipes seem affected. If you have not sync the repos in a while it could help to sync them as some recipes might have been updated.


0 Kudos