https://source.codeaurora.org/external/autobsps32/extra/ can't acess

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

https://source.codeaurora.org/external/autobsps32/extra/ can't acess

1,144 Views
WenChao
Contributor II

Hi:

  Git clone https://source.codeaurora.org/external/autobsps32/extra/  failed, I can't open the link, could you help me with it?

0 Kudos
6 Replies

1,120 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

There is a migration on going from Code Aurora to GitHub, hence Code Aurora links are not working. One of our coworkers has posted a solution for a similar problem, thread below:

git://source.codeaurora.org/external/autobsps32/li... - NXP Community

Please, let us know if this information was helpful or not.

0 Kudos

1,100 Views
WenChao
Contributor II

thank You very much, I have done the two steps and succeed.

 repo init -u https://github.com/nxp-auto-linux/auto_yocto_bsp -b release/bsp35.0
 repo sync 

but when I (1)./sources/meta-alb/scripts/host-prepare.sh  √  (2)source nxp-setup-alb.sh -m s32r45evb √

(3)bitbake fsl-image-base  there is an error. ×    I check there is no file in mete-security.

 

 

0 Kudos

1,082 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Did you had any errors when doing the "repo sync" command? Can you share with us the whole command log that you are doing?

Also, we will provide the GitHub page for BSP35, which seems to be already updated with the new links. Help us verify if there was additional steps missing on your setup.

GitHub - nxp-auto-linux/auto_yocto_bsp at release/bsp35.0

Please, let us know.

0 Kudos

1,069 Views
WenChao
Contributor II

I check  repo GitHub - nxp-auto-linux/auto_yocto_bsp at release/bsp35.0 ,

when I tried to repo sync many times, it still can't git  sources/meta-freescale
sources/meta-security source codes. could you help me with it? 

LOG :

repo init -u https://github.com/nxp-auto-linux/auto_yocto_bsp -b release/bsp35.0
repo sync

fatal: unable to access 'https://github.com/nxp-auto-linux/auto_yocto_bsp/': Operation timed out after 300040 milliseconds with 0 out of 0 bytes received
manifests: sleeping 4.0 seconds before retrying
fatal: unable to access 'https://github.com/nxp-auto-linux/auto_yocto_bsp/': Failed to connect to github.com port 443: Connection refused
Fetching: 55% (5/9) Last synced: meta-linaro
fatal: unable to access 'https://github.com/nxp-auto-linux/meta-alb/': Failed to connect to github.com port 443: Connection refused

meta-alb:
fatal: unable to access 'https://github.com/nxp-auto-linux/meta-alb/': Failed to connect to github.com port 443: Connection refused
meta-alb: sleeping 4.0 seconds before retrying
fatal: unable to access 'https://github.com/nxp-auto-linux/meta-alb/': Failed to connect to github.com port 443: Connection refused

meta-alb:
fatal: unable to access 'https://github.com/nxp-auto-linux/meta-alb/': Failed to connect to github.com port 443: Connection refused
error: Cannot fetch meta-alb from https://github.com/nxp-auto-linux/meta-alb
Fetching: 100% (9/9), done in 3m12.064s
Fetching: 100% (1/1), done in 1.006s
fatal: this operation must be run in a work tree
error.GitError: Cannot checkout meta-freescale: Cannot initialize work tree for meta-freescale
error: Cannot checkout meta-freescale
fatal: this operation must be run in a work tree
error.GitError: Cannot checkout meta-security: Cannot initialize work tree for meta-security
error: Cannot checkout meta-security

error: Unable to fully sync the tree.
error: Downloading network changes failed.
error: Checking out local projects failed.
Failing repos:
sources/meta-freescale
sources/meta-security

 

 

0 Kudos

1,057 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

This seems to be related to a proxy connection. Are you behind a proxy? We had these problems ourselves due to the company proxy, and we needed to use VM's to be able to fetch the sources.

How is your current setup?

Please, let us know.

0 Kudos

1,047 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

We have also received the following comment from our internal team:

"Can they "git clone" just the repositories that are failing for repo sync? Wherever they want to do the "git clone" command, just to confirm there is no problem on the repository itself."

Please, let us know.

0 Kudos