<dvergatal>
and that is why your install command cannot stat it because the file /home/tdowty/cfc510p/christian_devel/poky/build/tmp/deploy/images/innoflight-cfc510-live-usb/grub-efi-bootx64.efi is not existing
lexano has quit [Ping timeout: 246 seconds]
Guest44 has joined #yocto
Guest44 has quit [Client Quit]
Thorn has joined #yocto
Thorn_ has quit [Ping timeout: 264 seconds]
yudjinn has joined #yocto
olani- has quit [Ping timeout: 255 seconds]
davidinux has quit [Ping timeout: 255 seconds]
davidinux has joined #yocto
benkard has joined #yocto
mulk has quit [Ping timeout: 272 seconds]
benkard is now known as mulk
locutusofborg has quit [Read error: Connection reset by peer]
locutusofborg has joined #yocto
jclsn has quit [Ping timeout: 255 seconds]
jclsn has joined #yocto
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
sgw has quit [Ping timeout: 252 seconds]
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
Saur_Home has quit [Client Quit]
Saur_Home has joined #yocto
ablu has quit [Ping timeout: 264 seconds]
ablu has joined #yocto
old_boy has joined #yocto
variksla has joined #yocto
old_boy has quit [Quit: Client closed]
kpo has quit [Ping timeout: 246 seconds]
kpo has joined #yocto
amitk has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
jmd has joined #yocto
mulk has quit [Ping timeout: 272 seconds]
alessioigor has joined #yocto
mkazantsev has joined #yocto
mulk has joined #yocto
mulk has quit [Ping timeout: 268 seconds]
variksla has quit [Quit: Client closed]
kpo has quit [Ping timeout: 255 seconds]
jmd has quit [Remote host closed the connection]
Chaser has joined #yocto
rfuentess has joined #yocto
linfax has joined #yocto
JerryM has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mulk has joined #yocto
mkazantsev has quit [Ping timeout: 240 seconds]
mkazantsev has joined #yocto
<mkazantsev>
Hello! I'm having an intermittent issue with the D1 Display Engine, wonder if anyone had something similar
<mkazantsev>
9 times out of 10 the color on the display is off, sometimes it's more blue, sometimes more green than it should be
<mkazantsev>
When I run modetest, for example, the colors are kinda mixed with blue, when modetest exits the whole screen is blue
mulk has quit [Ping timeout: 268 seconds]
<mkazantsev>
In memory, images have the correct color
<mkazantsev>
TCON LCD test patters are correct
mulk has joined #yocto
Chaser has joined #yocto
<mkazantsev>
mixer registers are the same when displaying the correct and incorrect colors
<mkazantsev>
not even sure where to look at this point
goliath has joined #yocto
Chaser has quit [Ping timeout: 240 seconds]
luc4 has joined #yocto
xmn has quit [Ping timeout: 255 seconds]
luc4 has quit [Ping timeout: 240 seconds]
frieder has joined #yocto
rob_w has joined #yocto
Kubu_work has joined #yocto
vladest has quit [Ping timeout: 255 seconds]
dmoseley has quit [Ping timeout: 264 seconds]
dmoseley_ has joined #yocto
florian_kc has joined #yocto
alessioigor has quit [Ping timeout: 246 seconds]
luc4 has joined #yocto
vladest has joined #yocto
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
alessioigor has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
leon-anavi has joined #yocto
mkazantsev has quit [Remote host closed the connection]
mkazantsev has joined #yocto
florian_kc has quit [Ping timeout: 255 seconds]
<mkazantsev>
wrong channel sorry
mkazantsev has quit [Quit: Leaving]
<JerryM>
kanavin: I've got several layer-setup.json files for different setups, mostly they are likt 90% the same and only differ in a few places, what do you think about applying fragmenst on a base file or similar solution?
mvlad has joined #yocto
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
<kanavin>
JerryM, I don't have any thoughts about that. why is that a problem?
<JerryM>
kanavin: besides duplication, it's really just a minor inconvenience, say I've got { A: refA, B: refB } and { A:refA, B: refFeature } and I want to update refA I got to do it in two files (and have two diffs that are the same change)
<kanavin>
JerryM, does json support includes natively?
<JerryM>
kanavin: I'm no expert, but I would assume not, I'd think this would need to be handled in the scripts
dgriego has quit [Ping timeout: 264 seconds]
ptsneves has joined #yocto
dgriego has joined #yocto
<kanavin>
JerryM, if you can think up a design proposal, and/or patches, please go ahead. I currently can't say how this could be supported.
<luc4>
Hello! Would it be possible to get tar.xz archives of each partition of my image? I tried to set the image fs type, but I'm only getting the rootfs, not the boot partition. I also tried to look at the wic command, but I do not see anything like this. I know I could mount each partition, but I would like to avoid it if possible. Any other option? Thanks.
rfuentess has quit [Remote host closed the connection]
rfuentess has joined #yocto
Guest59 has joined #yocto
jmiehe has joined #yocto
<rburton>
correct, a bundled initramfs is literally a cpio archive glued onto the end of the kernel
alperak has joined #yocto
<JerryM>
kanavin: I'll do some experiments and see if/what works
<dvergatal>
rburton: so now I have a question because what I was going to do was to create an instalator image with bundled initramfs and that image would be responsible for deploying my main image and inside it would be another initramfs bundle but this configuration is rather impossible to achieve in one distro right?
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
<rburton>
dvergatal: just don't use a bundled initramfs
<dvergatal>
rburton: currently i'm not and it is working
<rburton>
a bundled initramfs is literally copied into RAM in its entirety, you don't want to put a huge target in that
<dvergatal>
I have separate kernell image and initramfs but I wanted to have it bundled
<dvergatal>
the installation initramfs I wanted to have as tiny as possible because it is only being used for the installation process
<rburton>
that's fine, just have it pick up the thing to install from the disk
<dvergatal>
and wanted to have it bundled with the kernel but from what I have read it is not possible to bundle more than 1 image
<rburton>
you can only have one initramfs image on a kernel, but that's not a yocto thing, its a linux thing
<rburton>
you can bundle the initramfs and keep the install image separate
<dvergatal>
right now I have instead of INSTALL INITRAMFS BUNDLE, kernel image and install initramfs
<dvergatal>
and my question should be if it is possible somehow to achieve what is on the image, I read about different kind of solutions for example to use another machine or distro for this install image in order to create separate bundle
<RP>
rburton: do you know where locale.aliases is supposed to live packages wise?
aladyshev has joined #yocto
prabhakalad has quit [Ping timeout: 255 seconds]
prabhakalad has joined #yocto
mihai has joined #yocto
rob_w has quit [Ping timeout: 264 seconds]
rfuentess has joined #yocto
<aladyshev>
I experience the strange issue. Sometimes when I perform `devtool modify linux-aspeed` I get the following error:
<aladyshev>
```WARNING: SRC_URI is conditionally overridden in this recipe, thus several devtool-override-* branches have been created, one for each override that makes changes to SRC_URI. It is recommended that you make changes to the devtool branch first, then checkout and rebase each devtool-override-* branch and update any unique patches there (duplicates
<aladyshev>
on those branches will be ignored by devtool finish/update-recipe)```
<aladyshev>
And the worst case is that local patches are not applied in this case
<rburton>
if you can replicate with master then please do file a bug
smokey has quit [Remote host closed the connection]
luc4 has quit [Ping timeout: 268 seconds]
smokey has joined #yocto
<aladyshev>
How to file a bug? I'm using yocto in the OpenBMC distribution, do I have to replicate it in native poky?
<rburton>
would be useful if you can. there's been a lot of fixes to devtool modify in master.
lexano has joined #yocto
<aladyshev>
Another issue that I've started to encounter recently is that the devtooled linux-aspeed git tree stucks at rebase or am operation:
<aladyshev>
Your branch is ahead of 'origin/dev-6.6' by 5 commits.
<aladyshev>
(use "git push" to publish your local commits)
<aladyshev>
You are currently rebasing.
<aladyshev>
(all conflicts fixed: run "git rebase --continue")
<aladyshev>
nothing to commit, working tree clean
<aladyshev>
```
<aladyshev>
However when I try to continue, I get:
<aladyshev>
```
<aladyshev>
$ git rebase --continue
<aladyshev>
warning: could not read '.git/rebase-apply/head-name': No such file or directory
<aladyshev>
```
<aladyshev>
Is this a known issue?
Guest59 has joined #yocto
Guest59 has quit [Quit: Client closed]
mulk has quit [Ping timeout: 260 seconds]
mulk has joined #yocto
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 246 seconds]
xmn has joined #yocto
targetdisk has quit [Remote host closed the connection]
joekale has quit [Ping timeout: 264 seconds]
jmiehe has quit [Quit: jmiehe]
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
vladest has quit [Ping timeout: 246 seconds]
luc4 has joined #yocto
lefty has joined #yocto
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 256 seconds]
|Xagen has quit [Ping timeout: 246 seconds]
sev99 has joined #yocto
joekale has joined #yocto
sev99 has quit [Client Quit]
pidge has joined #yocto
lefty83 has joined #yocto
alperak has quit [Quit: Client closed]
lefty has quit [Quit: Client closed]
lefty83 is now known as lefty
alperak has joined #yocto
<moto-timo>
RP: dang it
vladest has joined #yocto
aladyshev has quit [Quit: Client closed]
Dr_Who has quit [Read error: Connection reset by peer]
JerryM has quit [Quit: Konversation terminated!]
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
Net147 has quit [Quit: Quit]
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
Vonter has quit [Ping timeout: 256 seconds]
Vonter has joined #yocto
Xagen has joined #yocto
mulk has quit [Ping timeout: 252 seconds]
mulk has joined #yocto
rfuentess has quit [Remote host closed the connection]
rm5248 has joined #yocto
goliath has quit [Quit: SIGSEGV]
<lefty>
Anybody had luck with the beagleplay machine in meta-ti-bsp? I'm finding when I boot my beagleplay with core-image-full-cmdline image pressing the USR button at power up to boot from the SD card, u-boot fails to load boot.scr and uEnv.txt, then seems to fallback to the eMMC and gets stuck at "Starting kernel...". If I boot from eMMC u-boot on the
<lefty>
eMMC detects the SD card and is at least able to boot, but I'm not sure which kernel image is being used (just that the rootfs is the SD card one).
<rm5248>
Hi, is it the case that the PREFERRED_VERSION_virtual/kernel can only be set in the distribution? I've tried setting it in my conf/machine/<machine>.conf file but it doesn't seem to take effect
ctraven has quit [Quit: Lost terminal]
<lefty>
rm5248 I believe you may have to specify the actual recipe that provides virtual/kernel with PREFERRED_VERSION (PREFERRED_VERSION_linux-yocto for instance).
gvmeson is now known as vmeson
<lefty>
I have done that in my machine.conf file before and it has worked (so long as a recipe for the specified version exists).
sev99 has joined #yocto
luc4 has quit [Ping timeout: 255 seconds]
alperak has quit [Quit: Client closed]
amitk_ has joined #yocto
xmn has quit [Ping timeout: 256 seconds]
alperak has joined #yocto
xmn has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
linfax has quit [Ping timeout: 246 seconds]
<lefty>
denix is meta-ti's beagleplay machine validated with Poky distro? I successfully core-image-full-cmdline with MACHINE=beagleplay but when I try to boot my beagleplay from an SD card flashed with core-image-full-cmdline-beagleplay.wic.xz I'm facing some weird issues. U-boot runs from the SD card, but when it actually boots the kernel it appears to
<lefty>
be trying to boot the kernel image from eMMC, and that just hangs indefinitely.
<rm5248>
so I figured out what the problem is: since I'm using the meta-atmel layer, it was set as PREFERRED_PROVIDER_virtual/kernel:sama5 = "linux-mchp". I had set PREFERRED_PROVIDER_virtual/kernel, not PREFERRED_PROVIDER_virtual/kernel:sama5.
simonew has quit [Ping timeout: 264 seconds]
<rm5248>
lefty: One thing that I did recently to debug stuff like that was to get to uboot and mount the rootfs over NFS. I'm not sure if that helps in your situation at all. I assume that your problem might be that uboot is configured to always run off of the eMMC, not from the SD card
<lefty>
I have console access so I can see u-boot's environment. It looks like it's failing to loadbootenv and loadbootscr are failing, and after that it's falling back to trying to boot from eMMC. What's strange is if I boot off of eMMC, the version of u-boot in the Debian Buster image detects the SD card and boots off of it (seemingly successfully).
<lefty>
So I can run both versions of u-boot, but the one built with meta-ti seems to be missing some stuff.
jmd has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
<dmoseley_>
Any plans for a Developer day around EOSS in Seattle? I'm trying to book my flights.
<rm5248>
does uboot see the SD card? IIRC it's the 'mmc' command that you can use to test the SD card
lefty has quit [Quit: Client closed]
lefty has joined #yocto
<lefty>
rm5248 mmc does see both devices, the eMMC and the SD card.
<lefty>
And it's able to read the partition table for device 1 (SD card).
<rm5248>
does it see the files on the SD card?
<lefty>
Not sure how to specify the device name to ls in u-boot...
<lefty>
Forgive my relatively limited familiarity with u-boot.
<rm5248>
I think you need to set the mmc dev, and then do 'fatls'
<lefty>
I can switch to device 1 (SD), but fatls by itself just gives me usage. "fatls /" says / is an invalid partition so evidently I'm not understanding the usage.
<lefty>
fatls requires an interface argument which I'm not sure what that should be.
<lefty>
If I plug the SD card into my PC there is no boot.scr or uEnv.txt file on the boot partition.
<lefty>
"fatls mmc 1:1" yields the same list of files as I see on my PC. EFI directory, Image (kernel), tiboot3.bin, tispl.bin, and u-boot.img.
<rm5248>
should there be? I'm not sure how it's supposed to boot, but if it's trying to load those files from the SD card and it fails that could be why.
leon-anavi has quit [Quit: Leaving]
<lefty>
I would agree with that assessment, which is why it seems to me the build is missing something. I'm trying to parse through u-boot's environment to understand what's going on and it seems that those files missing is causing it to fall back to eMMC.
<lefty>
It's also not clear to me the difference between the beaglplay machine and the beagleplay-k3r5 machine and which I should be using. I'm struggling to find great documentation for the meta-ti layer or Yocto use in general on the beagleplay.
<denix>
lefty: which branch?
<lefty>
denix master and kirkstone both yield the same behavior for me.
<denix>
lefty: try one of the "wip" branches - there are some config changes pending for u-boot
<denix>
or -next
<lefty>
Does wip stand for something? Wasn't sure what those were.
<lefty>
k3r5.inc is what led me to believe it's for the RT core, though I have yet to play around with any SOCs that have a separate RT core so I'm not very familiar with how this all works.
<sotaoverride>
lefty: work in progress (WIP)
<denix>
wip = work in progress
<lefty>
Thanks
<lefty>
I'll give one of those branches a shot.
<lefty>
Right now the key portion it seems to be breaking down at is "SD/MMC found on device 1
<lefty>
Failed to load 'boot.scr'
<lefty>
Failed to load 'uEnv.txt'
<lefty>
switch to partitions #0, OK
<lefty>
mmc0(part 0) is current device"
<lefty>
So it tries to boot from device 1, but then after the two failures it switches back to device 0.
<denix>
lefty: TI K3 is a heterogeneous arch with bunch of Cortex-R5 MCUs and Cortex-A53/A72 big GP cores. in order to build for those cores, meta-ti uses "k3r5" multiconfig
<denix>
lefty: and neither of boot.scr nor uEnv.txt are required and those are not critical errors
<lefty>
Right, but don't all beagleplay boards have the AM652 with this heterogeneous arch?
<denix>
there's simply something's wrong with SD driver
<lefty>
Is that what's causing the switch back to device 0?
nayfe has quit [Quit: Client closed]
<lefty>
I'm seeing some pca953x errors as well, "i2c_write: error waiting for data ACK (status=0x116)
<lefty>
When would I want to set MACHINE=beagleplay-k3r5 though? Or MACHINE=beagleplay if all beagleplay boards use the AM62x?
<lefty>
Is the gpio expander used for SD card communications at all? Could that cause the fallback to eMMC?
<lefty>
I don't actually see a gpio expander in the schematic.
<denix>
k3r5 multiconfig is used automatically when the required dependencies are pulled in
<lefty>
Okay, I have master-wip building at the moment. Have to leave here shortly but will test it out when I get back. Thanks for the help.
xmn has quit [Ping timeout: 268 seconds]
xmn has joined #yocto
frieder has quit [Remote host closed the connection]
ptsneves has quit [Ping timeout: 246 seconds]
kpo has joined #yocto
GNUmoon has quit [Ping timeout: 255 seconds]
lefty has quit [Ping timeout: 250 seconds]
GNUmoon has joined #yocto
pvogelaar has quit [Read error: Connection reset by peer]
tangofoxtrot has quit [Ping timeout: 264 seconds]
tangofoxtrot has joined #yocto
alperak has quit [Quit: Client closed]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
mort has quit [Read error: Connection reset by peer]
mort has joined #yocto
florian_kc has joined #yocto
goliath has joined #yocto
GNUmoon has quit [Ping timeout: 255 seconds]
lefty has joined #yocto
GNUmoon has joined #yocto
<lefty>
denix still facing the same issue with master-wip. One other thing I notice is u-boot initially prints out a line "Loading Environment from nowhere... OK", which seems rather odd. There's also an error "Error: Can't set serial# to SSSS" and also a few lines related to the Ethernet phy and a failure there, none of which would seem to be related to
<lefty>
u-boot falling back to eMMC.
smokey has quit [Remote host closed the connection]
smokey has joined #yocto
olani- has joined #yocto
<lefty>
Same on master-next as well. Abridged output: "mmc1 is current device", then "SD/MMC found on device 1", then two errors related to boot.scr and uEnv.txt, then "switch to partitions #0, OK", then "mmc0(part0) is current device", is the switch to partition 0 specifying the wrong device (or no device) perhaps?
smokey has quit [Remote host closed the connection]
Minvera2 has joined #yocto
Minvera has quit [Ping timeout: 264 seconds]
davidinux has quit [Ping timeout: 264 seconds]
davidinux has joined #yocto
olani- has quit [Ping timeout: 255 seconds]
Minvera2 has quit [Ping timeout: 256 seconds]
alessioigor has quit [Quit: alessioigor]
<lefty>
Okay, I think I figured it out at least partways, distro_bootcmd runs bootcmd_${target} for target in boot_targets, and boot_targets has mmc0 before mmc1, causing the switch to mmc0 and the failed boot. Running bootcmd_mmc1 manually results in a system that boots, but never gives me a login prompt, so I'm making progress. denix is the attempt to
<lefty>
boot from mmc0 expected? I guess my expectation is that the first boot target would be eMMC if USR wasn't pressed when u-boot was executed or SD if it was pressed.
<lefty>
Or maybe just try to boot SD first, if there's no SD card present or if it's not a properly formatted SD card presumably that will fail and distro_bootcmd will then proceed with eMMC boot?
lefty has quit [Quit: Client closed]
florian_kc has quit [Ping timeout: 240 seconds]
lefty has joined #yocto
<lefty>
denix beagleplay.conf sets UBOOT_MACHINE to am62x_evm_a53_defconfig, shouldn't it be am625_beagleplay_a53_defconfig? I suspect that is where my bogus u-boot environment is coming from.
jmd has quit [Remote host closed the connection]
<lefty>
Hmm, it didn't like that. Even though there is a am625_beagleplay_a53.config file in configs.
<denix>
lefty: that's a config fragment and it is being applied on top of the defconfig - see that later in beagleplay.conf
<lefty>
denix the config fragment doesn't appear later on in beagleplay.conf in master. Which branch?
<lefty>
After UBOOT_MACHINE it just sets a few PREFERRED_PROVIDERS, then KERNEL_DEVICETREE, and MACHINE_GUI_CLASS, that's it.
<denix>
lefty: I already told you earlier - wip or -next
<lefty>
Okay, I'll take a look at those again.
Minvera has joined #yocto
<lefty>
Okay, I had to do a git pull and I see it now in master-wip (not in -next). I'll give it another shot.
<lefty>
I'm guessing the warnings I was seeing about the gpio expander were due to the incorrect device tree being loaded perhaps.
<lefty>
Since it was loading the one for the evaluation kit.
<lefty>
denix still the same issue with an unexpected u-boot env. default_device_tree is still ti/k3-am625-sk and boot_targets still starts with mmc0. I'll revisit this later tonight. Definitely learned quite a bit about u-boot and u-boot configuration today though, which is my whole goal in playing around with this.
<lefty>
Maybe not entirely broken anymore, my system actually boots now if I "run bootcmd_mmc1", otherwise it still defaults to mmc0. And I now actually get a login prompt.
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
xmn has quit [Quit: ZZZzzz…]
Xagen has quit [Ping timeout: 256 seconds]
florian_kc has joined #yocto
Xagen has joined #yocto
<rburton>
khem: i see you fired a meta-clang, and it just warned in rpm. are you digging into that?
amitk_ has quit [Remote host closed the connection]
lefty has quit [Quit: Client closed]
sev99 has quit [Quit: Client closed]
mvlad has quit [Remote host closed the connection]
<khem>
rburton: not yet but I did see the warning
<khem>
its with clang-18 btw.
<khem>
which is still in yoe/mut
fermion has quit [Quit: Connection closed for inactivity]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
olani- has joined #yocto
pretec has joined #yocto
<pretec>
Hi
goliath has quit [Quit: SIGSEGV]
joekale has quit [Ping timeout: 256 seconds]
llu has joined #yocto
Kubu_work has quit [Quit: Leaving.]
olani- has quit [Ping timeout: 256 seconds]
olani- has joined #yocto
<moto-timo>
What do folks want to know about writing python recipes?
<moto-timo>
I'm going to write a blog post or two or a series.
llu has quit [Quit: leaving]
<moto-timo>
LetoThe2nd: and I have been threatening to do a live coding session also... but that never happened yet.
<moto-timo>
lol
<moto-timo>
You can watch me as I upgrade a python recipe in oe-core and try not to curse too much because I'm on camera.