Introduction to Embedded Linux Part 1 - Buildroot | Digi-Key Electronics
ฝัง
- เผยแพร่เมื่อ 14 มิ.ย. 2024
- Linux is a powerful operating system that can be compiled for a number of platforms and architectures. One of the biggest draws is its ability to be customized for an application. Tools like Buildroot, OpenWRT, and Yocto Project help us create custom Linux distributions for embedded systems.
In this video series, we will explore Buildroot and the Yocto Project. We also demonstrate how you might develop applications for embedded Linux. We will not dive into the specifics of how each of these systems work but give you a good starting place so you can read or watch more advanced material about working with embedded Linux.
See this written tutorial if you would like to review the commands issued in this tutorial for Buildroot: www.digikey.com/en/maker/proj...
To start, we provide some reasons and examples as to why you might want to use embedded Linux over other platforms, such as bare-metal programming on microcontrollers and an RTOS. Often, your application will dictate the use of one platform over another. Embedded Linux offers the ability to reuse high-level code written and tested by others that work across a variety of platforms. This can save you development time when you need things like networking, graphics, cryptography, audio, machine learning, etc.
We introduce Buildroot as one of the easiest tools to use for creating a custom Linux image. We demonstrate it by creating a Linux distribution for the STM32MP157D-DK1 single board computer. From there, we flash the distribution image onto an SD card and load Linux on the board, which allows us to log in with a serial terminal to do basic file manipulation and script writing.
Product Links:
www.digikey.com/en/products/d...
Related Videos:
• STM32MP1 workshop - 1 ...
Related Project Links:
www.digikey.com/en/maker/proj...
Related Articles:
forum.digikey.com/c/eewiki/li...
Learn more:
Maker.io - www.digikey.com/en/maker
Digi-Key’s Blog - TheCircuit www.digikey.com/en/blog
Connect with Digi-Key on Facebook / digikey.electronics
And follow us on Twitter / digikey - วิทยาศาสตร์และเทคโนโลยี
![One More Round [Maker Update] | Maker.io](http://i.ytimg.com/vi/w_mLmJ3PXjk/mqdefault.jpg)
I’m not native English speaker, but your pronunciation is perfect, I understand all words you speak, thank you
The timing of this series couldn't be more perfect than this for me.
Same here dude. Same.
Same here, my lichee pi nano will arrive in a couple Weeks and I already started to go deeper in the matter of Linux and C than I've ever done before.
YES! I am SOO happy to see this! Your STM32 series was a fantastic introduction to that micro controller family. If this series is even half as good as that then I am super excited!
I was just about to skip on the best Linux resource on the internet, thank god I clicked on this video. Please Please make a comprehensive series on the three (especially Yocto). Thanks alot guyz!
Top marks for clarity. Nice to see what can be a complex subject communicated so clearly.
This content is super high quality! Relevant, well considered, well presented = USEFUL!
Love it.
Thanks Shawn. I will book this weekend mainly for your great tutors in the past months & years!
Thanks Shawn, for your efforts in making these videos.
That is High Quality Content. It is worth creating a whole course even bigger than the tutorials that will be available with tasks and more detailed explanations!
The introduction is great. I have worked with buildroot on and off for years. You can split the build into components, boot loaders, kernel, device-tree, root filesystem. This makes updating the kernel easy as long as you can just update each part on your SD card. You can make these components from the buildroot build command line. The best way to figure this out is 'make help' in the buildroot directory, there is a lot of information there. Hope I have not just taken the subject of an up and coming episode of this series. Keep up the good work I will be able to point co-works at this series instead of writing lots of documentation.
You have not...I actually switch to Yocto starting in the next episode :) That's really cool to hear about how Buildroot can be split into components.
I've been working with Yocto on and off for a couple of years. It is extremely powerful. Just finished a custom build for a client using i.MX6 ULL chip. Never would have been able to do it without yocto. Looking forward to the series. I still have a lot to learn, I think my work flow needs improving. I've notice over the last three years the need for developers to be using Linux to sky rocket. I'm coming into contact with companies where only the admin staff are on Windows. Management on Mac. Everyone else on Linux.
You should really have a look at the ISAR project which is based off Yocto. It combines Yocto with prebuilt packages from debian/apt.
Does i.MX6 cost efeective? compared to stm32
buildroot is WAY easier than yocto. To date I have not seen anything that you could do with yocto that you cannot do in buildroot....easier. Yocto can take years to properly understand, buildroot....basically an afternoon. It is simpler but not hard to customize.
This is amazing. Looking forward to the next episode!
Excellent series - Thank you.
I use buildroot and yocto quite a bit, and welcome these videos.
Notes:
a) Append 'status=progress' to the dd line to have an indication of dd's progress.
b) When using usermod to add yourself to a group (here dialout), one needs to use 'newgrp dialout' to activate it - else you have to open a new terminal to get it activated.
Thanks a lot for all the work that went into making these videos!
may i ask, what do you use it for? I'm curious on what kind of career direction embedded linux could actually direct to
AWESOME! It took me the better part of the day to get this working on an STM32MP157C_DK2 - mostly due to many problems with VirtualBox, but man did I learn a lot! Thank you!
这个视频太棒了！UP主的发音非常精准清晰！
For dd command use "status=progress" to actually see the progress of dd command .
Nice tutorial !!!
while there are many buildroot guides on youtube, only ONE is explained by a guy in a bowtie. Respect
Great video! Build time for a raspberry pi zero w (v1.1) took my Thinkpad T470 about 1 hour and 9 minutes to run "make". Excited to learn more from this series!
I really love your tutorials Shawn
I like these series, keep them going
This was so clear and concise. Thank you!
Love your video, Shawn. Thank you!!
Great channel!
Direct and concise
Nice timing, I'm playing with a AllWinner D1 64 bit RISC-V board, for fun I want to do exactly this. It's on my ever growing stack of ToDo's...
Thanks as ever for all your work, it's excellent!
Risc V, cutting edge, does gcc compile for that ?
@@jyvben1520 Yes! :)
Thank you very much for making suck an informative video on buildroot. you made it really easy to understand.
Very good. Looking forward to seeing next videos 👍👍👍
Thank you for a wonderful video, it gave me a good introduction, i finnaly got my first Raspberry,and im excited to get started
waiting for next part !
I have been learning linux since before Red Hat's IPO. It's ability to run on old hardware, has made me always think about task oriented hardware. People throw old hardware to the curb because it is running slow. If it only has one task, it is a speed demon at that task
imagine the amount of old electronics in the landfill due to WINDOZE!!
dd status=progress option is available in Ubuntu since 16.04 ;)
These tutorials are gold
this is awesome, hopefully as great as the stm32 serie
Correction: We do not have to completely rebuild the entire image in buildroot when we make any changes. We can avoid distclean and buildroot build system will automatically detect which changes are made and it will only build those packages where you make the changes.
Good catch, thanks!
Very good quality stuff, thank you !
Very interesting, and very nicely explained.
If you add "status=progress" the the dd comand it will show the progress as it goes.
Great Video !!! Please, more !!!
Great helpful video! Thank u so much!
Good job Shawn.
17:40 Add `status=progress` to the `dd` command line. to show progress. Or pipe through `pv`.
Been wanting to know what buildroot is/does for some time. I feel that I now have a good foundation. Thanks.
to speed up make times: you can run make with the jobs flag. make -j12 for example for a system with 12 logical cores.
Oo! Can't wait to try next! lolz...still doing my first linux project!
Btw when using dd you can add status=progress to show output
Nice video series.... Thank you Mr. Clark Kent :)
wow ,im a bit late to the party but im glad i followed all the steps successfully 🎉😅, thank you sir.
This quality is too good to be free honestly
Thanks for this video 👍🏻
For dd command, using oflag=sync will force every byte written over SD instead of buffer and status=progress to show realtime transfer information
Good to know about the sync argument, thanks! status=progress does not work on my version of Linux Mint, for whatever reason (that status just shows up at the end after dd is done).
Good video.
I'm currious about the underlying process here.
Where does Buildroot find its cross-compiler and linker ?
Awesome Video! Try status=progress with dd command for progress bar
Harika bir video. Çok bilgilendirici
Thank you for your effort 🤍
Cool video, thanks :)
Would be nice if you could go through some options in buildroot and show how complicated it would be to do something like add an i2c port or add some files to the image.
That's something I'm planning to do in the next few episodes using Yocto :)
Well explained.
I'm definitely an openwrt fanboy. Routers are easy to come by (since no-one is happy with their 100Mb gear anymore) and have all the resources to be used as IoT controllers. And they are quite secure as openwrt is built with security in mind.
Are you saying you re-purpose the routers to do things besides being a router? Or do you just repurpose them as routers running openwrt?
You are champ dude🙌
@ShawnHymel The keyboard you are using looks and sounds amazing! What is it?
i am waiting part 2
Thank you
This is awesome. When's part two??
Part 2 dropped yesterday :) th-cam.com/video/2-PwskQrZac/w-d-xo.html
This guy looks like Henry Cavill.
I have wanted to dive into embedded Linux for a few years now and was wondering if you'd recommend this book: Mastering Embedded Linux Programming 3rd Edition
Amazing!
Hello Shawn and Digi-Key! Thanks for the amazing introduction to Embedded Linux and Buildroot!
how to use gcc on the generated embedded linux image.
because when i use pip to install python frameworks, i get a compile error, the system always works with the cross compiler that generated the linux image
Good question! From what I've gathered, you can't use Buildroot to include a compiler on the target (buildroot.org/downloads/manual/manual.html#faq-no-compiler-on-target). You can use another system (e.g. Yocto) to add such packages. In a future episode, I plan to show you how can cross-compile on your host machine to include a custom application in the target image.
Thank you!!
I was just looking for this content, and you made a series of tutorial about it... Can I ask that you take my tuition money?
Please start with an FPGA series!!
That guy is amazing
You can do motor control using FreeRTOS for instance, just use kernel unaware interrupts for time critical interrupts that do the control work and the rest can be easily handled by OS threads. The price you pay is less time for OS tasks...
i'm a fan of SoC with FPGA for motor control and ARM (maybe multi-core) running embedded linux. best of both worlds
Make sure you run the "sync" command after you run "dd" like that to be sure all the writes are actually flushed to the sd card before you remove it.
From what I understand, umount will do a sync before unmounting the drive. So long as I do a `umount` or `sync`, I should be good.
@@ShawnHymel you may be right, but in the video you said "now all we have to do is remove the card from our computer" so I figured a clarification would be good :)
@@AdamMaryniuk Good catch, thanks :) Agreed, `sync` or `umount` is always a good idea!
my stm32 board does not have a memory slot. what should be the right place to find the interface diagram. I can see stm32f429 is listed and I am using the Discovery board with OTG support.
18:18 How did you know UART 4 was tied to the on-board ST-Link debugger? And how did you know the config file has UART 4 used as the console port by default?
Thank youuuu . How I could run a dotnet app on Yocto image ?
Can you make video on odyssey stm32mp135d board for how to build a buildroot operating system on that board
Can I use STM32MP157f-dk2 kit along with this series?
Could this be customized for Old PC's e.g (some have as low as 32MB), I know it's out of video subject, but this one of few videos about Buildroot .
What are some simple projects I can do to practice this
Will stm32f446re can be used??
Can we use raspberry pi for development instead of stm32?
how to add build essential and ncurses packages? I am a layman and can only directly see this video to practice but there is an error
good But I met build error when I set an stm32f429 disco ... ubuntu 16.04
Hi, why is strict timing mentioned in baremetal when a RTOS is always mentioned for deterministic behaviour?
Great question! Most RTOSes can be made to be deterministic or non-deterministic, depending on how you configure the scheduler and heap allocation. As a result, your application is not guaranteed to be completely deterministic just because you use an RTOS (although, with the right settings, you can make it so).
I might not have described it correctly in the video...but my thoughts for "strict timing" for baremetal include things like needing to sample a sensor every 200 microseconds. A time slice in most RTOSes is 1-10ms, so an RTOS won't help you meet that timing requirement. You can combine baremetal techniques and an RTOS (e.g. use a hardware timer to set up a sampling schedule and feed the data to a FIFO that's read by an RTOS task).
@@ShawnHymel Understood!, thanks, I also check your videos about FreeRTOS, they are great, could you recommend us extra material (courses, books, etc) to learn more about FreeRTOS and embedded Linux?
How can I run my C program on this default Linux configuration ?
17:40 use ctrl+t to display dd progress.
Thanks for the tip! I'll give it a shot, but I don't know if it works on all flavors: askubuntu.com/questions/215505/how-do-you-monitor-the-progress-of-dd
Command line is to take charge. GUI is for spectators! 😎
Very true😂
Well, OpenWRT are general and not only for routers. And yes, it has packages, so you have packages that you don't need to rebuild to get.
I'd like to create my own portable device based on linux. How can I manage it?
I like gtkterm for a terminal program. This is a GUI program, and it runs under KDE with some extra baggage.
@2:06 I think you mean JTOS, as in Jitter Time Operating System.
Excellent I've been learning python for 2 years now. Was wondering if Linux would be useful in conjunction with python. I don't particularly care raspberry pi because of the amount of current it uses. Can't really do a stand alone project with it. But I'm glad brought up another board to use which is probably less of a energy hog.
Really cool that SpaceX uses Linux to run the rockets
In my opinion, Linux and Python are two peas in a pod. Even if you're not too interested in Raspberry Pi; Linux itself, as pointed out in the video, is a very popular and powerful operating system. Learning how to use Linux isn't too difficult if you're already familiar with systems like Windows or MacOS. There is also a massive community of developers and users to support you in your pursuits.
Python and Linux are both very useful in terms of embedded systems. SBC's and other small standalone electronics can be hard to develop for, especially if the hardware or applications are custom. This video series should elaborate more on the challenges of programming on embedded devices, but suffice it to say that having a good working knowledge of Linux is very handy if you're looking to program embedded devices yourself. I hope that helps.
Adafruit m0 express uses Circuitpython and uses less than 500 mA
Good vedio
Great overview! I needed this to see what I want to do with my Raspberry Pi. BTW, _router_ (a device that _routes_ packets) is pronounced identically to "rooter" because _route_ is pronounced identically to "root". A _router_ (a device that _routs_ things) would be a device that creates grooves in wood or metal, since the word there is _rout._
Always curious as to why Digico uses embedded windows instead of Linux for their audio consoles.
Most likely a business decision long ago, it allowed them to share the same code base with the offline software (which is only available for Windows). Personally I would love to see them switch to a linux based console with offline software ported to macOS. That would be such a massive rewrite that they aren’t likely to go that route unless some external factor forced their hand.
I get this error when I typed in "make stm32mp157a_dk1_defconfig" .
Error: "make: Nothing to be done for 'stm32mp157a_dk1_defconfig'"
I am using WSL2. Any idea what is the problem? I am in the current folder that is configs where I can see the file for stm32. But I get this error.
Hello Butterfruit,
i came across the same issue.
It turned out that i executed the "make stm157....." command in the "configs" folder.
When you're in the "buildroot" folder it works fine.
@@mike_lennies Thank you for taking a moment to answer that Mike. I really appreciate it!! You actually helped me out there.
@@mike_lennies Thanks dude
Do you double as Clark Kent?
Only on Tuesdays ;)
You can always install VirtualBox and run Linux installations from there. And there are always possible to make some USB devices visible to the Virtual machine running Mint, Ubuntu or Debian.
I don't see Android.
Why?
Is it totally unsuitable for IOT?
Too heavy. There have been attempts to create a version for IoT.
I'm sorry it was a bit confusing! I promise that if you take your ti over the next few days and weeks, tNice tutorials stuff will make sense. Most