<jclsn>
The second one after the else statement, seems to be a placeholder only, but when using the first one, trying to address the pin by its gpio-line-name from the device tree, it doesn't work either
<marex>
what do you mean by two implementations ?
<marex>
why do you use this ancient version ?
slobodan has joined #u-boot
<jclsn>
There are the gpio_lookup_name and the name_to_gpio functions. The name_to_gpio has a weak link to dectoul(). Seems like it wasn't functional in that version. We are also stuck on that version unfortunately
<marex>
the later seems like legacy api
<marex>
what is the question ?
<jclsn>
How would you use the gpio set function? I would assume to use the gpio-line-name from the device tree.
<jclsn>
But that results in a GPIO: 'SW_RESET_N' not found in my case
<jclsn>
I already read the documentation on it, but it isn't clear to me
Guest40 has quit [Quit: Client closed]
<jclsn>
I guess the command can only handle gpio numbers?
<jclsn>
Ah got it
<jclsn>
gpio -a showed all labels
<jclsn>
gpio status -a I meant
<jclsn>
I wonder why the command doesn't make use of the gpio-line-names in the device tree though
<marex>
jclsn: run gpio status
<marex>
pick gpio
<marex>
run gpio set/clear/toggle <gpio>
<jclsn>
I already got it thanks
Guest40 has joined #u-boot
frieder has joined #u-boot
frieder has quit [Remote host closed the connection]
<Guest40>
after flashing the image i created with yocto to the sd card, it works work without any boot problems with coral dev board(imx8mq). however, when i flash the same image to emmc with "ums 0 mmc 0" and balena, it does not boot. in addition, i need to flash imx-boot to mmcblk0boot0 with fastboot mode. what could it be caused by? is it because the
<Guest40>
emmc partitions are physical?
<Guest40>
likewise, when i flash another image i created for raspberrypi cm4 with using the rpiboot tool, it can boot directly from emmc.
<Guest40>
maybe everything makes sense, but i don't quite understand. sadly, rookie here :D
<Guest40>
i started digging inside the rpiboot tool. maybe something will show up. i'm grateful for any idea.
<cambrian_invader>
jclsn: well, the reason U-Boot doesn't use the gpio-line-names is because usually when you need to use a particular GPIO for a particular purpose, you do it in C
<cambrian_invader>
so no one has gotten around to adding support for that property
Guest40 has joined #u-boot
mmu_man has quit [Ping timeout: 240 seconds]
monstr has quit [Remote host closed the connection]
jaganteki has quit [Ping timeout: 246 seconds]
frieder has quit [Remote host closed the connection]
mmu_man has joined #u-boot
jaganteki has joined #u-boot
d-s-e has joined #u-boot
mmu_man has quit [Ping timeout: 240 seconds]
mmu_man has joined #u-boot
mckoan is now known as mckoan|away
mmu_man has quit [Ping timeout: 240 seconds]
ldevulder_ has joined #u-boot
ldevulder has quit [Ping timeout: 240 seconds]
stefanro has quit [Quit: Leaving.]
derRichard has quit [Server closed connection]
derRichard has joined #u-boot
goliath has joined #u-boot
mmu_man has joined #u-boot
d-s-e has quit [Quit: Konversation terminated!]
Guest40 has quit [Quit: Client closed]
aak-rookie has joined #u-boot
vagrantc has joined #u-boot
SlimeyX has quit [Ping timeout: 252 seconds]
SlimeyX has joined #u-boot
aak-rookie has quit [Quit: Client closed]
soxrok2212 has joined #u-boot
<soxrok2212>
hi :) is it possible to pack a squashfs rootfs inside a FIT image?
fionera has quit [Server closed connection]
fionera has joined #u-boot
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #u-boot
jaganteki has quit [Quit: Client closed]
<Tartarus>
Just say it's the ramdisk/initrd, yes?
<soxrok2212>
Tartarus: i did try that, but it seems to not know how to mount it
<Tartarus>
the kernel?
<soxrok2212>
in my .its, i have a "rootfs" node with the data being the squashfs blob, and the type set to "filesystem"
<soxrok2212>
i set the bootargs to have "root=fit:rootfs rootfstype=squashfs" but it fails with "VFSL Cannot open root device "fit:rootfs""
<soxrok2212>
yeah, the kernel
<soxrok2212>
lemme try changing it to be the initrd
jaganteki has joined #u-boot
jaganteki has quit [Ping timeout: 246 seconds]
<soxrok2212>
Tartarus: no luck, any other ideas?
<Sout_>
can you even manipulate the boot args from fit image?. If you want the signing you can boot to a signed ramfs, then check the signature of the squashfs image with something like dm-verity (huge pia). 2. i thought root is looking for /dev entry
<soxrok2212>
ive just been modifying boot args from the cli
<soxrok2212>
i agree about root, i thought it was looking in /dev too but i was told it can reference a fit image for it too
<soxrok2212>
not sure how accurate that is
<Tartarus>
I mean, yeah, no "fit:rootfs" isn't a valid kernel argument
<Tartarus>
it should be root=/dev/ram or whatever like normal for an initrd rootfs