jkercher

joined 1 month ago
[–] 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.

[–] jkercher@programming.dev 2 points 1 week ago* (last edited 1 week ago) (1 children)

Right now, the most common target we have at work is variscite imx6,7 and 8. Nxp has leaned heavily into yocto. To be clear, this would be an outside of work thing, but I'll probably yoke one of our dev boards.

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

Hey! I know the guy working on this. Super cool, detail oriented guy.

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

Ha. I've never used buildroot, but I think I'm going to have a go at it. I promise not to use python ;]

Thank you for the insight.

6
submitted 1 week ago* (last edited 1 week ago) by jkercher@programming.dev to c/embedded@programming.dev
 

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.