Project

General

Profile

Yocto MDK Status

Added by Tom Riddle 12 months ago

Ok, looks like it may be the appropriate time for us here to cut over to the Yocto MDK. We've been on the MDK_2014-01-13 but the filesystem limitations are starting to hold us back. We've done a significant amount of kernel work integrating in a new codec and want to make sure we pull that work forward properly. Are there any instructions that I can follow to get started? Thanks Tom


Replies (27)

RE: Yocto MDK Status - Added by Bob Duke 12 months ago

Hi Tom,

We've released some Yocto-based MDKs under the Files tab. The latest is 2018.04. We don't have full documentation for creating your own Yocto-based MDK yet.

The README file listed with the 2018.04 release has a link to the source code and build scripts used to build the MDK. You can change the location of the kernel repository to point to your custom version.

That said, if you haven't used Yocto before, this is easier said than done. A good first step would be to try the 2018.04 MDK by copying over your kernel manually. This will allow you to verify there are no other software/filesystem problems. Then, you can work on getting your own Yocto build in place if you desire.

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

Hi Bob, Thanks, BTW, what version of Ubuntu are you hosting the 2018.04 Yocto-based MDK on? Regs, Tom

RE: Yocto MDK Status - Added by Jonathan Cormier 12 months ago

It was built on Ubuntu 16.04

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

Hi,

So I've been using the following kernel and have a number of changes.

On branch mitydsp-linux-v3.2

According to the git log this was the last commit

commit ce5d9bb2f9a2405a6321e3603e0c5dcaf9f47d6b
Author: Gregory Gluszek <>
Date: Fri Nov 17 11:22:27 2017 -0500

HFM: Chanages to get CAN to work.
Pinmux issues were causing CAN not to probe properly.
Also defconfig had some out of date configurations.

I'm wondering where to go to stay in sync with your latest kernel version, is this the git repo I should be monitoring?

https://support.criticallink.com/gitweb/?p=linux-davinci.git;a=summary

RE: Yocto MDK Status - Added by Gregory Gluszek 12 months ago

Hi Tom,

The 3.2 branch you are following is the one to track for our latest updates for the L138 platform.

Thanks,
\Greg

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

Hi,

I pulled over my kernel sources and it builds. Next I am attempting to build some of the 2018 MDK examples. Running into things like ${MDK} was not set, path issues, etc. So beyond installing the MDK and sourcing this file (below), is there any other steps to building the examples?

environment-setup-arm926ejste-criticallink-linux-gnueabi

For example after manually exporting ${MDK}, mmap example built

mdkextrafiles/examples/mmap_demo/

Next went to build in the ARM dir

mdkextrafiles/examples/DspHelloWorld/ARM$

Had to start tweaking the includes in the Makefile to find things like dspapp.h, etc

perhaps I have missed a step somewhere or is this normal to have to dig into the Makefiles and modify?

Thanks, Tom

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

Following up here... I basically had to update the CC assignment in the Makefile so it could find --sysroot, now it builds correctly. Are these Makefile mods expected or have I missed an MDK setup step somewhere? Please advise, thanks

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

I have successfully built Yocto core, however when I try to build meta-criticallink I get the following error. Any help would be appreciated.

