[beagleboard] Re: How does one find the TCP address of a BBB ?
Keep in mind that if you have a serial debug cable, then you can monitor the BBB boot messages, during which it displays all of the configured network interfaces (among much other stuff). http://www.elinux.org/Beagleboard:BeagleBone_Black_Serial -Chris -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Raw device on I2C bus
Hi Helmut, I'm afraid that I can't help with BoneScript. Perhaps a good solution does exist (and other will chime in). However, another option would be to use Python. I am doing this now, and talking to my I2C devices is working fine. For Python, one needs to install 'smbus': apt-get install python-smbus Regards, Chris On Tuesday, June 17, 2014 9:16:47 AM UTC-4, Helmut Friederici wrote: Hi folks, I have a hardware circuit (internally named SAL) based on a MSP430 microcontroller which should be connected via I2C to the BBB. After physically connecting the SAL via I2C to the BBB it responds to i2cdetect correctly and I am able to start some actions via i2cget because my SAL software interprets register numbers as internal commands - not nice but it works (partially). But what I really want is to start actions by executing scripts based on BoneScript. As far as I understand there is a suitable driver needed for this device which obviously doesn't exist. Am I right? Or could the dummy driver be used in any way and how? In Bonescript I can create a new dummy device at a given address and I can read and write files but are there any files connected to the dummy driver which I can read/write to communicate with my device? Sorry for those basic questions but I have never done anything with I2C. Any help/hint is appreciated Helmut -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Eth0 config on BBB (default Angstrom image 2013.09.04)
Cody, From your linked page I followed: root@beaglebone:~# ifconfig eth0 192.168.0.50 netmask 255.255.255.0 up and it seems to work fine. root@beaglebone:~# ifconfig eth0 Link encap:Ethernet HWaddr 1C:BA:8C:98:51:96 inet addr:192.168.0.50 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::1eba:8cff:fe98:5196/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:440 errors:0 dropped:0 overruns:0 frame:0 TX packets:75 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:194321 (189.7 KiB) TX bytes:13314 (13.0 KiB) Interrupt:56 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:716 errors:0 dropped:0 overruns:0 frame:0 TX packets:716 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:50064 (48.8 KiB) TX bytes:50064 (48.8 KiB) usb0 Link encap:Ethernet HWaddr EE:50:BC:2B:38:79 inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:365684 errors:0 dropped:0 overruns:0 frame:0 TX packets:29997 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:177609506 (169.3 MiB) TX bytes:5316659 (5.0 MiB) I can now now ssh via eth0 and usb. Thanks! -Chris On Wednesday, May 14, 2014 3:25:42 PM UTC-4, cody wrote: This may help http://www.cyberciti.biz/tips/howto-ubuntu-linux-convert-dhcp-network-configuration-to-static-ip-configuration.html -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Cannot run a python script on powerup
Nobody else has chimed in - and nearly anyone would be more qualified... Could it be that you didn't properly specify 'python' in the execstart section of [Service]? This: ExecStart=/home/root/py-gaugette/samples/python new_test.py Should be this: ExecStart=/usr/bin/python new_test.py -Chris On Tuesday, May 13, 2014 7:21:09 AM UTC-4, mike rankin wrote: I found a great post over at: http://stackoverflow.com/questions/11152657/angstrom-start-up-processes-beagleboneon how to have a python script run on power up. My python code that displays text on an oled screen runs fine on Angstrom when I run it manually. The web page says to: Create a new file in /lib/systemd/system/ (rfidreader.service in my example) with a content like: [Unit] Description=Start Python RFID reader [Service] WorkingDirectory=/...Python script path.../ ExecStart=/usr/bin/python rfidreader.py KillMode=process [Install] WantedBy=multi-user.target Then execute the following command to install the service: systemctl enable rfidreader.service To start the service, you can reboot or execute systemctl start rfidreader.service To check if the service is running and get the latest outputs from the script: systemctl status rfidreader.service *My code:* [Unit] Description=Start Python Oled [Service] WorkingDirectory=/home/root/py-gaugette/samples/ ExecStart=/home/root/py-gaugette/samples/python new_test.py KillMode=process [Install] WantedBy=multi-user.target *My error message:* root@beaglebone:~# systemctl status oled.service oled.service - Start Python Oled Loaded: loaded (/lib/systemd/system/oled.service; enabled) Active: *failed* (Result: exit-code) since Tue 2014-05-13 00:12:38 GMT+3; 23s ago Process: 666 ExecStart=/home/root/py-gaugette/samples/python new_test.py *(code=exited, status=203/EXEC)* CGroup: name=systemd:/system/oled.service May 13 00:12:38 beaglebone systemd[1]: Starting Start Python Oled... May 13 00:12:38 beaglebone systemd[1]: Started Start Python Oled. May 13 00:12:38 beaglebone systemd[1]: *oled.service: main process exited, code=exited, status=203/EXEC* May 13 00:12:38 beaglebone systemd[1]: *Unit oled.service entered failed state* -- 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. For more options, visit https://groups.google.com/d/optout.
