When the executable is not successful, the journalctl output stops with the following line:
> Jan 01 00:00:07 beaglebone kernel: gpiochip_add: registered GPIOs 0 to 31 > on device: gpio > when the executable is successful, this line follows: > Jan 01 00:00:07 beaglebone kernel: OMAP GPIO hardware version 0.1 > Why would the beaglebone black stop after the gpiochip_add? I am getting the same results using crontab and the service method below. For some reason the executable file is being cleared most of the time after being called at boot up. 1. Compile the required code. 2. Create a bash script that will launch the code at boot/ startup cd /usr/bin/ Type nano <scriptname.sh> #!/bin/bash /home/root/<name_of_compiled_code> Save and grant execute permission chmod u+x /usr/bin/<scriptname>.sh 3. Create the service nano /lib/systemd/<scriptname>.service 4. Edit the above file as necessary to invoke the different functionalities like network. Enable these only if the code needs that particular service. Disable unwanted ones to decrease boot time. [Unit] Description=<description of code> After=syslog.target network.target [Service] Type=simple ExecStart=/usr/bin/<scriptname>.sh [Install] WantedBy=multi-user.target 5. Create a symbolic link to let the device know the location of the service. cd /etc/systemd/system/ ln /lib/systemd/<scriptname>.service <scriptname>.service 6. Make systemd reload the configuration file, start the service immediately (helps to see if the service is functioning properly) and enable the unit files specified in the command line. systemctl daemon-reload systemctl start <scriptname>.service systemctl enable <scriptname>.service -- 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]. For more options, visit https://groups.google.com/d/optout.
