Embedded

263 readers

1 users here now

We talk and share about anything Embedded, including;

PCB Design.
Hardware architecture.
Embedded platforms and chipsets.
Protocols.
Embedded programming.
Digital Logic.
FPGA.
VHDL, System Verilog...etc.
Intel Quartus, AMD Xilinx...etc.
DIP, DSP.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

Ategon@programming.dev

Mustafaalbazy@programming.dev

Embedded Linux without Yocto (programming.dev)

submitted 2 weeks ago* (last edited 2 weeks ago) by jkercher@programming.dev to c/embedded@programming.dev

8 comments fedilink hide all child comments

Hello all, I'm an embedded software guy struggling with Yocto. I'm not asking for assistance as I cannot be saved. Rather, I'd like to make my own. How hard it would be to put a Linux distro onto a device without it? For example, if I were to get a perfectly good distro (let's just say Debian) with the right architecture going in a container. Is there a simple way to combine that with u-Boot, and other crap from a SoC manufacturer to build an image? If that is oversimplifying, I've done Linux from scratch before, and I'd be willing to go that route as well. I guess the issue boils down to the specifics like building the image and anything else that I'm not aware of.

So, what part of this idea is going to be a lot harder than I'm giving it credit for?

By the way, I'm aware of Buildroot. This is more for learning purposes, and who knows... maybe I will actually make something out of it.

you are viewing a single comment's thread
view the rest of the comments

[–] tazvok@lemmy.world 2 points 1 week ago (1 children)

The difficult part of this is building the filesystem and dependencies you want and having them be happy with your cross compiler. NXP parts have decent support for running whatever you want on them and can boot a raw kernel+dtb+United straight from u-boot

[–] jkercher@programming.dev 1 points 1 week ago

Yeah. Using yocto, I know what I want and can do it in Linux. But, "how make yocto do it" becomes an entirely different thing. It would be nice to have a simple container->image pipeline.