======
rurisond@skyskip-minidell:/export/software/mitydsp/sources/poky/yocto-archive$ bitbake meta-criticallink
WARNING: Layer criticallink should set LAYERSERIES_COMPAT_criticallink in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer criticallink should set LAYERSERIES_COMPAT_criticallink in its conf/layer.conf file to list the core layer names it is compatible with.
ERROR: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-ti/cl-dsplink/cl-dsplink.bb: Error executing a python function in : | ETA: --:--:-- The stack trace of python calls that resulted in this exception/failure was: File: '<code>', lineno: 2, function: <module> 0001:__anon_25__export_software_mitydsp_sources_poky_meta_classes_patch_bbclass(d) *** 0002:__anon_681__export_software_mitydsp_sources_poky_meta_classes_base_bbclass(d) 0003:__anon_1317__export_software_mitydsp_sources_poky_meta_classes_insane_bbclass(d) 0004:__anon_251__export_software_mitydsp_sources_poky_meta_classes_package_bbclass(d) 0005:__anon_718__export_software_mitydsp_sources_poky_meta_classes_package_rpm_bbclass(d) 0006:__anon_25__export_software_mitydsp_sources_poky_meta_classes_debian_bbclass(d) File: '/export/software/mitydsp/sources/poky/meta/classes/base.bbclass', lineno: 578, function: __anon_681__export_software_mitydsp_sources_poky_meta_classes_base_bbclass 0574: needsrcrev = False 0575: srcuri = d.getVar('SRC_URI') 0576: for uri in srcuri.split(): 0577: (scheme, _ , path) = bb.fetch.decodeurl(uri)[:3] *** 0578: 0579: # HTTP/FTP use the wget fetcher 0580: if scheme in ("http", "https", "ftp"): 0581: d.appendVarFlag('do_fetch', 'depends', ' wget-native:do_populate_sysroot') 0582: File: '/export/software/mitydsp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 368, function: decodeurl 0364: """ 0365: 0366: m = re.compile('(?P<type>[^:]*)://((?P<user>[^/;]+)@)?(?P<location>[^;]+)(;(?P<parm>.*))?').match(url) 0367: if not m: *** 0368: raise MalformedUrl(url) 0369: 0370: type = m.group('type') 0371: location = m.group('location') 0372: if not location: Exception: bb.fetch2.MalformedUrl: The URL: '${CL_SOURCE_GIT_HOST}${CL_SOURCE_GIT_PATH}mitydsp-l138-dsplink.git;protocol=git;branch=master;destsuffix=/export/software/mitydsp/sources/poky/build/tmp/work/qemux86-poky-linux/cl-dsplink/1.0-r0/dsplink' is invalid and cannot be interpreted WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.2.1.bb: Exception during build_dependencies for do_configure WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.2.1.bb: Error during finalise of /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.2.1.bb WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_svn.bb: Exception during build_dependencies for do_configure WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_svn.bb: Error during finalise of /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_svn.bb WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.1.bb: Exception during build_dependencies for do_configure WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.1.bb: Error during finalise of /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.4.1.bb ERROR: Failed to parse recipe: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-ti/cl-dsplink/cl-dsplink.bb WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.1.2.bb: Exception during build_dependencies for do_configure WARNING: /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.1.2.bb: Error during finalise of /export/software/mitydsp/sources/poky/yocto-archive/meta-criticallink/recipes-net/net-snmp/net-snmp_5.1.2.bb Summary: There were 10 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

RE: Yocto MDK Status - Added by Aidan Klein 12 months ago

Hi Tom,

From your error message it looks like CL_SOURCE_GIT_HOST and CL_SOURCE_GIT_PATH aren't defined. These variables are defined in Critical Link's Yocto distro, cl-systemd.

Since you're building for the MityDSP-L138 you should checkout the meta-mitydsp-l138 layer. This layer contains recipes specific to the MityDSP-L138. The layer can be found on CL's support site: https://support.criticallink.com/gitweb/?p=meta-mitydsp-l138.git

This layer provides configuration files for bitbake. These files are found at: meta-mitydsp-l138/conf/machine/local.conf.sample and meta-mitydsp-l138/conf/machine/bblayer.conf.sample. Back up your build's config files, conf/local.conf and conf/bblayers.conf, and then copy the sample config files over your build's config files.
These will configure your build to use the cl-systemd distribution.

The L138's root file system can then be built with:

bitbake mitydsp-l138-image

RE: Yocto MDK Status - Added by Tom Riddle 12 months ago

Thanks, Aidan. that's helpful. I still had a number of errors, but they may be related to other items here that are not setup properly.

So I'd like to ask a few general setup questions, following the general yocto install instructions, I did this

git clone git://git.yoctoproject.org/poky

git checkout tags/yocto-2.5 -b my-yocto-2.5

and built "core-image-minimal" successfully, then moved onto bringing in the yocto-archive,

How I did that "may or may not be correct"? Just extracting the "yocto-archive" mitydsp-l138-yocto-archive-2018-04-13.tar.xz by itself and sourcing oe-init-build-env from that sees it complain that there is no ".templateconf" file. If I bring "yocto-archive" into poky and modify the conf files as you directed, then it initially complained about

ERROR: Layer yocto is not compatible with the core layer which only supports these series: (layer is compatible with sumo)

That lead me to do an additional bringover of the layers.conf file, but ran into other errors. Anyway I just want to make sure I'm starting with the right checkout and/or the right approach. Hope this makes sense, Tom

