Am Freitag, 29. März 2019 21:18:58 UTC+1 schrieb CM:
>
> Your suggested steps did work to connect uio5, thanks! It reverts to the
> disconnected state on reboot, however.
>
Good!
>
> I do have several services running, including for the IMU and the analog
> in (using libpruio). So my service isn't explicitly changing uio5, but
> maybe it invokes it too early in the boot process.
>
Sure, your service must not start before the driver is loaded. Here is an
example how I start one of my projects
File /etc/systemd/system/solar.service
[Unit]
Description=Start controller (/etc/default/solar-regler.sh)
[Service]
Type=oneshot
ExecStart=/etc/default/solar-regler.sh
StandardOutput=tty
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
File /etc/default/solar-regler.sh (the program to start is called
solar-regler)
#!/bin/sh -e
# load PRU kernel driver and start contoller (Jessie)
uio=/dev/uio5
# wait until kernel driver created the socket nodes
until test -e ${uio}; do sleep 1; done
# start controller
/usr/local/bin/solar-regler &
Regards
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/1763291d-3475-4741-9fb0-cfb4ef1dd270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
