SOLUTION
the pru wasn't finding the file, because path is not set
1. #!/bin/bash
2. sleep 45
3. *cd /home*
4. /home/main
On Friday, 26 June 2015 17:56:36 UTC+10, Dieter Wirz wrote:
>
> 8.6 s after boot starts seems still to be quite early. You can can
> change the boot order in sy
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 ÜÝÜ wrote:
> running BeagleBoard.org
if someone who has the time and know how, could quickly test would be
appreciated;
I have made a quick program, which uses the user LEDs
same behavior; works great when executed from console, does not work when
executed at boot time
main.cpp
//
#include
#include
#include
#include
#i
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
How do you invoke the startupscript? (Maybe it's to early during boot.)
On Thu, Jun 25, 2015 at 10:35 AM, terra ÜÝÜ 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 synchron
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/i