Let me know what the "yocto-archive" should be using and I'll give it another shot. Thanks, Tom

RE: Yocto MDK Status - Added by Aidan Klein 12 months ago

The yocto-archive contains all of the necessary files to build the MDK (with the exception of the missing file).

I'm working on adding the .templateconf to the archive for future releases. In the mean time, the contents of the file are:

# Template settings
TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf}

The 2018 MDK build will require some older versions of libraries. I've found that the MDK should be built under a Ubuntu 14.04 environment with Yocto's required packages installed.

The provided MDK examples were re-used from an older non-Yocto based MDK. The build process has changed a bit with the Yocto MDK. I'm looking into this issue.

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi, So in the building of the yocto-archive it seems to get pretty far until these errors appear

ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to connect to wanda.syr.criticallink.com:
wanda.syr.criticallink.com[0: 72.90.70.109]: errno=Connection timed out

Is this the correct URL?

Thanks, Tom

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Ok, Will try again... hope I can get an answer to the network question... it appears to fail at trying to fetch the following

Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-mitydsp-l138/recipes-bsp/fpga-drivers/fpga-driver-modules.bb, do_fetch
/export/software/L138/yocto-archive/meta-criticallink/recipes-ti/cl-dsplink/cl-dsplink.bb, do_fetch
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

The same network error

fatal: unable to connect to wanda.syr.criticallink.com:

Complete log below =========
openbts@harlan:/export/software/L138/yocto-archive/build$ bitbake mitydsp-l138-image
Loading cache: 100% |################################################################################################################################| ETA: 00:00:00
Loaded 2015 entries from dependency cache.
Parsing recipes: 100% |##############################################################################################################################| Time: 00:00:02
Parsing of 1595 .bb files complete (1580 cached, 15 parsed). 2029 targets, 155 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.22.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-criticallink-linux-gnueabi"
MACHINE = "mityomapl138"
DISTRO = "cl-systemd"
DISTRO_VERSION = "1.6.0"
TUNE_FEATURES = "armv5 thumb dsp arm926ejs"
TARGET_FPU = "soft"
meta-mitydsp-l138
meta-criticallink
meta-ti
meta-linaro-toolchain
meta-oe
meta-networking
toolchain-layer
meta
meta-yocto
meta-yocto-bsp = "<unknown>:<unknown>"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to connect to wanda.syr.criticallink.com:
wanda.syr.criticallink.com[0: 72.90.70.109]: errno=Connection timed out

ERROR: Logfile of failure stored in: /export/software/L138/yocto-archive/build/tmp/work/mityomapl138-criticallink-linux-gnueabi/fpga-driver-modules/1.0-r1/temp/log.do_fetch.24819
Log data follows: | DEBUG: Executing python function do_fetch | DEBUG: Executing python function base_do_fetch | DEBUG: Fetcher accessed the network with the command git ls-remote git://wanda.syr.criticallink.com/home/git/mitydsp-l138-fpga.git refs/heads/master refs/tags/master^{} | DEBUG: Running export SSH_AUTH_SOCK="/run/user/1001/keyring-qDTJF0/ssh"; export PATH="/export/software/L138/yocto-archive/scripts:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/bin/arm926ejste-criticallink-linux-gnueabi:/export/software/L138/yocto-archive/build/tmp/sysroots/mityomapl138/usr/bin/crossscripts:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/sbin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/bin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/sbin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/bin:/export/software/L138/yocto-archive/scripts:/export/software/L138/yocto-archive/bitbake/bin:/var/lib/redhawk/core/bin:/usr/lib/jvm/java-7-openjdk-i386/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/export/rangenet/hardware/RNRAD3/firmware/arm-2011.03/bin:/export/rangenet/hardware/RNRAD3/firmware/cyfx3sdk/util/elf2img"; export HOME="/home/openbts"; git ls-remote git://wanda.syr.criticallink.com/home/git/mitydsp-l138-fpga.git refs/heads/master refs/tags/master^{} | DEBUG: Python function base_do_fetch finished | DEBUG: Python function do_fetch finished | ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output: | fatal: unable to connect to wanda.syr.criticallink.com: | wanda.syr.criticallink.com[0: 72.90.70.109]: errno=Connection timed out | |
ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to connect to wanda.syr.criticallink.com:
wanda.syr.criticallink.com[0: 72.90.70.109]: errno=Connection timed out

