Thanks for your interest in the Intel Edison Platform.
We would like to know if you are receiving some error message after enabling the script or while it is running. Also, we’d like to share this link: How to create a system service with systemd on Edison and Galileo’s eglibc image, this procedure is similar to the one you provided, however, it could help you.
Here is the problem...
To use Edison in BLE mode with Bleno, you need to run this at each restart
rfkill unblock bluetooth
killall bluetoothd (or, more permanently) systemctl disable bluetooth
hciconfig hci0 up
What I need to figure out, and need help with, is where to put these 3 lines in the startup script (whether your link or mine) . Do I need to create a specific service file (like in the example, in which case, what I have do not work) or do I update an existing script.
You can create a script and include those commands there, in order to do it, follow these steps:
- Create the script: vi my_script.sh
#!/bin/bash # My first script rfkill unblock bluetooth killall bluetoothd (or, more permanently) systemctl disable bluetooth hciconfig hci0 up
2. Set up permission: chmod u+x my_script.sh
Once you have created your script, we have to create a system service:
- Create the service file here: /etc/system/system
- /etc/systemd/system# vi my_service.service
[Unit] Description = Setting up Edison BLE After = network.service [Service] ExecStart =/bin/bash /home/root/my_script.sh [Install] WantedBy = multi-user.target
3. Enable the service: systemctl enable my_service.service
Now that you have created the script and enabled the service, every time you reboot the Edison your script should run and configure the Edison.
Hope you find this information useful. If you any question please let us know and we’ll happy to help you.
We would like to know if you tried our previous suggestions to create the script and the system service, also, if you have any question, let us know please.
Thanks for checking back in we've been running some tests based on the script and it looks like it is working. Seems that our mistake was trying to put all the "startup" scripts in one place.