I am facing this issue now.
USING REPO INIT:
repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth
manifests:
fatal: unable to connect to git.freescale.com:
git.freescale.com[0: 192.88.156.202]: errno=Connection refused
Is there an issue with the server? I am facing this issue from 29/02/2020.
I'm having troubles cloning linux-imx specifically imx_4.1.15_2.0.0_ga.
Running bitbake I get:
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
ERROR: linux-imx-4.1.15-r0 do_fetch: Function failed: Fetcher failure for URL: 'git://git.freescale.com/imx/linux-imx.git;protocol=git;branch=imx_4.1.15_2.0.0_ga'. Unable to fetch URL from any source.
after some time or:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
ERROR: linux-imx-4.1.15-r0 do_fetch: Function failed: Fetcher failure for URL: 'git://git.freescale.com/imx/linux-imx.git;protocol=git;branch=imx_4.1.15_2.0.0_ga'. Unable to fetch URL from any source.
when it fails immediately.
Cloning manually also fails with either early end of file or could not read.
Didn't work yesterday either, but used to last week.
U-Boot do_fetch() completed on the second attempt.
Cloning from Github works fine so I guess the freescale repository is having hickups again.
(A Mirror would be great for this case)
Today having the same problem.
Because this is a re-occurring issue a mirror would very helpful.
Hi, we are working internally to get this resolved. The GIT managers are aware of the issue and we are working to find the root cause and solution. In the meantime, you can navigate to the GIT website and download packages from there. We hope to have it resolved soon.
I think the following git clone used to work, but not anymore...
$ git clone git://git.freescale.com/ppc/sdk/usdpaa/usdpaa-apps.git
Cloning into 'usdpaa-apps'...
fatal: unable to connect to git.freescale.com:
git.freescale.com[0: 192.88.156.202]: errno=Connection refused
Any replys from NXP? Are they aware of the issue?
I've not seen any responses from NXP.
How do we prompt them?
Also getting either connection refused or timeout
That could be what I'm seeing as well!