Not in this series, unfortunately :( Good to know there's interest! I might want to tackle driver writing as its own series (and I'd probably use something like Raspberry Pi for that and skip Yocto).
Hey, where can i read about this Linux I2C problem?! I was able to use i2c. And wondered what is the difference between library and driver. Can use both in my project. 😊
One thing to mention is that when you edit the .config file via menuconfig you need to create a fragment file or save the defconfig, because if, for some reason, the linux recipe gets cleaned or unpacked again, your edit will be lost, and you will need to run menuconfig again.
If this is a hack, what’s the right way to change the i2c clock speed? I’m using boot2qt on a Toradex SoM. I tracked down the imx8mp-verdin.dts file in the same directory you are using but changed the clock speed right there. I then used dtc to create a new dtb file which I copied to the /boot/ dir, however, it hasn’t changed the bus speed. Where is the kernel told which dtb file to load?
@@AbdulRehman-eq3ns FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:" didn't work for me, I had to modify it to FILESEXTRAPATHS:prepend := "${THISDIR}:". I'm running it with kirkstone.
Ugh! You've created the patch the really hard way. It is far easier to go to the git repository where the sources came from (down under tmp/work/....) and make your edits there. Then do one of the following: "git diff" - which will make the diff file, that you can use as your patch commit your change to your local git repo. Then use the "git format-patch" command against the new commit to let it generate the patch file, including its filename. You don't have to worry about messing up the git repository where the sources came from because it's all local and Bitbake will blow it away once you integrate the patch with your layer. Once it sees the patch, it will re-fetch the git repo (via a do_fetch step) and will then apply your patch (via a do_patch step) before compilation. Using "git format-patch" is actually the best, because the resulting patch file will have information from the commit you made, including your e-mail address, its timestamp and the full commit message. So when bitbake later applies the patch, it should (using "git am" internally) apply it as a local commit, which you can then see in your local git clone's log. Manually constructing a patch file is just painful and error prone for all but the most trivial instances.
i think usually you include things like bsp layers as git submodules, so messing with the files in there might result in conflict once updates to the layers get rolled out. Idk tho, im still very new. Also in a way its much cleaner and a separation of concerns when it comes to the layers.
This guy is providing you so much knowledge for free in an easy to absorb way and you are complaining it's too long? Did you expect to gain all of this knowledge in what, 5 minutes?
Loving the series! Also wanted to say it would be awesome to see driver writing in the future!
Can't wait for the next one, This is gold!
any idea why when I run the bitbake -c menuconfig busybox that I end up getting a warning: do_compile tained warnings
Did you manage to solve this issue? I am getting it as well
Free knowledge. Wow!
I wish all universities taught students like that 😁🤣😂
Can't wait for the next one! When will we write our own drivers?! For example for the SPI peripherals?! :D
Not in this series, unfortunately :( Good to know there's interest! I might want to tackle driver writing as its own series (and I'd probably use something like Raspberry Pi for that and skip Yocto).
Hey, where can i read about this Linux I2C problem?! I was able to use i2c. And wondered what is the difference between library and driver. Can use both in my project. 😊
could you please explain about SPI interfacing in the device tree? and also explain register mapping and its settings.
One thing to mention is that when you edit the .config file via menuconfig you need to create a fragment file or save the defconfig, because if, for some reason, the linux recipe gets cleaned or unpacked again, your edit will be lost, and you will need to run menuconfig again.
Good point, thank you! I talk about creating a defconfig in an upcoming episode (when we enable WiFi networking).
I'm unable to add i2cdetect to my custom image, could you please describe the steps you followed to make it work please
you would only change the status label to be equal "okay"
If this is a hack, what’s the right way to change the i2c clock speed? I’m using boot2qt on a Toradex SoM. I tracked down the imx8mp-verdin.dts file in the same directory you are using but changed the clock speed right there. I then used dtc to create a new dtb file which I copied to the /boot/ dir, however, it hasn’t changed the bus speed. Where is the kernel told which dtb file to load?
Hi do you know what is the new syntax for FILESEXTRAPATHS_prepend
Its giving me an error that I'm using older syntax
New syntax
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
@@AbdulRehman-eq3ns FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:" didn't work for me, I had to modify it to FILESEXTRAPATHS:prepend := "${THISDIR}:". I'm running it with kirkstone.
Ugh! You've created the patch the really hard way. It is far easier to go to the git repository where the sources came from (down under tmp/work/....) and make your edits there. Then do one of the following:
"git diff" - which will make the diff file, that you can use as your patch
commit your change to your local git repo. Then use the "git format-patch" command against the new commit to let it generate the patch file, including its filename. You don't have to worry about messing up the git repository where the sources came from because it's all local and Bitbake will blow it away once you integrate the patch with your layer. Once it sees the patch, it will re-fetch the git repo (via a do_fetch step) and will then apply your patch (via a do_patch step) before compilation.
Using "git format-patch" is actually the best, because the resulting patch file will have information from the commit you made, including your e-mail address, its timestamp and the full commit message. So when bitbake later applies the patch, it should (using "git am" internally) apply it as a local commit, which you can then see in your local git clone's log.
Manually constructing a patch file is just painful and error prone for all but the most trivial instances.
What is the reason for using a patch instead of modifying the original dts file?
i think usually you include things like bsp layers as git submodules, so messing with the files in there might result in conflict once updates to the layers get rolled out. Idk tho, im still very new.
Also in a way its much cleaner and a separation of concerns when it comes to the layers.
I think I lost the plot in this part of the series.
Tooooooo loooooonnnnnnnnngggggggg!!!!!!!
This guy is providing you so much knowledge for free in an easy to absorb way and you are complaining it's too long? Did you expect to gain all of this knowledge in what, 5 minutes?
the absolute state of this persons attention span