• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 932 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

Compiler/AM3352: using poky/yocto to create a read-only-filesystem with systemd

Compiler/AM3352: deploying kernel modules in squashfs output from yocto/poky

Richard_McAleer
Intellectual 460 points
Part Number: AM3352


Tool/software: TI C/C++ Compiler

Hi

I am working at present on a board based on the am335x-evm and beaglebone black; using poky/yocto to build the system.
I the past I have had everything I need working from a hand rolled soultion using an old TISDK.
It will be booting and running from SPI NOR flash: with u-boot lifting the dtb and kernel in to RAM before launching the kernel with a squashfs ro-ROOTFS.

I have defined a custom image: myboard-image-debug and can build that happily.

At present in my build/tmp/deploy/images/myboard-image-debug I have seperate artefacts for: MLO, uboot, zImage, dtb, rootfs.squashfs, modules-myboard.tgz (along with some others while I do most of the development on an SDCARD)

What am am trying to work out at the moment is how to incorporate any kernel modules I need in to the squashfs that is created for the file system?
I hope to have most drivers built in to the kernel but previously it was necessary to modprobe the g_multi usb gadget.

One thought I've had would be to add an override to the do_install for the linux-ti-staging?

Thanks for any suggestions you can provide

All the best
- Richard

  • 0
    TI__Mastermind 30736 points

    Richard,

    You can build g_mult in and pass parameters to it via the kernel command line:

    optargs='g_ether.host_addr=aa:bb:cc:dd:33:52'

    This can be set via U-Boot.

    The other options you list may certainly be valid and might be worth exploring with the broader Yocto community. 

    Thanks.

  • 0 in reply to RonB
    Intellectual 460 points

    looks as though the solution is to add "kernel-modules" to the IMAGE_INSTALL variable for the image recipe

    that results in the modules directory being created within /lib of the rootfs 

    Hope that helps anyone else looking for this

    All the best

    - Richard