AnsweredAssumed Answered

Explain fetching packages and compressed files from NXP & how to mirror for SDK 2.0

Question asked by pro-supportengineer Employee on Dec 19, 2016

For NXP SDK 2.0/1609/1611 there are numerous packages and compressed files downloaded from various NXP mirrors. Below is only one of many examples.  If a REVSRC between updates changes, as it will, then a previous update will break the bitbake when attempting to fetch from an updated NXP mirror with a new source revision  This failure is seen with 1609 because NXP has moved the NXP repository to 1611 changing source revision keys.  This means the bitbakes will continually be breaking every time customer's try to use a previous version and have not upgraded to the latest version.  The merge process may take time preventing a quick move to the latest update and in the mean time, bitbake will break.

 

Customers are requesting how they can create a repository independent of the NXP fetch process in the NXP bitbake recipes without changes all of the recipes that do fetches.

 

1) For instance, if customers use the downloads directory in SDK 2.0/1609 and the sources directory and place these in their own repo, will this prevent bitbake recipes from fetching additional compressed files? Or, will this break the bitbake and not prevent attempts to fetch?

 

2) The bitbake and any fetches will extract first from the downloads directory, and if the compressed file or packages is found, it will avoid attempting to do a fetch?

 

3) What if the cache directory is used, will this avoid fetches from the NXP site?

 

4) When a customer needs to create a repo independent of NXP mirror sites, what is the recommended process for doing so?

 

5) After answering the above questions, pease explain the fetch process for customers.  Where and when do all the fetches occur?  Please provide a document and explanation of the fetch process so customers so they can create an independent repo without fetching from NXP when needed for each update/release.  The yocto recipes have been modified specifically to fetch from NXP sites, so NXP documentation is needed to clarify this.

 

 

build_ls1043ardb/tmp/work/x86_64-linux/gnu-config-native/20150728+gitAUTOINC+b576fa87c1-r0/temp/

 

 

log.do_fetch.9910|25 col 8| DEBUG: Fetcher accessed the network with the command /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/neo/git/neo_mcu_eos-qoriq_v2_sources/downloads 'http://git.freescale.com/source/beecrypt-4.2.1.tar.gz'
log.do_fetch.9916|25 col 8| DEBUG: Fetcher accessed the network with the command /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/neo/git/neo_mcu_eos-qoriq_v2_sources/downloads 'http://git.freescale.com/source/psmisc-22.21.tar.gz'
log.do_fetch.9924|25 col 8| DEBUG: Fetcher accessed the network with the command /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/neo/git/neo_mcu_eos-qoriq_v2_sources/downloads 'http://git.freescale.com/source/strace-4.10.tar.xz'
log.do_fetch.994|25 col 8| DEBUG: Fetcher accessed the network with the command /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/neo/git/neo_mcu_eos-qoriq_v2_sources/downloads 'http://git.freescale.com/source/git2_github.com.Sirupsen.logrus.git.tar.gz'
log.do_fetch.994|28 col 8| DEBUG: Fetcher failure: Fetch command failed with exit code 8, output:
log.do_fetch.994|33 col 8| DEBUG: Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/Sirupsen/logrus.git /home/neo/git/neo_mcu_eos-qoriq_v2_sources/downloads/git2/github.com.Sirupsen.logrus.git

Outcomes