Open briantdavis opened 8 years ago
I have successfully run some test initalization scripts, please see the most recent pull request.
As of now, It does no more than stated.
I have verified its functionality through a boot, however please note that I do not manage any possible errors during initialization.
I imagine that I could get the "Enable I2C" script working for the next commit.
The script now searches for and runs "Enable_third_i2c.sh"
However, I recently noticed that this script actually executes during startup AND shutdown which could be bad in its current form. I have started looking into it, but I may have some trouble understanding it.
So, the entire issue was the fact that I had a bad directory call in my init script, for details, see pull request 12.
It should work as intended.
It doesn't handle errors, but is that a concern with init scripts?
testenv to be deleted next commit
At the moment I need to run the "Enable_i2c" script as root each time I power-on the BBB to enable I2C2.
It would be advantageous to develop a location / script which is automatically executed as root upon power-on so that we can (for now) configure the board, for example Enable I2C2.
Eventually, we will want the DAQ application to automatically run upon power-up, so this will be essential for the flying article.