Become a leader in the IoT community!
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
Hello @ming_58391 ,
while running bitbake
`NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz;sha256sum=1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030 (will check PREMIRRORS first)`
It’s just stuck at this point
is it the mirror issue or something else?
Every now and then I have seen builds get stuck. Typically, it’s when I’m up against a deadline and don’t have time to debug – so I often just go for the Microsoft fix and just reboot the whole thing and start again! That will often fix it.
One day, I really should set aside the time to dive into why….
I see,
also crops seems to be a temp container
plus it doesnt have sudo
Crops is mainly to be used as a build container. All the other work (writing recipes, flashing images, etc) would be done from the normal host filesystem
I must admit, I cheat and actually write my own Dockerfiles that include all the tools I want to play with
Ahhh,
got it.
makes sense
lessen the hassle
so, i ran the crops container,
sourced the oe-init-build-env
ran bitbake
but now a new error—Machine is invalid
OK – what is the contents of your `build/conf/bblayers.conf` file? It needs to include the meta-file from meta-renesas directory that includes your machine.
Loking at the repo, you probably need to include `meta-renesas/meta-rzg2l` as well as `meta-renesas/meta-rz-common`
got it fixed
there was a stray / in my conf
bitbake failed
seems to be bad request sent to aws
hmm,
Ming, any pointers?
isnt this a aws auth issue?
I have the same thought process
can we use the rz files rather do we need to use iwave
I don’t think rz keeps the copy of the bsp of the vendor
it’d rz hardwaree though?
This looks like you have added meta-iwave. Looking at the url: http://git-codecommit.ap-south-1.amazonaws.com that needs a login, so you would need to provide authentication.
As @superbike_z asked, do you _need_ it?
Yes
Why do you need the iwave stuff
Open to anything
As long as it work
I meant yes for thar
Can you perhaps open a ticket for this and document the efforts of GitHub. That way I can find help for us
got it fixed!
now, leading us to out last error
`| WARNING: /workdir/iwg56-release-bsp/build-iwg56m/tmp/work/x86_64-linux/binutils-native/2.31.1-r0/temp/run.do_compile.417791:1 exit 1 from ‘exit 1’
| ERROR: Execution of ‘/workdir/iwg56-release-bsp/build-iwg56m/tmp/work/x86_64-linux/binutils-native/2.31.1-r0/temp/run.do_compile.417791’ failed with exit code 1
ERROR: Task (virtual:native:/workdir/iwg56-release-bsp/build-iwg56m/../sources/meta-renesas/meta-rz-common/recipes-debian/buster/binutils/binutils_debian.bb:do_compile) failed with exit code ‘1’
NOTE: Tasks Summary: Attempted 908 tasks of which 473 didn’t need to be rerun and 3 failed.
Summary: 3 tasks failed:
/workdir/iwg56-release-bsp/build-iwg56m/../sources/meta-renesas/meta-rz-common/recipes-debian/buster/binutils/binutils-cross_debian.bb:do_compile
virtual:multilib:lib32:/workdir/iwg56-release-bsp/build-iwg56m/../sources/meta-renesas/meta-rz-common/recipes-debian/buster/binutils/binutils-cross_debian.bb:do_compile
virtual:native:/workdir/iwg56-release-bsp/build-iwg56m/../sources/meta-renesas/meta-rz-common/recipes-debian/buster/binutils/binutils_debian.bb:do_compile
Summary: There were 2 WARNING messages shown.
Summary: There were 6 ERROR messages shown, returning a non-zero exit code.`
now, i dont why binutils isnt installing, as normally it does get installed pretty easily when i try with bbb
cause of that, rest are failing due to it being a dependency
Hey @melta101 please if you could detail the yocto approach you have taken and the issues you are facing on a ticket, we can have some one help us but we need the thing broken down,.
Doiing it now
list of cmd i went through
1. sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm p7zip-full libyaml-dev \
libssl-dev bmap-tools
2. mkdir ~/bin
3. curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
4. chmod a+x ~/bin/repo
5. export PATH=~/bin:$PATH
6. git config –global user.name “Your Name”https://iwave-at-518522664578:S0ppFM%2ftJqihb3CuCATteqz%2f8oQ0HiVnl%2b%2b3wLGOZsg%[email protected]
7. git config –global user.email “Your Email”
8. git config –global credential.helper ‘store –file ~/.iwave-credentials’
9. cat <
EOF
# download the meta layers
10. mkdir iwg56-release-bsp; cd iwg56-release-bsp
11. repo init -u https://git-codecommit.ap-south-1.amazonaws.com/v1/repos/iwave-rz-manifest -b iwave-linux-dunfell -m iwg56m_rzg2v2l_3.0.6u2_0.2.xml
# change directory to the yocto setup path and set the env build path
12. TEMPLATECONF=$PWD/sources/meta-iwave/docs/template/conf/ source sources/poky/oe-init-build-env build-iwg56m
# update local.conf by adding “MACHINE=rzg2l-iwg56m”
# on the yocto setup path, run bitbake
14. bitbake core-image-weston
currently failing at bitbake as binutils isnt compiling…..
once fixed
this provides you u-boot bin, boards dtb, kernel image and rootfs bin
@ming_58391 @owuor_99089 @32bitwidesaviour please see above and our ticket here https://github.com/DevHeadsCommunity/motor-control-linux-HMI/issues/9
@melta101 @superbike_z
I was talking with people at the OpenEmbedded Workshop yesterday and was advised to use the community BSP instead as the main one is not getting the support.
https://github.com/renesas-rz/rz-community-bsp/tree/scarthgap/meta-rz-bsp
wow
will try this one once
is kas a new tool?
https://github.com/siemens/kas
Don’t know that it is new, comes from pedigree though
Kas has been around for a while. I know I have only just started looking at it recently and it is gaining popularity in the community.
i see,
this reminds me b4 for sending patches
oh
i thought i added the doubt here
@eLinux Lead π§
@ming_58391 there seems to be dead repos?
in the community version
Now that I’m back from FOSDEM & The OpenEmbedded Workshop, I’m am doing a test build myself.
I’ll let you know my results
trying to replicate the issue of an old T450 thinkpad
18hrs and counting lol
looking good
Ouch, would it be easy to build this on a vps
Also Iβm on a T470
might be with pre-built artifacts
we have some vpses, we can sort you out with one another day for a build is a bit of a pain
any success, Ming and Mavin?
Yes – I got some timeouts while downloading some packages (similar to you), but re-ran the `./kas-container build` a couple of times and it completed
oh, that’s great!
so no changes?
just re run
`./kas-container build –update –force-checkout kas/yocto/scarthgap.yml:kas/opt/debug.yml:kas/image/renesas-image-demo.yml:kas/machine/smarc-rzg2l.yml:kas/kernel/cip-6.1.yml`
My computer isn’t powerful enough to handle the build
Crashes all the time
Thus leading to timeout
Could I gain the access to the vps
It may be you would need to reduce the number of parallel threads for the build
You would want to add the line
`BB_NUMBER_THREADS = XX`
to your `local.conf`
As a rule of thumb, XX is the lower of:
1. The number of CPU Cores you have
2. Your memory / 2G
e.g., for a system that has 24 cores, but only 16Gb of memory, I would choose `BB_NUMBER_THREADS = 8`
For this repo:
First – have you setup the system with `./kas-container menu`
That will save a configuration
Then run `./kas-container shell`
to drop you into a shell with everything set up
Edit `build/conf/local.conf` and add the `BB_NUMBER_THREADS` line with a suitable limit
Run `bitbake renesas-image-demo`
running it once more
stops while compiling gcc
As this is now based on the latest LTS version of Ycoto (Scarthgap) – are you using the latest Ubunto to build it?
24.04
Can you run
`cat /proc/cpuinfo`
`cat /proc/memino`
`df -h`
cat /proc /cpuinfo
processor : 11
vendor_id : AuthenticAMD
cpu family : 23
model : 96
model name : AMD Ryzen 5 4600H with Radeon Graphics
stepping : 1
microcode : 0x8600106
cpu MHz : 1587.658
cache size : 512 KB
physical id : 0
siblings : 12
core id : 6
cpu cores : 6
apicid : 13
initial apicid : 13
fpu : yes
fpu_exception : yes
cpuid level : 16
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca
bugs : sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass retbleed smt_rsb srso
bogomips : 5989.12
TLB size : 3072 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14]
**cat /proc/meminfo **
MemTotal: 7469496 kB
MemFree: 272772 kB
MemAvailable: 4912392 kB
Buffers: 677516 kB
Cached: 3182292 kB
SwapCached: 0 kB
Active: 2996304 kB
Inactive: 2366828 kB
Active(anon): 1520504 kB
Inactive(anon): 29124 kB
Active(file): 1475800 kB
Inactive(file): 2337704 kB
Unevictable: 80 kB
Mlocked: 80 kB
SwapTotal: 2097148 kB
SwapFree: 2097148 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 612 kB
Writeback: 0 kB
AnonPages: 1503440 kB
Mapped: 788860 kB
Shmem: 46220 kB
KReclaimable: 1130664 kB
Slab: 1438564 kB
SReclaimable: 1130664 kB
SUnreclaim: 307900 kB
KernelStack: 16700 kB
PageTables: 33108 kB
SecPageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 5831896 kB
Committed_AS: 8479404 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 78516 kB
VmallocChunk: 0 kB
Percpu: 16960 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
Unaccepted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 509384 kB
DirectMap2M: 7213056 kB
DirectMap1G: 0 kB
**df -h**
Filesystem Size Used Avail Use% Mounted on
tmpfs 730M 2.6M 727M 1% /run
/dev/sda3 196G 127G 59G 69% /
tmpfs 3.6G 8.5M 3.6G 1% /dev/shm
tmpfs 5.0M 20K 5.0M 1% /run/lock
efivarfs 128K 42K 82K 34% /sys/firmware/efi/efivars
tmpfs 3.6G 0 3.6G 0% /run/qemu
/dev/sda1 261G 166G 82G 68% /home/melta101/Documents
/dev/nvme0n1p1 256M 95M 162M 37% /boot/efi
tmpfs 730M 308K 730M 1% /run/user/1000
/dev/sdb1 30G 3.8G 27G 13% /media/melta101/6463-3237
What did you set for the BB_NUMBER_THREADS ?
initially at 4
crashed
then set it at 2
which showed a compile error
towards GCc
It may be worth cleaning the GCC recipe
Just trying to remember the full name of the GCC recipe….
Did it fail on `ggc-cross-arch64` ?
lots of undefined within gcc build
gcc-cross is the prob
I would try:
`bitbake -c cleanall gcc-cross`
And then try again
try solo running bitbake gcc-cross-aarch64
The `-c cleanall` will get rid of any cached stuff in case there is something lurking from the crashed builds
builder@ba7225b12852:/build$ bitbake -c cleanall gcc-cross
Loading cache: 100% |################################################################################################| Time: 0:00:00
Loaded 3304 entries from dependency cache.
ERROR: Nothing PROVIDES ‘gcc-cross’. Close matches:
crash-cross
Summary: There was 1 ERROR message, returning a non-zero exit code.
ah mb
its gcc-cross-aarch64
removed the cache
should i rerun bitbake for gcc?
It would do no harm
it’s running
it’s been at 99% for a long time,
but atleast it didnt crash
That’s an improvement π
hopefully it doesnt timeout
builder@ba7225b12852:/build$ bitbake gcc-cross-aarch64
Loading cache: 100% |################################################################################################| Time: 0:00:00
Loaded 3304 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = “2.8.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “universal”
TARGET_SYS = “aarch64-poky-linux”
MACHINE = “smarc-rzg2l”
DISTRO = “poky”
DISTRO_VERSION = “5.0.6”
TUNE_FEATURES = “aarch64 crypto cortexa55”
TARGET_FPU = “”
meta-rz-bsp = “scarthgap:cc5949a95747f44b5ad067a8088762afcbe8a7d6”
meta-arm
meta-arm-toolchain = “HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d”
meta-oe = “HEAD:3c293e14492f01e22a64004e2330fb620c27578a”
meta-rz-panfrost = “HEAD:7ec5305383a312f79706f6e2c4df6ab00b2bcf6e”
meta
meta-poky = “HEAD:7117d115eab7351ecf21388ec720a3bb5f4a9b30”
Sstate summary: Wanted 11 Local 0 Mirrors 0 Missed 11 Current 191 (0% match, 94% complete)################# | ETA: 0:00:00
Initialising tasks: 100% |###########################################################################################| Time: 0:00:00
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 630 tasks of which 612 didn’t need to be rerun and all succeeded.
**atlast**
trying bitbake renesas-image-demo
it’s interesting, why’s qemu getting compiled?
it’s running
still 0 error
In most instances qemu gets compiled, because once you have an image in Yocto, you can nearly always test it with qemu
oh man
it just crashed at 31%
0 errors though
let me switch off all application BG process
maybe it’s the chrome that’s limiting the RAM
oh okay,
basically test run prior to flashing it up
Possibly.
For big builds, I often use `top` and just start killing stuff I don’t need to give me as much power as I can get hold of.
I then need to try and convince my financial director that I need more RAM, more disk. As I’m married to the financial director and the company is just the two of us – this is often met with a refusal to sign off on it π
i am at that situation
no background task,
running on 2 threads
42% done, 0 error
and….my mouse stopped responding
Sstate summary: Wanted 1578 Local 0 Mirrors 0 Missed 1578 Current 1188 (0% match, 42% complete)############ | ETA: 0:00:00
Initialising tasks: 100% |###########################################################################################| Time: 0:00:03
NOTE: Executing Tasks
Setscene tasks: 2766 of 2766
Currently 1 running tasks (2787 of 5668) 49% |######################################## |
0: linux-cip-6.1.127-cip36+git-r0 do_compile
it’s been stuck at 49% for about 30 mins
@ming_58391,
got a compile fail at coreutils-native
also does kas container use persistance volume or a temp one?
builder@d9b7b7e88b7b:/build$ bitbake renesas-image-demo
Build Configuration:
BB_VERSION = “2.8.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “universal”
TARGET_SYS = “aarch64-poky-linux”
MACHINE = “smarc-rzg2l”
DISTRO = “poky”
DISTRO_VERSION = “5.0.6”
TUNE_FEATURES = “aarch64 crypto cortexa55”
TARGET_FPU = “”
meta-rz-bsp = “scarthgap:cc5949a95747f44b5ad067a8088762afcbe8a7d6”
meta-arm
meta-arm-toolchain = “HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d”
meta-oe = “HEAD:3c293e14492f01e22a64004e2330fb620c27578a”
meta-rz-panfrost = “HEAD:7ec5305383a312f79706f6e2c4df6ab00b2bcf6e”
meta
meta-poky = “HEAD:7117d115eab7351ecf21388ec720a3bb5f4a9b30”
Sstate summary: Wanted 1375 Local 0 Mirrors 0 Missed 1375 Current 1391 (0% match, 50% complete)############ | ETA: 0:00:00
Initialising tasks: 100% |###########################################################################################| Time: 0:00:03
NOTE: Executing Tasks
WARNING: boost-native-1.84.0-r0 do_fetch: Checksum failure encountered with download of https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.bz2 – will attempt other sources if available
WARNING: linux-cip-6.1.127-cip36+git-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-cip/6.1.127-cip36+git/lib/oid_registry_data.c in package linux-cip-src contains reference to TMPDIR
File /usr/src/debug/linux-cip/6.1.127-cip36+git/drivers/video/logo/logo_linux_clut224.c in package linux-cip-src contains reference to TMPDIR
File /usr/src/debug/linux-cip/6.1.127-cip36+git/drivers/tty/vt/consolemap_deftbl.c in package linux-cip-src contains reference to TMPDIR [buildpaths]
NOTE: Tasks Summary: Attempted 5668 tasks of which 3860 didn’t need to be rerun and all succeeded.
Summary: There were 2 WARNING messages.
**
Bitbake is done!!**
builder@d9b7b7e88b7b:/build$ ls tmp/deploy/images/smarc-rzg2l/
bl2_bp-smarc-rzg2l.bin
Image-smarc-rzg2l.bin
renesas-image-demo-smarc-rzg2l-20250206185735.spdx.tar.zst
u-boot.bin
bl2_bp-smarc-rzg2l.srec
modules–6.1.127-cip36+git0+a0c8c13db2-r0-smarc-rzg2l-20250206185735.tgz
renesas-image-demo-smarc-rzg2l-20250206185735.tar.gz
u-boot-renesas-initial-env
fip-smarc-rzg2l.bin
modules-smarc-rzg2l.tgz
renesas-image-demo-smarc-rzg2l-20250206185735.testdata.json u-boot-renesas-initial-env-smarc-rzg2l
fip-smarc-rzg2l.srec
r9a07g044l2-smarc–6.1.127-cip36+git0+a0c8c13db2-r0-smarc-rzg2l-20250206185735.dtb renesas-image-demo-smarc-rzg2l.manifest
u-boot-renesas-initial-env-smarc-rzg2l-2021.10-r0
Flash_Writer_SCIF_RZG2L_SMARC_PMIC_DDR4_2GB_1PCS.mot
r9a07g044l2-smarc.dtb
renesas-image-demo-smarc-rzg2l.spdx.tar.zst
u-boot-smarc-rzg2l-2021.10-r0.bin
Image
r9a07g044l2-smarc-smarc-rzg2l.dtb
renesas-image-demo-smarc-rzg2l.tar.gz
u-boot-smarc-rzg2l.bin
Image–6.1.127-cip36+git0+a0c8c13db2-r0-smarc-rzg2l-20250206185735.bin
renesas-image-demo-smarc-rzg2l-20250206185735.manifest
renesas-image-demo-smarc-rzg2l.testdata.json
Got the juicy stuffs
will burn it in SD card tom.
wicked work @melta101
can you share a kas script to replicate the build?
or whatever artefact you have?
sure
CONTRIBUTE TO THIS THREAD