Re: [beagleboard] Network IP address assignments

2018-12-05 Thread Richard
Many many thanks. ~Richard On Wednesday, December 5, 2018 at 3:51:04 PM UTC-5, RobertCNelson wrote: > > On Wed, Dec 5, 2018 at 2:38 PM Richard > > wrote: > > > > Hi! I'm having difficulty understanding and modifying the BBBW network > configuration. > > > > At boot on the BBBW, somehow,

Re: [beagleboard] Network IP address assignments

2018-12-05 Thread Robert Nelson
On Wed, Dec 5, 2018 at 2:38 PM Richard wrote: > > Hi! I'm having difficulty understanding and modifying the BBBW network > configuration. > > At boot on the BBBW, somehow, these IP addresses are assigned > SoftAP0: 192.168.8.1 /etc/default/bb-wl18xx (changeable) > lo: 127.0.0.1 > usb0:

Re: [beagleboard] Network IP address assignments

2018-12-05 Thread Mike Brandon
Sorry, copied and pasted from my application code that is driving the network configuration...the {0} in NetworkInterfaceBlackist is eth0 Mike On Wed, Dec 5, 2018 at 3:45 PM Mike Brandon wrote: > In my limited experience, I ran into a lot of issues trying to modify the > network settings as

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

2018-12-05 Thread Jim F
Harke, You should try running your script from the cli using the exact same command you use for the exec start line in your service file. It should give you the same errors you are seeing. That would be good. If not, the problem is that your environment doesn't match. It will probably end up

Re: [beagleboard] Network IP address assignments

2018-12-05 Thread Mike Brandon
In my limited experience, I ran into a lot of issues trying to modify the network settings as you are running into. I *believe* that the network settings are being controlled by conman. So I added to / etc/connman/main.conf the following: NetworkInterfaceBlacklist=SoftAp0,usb0,usb1,{0},can0,can1

[beagleboard] Network IP address assignments

2018-12-05 Thread Richard
Hi! I'm having difficulty understanding and modifying the BBBW network configuration. At boot on the BBBW, somehow, these IP addresses are assigned SoftAP0: 192.168.8.1 lo: 127.0.0.1 usb0: 192.168.7.2 usb1: 192.168.6.2 wlan0: 192.168.1.xxx But I can't figure out where each of these

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

2018-12-05 Thread Harke Smits
login as: debian debian@Beaglebone's password: The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

2018-12-05 Thread Harke Smits
Hello Jim and Seth, Thank you for your support. The service test scripts all run fine. My own scripts persist in the error given above. My own service loads but aborts at import serial, which, I guess, has not so much to do with serial, as with something else. I will try and upload the relevant

[beagleboard] Facing problems booting via NFS

2018-12-05 Thread Juho R
*Hi,* *I know there is many topics about NFS and TFTP. But I still could not find why my board is not booting via NFS.. Have been trying couple of days many many different ways now and I have no clue where it goes wrong and its getting frustrating now.* *I believe there might be something

Re: [beagleboard] Re: 1-wire on BB Blue

2018-12-05 Thread TJF
Hi Jim! I cannot answer your questions, but perhaps point you to a further solution: Some years ago I needed multiple Dallas temperature sensors input for a project, and tested the kernel driver. I found out that (at this time) the kernel driver doesn't support simultaneous measurements from

Re: [beagleboard] Beaglebone Black SPI with GPIO CS

2018-12-05 Thread jamesgao
Excellent, thank you! I got my GPIO CS pins to work. For reference (in case anyone needs the same information), here's my dts file: /dts-v1/; /plugin/; / { compatible = "ti,beaglebone", "ti,beaglebone-black"; /* identification */ part-number = "BB-SPICAPE-01"; version = "00A0"; fragment@0 {

[beagleboard] I2C busses mixed up?

2018-12-05 Thread Harke Smits
Hello Learned group, I have an I2C problem that I confuses me: I have activated I2C1 in uEnv.txt. That works. Now i2cdetect -y -r i (for i = 0,1,2) gives a quick response. However, i2c2 behaves like i2c1. i=1 shows nothing connected, 0 shows some UU's and 2 shows devices I can recognise: I can