ERROR: Logfile of failure stored in: /export/software/L138/yocto-archive/build/tmp/work/mityomapl138-criticallink-linux-gnueabi/cl-dsplink/1.0-r0/temp/log.do_fetch.24820
Log data follows: | DEBUG: Executing python function do_fetch | DEBUG: Executing python function base_do_fetch | DEBUG: Fetcher accessed the network with the command git ls-remote git://wanda.syr.criticallink.com/home/git/mitydsp-l138-dsplink.git refs/heads/master refs/tags/master^{} | DEBUG: Running export SSH_AUTH_SOCK="/run/user/1001/keyring-qDTJF0/ssh"; export PATH="/export/software/L138/yocto-archive/scripts:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/bin/arm926ejste-criticallink-linux-gnueabi:/export/software/L138/yocto-archive/build/tmp/sysroots/mityomapl138/usr/bin/crossscripts:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/sbin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/usr/bin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/sbin:/export/software/L138/yocto-archive/build/tmp/sysroots/i686-linux/bin:/export/software/L138/yocto-archive/scripts:/export/software/L138/yocto-archive/bitbake/bin:/var/lib/redhawk/core/bin:/usr/lib/jvm/java-7-openjdk-i386/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/export/rangenet/hardware/RNRAD3/firmware/arm-2011.03/bin:/export/rangenet/hardware/RNRAD3/firmware/cyfx3sdk/util/elf2img"; export HOME="/home/openbts"; git ls-remote git://wanda.syr.criticallink.com/home/git/mitydsp-l138-dsplink.git refs/heads/master refs/tags/master^{} | DEBUG: Python function base_do_fetch finished | DEBUG: Python function do_fetch finished | ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output: | fatal: unable to connect to wanda.syr.criticallink.com: | wanda.syr.criticallink.com[0: 72.90.70.109]: errno=Connection timed out | |
ERROR: Task 1426 (/export/software/L138/yocto-archive/meta-mitydsp-l138/recipes-bsp/fpga-drivers/fpga-driver-modules.bb, do_fetch) failed with exit code '1'
ERROR: Task 1411 (/export/software/L138/yocto-archive/meta-criticallink/recipes-ti/cl-dsplink/cl-dsplink.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2519 tasks of which 2517 didn't need to be rerun and 2 failed.
Waiting for 0 running tasks to finish:

Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-mitydsp-l138/recipes-bsp/fpga-drivers/fpga-driver-modules.bb, do_fetch
/export/software/L138/yocto-archive/meta-criticallink/recipes-ti/cl-dsplink/cl-dsplink.bb, do_fetch
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

RE: Yocto MDK Status - Added by Jonathan Cormier 11 months ago

Thanks for the extra info. wanda.syr.criticallink.com is an internal server, CL_SOURCE_GIT_HOST should point to support.criticallink.com instead. Sorry about that.

meta-criticallink/conf/distro/cl-source.inc
1:CL_SOURCE_GIT_HOST ?= "git://support.criticallink.com" 
3:CL_SOURCE_GIT_HOST="git://wanda.syr.criticallink.com" 

This is set correctly in the git repo. But not in the source archive: mitydsp-l138-yocto-archive-2018-04-13.tar.xz

 $ git remote -v
origin    https://support.criticallink.com/git/meta-criticallink.git (fetch)
origin    https://support.criticallink.com/git/meta-criticallink.git (push)
 $ git branch
* daisy
 $ ag CL_SOURCE_GIT_HOST
conf/distro/cl-source.inc
1:CL_SOURCE_GIT_HOST ?= "git://support.criticallink.com" 

recipes-ti/cl-dsplink/cl-dsplink.bb
11:SRC_URI = "${CL_SOURCE_GIT_HOST}${CL_SOURCE_GIT_PATH}${CL_SOURCE_REPO};protocol=git;branch=${BRANCH};destsuffix=${S}" 

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi, thanks... suspected that was the case but didn't know where the setting was at. It successfully fetched and is moving on now.

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi, One last question... I built with "-k" to get past these two fetch errors,

Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-support/vim/vim_7.4.258.bb, do_fetch
/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-devtools/ltrace/ltrace_git.bb, do_fetch

see complete log below. Any suggestions on how to remedy this?

Thanks, Tom

==============

NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL hg://vim.googlecode.com/hg/;protocol=https;module=vim, attempting MIRRORS if available
WARNING: Failed to fetch URL git://anonscm.debian.org/collab-maint/ltrace.git, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 255, output:
warning: vim.googlecode.com certificate with fingerprint 1a:0d:d9:dd:e5:27:a6:f1:03:f1:fd:dc:63:fa:ee:65:7b:93:e0:65 not verified (check hostfingerprints or web.cacerts config setting)
abort: HTTP Error 404: Not Found

ERROR: Function failed: Fetcher failure for URL: 'hg://vim.googlecode.com/hg/;protocol=https;module=vim'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /export/software/L138/yocto-archive/build/tmp/work/arm926ejste-criticallink-linux-gnueabi/vim/7.4.258-r0/temp/log.do_fetch.4002
ERROR: Task 1066 (/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-support/vim/vim_7.4.258.bb, do_fetch) failed with exit code '1'
ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository '/export/software/L138/yocto-archive/build/downloads/git2/anonscm.debian.org.collab-maint.ltrace.git'...
fatal: unable to connect to anonscm.debian.org:
anonscm.debian.org[0: 194.177.211.202]: errno=Connection refused
anonscm.debian.org[1: 2001:648:2ffc:deb::211:202]: errno=Connection refused

ERROR: Function failed: Fetcher failure for URL: 'git://anonscm.debian.org/collab-maint/ltrace.git'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /export/software/L138/yocto-archive/build/tmp/work/arm926ejste-criticallink-linux-gnueabi/ltrace/1_7.2+gitAUTOINC+f44b284219-r0/temp/log.do_fetch.4001
ERROR: Task 1497 (/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-devtools/ltrace/ltrace_git.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4908 tasks of which 2833 didn't need to be rerun and 2 failed.
No currently running tasks (4907 of 4940)

Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-support/vim/vim_7.4.258.bb, do_fetch
/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-devtools/ltrace/ltrace_git.bb, do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There were 4 ERROR messages shown, returning a non-zero exit code.

RE: Yocto MDK Status - Added by Jonathan Cormier 11 months ago

It looks like the vim repo has been moved. googlecode.com is no longer a valid url. Looking at more recent vim recipes point to git://github.com/vim/vim.git.

Similarly the ltrace url isn't reachable. However the more recent recipes still reference this url so it might only be down temporarily.

 $ git clone git://anonscm.debian.org/collab-maint/ltrace.git
Cloning into 'ltrace'...
fatal: unable to connect to anonscm.debian.org:
anonscm.debian.org[0: 194.177.211.202]: errno=Connection refused
anonscm.debian.org[1: 2001:648:2ffc:deb::211:202]: errno=Network is unreachable

Note you can grab the sources from the source archive and should be able to put them in the correct location: https://support.criticallink.com/files/mitydspl138/mdksrc/mitydsp-l138-sources-archive-2018-04-13.tar.xz
Locations:
tmp/deploy/sources/arm-criticallink-linux-gnueabi/vim-7.4.258-r0/ -> downloads/
tmp/deploy/sources/arm-criticallink-linux-gnueabi/ltrace-1_7.2+gitAUTOINC+f44b284219-r0/ -> downloads/

you might also have to create .done files like the other files in the downloads folder.

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Thanks Jonathan I will give that a try, in the meantime there are a few other questions.

So we have a 3.2 kernel here with a moderate number of modifications that is based on the 2011 MDK kernel source. We can continue to build it separately, but it would be nice to integrate it with the latest Critical Link kernel and the Yocto MDK build process, what would be the preferred method?

I believe this is where the kernel sources end up at?

./tmp/work/mityomapl138-criticallink-linux-gnueabi/linux-davinci/3.2+gitAUTOINC+69ffdd9a2e-r0/linux/

Now that we have the yocto-archive built, where is the rootfs located at? Here is where I found u-boot, kernel uImage & modules.

tmp/deploy/images/mityomapl138/

thanks, Tom

RE: Yocto MDK Status - Added by Bob Duke 11 months ago

Tom Riddle wrote:

Thanks Jonathan I will give that a try, in the meantime there are a few other questions.

So we have a 3.2 kernel here with a moderate number of modifications that is based on the 2011 MDK kernel source. We can continue to build it separately, but it would be nice to integrate it with the latest Critical Link kernel and the Yocto MDK build process, what would be the preferred method?

Tom, if you have the Yocto build working, you can modify the kernel recipe in meta-mitydsp-l138 to point to your desired kernel: https://support.criticallink.com/gitweb/?p=meta-mitydsp-l138.git;a=blob;f=recipes-kernel/linux/linux-davinci_3.2.bb;h=095ea9f252aab6392b19a4ad7b6db4ec0895aefe;hb=refs/heads/daisy

Now that we have the yocto-archive built, where is the rootfs located at? Here is where I found u-boot, kernel uImage & modules.

tmp/deploy/images/mityomapl138/

There should be a tar.bz2 file in that directory that contains the rootfs.

-Bob

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi Bob, thanks for the quick response, I'll start playing with the recipe.

On the rootfs question, can't seem to find the file, see the dir listing below. Perhaps I need to build or execute something else? All I have done to date is

bitbake mitydsp-l138-image

Regs, Tom

openbts@harlan:/export/software/L138$ ls ltrh yocto-archive/build/tmp/deploy/images/mityomapl138/
total 3.5M
-rw-r--r-
2 openbts openbts 2.5M Aug 17 23:51 uImage--3.2+git0+69ffdd9a2e-r0.100-mityomapl138-20180818025807.bin
rw-rw-r- 2 openbts openbts 549K Aug 17 23:51 modules--3.2+git0+69ffdd9a2e-r0.100-mityomapl138-20180818025807.tgz
rw-rw-r- 2 openbts openbts 294 Aug 17 23:51 README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
lrwxrwxrwx 1 openbts openbts 66 Aug 17 23:51 uImage-mityomapl138.bin -> uImage--3.2+git0+69ffdd9a2e-r0.100-mityomapl138-20180818025807.bin
lrwxrwxrwx 1 openbts openbts 66 Aug 17 23:51 uImage -> uImage--3.2+git0+69ffdd9a2e-r0.100-mityomapl138-20180818025807.bin
lrwxrwxrwx 1 openbts openbts 67 Aug 17 23:51 modules-mityomapl138.tgz -> modules--3.2+git0+69ffdd9a2e-r0.100-mityomapl138-20180818025807.tgz
-rwxr-xr-x 2 openbts openbts 247K Aug 22 10:50 u-boot-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin
-rwxr-xr-x 2 openbts openbts 247K Aug 22 10:50 u-boot-ubl-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin
lrwxrwxrwx 1 openbts openbts 56 Aug 22 10:50 u-boot-ubl-mityomapl138.bin -> u-boot-ubl-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin
lrwxrwxrwx 1 openbts openbts 56 Aug 22 10:50 u-boot-ubl.bin -> u-boot-ubl-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin
lrwxrwxrwx 1 openbts openbts 52 Aug 22 10:50 u-boot-mityomapl138.bin -> u-boot-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin
lrwxrwxrwx 1 openbts openbts 52 Aug 22 10:50 u-boot.bin -> u-boot-mityomapl138-1.0+gitAUTOINC+7b1691407e-r0.bin

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi Folks... any feedback on where the image might be? Thanks, Tom

RE: Yocto MDK Status - Added by Jonathan Cormier 11 months ago

Could you provide a log of your bitbake command plus output in an attached file?

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi Jonathan,

We open a shell, go to yocto-archives dir, set the env

source oe-init-build-env

then execute

bitbake -k mitydsp-l138-image

to bypass the two repos that are not available. Please see the attached gzip file of the log. Let me know what else you need. Thanks, Tom

RE: Yocto MDK Status - Added by Jonathan Cormier 11 months ago

Tom Riddle wrote:

Hi Jonathan,

We open a shell, go to yocto-archives dir, set the env

source oe-init-build-env

then execute

bitbake -k mitydsp-l138-image

to bypass the two repos that are not available. Please see the attached gzip file of the log. Let me know what else you need. Thanks, Tom

       -k, --continue
              continue as much as possible after an error. While  the  target  that  failed,  and
              those  that depend on it, cannot be remade, the other dependencies of these targets
              can be processed all the same.

There is your problem, you have to solve the errors for the build to complete. All the -k option will do is give you a better chance of finding all the errors instead of having to fix one error at a time.

RE: Yocto MDK Status - Added by Tom Riddle 11 months ago

Hi, well it was easier then trying to fix the two repo failures, (which I will do)... just running bitbake again without the -k saw it succeed and now have the jffs image. Tom

(1-25/27)
Add picture from clipboard (Maximum size: 500 MB)