ConnectCore MP15: DEY setup snags

Embedded Devices
1

On a freshly setup Ubuntu 22.04.1 LTS system, going through the DEY setup steps for the CCMP15 devkit board. Hit a snag after making the docker, described below.

I have completed the prior steps for installing all the linux packages and that was easy.

Docker setup, I get up to 2.4.2:

https://www.digi.com/resources/documentation/digidocs/embedded/dey/4.0/ccmp15/yocto_t_set-up-docker-linux

At the repo sync command to update the repo inside the container, errors occur.

repo: reusing existing repo client checkout in /usr/local/dey-4.0
repo has been initialized in /usr/local/dey-4.0
dey@2957ac3f88ee:/usr/local/dey-4.0$ repo sync -j8
remote: Enumerating objects: 3, done.
remote: Counting objects: 100% (3/3), done.
remote: Total 3 (delta 1), reused 3 (delta 1), pack-reused 0
Fetching: 100% (14/14), done in 1m10.609s
.repo/repo: project not found in manifest.
NOT Garbage collecting: 0% (0/14), done in 0.005s
info: A new version of repo is available
warning: repo is not tracking a remote branch, so it will not receive updates
repo reset: error: Entry ‘.github/workflows/test-ci.yml’ not uptodate. Cannot merge.
fatal: Could not reset index file to revision ‘v2.31^0’.

I know P4, Git, SVN but this is my first time around the block with ‘repo’ so I am unclear on what state I am in now or how to unblock it.

I also noticed the “new version of repo is available” note, which is odd since I did the steps at section 2.4.1 to get it updated to latest.

repo version response (edited to un-trigger this forum’s “new users can only include two links” filter)

dey@2957ac3f88ee:/usr/local/dey-4.0$ repo --version
repo version v2.30
(tracking refs/heads/stable)
(Wed, 16 Nov 2022 18:26:49 +0000)
repo launcher version 2.30
(from /usr/local/bin/repo)
(currently at 2.30)
repo User-Agent git-repo/2.30 (Linux) git/2.34.1 Python/3.10.6
git 2.34.1
git User-Agent git/2.34.1 (Linux) git-repo/2.30
Python 3.10.6 (main, Nov 2 2022, 18:53:38) [GCC 11.3.0]
OS Linux 5.15.0-60-generic (#66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023)
CPU x86_64 (x86_64)

Should I skate past this update problem and try to build a project for the MP15 devkit board ? Or might it be better to nuke the /usr/local/dey-4.0 dir in the container and just check out a clean copy?

2

I made some progress: I deleted everything under /usr/local/dey-4.0 and re-inited the repo there

repo init -u GitHub - digi-embedded/dey-manifest: Digi Embedded for Yocto manifest -b kirkstone

Now I have this bitbake running:

bitbake dey-image-qt

So it seems that whatever state the original docker image is in, is not friendly to updating the repo, but it has no problem checking out a clean copy. (Or I misunderstand what repo commands should be doable in the base docker, entirely possible as I am repo newb)

Build Configuration:
BB_VERSION = “2.0.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “ubuntu-22.04”
TARGET_SYS = “arm-dey-linux-gnueabi”
MACHINE = “ccmp15-dvk”
DISTRO = “dey”
DISTRO_VERSION = “4.0-r1”
TUNE_FEATURES = “arm vfp cortexa7 neon vfpv4 thumb callconvention-hard”
TARGET_FPU = “hard”
meta
meta-poky
meta-yocto-bsp = “HEAD:86e9630511321530ba6f19ebedbaebad1a89a89f”
meta-oe
meta-python
meta-networking
meta-webserver = “HEAD:278ec081a64e6a7679d6def550101158126cd935”
meta-qt5 = “HEAD:44d44933200287f7d17cf6981af4b4a0961c308d”
meta-swupdate = “HEAD:91de63c006e886eba8d9c263c9aa55d4c7632072”
meta-webkit = “HEAD:ff5ab70d54ad250f57328d6e7c2c37b9ceaf3748”
meta-timesys = “HEAD:4d03b3bd68eb3df01ce99935e1e2939b53eb8ad4”
meta-st-stm32mp = “HEAD:1becb4e422555dc9735c65cc0a0f0d2d534bcc43”
meta-digi-arm
meta-digi-dey = “HEAD:fbc92e45b3d19ca0313f80245a1d5574eb69ff3a”

NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.7/x86_64-nativesdk-libc-3.7.tar.xz;sha256sum=b110bf2e10fe420f5ca2f3ec55f048ee5f0a54c7e34856a3594e51eb2aea0570 (will check PREMIRRORS first)
Initialising tasks: 100% |#######################################################################################################################| Time: 0:00:04
Sstate summary: Wanted 2410 Local 0 Mirrors 0 Missed 2410 Current 0 (0% match, 0% complete)
NOTE: Executing Tasks

3

I got past the problems in building by just deleting the repo inside the container at /usr/local/dey-4.0 and checking it out clean. After that I was able to complete the bitbake and move onto setting up NFS boot. I don’t have that working 100% yet, that will be a new topic.

I don’t understand why I was not able to do the update to the original copy of the repo per website directions, but that’s not blocking me any more.

4

yes, I’ve seen this as well and reported it to engineering. For now, delete everything in the /local/deyXXX folder including .github folder