8.6 s after boot starts seems still to be quite early. You can can change the boot order in systemd e.g with Type=idle or with After=... An alternative might be: echo "@reboot root /pathto/myscript.sh" >> /etc/crontab HTH
On Fri, Jun 26, 2015 at 4:26 AM, terra ÜÝÜ <[email protected]> wrote: > running BeagleBoard.org Debian Image 2015-03-01 > > startup (from > https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time) > is invoked via; > > systemd > bash script has a delay, increased it to 2 min still same non-running of the > PRU. > > given the large delay; I have logged in and checked, program was not running > I executed it(via putty), and it ran 100% fine. > > I killed the program, waited for the start-up script to kick in > the start up script executed the program and its running fine. > > kinda not sure where to next? > > to recap > I login(via putty) > ps ax|grep myprogam > does not show my program running > I execute program > cd /home > myprogam & > > I kill the program > kill -9 myprogramPID > > 2 minutes pass, and the program executes and runs 100% good. > > If I restart login(via putty) and wait 2 minutes, the program executed but > no PRU activity. > > I do get, error below consistently upon boot-up, but does not seem to effect > the operation of the PRU. > root@beaglebone:~# dmesg|grep pru > [ 8.606803] omap_hwmod: pruss: failed to hardreset > root@beaglebone:~# > > > On Thursday, 25 June 2015 20:43:26 UTC+10, Dieter Wirz wrote: >> >> How do you invoke the startupscript? (Maybe it's to early during boot.) >> >> On Thu, Jun 25, 2015 at 10:35 AM, terra ÜÝÜ <[email protected]> wrote: >> > Hi, >> > >> > I have a basic application which use PRU1. program works 100% when >> > executes >> > as "root" from user space (via putty). >> > I have a bash start up script, which synchronizes with RTC and executes >> > my >> > program. >> > cat /usr/share/rtc_ds3231/clock_init.sh >> > >> > #!/bin/bash >> > sleep 15 >> > echo ds3231 0x68 > /sys/class/i2c-adapter/i2c-1/new_device >> > hwclock -s -f /dev/rtc1 >> > hwclock -w >> > /home/myprogram >> > >> > as a result, the time synch is working, the program executes (ps ax|grep >> > myprogram) shows it running; though no PRU1 activity. >> > I need to login as root (via putty) kill the process and start is again >> > (as >> > root), and it works just fine. Literally no other actions are taken, >> > killing >> > the program multiple times still results in 100% operation each time. >> > ps ax|grep myprogram >> > kill -9 myprogramPID >> > /home/myprogram & >> > >> > Kind help would be most appreciated >> > Thank You >> > >> > -- >> > 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. > > -- > 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. -- 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.
