Background: I'm trying to bring up the pi zero w's bluetooth using systemd. Started with rocko and then moved to 'master' of meta-raspberry pi, sync'd about a week ago after noticing that there were some recent updates in this area.
There was an initial problem with /dev/serial1 not showing up...I found udev-rules-rpi.bb, added it to my layer, and when it still didn't show up in my rootfs, I punted and installed it in /etc/udev/rules.d by hand and now /dev/serial1 shows up. Given time, I can probably fix the recipe on my own, so moving on. But brcm43438.service still fails on boot. Despite having "After=dev-serial1.device" in the service Unit section, it fails with: Mar 17 16:21:13 raspberrypi0-wifi systemd[1]: Started Broadcom BCM43438 bluetooth HCI. Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't open serial port: No such file or directory Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't initialize device: No such file or directory Mar 17 16:21:14 raspberrypi0-wifi systemd[1]: [[0;1;39mbrcm43438.service: Main process exited, code=exited, status=1/FAILURE[[0m Mar 17 16:21:14 raspberrypi0-wifi systemd[1]: [[0;1;39mbrcm43438.service: Unit entered failed state.[[0m Mar 17 16:21:14 raspberrypi0-wifi systemd[1]: [[0;1;39mbrcm43438.service: Failed with result 'exit-code'.[[0m If, after booting and ssh'ing into pi, I restart the service, it starts successfully. Any hints about what I might change to get the brcm43438.service to start correctly the first time (every time)? John
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto