Become a leader in the IoT community!

Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.

Step 1 of 5

CREATE YOUR PROFILE *Required

OR
Step 2 of 5

WHAT BRINGS YOU TO DEVHEADS? *Choose 1 or more

Connect & collaborate 🀝with other tech professionals
Learn & Grow πŸ“š
Contribute Experience & Expertise πŸ”§
Step 3 of 5

WHAT'S YOUR INTEREST OR EXPERTISE? *Choose 1 or more

Hardware Design πŸ’‘
Embedded Software πŸ’»
Edge Networking ⚑
Step 4 of 5

Personalize your profile

Step 5 of 5

Read & agree to our COMMUNITY RULES

  1. We want this server to be a welcoming space! Treat everyone with respect. Absolutely no harassment, witch hunting, sexism, racism, or hate speech will be tolerated.
  2. If you see something against the rules or something that makes you feel unsafe, let staff know by messaging @admin in the "support-tickets" tab in the Live DevChat menu.
  3. No age-restricted, obscene or NSFW content. This includes text, images, or links featuring nudity, sex, hard violence, or other graphically disturbing content.
  4. No spam. This includes DMing fellow members.
  5. You must be over the age of 18 years old to participate in our community.
  6. You agree to our Terms of Service (https://www.devheads.io/terms-of-service/) and Privacy Policy (https://www.devheads.io/privacy-policy)
By clicking "Finish", you have read and agreed to the our Terms of Service and Privacy Policy.

Overriding CMDLINE_ROOTFS in Yocto for Raspberry Pi

I’m trying to make some changes to the cmdline that’s passed to my Linux kernel at boot. I see a recipe provided by meta-raspberrypi called `rpi-cmdline` which defines a variable `CMDLINE_ROOTFS ?= …`. I am trying to override that variable. I’ve tried in two places:
1. In my image recipe, by just adding `CMDLINE_ROOTFS = “…”`
2. In `build/conf/local.conf` where I tried appending the same line defining the value.

However when I build and look at the resulting `cmdline.txt` file, the variable change doesn’t seem to have taken as the defaults are still used. Am I misunderstanding variable scoping for bitbake recipes perhaps?

  1. ssnover#0000

    Naturally, got something working right after asking for help. I ran `bitbake rpi-cmdline` and that caused the file to regenerate. It’s not clear to me how I would get it to regenerate when building the main image target with `bitbake megabit-image-base`. I guess I need to express to `bitbake` that there’s a dependency in some way?

  2. ming_58391#0000

    BitBake is looking for a change in the recipe.
    When you added `CMDLINE_ROOTFS` to either your image recipe or `local.conf` that does not tell BitBake that the _recipe_ has changed.

    The was Yocto expects you to do it is to create a `.bbappend` file. So in your case, in your instance you would create a file in your layer `meta-your-layer/recipes-bsp/bootfiles/rpi-cmdline_%.bbappend` and put the `CMDLINE_ROOTFS` in there.

    Now the hash of the append file is part of the has of the recipe. If you then change the append file, BitBake sees that the recipe has changed and will re-build it.

  3. ssnover#0000

    Oh interesting, does bitbake literally append the contents of bbappend files during its parse? That makes it much more intuitive, I was looking for variables similar to `DEPENDS`.

    Thank you!

CONTRIBUTE TO THIS THREAD

Browse other questions tagged 

Leaderboard

RANKED BY XP

All time
  • 1.
    Avatar
    @Nayel115
    1620 XP
  • 2.
    Avatar
    @UcGee
    650 XP
  • 3.
    Avatar
    @melta101
    600 XP
  • 4.
    Avatar
    @chitour
    600 XP
  • 5.
    Avatar
    @lifegochi
    250 XP
  • 6.
    Avatar
    @Youuce
    180 XP