Re: [yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+
Thanks Marek! I pretty sure it doesn't boot, but I haven't confirmed it as you suggested it. I have never connected to the uart interface directly on the GPIO or via bluetooth. It probably takes me more time to figure it out and to do this than trying the thud branch as @agherzan has mentioned here: https://github.com/agherzan/meta-raspberrypi/issues/373 I am also using meta-mender, do I need to upgrade all layers to thud than? Regards, Markus On Fri, 1 Feb 2019 at 13:17, Belisko Marek wrote: > On Fri, Feb 1, 2019 at 1:11 PM Markus W wrote: > >> Hi! >> >> I have been running a yocto image (sumo) on a raspberry 3 B+ without any >> problems, but wanted to test the new raspberry Pi 3 A+ board with it but I >> just get the Rainbow screen on boot. I have updated meta-openembedded to >> the latest sumo and meta-raspberry was still up to date with the latest >> (sumo) and still the same result. >> > >> My question: Has anybody been running sumo on a raspberrypi 3 a+ >> successfully? I have been googling around for issues but can't find >> anything on the new board and yocto. Seems that I am missing something. >> > Can you connect serial console and add enable_uart=1 to config.txt and > verify? This looks like it doesn't boot. You can also ask on [1] > >> >> Regards, >> Markus >> > -- >> > > [1] - https://github.com/agherzan/meta-raspberrypi/issues > > BR, > > marek > >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > > > -- > as simple and primitive as possible > - > Marek Belisko - OPEN-NANDRA > Freelance Developer > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > Tel: +421 915 052 184 > skype: marekwhite > twitter: #opennandra > web: http://open-nandra.com > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+
Hi! I have been running a yocto image (sumo) on a raspberry 3 B+ without any problems, but wanted to test the new raspberry Pi 3 A+ board with it but I just get the Rainbow screen on boot. I have updated meta-openembedded to the latest sumo and meta-raspberry was still up to date with the latest (sumo) and still the same result. My question: Has anybody been running sumo on a raspberrypi 3 a+ successfully? I have been googling around for issues but can't find anything on the new board and yocto. Seems that I am missing something. Regards, Markus -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer
Thanks Uwe!
I tried the global approach by adding the following to my local.conf file:
ROOTFS_POSTPROCESS_COMMAND += "my_setcap_function"
my_setcap_function() {
setcap cap_net_raw+eip ${IMAGE_ROOTFS}/usr/bin/node
}
But got the following warning:
WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: Function
my_setcap_function doesn't exist
I have tried to add the function into a recipe but this doesn't work
either. Where should the function be defined?
Regards,
Markus
On Fri, 9 Nov 2018 at 15:35, Uwe Geuder wrote:
> Hi!
>
>
> On Fri, Nov 9, 2018 at 12:16 PM Markus W markus4dev-at-gmail.com wrote:
>
> > On Thu, 8 Nov 2018 at 22:53, Piotr Tworek wrote:
> ...
> >> pkg_postinst_ontarget_${PN} () {
> >>setcap cap_net_raw+eip $D${bindir}/node
> >> }
> ...
> > How can this be achieved when the rootfs is created and not on first
> > boot? I would like not to ship libcap binaries with the target in
> > production.
>
> Ideally I would do it "locally" in do_install of the node recipe (you can
> append extra statements to the task in your own .bbappend in your own
> layer, don't edit existing recipes)
>
> That of course requires that the package manager preserves the
> capabilites. I have no experience which package manager would do
> or not do that.
>
> "Globally" you can do it by appending a new function to
> ROOTFS_POSTPROCESS_COMMAND
>
> https://www.yoctoproject.org/docs/2.5.1/mega-manual/mega-manual.html#var-
> ROOTFS_POSTPROCESS_COMMAND
>
> This is done in your image recipe.
>
> Regards,
>
> Uwe Geuder
> Neuro Event Labs Oy
> Tampere, Finland
> uwe.gex...@neuroeventlabs.com (Bot check: fix one obvious typo)
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer
Thanks Piotr, that worked!
How can this be achieved when the rootfs is created and not on first boot?
I would like not to ship libcap binaries with the target in production.
/Markus
On Thu, 8 Nov 2018 at 22:53, Piotr Tworek wrote:
> Hi Markus,
>
> Have you tried doing it in the postinst step executed on your target? Try:
>
> pkg_postinst_ontarget_${PN} () {
> setcap cap_net_raw+eip $D${bindir}/node
> }
>
> RDEPENDS_${PN} += "libcap-bin"
>
> /ptw
>
> > I have tested to set capabilities on the node binary within a custom
> recipe
> > (custom layer) but that failed.
> >
> > pkg_postinst_${PN} () {
> > setcap cap_net_raw+eip $D${bindir}/node
> > }
> > PACKAGE_WRITE_DEPS = "libcap-native"
> > RDEPENDS_${PN} = "libcap"
> >
> > The error message:
> >
> > ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: [log_check]
> > core-image-full-cmdline: found 1 error message in the logfile:
> > [log_check] Failed to set capabilities on file
> >
> `/home/ubuntu/yocto-sumo/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core
> > -image-full-cmdline/1.0-r0/rootfs/usr/bin/node' (No such file or
> directory)
> >
> > When I check the node binary is there in the rootfs directory. It seems
> > that when the the pkg_postinst function is executed the node binary is
> not
> > there.
> >
> > What am I missing? Any answer is much appreciated!
> >
> > Regards,
> > Markus
> >
> > On Wed, 7 Nov 2018 at 11:32, Markus W wrote:
> > > Hi!
> > >
> > > Background:
> > > In my raspberry project I am developing a nodejs app that needs access
> to
> > > bluetooth/ble device. I want to run the node application as non root
> user
> > > for security reasons. In order to get access from within the app, the
> node
> > > binary need to have the following capability cap_net_raw+eip set. I am
> > > using the nodejs recipe from meta-oe and added it in my local.conf:
> > >
> > > IMAGE_INSTALL_append = " nodejs i2c-tools bluez5 kernel-image
> > > kernel-devicetree"
> > >
> > > Question:
> > > Where should I apply the following command? setcap cap_net_raw+eip
> > > /usr/bin/node
> > >
> > > What are my options? Can I create a recipe in a different package that
> > > will apply the above command on the meta-oe package for the nodejs
> recipe?
> > >
> > > I have been following this thread (
> > > https://lists.yoctoproject.org/pipermail/yocto/2016-June/030811.html),
> > > but the node binaries and my node-app are in different layers and
> > > packages.
> > >
> > > Any advice how to do this is much appreciated?
> > >
> > > Regards,
> > > Markus
>
>
>
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer
I have tested to set capabilities on the node binary within a custom recipe
(custom layer) but that failed.
pkg_postinst_${PN} () {
setcap cap_net_raw+eip $D${bindir}/node
}
PACKAGE_WRITE_DEPS = "libcap-native"
RDEPENDS_${PN} = "libcap"
The error message:
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: [log_check]
core-image-full-cmdline: found 1 error message in the logfile:
[log_check] Failed to set capabilities on file
`/home/ubuntu/yocto-sumo/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/rootfs/usr/bin/node'
(No such file or directory)
When I check the node binary is there in the rootfs directory. It seems
that when the the pkg_postinst function is executed the node binary is not
there.
What am I missing? Any answer is much appreciated!
Regards,
Markus
On Wed, 7 Nov 2018 at 11:32, Markus W wrote:
> Hi!
>
> Background:
> In my raspberry project I am developing a nodejs app that needs access to
> bluetooth/ble device. I want to run the node application as non root user
> for security reasons. In order to get access from within the app, the node
> binary need to have the following capability cap_net_raw+eip set. I am
> using the nodejs recipe from meta-oe and added it in my local.conf:
>
> IMAGE_INSTALL_append = " nodejs i2c-tools bluez5 kernel-image
> kernel-devicetree"
>
> Question:
> Where should I apply the following command? setcap cap_net_raw+eip
> /usr/bin/node
>
> What are my options? Can I create a recipe in a different package that
> will apply the above command on the meta-oe package for the nodejs recipe?
>
> I have been following this thread (
> https://lists.yoctoproject.org/pipermail/yocto/2016-June/030811.html),
> but the node binaries and my node-app are in different layers and packages.
>
> Any advice how to do this is much appreciated?
>
> Regards,
> Markus
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
Probably, I'm learning ;-)
On Wed, 7 Nov 2018 at 12:59, Outback Dingo wrote:
> couldnt this have been a udev_append.bb
>
> instead of writing your own my-rules
> On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote:
> >
> > This my bb file and than I have added the following to local.conf
> IMAGE_INSTALL_append = " my-rules ...".
> >
> > SUMMARY = "My rules"
> > LICENSE = "CLOSED"
> > PR = "r1"
> >
> > SRC_URI = "file://90-interfaces.rules"
> >
> > do_install[nostamp] = "1"
> > do_unpack[nostamp] = "1"
> >
> > do_install () {
> > install -d ${D}${sysconfdir}/udev/rules.d
> > install -m 0666 ${WORKDIR}/90-interfaces.rules
> ${D}/etc/udev/rules.d/90-interfaces.rules
> >
> > }
> >
> > FILES_${PN} += " /etc/udev/rules.d/90-interfaces.rules"
> >
> > PACKAGES = "${PN}"
> > PROVIDES = "my-rules"
> >
> > Hope this helps
> >
> > /Markus
> >
> > On Wed, 7 Nov 2018 at 12:41, Outback Dingo
> wrote:
> >>
> >> so curious, as im trying to add 2 udev rules also that i require in my
> >> build, so how was your recipe configured?
> >>
> >> mine keeps telling me i have a conflict between packages as they both
> >> install files to the same name and same place
> >> On Wed, Nov 7, 2018 at 4:53 PM Outback Dingo
> wrote:
> >> >
> >> >
> >> >
> >> > On Wed, Nov 7, 2018, 16:44 Markus W >> >>
> >> >> I have resolved this issue. My problem was that in my layer I have a
> >> >> recipe-core and within that I had the following structure
> >> >> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir
> on
> >> >> the same level.
> >> >>
> >> >> By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
> >> >> suddenly worked.
> >> >>
> >> >> Cool
> >> >>
> >> >>
> >> >> Regards,
> >> >> Markus
> >> >>
> >> >> On Tue, 6 Nov 2018 at 14:06, Outback Dingo
> wrote:
> >> >> >
> >> >> > On Tue, Nov 6, 2018 at 11:57 AM Markus W
> wrote:
> >> >> > >
> >> >> > > Hi!
> >> >> > >
> >> >> > > I want to append the rules in the
> >> >> > > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules
> below from
> >> >> > > within my own recipe. I can´t figure out how to do that.
> >> >> > >
> >> >> > > I have tried to add those rules as separate rules file in a
> recipe in
> >> >> > > my own layer. After the build I can see that the rules file is
> in the
> >> >> > > correct directory /etc/udev/rules.d (next to 99-com.rules) but
> the
> >> >> > > rules didn't get applied. The groups below I have created by
> >> >> > > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r
> i2c;
> >> >> > > -r gpio") in a different layer with a higher priority than the
> layer
> >> >> > > with the rules recipe.
> >> >> > >
> >> >> > > Not sure why this is not working. Any suggestions?
> >> >> > >
> >> >> > > 90-interfaces.rules file:
> >> >> > >
> >> >> > > SUBSYSTEM=="input", GROUP="input", MODE="0660"
> >> >> > > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> >> >> > > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> >> >> > > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
> >> >> > >
> >> >> > > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> >> >> > > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> >> >> > > chown -R root:gpio /sys/class/gpio && chmod -R 770
> /sys/class/gpio;\
> >> >> > > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> >> >> > > /sys/devices/virtual/gpio;\
> >> >> > > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> >> >> > > '"
> >> >> > >
> >> >> >
> >> >> > might help to post the recipe used.
> >> >> >
> >> >> >
> >> >> > > Regards,
> >> >> > > Markus
> >> >> > > --
> >> >> > > ___
> >> >> > > yocto mailing list
> >> >> > > yocto@yoctoproject.org
> >> >> > > https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
This my bb file and than I have added the following to local.conf
IMAGE_INSTALL_append = " my-rules ...".
SUMMARY = "My rules"
LICENSE = "CLOSED"
PR = "r1"
SRC_URI = "file://90-interfaces.rules"
do_install[nostamp] = "1"
do_unpack[nostamp] = "1"
do_install () {
install -d ${D}${sysconfdir}/udev/rules.d
install -m 0666 ${WORKDIR}/90-interfaces.rules
${D}/etc/udev/rules.d/90-interfaces.rules
}
FILES_${PN} += " /etc/udev/rules.d/90-interfaces.rules"
PACKAGES = "${PN}"
PROVIDES = "my-rules"
Hope this helps
/Markus
On Wed, 7 Nov 2018 at 12:41, Outback Dingo wrote:
> so curious, as im trying to add 2 udev rules also that i require in my
> build, so how was your recipe configured?
>
> mine keeps telling me i have a conflict between packages as they both
> install files to the same name and same place
> On Wed, Nov 7, 2018 at 4:53 PM Outback Dingo
> wrote:
> >
> >
> >
> > On Wed, Nov 7, 2018, 16:44 Markus W >>
> >> I have resolved this issue. My problem was that in my layer I have a
> >> recipe-core and within that I had the following structure
> >> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
> >> the same level.
> >>
> >> By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
> >> suddenly worked.
> >>
> >> Cool
> >>
> >>
> >> Regards,
> >> Markus
> >>
> >> On Tue, 6 Nov 2018 at 14:06, Outback Dingo
> wrote:
> >> >
> >> > On Tue, Nov 6, 2018 at 11:57 AM Markus W
> wrote:
> >> > >
> >> > > Hi!
> >> > >
> >> > > I want to append the rules in the
> >> > > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below
> from
> >> > > within my own recipe. I can´t figure out how to do that.
> >> > >
> >> > > I have tried to add those rules as separate rules file in a recipe
> in
> >> > > my own layer. After the build I can see that the rules file is in
> the
> >> > > correct directory /etc/udev/rules.d (next to 99-com.rules) but the
> >> > > rules didn't get applied. The groups below I have created by
> >> > > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r
> i2c;
> >> > > -r gpio") in a different layer with a higher priority than the layer
> >> > > with the rules recipe.
> >> > >
> >> > > Not sure why this is not working. Any suggestions?
> >> > >
> >> > > 90-interfaces.rules file:
> >> > >
> >> > > SUBSYSTEM=="input", GROUP="input", MODE="0660"
> >> > > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> >> > > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> >> > > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
> >> > >
> >> > > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> >> > > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> >> > > chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
> >> > > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> >> > > /sys/devices/virtual/gpio;\
> >> > > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> >> > > '"
> >> > >
> >> >
> >> > might help to post the recipe used.
> >> >
> >> >
> >> > > Regards,
> >> > > Markus
> >> > > --
> >> > > ___
> >> > > yocto mailing list
> >> > > yocto@yoctoproject.org
> >> > > https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-oe] Set linux capabilities on binary on a recipe in meta-oe layer
Hi! *Background:* In my raspberry project I am developing a nodejs app that needs access to bluetooth/ble device. I want to run the node application as non root user for security reasons. In order to get access from within the app, the node binary need to have the following capability *cap_net_raw+eip *set. I am using the nodejs recipe from meta-oe and added it in my local.conf: IMAGE_INSTALL_append = " *nodejs* i2c-tools bluez5 kernel-image kernel-devicetree" *Question:* Where should I apply the following command? *setcap cap_net_raw+eip /usr/bin/node* What are my options? Can I create a recipe in a different package that will apply the above command on the meta-oe package for the nodejs recipe? I have been following this thread ( https://lists.yoctoproject.org/pipermail/yocto/2016-June/030811.html), but the node binaries and my node-app are in different layers and packages. Any advice how to do this is much appreciated? Regards, Markus -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
I have resolved this issue. My problem was that in my layer I have a
recipe-core and within that I had the following structure
udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
the same level.
By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
suddenly worked.
Regards,
Markus
On Tue, 6 Nov 2018 at 14:06, Outback Dingo wrote:
>
> On Tue, Nov 6, 2018 at 11:57 AM Markus W wrote:
> >
> > Hi!
> >
> > I want to append the rules in the
> > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
> > within my own recipe. I can´t figure out how to do that.
> >
> > I have tried to add those rules as separate rules file in a recipe in
> > my own layer. After the build I can see that the rules file is in the
> > correct directory /etc/udev/rules.d (next to 99-com.rules) but the
> > rules didn't get applied. The groups below I have created by
> > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
> > -r gpio") in a different layer with a higher priority than the layer
> > with the rules recipe.
> >
> > Not sure why this is not working. Any suggestions?
> >
> > 90-interfaces.rules file:
> >
> > SUBSYSTEM=="input", GROUP="input", MODE="0660"
> > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
> >
> > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> > chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
> > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> > /sys/devices/virtual/gpio;\
> > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> > '"
> >
>
> might help to post the recipe used.
>
>
> > Regards,
> > Markus
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
Hi!
I want to append the rules in the
recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
within my own recipe. I can´t figure out how to do that.
I have tried to add those rules as separate rules file in a recipe in
my own layer. After the build I can see that the rules file is in the
correct directory /etc/udev/rules.d (next to 99-com.rules) but the
rules didn't get applied. The groups below I have created by
inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
-r gpio") in a different layer with a higher priority than the layer
with the rules recipe.
Not sure why this is not working. Any suggestions?
90-interfaces.rules file:
SUBSYSTEM=="input", GROUP="input", MODE="0660"
SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
/sys/devices/virtual/gpio;\
chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
'"
Regards,
Markus
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi]
Hi!
I want to append the rules in the
recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
within my own recipe. I can´t figure out how to do that.
I have tried to add those rules as separate rules file in a recipe in
my own layer. After the build I can see that the rules file is in the
correct directory /etc/udev/rules.d (next to 99-com.rules) but the
rules didn't get applied. The groups below I have created by
inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
-r gpio") in a different layer with a higher priority than the layer
with the rules recipe.
Not sure why this is not working. Any suggestions?
90-interfaces.rules file:
SUBSYSTEM=="input", GROUP="input", MODE="0660"
SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
/sys/devices/virtual/gpio;\
chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
'"
Regards,
Markus
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] Problem enabling w1-gpio
Hi again! I should have mentioned that the image will also include a meta-mender layer for updates. Additionally an extra layer for setting up the wifi & ble for rpi and an application layer. So I am looking for an automated approach where I can make production updates through mender. I also have tried the RPI_EXTRA_CONFIG flag to set dtoverlay that didn't make any difference. INHERIT += "mender-full" MACHINE = "raspberrypi3" RPI_USE_U_BOOT = "1" MENDER_PARTITION_ALIGNMENT = "4194304" MENDER_BOOT_PART_SIZE_MB = "40" IMAGE_INSTALL_append = " nodejs bluez5 kernel-image kernel-devicetree mender-wait-for-timesync" IMAGE_FSTYPES_remove += " rpi-sdimg" DISTRO_FEATURES_append = " bluez5 bluetooth systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "" IMAGE_FSTYPES = "ext4" SDIMG_ROOTFS_TYPE = "ext4" # SPI, i2c and w1-gpio settings ENABLE_SPI_BUS = "1" ENABLE_I2C = "1" RPI_EXTRA_CONFIG = ' \n \ dtoverlay=w1-gpio \n \ ' On Sat, 6 Oct 2018 at 03:13, Khem Raj wrote: > On Fri, Oct 5, 2018 at 9:27 AM Andrei Gherzan wrote: > > > > Hi Markus, > > > > On Fri, Oct 5, 2018 at 4:28 PM Markus W wrote: > >> > >> Hi! > >> > >> I'm creating a yocto image (sumo) for the raspberrypi and got stuck on > how to enable the one-wire interface on boot. > >> > >> I have enabled the SPI bus and I2C in my local.conf file. > >> > >> ENABLE_SPI_BUS = "1" > >> ENABLE_I2C = "1" > >> > >> and checked that they are loaded on boot. > >> > >> I'm struggling to figure out where to set "dtoverlay=w1-gpio" and how > to enable the w1-gpio module on boot. The /boot/config.txt file doesn't > exist by default after startup. If I create this file with the line above > directly on the rpi and reboot it, the w1-gpio interface is still not > enabled. > > > > > > /boot when you run up the image is on the rootfs while the file you are > looking for is in the boot partition. You will need to mount (or set a boot > mount - fstab, systemd etc) the boot partition (p1) and you will see the > file afterwards. Alternatively, just mount the SD card's partitions on your > working station and modify the file offline. > > > > if one starts using wic image instead of old sd-card image types then > boot is automounted. > > Just add > > IMAGE_FSTYPES += "wic.xz" > > for nice xz compressed wic image. > > > --- > > Andrei > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] Problem enabling w1-gpio
Hi! I'm creating a yocto image (sumo) for the raspberrypi and got stuck on how to enable the one-wire interface on boot. I have enabled the SPI bus and I2C in my local.conf file. ENABLE_SPI_BUS = "1" ENABLE_I2C = "1" and checked that they are loaded on boot. I'm struggling to figure out where to set "dtoverlay=w1-gpio" and how to enable the w1-gpio module on boot. The /boot/config.txt file doesn't exist by default after startup. If I create this file with the line above directly on the rpi and reboot it, the w1-gpio interface is still not enabled. What is the proper way to do this? Thanks for any help! Regards, Markus -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
