Not positive, but I think you misnamed the file in 
/lib/systemd/system/config_custom.sh when it should have ended in service.


On Monday, April 1, 2019 at 10:15:30 AM UTC-4 catalin...@gmail.com wrote:

> Your issue might be different, depending on what you have installed, but 
> I'll write down what solution worked for me(I used socket.io and 
> serialport):
> - clean install of Debian 8.3(should be the same for newer dists)
> - npm install socket.io
> - npm install serialport
> - apt-get update
> - apt-get dist-upgrade
> - cd /var/lib/cloud9 npm update
>
> - create config_custom.sh
> - nano /usr/bin/config_custom.sh
> #!/bin/bash
> config-pin P9.24 uart 
> config-pin P9.26 hart
>
> - set execution rights
> - chmod u+x /usr/bin/config_custom.sh
> - create service 
> - nano /lib/systemd/system/config_custom.sh
>
> [Unit]
> Description=Config uart1 ex tx pins
> After=generic-board-startup.service
>
> [Service]
> Type=simple
> ExecStart=/usr/bin/config_custom.sh
>
> [Install]
> WantedBy=multi-user.target
>
> - enable service
> systemctl daemon-reload
> systemctl enable config_custom.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7a2e7511-799d-4e4b-9e64-5b7e98894dcan%40googlegroups.com.

Reply via email to