[beagleboard] Booting a Cape-enabled kernel on a bare bbb
Hi, before shooting into my own feets and possibly harm the hardware: I am using Linux 3.8.13-bone67 by Robert Nelson with Gentoo linux. To the BBB I normally use for this there are attached a LCD7 display, an RTC via GPIOs and an Audio Cape. To get this running I needed to disable the LEDs of the Audio board. I want to boot the same kernel on a second BBB without any cape/RTC attached. Is it failsafe or are there any problems with this? (There is no software in userspace, which accesses the not existing hardware automagically.) Thank you very much for any help in advance! Best regards and have a nice weekend! mcc -- 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: Issue getting DS18B20 temperature sensor working
I was able to get the sensor showing up (switched + and -... Yeah to
quick), however I'm not able to get correct temperature readings with a new
sensor.
I need to mention that I have the Parasitic version DS18B20+, does that
work with 3.3VDC or do I need to connect it to 5VDC (which the BBB does not
support I believe, 5VDC inputs..)
root@bbb:~# for i in `find /sys/devices/w1_bus_master1/ -type d -iname
28-*`; do echo -n $i' '; grep -oE t=[0-9]+$ $i/w1_slave; done;
/sys/devices/w1_bus_master1/28-057ee219 t=85000
/sys/devices/w1_bus_master1/28-057efe1e t=85000
Was
On Saturday, August 30, 2014 1:01:18 PM UTC+2, Michaël Vaes wrote:
Hi -
I'm stuck getting my DS18B20 temperature sensor working on my Beaglebone
Black. I installed and loaded the DTC overlay but Im not getting the '28-*'
files in my '/sys/devices/w1_bus_master1/' directory.
*Wiring*
https://dl.dropboxusercontent.com/u/97513059/ds18b20-temperature-sensor.pdf
*Software*
Debian 7.6
Kernel: 3.8.13-bone50
*My sensor:* http://www.mouser.com/ds/2/256/DS18B20-28978.pdf
*My DTS file:* http://pastebin.com/ma7qd6HK
*Latest version of dtc: *https://raw.githubusercontent.com/RobertCNelson/
tools/master/pkgs/dtc http://goog_1232883269.sh
*Install*
root@bbb:~# cat one-wire-temp-sensor_p8-11.sh
#!/bin/bash
#
# BBB One Wire Temperature sensor (DS18B20)
#
sName='w1';
sInput=$sName'.dts';
sOutput=${sName:0:16}'-00A0.dtbo';
# Build
/usr/local/bin/dtc -O dtb -o $sOutput -b 0 -@ $sInput;
cp $sOutput /lib/firmware/;
echo $sName /sys/devices/bone_capemgr.9/slots;
*GPIO's*
Pin P8.11 gets high, when I test the voltage it's 3.3VDC.
root@bbb:~# cat /sys/kernel/debug/gpio
GPIOs 0-31, gpio:
gpio-6 (mmc_cd ) in lo
GPIOs 32-63, gpio:
gpio-45 (w1 ) in hi
gpio-52 (eMMC_RSTn ) out lo
gpio-53 (beaglebone:green:usr) out lo
gpio-54 (beaglebone:green:usr) out lo
gpio-55 (beaglebone:green:usr) out hi
gpio-56 (beaglebone:green:usr) out lo
GPIOs 64-95, gpio:
GPIOs 96-127, gpio:
*Overlays*
HDMI disabled, w1 overlay loaded
root@bbb:~# cat /sys/devices/bone_capemgr.9/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
8: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
*dmesg*
root@bbb:~# dmesg | tail -n11
[ 167.078501] bone-capemgr bone_capemgr.9: part_number 'w1', version
'N/A'
[ 167.078681] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 167.078726] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 8
[ 167.078775] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,w1'
[ 167.079020] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'w1-00A0.dtbo
[ 167.079067] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'w1-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 167.082029] bone-capemgr bone_capemgr.9: slot #8: dtbo 'w1-00A0.dtbo'
loaded; converting to live tree
[ 167.082504] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 167.089775] of_get_named_gpio_flags exited with status 45
[ 167.089820] of_get_named_gpio_flags: can't parse gpios property
[ 167.097793] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
*Tryouts without success*
- Reboots :o)
- Using another temperature sensor
- Updating the OS
- Changing the DTS file to use another pin like 'P9.22'
-
http://hipstercircuits.com/dallas-one-wire-temperature-reading-on-beaglebone-black-with-dto/
- Changing 'gpios = gpio2 13 0;' to 'gpios = gpio1 13 0;'
*What concerns me and where I cannot seem to get rid of in dmesg/b*
...
--
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: Issue getting DS18B20 temperature sensor working
I was able to get the sensor showing up (switched + and -... Yeah to
quick), however I'm not able to get correct temperature readings with a new
sensor.
I need to mention that I have the Parasitic version DS18B20+, does that
work with 3.3VDC or do I need to connect it to 5VDC (which the BBB does not
support I believe, 5VDC inputs..)
root@bbb:~# for i in `find /sys/devices/w1_bus_master1/ -type d -iname
28-*`; do echo -n $i' '; grep -oE t=[0-9]+$ $i/w1_slave; done;
/sys/devices/w1_bus_master1/28-057ee219 t=85000
/sys/devices/w1_bus_master1/28-057efe1e t=85000
Thanks,
*Michaël*
On Saturday, August 30, 2014 1:01:18 PM UTC+2, Michaël Vaes wrote:
Hi -
I'm stuck getting my DS18B20 temperature sensor working on my Beaglebone
Black. I installed and loaded the DTC overlay but Im not getting the '28-*'
files in my '/sys/devices/w1_bus_master1/' directory.
*Wiring*
https://dl.dropboxusercontent.com/u/97513059/ds18b20-temperature-sensor.pdf
*Software*
Debian 7.6
Kernel: 3.8.13-bone50
*My sensor:* http://www.mouser.com/ds/2/256/DS18B20-28978.pdf
*My DTS file:* http://pastebin.com/ma7qd6HK
*Latest version of dtc: *https://raw.githubusercontent.com/RobertCNelson/
tools/master/pkgs/dtc http://goog_1232883269.sh
*Install*
root@bbb:~# cat one-wire-temp-sensor_p8-11.sh
#!/bin/bash
#
# BBB One Wire Temperature sensor (DS18B20)
#
sName='w1';
sInput=$sName'.dts';
sOutput=${sName:0:16}'-00A0.dtbo';
# Build
/usr/local/bin/dtc -O dtb -o $sOutput -b 0 -@ $sInput;
cp $sOutput /lib/firmware/;
echo $sName /sys/devices/bone_capemgr.9/slots;
*GPIO's*
Pin P8.11 gets high, when I test the voltage it's 3.3VDC.
root@bbb:~# cat /sys/kernel/debug/gpio
GPIOs 0-31, gpio:
gpio-6 (mmc_cd ) in lo
GPIOs 32-63, gpio:
gpio-45 (w1 ) in hi
gpio-52 (eMMC_RSTn ) out lo
gpio-53 (beaglebone:green:usr) out lo
gpio-54 (beaglebone:green:usr) out lo
gpio-55 (beaglebone:green:usr) out hi
gpio-56 (beaglebone:green:usr) out lo
GPIOs 64-95, gpio:
GPIOs 96-127, gpio:
*Overlays*
HDMI disabled, w1 overlay loaded
root@bbb:~# cat /sys/devices/bone_capemgr.9/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
8: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
*dmesg*
root@bbb:~# dmesg | tail -n11
[ 167.078501] bone-capemgr bone_capemgr.9: part_number 'w1', version
'N/A'
[ 167.078681] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 167.078726] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 8
[ 167.078775] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,w1'
[ 167.079020] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'w1-00A0.dtbo
[ 167.079067] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'w1-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 167.082029] bone-capemgr bone_capemgr.9: slot #8: dtbo 'w1-00A0.dtbo'
loaded; converting to live tree
[ 167.082504] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 167.089775] of_get_named_gpio_flags exited with status 45
[ 167.089820] of_get_named_gpio_flags: can't parse gpios property
[ 167.097793] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
*Tryouts without success*
- Reboots :o)
- Using another temperature sensor
- Updating the OS
- Changing the DTS file to use another pin like 'P9.22'
-
http://hipstercircuits.com/dallas-one-wire-temperature-reading-on-beaglebone-black-with-dto/
- Changing 'gpios = gpio2 13 0;' to 'gpios = gpio1 13 0;'
*What concerns me and where I cannot seem to get rid of in dmesg/b*
...
--
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: Can't set static IP
Hi just a thought but try a lower IP address... I know on my modem/router it comes with a configured range valid between 0 to 50. I'm not sure why it does that. On Saturday, 27 September 2014 11:14:19 UTC+2, Pascal De Oliveira wrote: Hello, I have a BBBK Rev B with Debian 7.6 booting from a SD card. I'm trying to set up a static IP. I have added the following lines in the /etc/network/interfaces file : auto eth0 iface eth0 inet static address 192.168.1.99 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.1.1 broadcast 192.168.1.255 This has no effect and it still use DHCP. What is wrong ? Thanks in adavance for any help. Pascal -- 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: PWM howto for BBB linux 3.16.x?
Bump, as I have the same question. Any updates? Thanks. -- 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: Beaglenes doesnot boot
What did the output from your FTDI cable show you? Did you look at the documentation (http://beaglesnes.sourceforge.net/BeagleSNES_Guide.pdf)? If so, what did you try from the troubleshooting section (section 4.1, pages 23 and 24)? Are you using an HDMI display with audio or only video (like a computer monitor)? Did you decompress the image prior to writing it to the microSD card (section 2.3, pages 10 and 11)? What software did you use to write the image to the microSD card? dd? Or something else? Can you see any partitions on the microSD card when you mount it on a Linux PC? On Saturday, September 27, 2014 9:33:21 AM UTC-4, marcus silva wrote: Hi. My beaglebone black does not work. It just doesnot boot. Any one have the same issue? BBB i think os rev b and beaglenes .06. -- 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] Re: Beaglenes doesnot boot
Thanks a lot all the answers. I will read the documentation and do all the tests and return tomorrow. I used HDMI DVI cabel. I used the same step and software to create SD card as BBB advised. Em 28/09/2014 11:59, Andrew Henderson hende...@icculus.org escreveu: What did the output from your FTDI cable show you? Did you look at the documentation (http://beaglesnes.sourceforge.net/BeagleSNES_Guide.pdf)? If so, what did you try from the troubleshooting section (section 4.1, pages 23 and 24)? Are you using an HDMI display with audio or only video (like a computer monitor)? Did you decompress the image prior to writing it to the microSD card (section 2.3, pages 10 and 11)? What software did you use to write the image to the microSD card? dd? Or something else? Can you see any partitions on the microSD card when you mount it on a Linux PC? On Saturday, September 27, 2014 9:33:21 AM UTC-4, marcus silva wrote: Hi. My beaglebone black does not work. It just doesnot boot. Any one have the same issue? BBB i think os rev b and beaglenes .06. -- 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. -- 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] BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel
Hello all. I have released a new port of Android for the BBB. This version uses AOSP 4.4.4 (KitKat) and the 3.8 Linux kernel. I have made build instructions and a pre-made image available at http://www.bbbandroid.org. I use a combination of AOSP repos and Rowboat build scripts, and I have a few custom repos for the kernel, bootloader, and additional external tools (such as i2c-tools). You can view the repo manifest XML file for the project here: https://github.com/hendersa/bbbandroid-manifest/blob/master/bbbandroid-aosp-4.4.4_r1-3.8.xml Because this Android image uses the 3.8 kernel, you should be able to just plug in your capes and go without any hassle: Built-in HDMI cape: http://i.imgur.com/q4AZQ95.jpg 4D Systems LCD capes: 4DCAPE-43T: http://i.imgur.com/6qHmgqX.jpg 4DCAPE-70T: http://i.imgur.com/UZLG7Or.jpg CircuitCo LCD capes: LCD3: http://i.imgur.com/LC7SrBB.jpg LCD4: http://i.imgur.com/1xBQ8R6.jpg LCD7: http://i.imgur.com/vxoqROE.jpg Andrew -- 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] Re: Beaglenes doesnot boot
If you are converting to DVI, then you are probably using a computer monitor without audio. BeagleSNES forces its resolution to 720x480, which is a CEA video mode that support both audio and video for HDMI televisions (480i). A standard computer monitor will typically not support this mode, meaning that your BeagleSNES system may be booting properly but you just can't see anything on the screen. You can try making a backup copy of the uEnv.txt file in the /boot partition and then removing the video=720x480@60-16 option from the kernel command line. The kernel will default to the highest resolution available for your monitor, but BeagleSNES will still assume only a 720x480 display. BeagleSNES is really only intended for use with HDMI televisions or the LCD3 cape, but you can usually coax it into working with a computer monitor (though you lose out on the audio unless you plug in a USB audio device and use that). Andrew On Sunday, September 28, 2014 11:11:29 AM UTC-4, marcus silva wrote: Thanks a lot all the answers. I will read the documentation and do all the tests and return tomorrow. I used HDMI DVI cabel. I used the same step and software to create SD card as BBB advised. Em 28/09/2014 11:59, Andrew Henderson hend...@icculus.org javascript: escreveu: What did the output from your FTDI cable show you? Did you look at the documentation (http://beaglesnes.sourceforge.net/BeagleSNES_Guide.pdf)? If so, what did you try from the troubleshooting section (section 4.1, pages 23 and 24)? Are you using an HDMI display with audio or only video (like a computer monitor)? Did you decompress the image prior to writing it to the microSD card (section 2.3, pages 10 and 11)? What software did you use to write the image to the microSD card? dd? Or something else? Can you see any partitions on the microSD card when you mount it on a Linux PC? On Saturday, September 27, 2014 9:33:21 AM UTC-4, marcus silva wrote: Hi. My beaglebone black does not work. It just doesnot boot. Any one have the same issue? BBB i think os rev b and beaglenes .06. -- 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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] Re: Beaglenes doesnot boot
Thanks Andrew you where correct. I just try it with an hdmi HDMI and it was just OK. I will try to show it on a meeting for 200people next month. Hope Evert thing works fine ;) Em 28/09/2014 12:24, Andrew Henderson hende...@icculus.org escreveu: If you are converting to DVI, then you are probably using a computer monitor without audio. BeagleSNES forces its resolution to 720x480, which is a CEA video mode that support both audio and video for HDMI televisions (480i). A standard computer monitor will typically not support this mode, meaning that your BeagleSNES system may be booting properly but you just can't see anything on the screen. You can try making a backup copy of the uEnv.txt file in the /boot partition and then removing the video=720x480@60-16 option from the kernel command line. The kernel will default to the highest resolution available for your monitor, but BeagleSNES will still assume only a 720x480 display. BeagleSNES is really only intended for use with HDMI televisions or the LCD3 cape, but you can usually coax it into working with a computer monitor (though you lose out on the audio unless you plug in a USB audio device and use that). Andrew On Sunday, September 28, 2014 11:11:29 AM UTC-4, marcus silva wrote: Thanks a lot all the answers. I will read the documentation and do all the tests and return tomorrow. I used HDMI DVI cabel. I used the same step and software to create SD card as BBB advised. Em 28/09/2014 11:59, Andrew Henderson hend...@icculus.org escreveu: What did the output from your FTDI cable show you? Did you look at the documentation (http://beaglesnes.sourceforge.net/BeagleSNES_Guide.pdf)? If so, what did you try from the troubleshooting section (section 4.1, pages 23 and 24)? Are you using an HDMI display with audio or only video (like a computer monitor)? Did you decompress the image prior to writing it to the microSD card (section 2.3, pages 10 and 11)? What software did you use to write the image to the microSD card? dd? Or something else? Can you see any partitions on the microSD card when you mount it on a Linux PC? On Saturday, September 27, 2014 9:33:21 AM UTC-4, marcus silva wrote: Hi. My beaglebone black does not work. It just doesnot boot. Any one have the same issue? BBB i think os rev b and beaglenes .06. -- 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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. -- 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] Re: Can't set static IP
Most home use routers come per-configured with DHCP addresses being in the range of *.02 to *.100, or less. The idea is to keep DHCP address in one small sub range while static ip's are above this. BTW has this issue been posted before ? Or did someone drag up an old post ? auto eth0 iface eth0 inet static address 192.168.1.99 netmask 255.255.255.0 *network 192.168.0.0 *--- wrong network based on the rest of the configuration gateway 192.168.1.1 broadcast 192.168.1.255 *network 192.168.0.0 *should be *network 192.168.1.0 *OR the rest of the configuration is wrong. On Sun, Sep 28, 2014 at 3:25 AM, DLF dumb.looks.f...@gmail.com wrote: Hi just a thought but try a lower IP address... I know on my modem/router it comes with a configured range valid between 0 to 50. I'm not sure why it does that. On Saturday, 27 September 2014 11:14:19 UTC+2, Pascal De Oliveira wrote: Hello, I have a BBBK Rev B with Debian 7.6 booting from a SD card. I'm trying to set up a static IP. I have added the following lines in the /etc/network/interfaces file : auto eth0 iface eth0 inet static address 192.168.1.99 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.1.1 broadcast 192.168.1.255 This has no effect and it still use DHCP. What is wrong ? Thanks in adavance for any help. Pascal -- 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. -- 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: Issue getting DS18B20 temperature sensor working
You can use either powered or parasitic modes for One-Wire devices -- there
isn't a distinct device for one mode or the other. The data sheet shows the
DS18B20 can operate down to 3V.
I'm not greatly versed in embedded Linux, nor in the BBB, but I've used
One-Wire devices (including DS18S20s) a fair bit. I avoid parasitic mode
whenever I can. Running a power line makes One-Wire systems much easier to
debug, and multi-wire cables aren't all that expensive.
Cheers, Tim
On Sunday, September 28, 2014 5:48:11 AM UTC-4, Michaël Vaes wrote:
I was able to get the sensor showing up (switched + and -... Yeah to
quick), however I'm not able to get correct temperature readings with a new
sensor.
I need to mention that I have the Parasitic version DS18B20+, does that
work with 3.3VDC or do I need to connect it to 5VDC (which the BBB does not
support I believe, 5VDC inputs..)
root@bbb:~# for i in `find /sys/devices/w1_bus_master1/ -type d -iname
28-*`; do echo -n $i' '; grep -oE t=[0-9]+$ $i/w1_slave; done;
/sys/devices/w1_bus_master1/28-057ee219 t=85000
/sys/devices/w1_bus_master1/28-057efe1e t=85000
Thanks,
*Michaël*
On Saturday, August 30, 2014 1:01:18 PM UTC+2, Michaël Vaes wrote:
Hi -
I'm stuck getting my DS18B20 temperature sensor working on my Beaglebone
Black. I installed and loaded the DTC overlay but Im not getting the '28-*'
files in my '/sys/devices/w1_bus_master1/' directory.
*Wiring*
https://dl.dropboxusercontent.com/u/97513059/ds18b20-temperature-sensor.pdf
*Software*
Debian 7.6
Kernel: 3.8.13-bone50
*My sensor:* http://www.mouser.com/ds/2/256/DS18B20-28978.pdf
*My DTS file:* http://pastebin.com/ma7qd6HK
*Latest version of dtc: *https://raw.githubusercontent.com/RobertCNelson/
tools/master/pkgs/dtc http://goog_1232883269.sh
*Install*
root@bbb:~# cat one-wire-temp-sensor_p8-11.sh
#!/bin/bash
#
# BBB One Wire Temperature sensor (DS18B20)
#
sName='w1';
sInput=$sName'.dts';
sOutput=${sName:0:16}'-00A0.dtbo';
# Build
/usr/local/bin/dtc -O dtb -o $sOutput -b 0 -@ $sInput;
cp $sOutput /lib/firmware/;
echo $sName /sys/devices/bone_capemgr.9/slots;
*GPIO's*
Pin P8.11 gets high, when I test the voltage it's 3.3VDC.
root@bbb:~# cat /sys/kernel/debug/gpio
GPIOs 0-31, gpio:
gpio-6 (mmc_cd ) in lo
GPIOs 32-63, gpio:
gpio-45 (w1 ) in hi
gpio-52 (eMMC_RSTn ) out lo
gpio-53 (beaglebone:green:usr) out lo
gpio-54 (beaglebone:green:usr) out lo
gpio-55 (beaglebone:green:usr) out hi
gpio-56 (beaglebone:green:usr) out lo
GPIOs 64-95, gpio:
GPIOs 96-127, gpio:
*Overlays*
HDMI disabled, w1 overlay loaded
root@bbb:~# cat /sys/devices/bone_capemgr.9/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
8: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
*dmesg*
root@bbb:~# dmesg | tail -n11
[ 167.078501] bone-capemgr bone_capemgr.9: part_number 'w1', version
'N/A'
[ 167.078681] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 167.078726] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 8
[ 167.078775] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,w1'
[ 167.079020] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'w1-00A0.dtbo
[ 167.079067] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'w1-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 167.082029] bone-capemgr bone_capemgr.9: slot #8: dtbo 'w1-00A0.dtbo'
loaded; converting to live tree
[ 167.082504] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 167.089775] of_get_named_gpio_flags exited with status 45
[ 167.089820] of_get_named_gpio_flags: can't parse gpios property
[ 167.097793] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
*Tryouts without success*
- Reboots :o)
- Using another temperature sensor
- Updating the OS
- Changing the DTS file to use another pin like 'P9.22'
-
http://hipstercircuits.com/dallas-one-wire-temperature-reading-on-beaglebone-black-with-dto/
- Changing 'gpios = gpio2 13 0;' to 'gpios = gpio1 13 0;'
*What concerns me and where I cannot seem to get rid of in dmesg/b*
...
--
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] MAC OS X: BBB running Angstrom Networking issues using USB
I've been having issues connecting to the outside network and I have absolutely no clue why... There was no issues in installing the drivers and accessing my browser at http://192.168.7.2 Also there was no issues to ssh into the root The BBB is running the latest upgrade: root@beaglebone:~# uname -a Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux In the Mac OSX (running ver. 10.9.5) I went into System Preferences Sharing Allowed Internet Sharing (via WIFI) for the BeagleBone Black Also, I disabled the Firewall by going into System Preferences Security Privacy Firewall Turn off Firewall I turned on the gatewaying in order to forward traffic onto the BBB by doing the following on the OS X terminal: sudo su ifconfig en3 192.168.7.1 (where en3 is the BBB's interface) sysctl -w net.inet.ip.fw.enable=1 sysctl -w net.inet.ip.forwarding=1 natd -interface en0 (where en0 is the interface for the Mac's Internet connection) ipfw add divert natd ip from any to any via en0 I followed some instruction found in this forum by modifing the /usr/bin/g-ether-load.sh script which sets up the USB Ethernet connection. I added the following 2 lines of codes to the bottom of the script file. /sbin/route add default gw 192.168.7.1 echo nameserver 8.8.8.8 /etc/resolv.conf Yet, for some reason I still cannot reach the outside network on the BBB: root@beaglebone:~# ping 8.8.8.8 connect: Network is unreachable root@beaglebone:~# ping www.google.com ping: unknown host www.google.com Below is the information of the network and the IP routing table when running ifconfig and route on the BBB root@beaglebone:~# ifconfig eth0 Link encap:Ethernet HWaddr 1C:BA:8C:90:38:5D UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) 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:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1520 (1.4 KiB) TX bytes:1520 (1.4 KiB) usb0 Link encap:Ethernet HWaddr 8E:1A:FF:1B:E6:B6 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:2166 errors:0 dropped:0 overruns:0 frame:0 TX packets:1527 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:176350 (172.2 KiB) TX bytes:561859 (548.6 KiB) root@beaglebone:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.7.0 * 255.255.255.252 U 0 00 usb0 After getting tired of having the same problem over and over I went on my friends computer (running Windows 7) and followed the instructions found in this tutorial and had no problems connecting the first try... https://www.youtube.com/watch?v=fzRVVtGNfj8list=UUf_sAmhBw7Tj7-2ujmLFoQg I'm assuming that there's an issue with the Mac internet sharing... What am I doing wrong? Any input would be appreciated.. Thanks!! -- 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] Re: how to change screen resolution
thanks, that works. Do you know if possible and if yes how to change the setting for the mouse? - I want it to be scan by the system as frequently as possible. On Friday, September 26, 2014 9:42:15 PM UTC+10, Charles Steinkuehler wrote: Edit uEnv.txt and set a custom resolution using the kernel command line: http://blog.machinekit.io/2013/07/custom-hdmi-resolution.html On 9/25/2014 5:46 PM, janszyma...@gmail.com javascript: wrote: I've modified the file /etc/xdg/lxsession/LXDE/autostart by adding @xrandr -s 640x480@75 It looks like this now: @lxpanel --profile LXDE @pcmanfm --desktop --profile LXDE @xrandr -s 640x480@75 Reboot, but still doesn't work. Any help, please. Jan On Thursday, 25 September 2014 09:36:18 UTC+10, janszyma...@gmail.com wrote: Hi, How to change the screen resolution on BBB with latest image and HDMI monitor connected? Currently working with 1920x1080 by default, but I need a lower resolution - 640x480@75. Jan -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- 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] Wireless mesh networking
Hi Brian, I had evaluated babel, OLSR, and Batman-adv two years ago on a test network of 5 beaglebones to demonstrate wifi mesh networking. I concluded Batman-adv was the one to explore further. I was using Robert Nelson's ubuntu (3.2 kernel) on beaglebone white then. I had tried three different long range wifi dongles from Alpha. The black one (http://www.amazon.com/ Alfa-AWUS036NHA-Wireless-Adaptor-Compatible/dp/B004Y6MIXS) has Atheros ar9271 chipset and has the best kernel support on Beaglebone. The more common model is based on realtek rtl8192cu chipset. Back then rtl8192cu driver on arm was not anywhere near ready. I would still strongly prefer AR9271 based wifi dongle today. I had to use a USB Y-cable to make sure there is sufficient current during boot time to power up the wifi dongle. BB only has a USB host port, so this was a bit inconvenient. I resorted to tie the 5V and GND lines of the USB to a 5V supply to ensure smooth boot. With a 14 omnidirectional antenna and tx-power cranked up full, I was able to sustain decent connectivity at ~300 meter per hop during field demonstration. For batman-adv, I configured every node's bat0 interface on 192.168.50.x subnet. (wlan0 has its own static address assignment in /etc/network/interfaces) When starting a mesh node, a startbatman.sh is called that has the following: modprobe batman-adv ifconfig wlan0 mtu 1528 batctl if add wlan0 ifconfig bat0 192.168.50.218 up batctl gw client ip route del default ip route add default via 192.168.50.1 On the node serving as gateway through its eth0, I had the additional lines for Network Address Translation. sysctl net.ipv4.ip_forward=1 iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE iptables --append FORWARD --in-interface bat0 -j ACCEPT You could add an @reboot line in /etc/crontab that calls your startbatman.sh on reboot every time. I have not updated this since the switch to 3.8 kernel, but I am pretty sure it would work on the current Debian image. I would recommend you use the 3.14 kernel to benefit from the more reliable USB. George On Fri, Sep 26, 2014 at 2:30 PM, Brian Anderson b...@nwlink.com wrote: Hi all, I am interested in setting up a wireless mesh network using a collection of BBBs (and possibly other devices). Does anyone have experience setting up a wireless mesh network using BBB? I am not really interested in a so-called wireless distribution system that is used to extend an SSID across a wide area using wireless mesh networking. I am much more interested in setting up a network of cooperating nodes that talk with each other (and to the internet via a gateway/mesh portal connected simultaneously to the internet and the mesh). In particular, I'm interested in: * What distro and kernel are you using? * Ideally this would be with one of RCNs Debian images, but if not, I'm interested in what you might have used. * If you have done something with a Linux based system other than a BBB, I'd like to know about that too. * What mesh routing protocol was used? Batman, Babel/AHCP, HWMP, OLSR, ... * Steps to configure the mesh network and gateway. * Did you use 802.11s? If so, presumably using the 802.11s support in the kernel? * WiFi chipset that was used (presumably supporting mesh mode). SOFTMAC or HARDMAC? I have researched the topic fairly extensively and can probably set something up via trial and error myself. Prior to diving into that, I wanted to see if anyone has already done some work with wireless mesh networking and BBB (or something else) and would be willing to share their experience and knowledge! Thanks in advance. Cheers, ba -- 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. -- 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] Wireless mesh networking
On 09/28/2014 04:29 PM, George Lu wrote: Hi Brian, I had evaluated babel, OLSR, and Batman-adv two years ago on a test network of 5 beaglebones to demonstrate wifi mesh networking. I concluded Batman-adv was the one to explore further. I was using Robert Nelson's ubuntu (3.2 kernel) on beaglebone white then. I had tried three different long range wifi dongles from Alpha. The black one (http://www.amazon.com/Alfa-AWUS036NHA-Wireless-Adaptor-Compatible/dp/B004Y6MIXS) has Atheros ar9271 chipset and has the best kernel support on Beaglebone. The more common model is based on realtek rtl8192cu chipset. Back then rtl8192cu driver on arm was not anywhere near ready. I would still strongly prefer AR9271 based wifi dongle today. I had to use a USB Y-cable to make sure there is sufficient current during boot time to power up the wifi dongle. BB only has a USB host port, so this was a bit inconvenient. I resorted to tie the 5V and GND lines of the USB to a 5V supply to ensure smooth boot. With a 14 omnidirectional antenna and tx-power cranked up full, I was able to sustain decent connectivity at ~300 meter per hop during field demonstration. For batman-adv, I configured every node's bat0 interface on 192.168.50.x subnet. (wlan0 has its own static address assignment in /etc/network/interfaces) When starting a mesh node, a startbatman.sh is called that has the following: modprobe batman-adv ifconfig wlan0 mtu 1528 batctl if add wlan0 ifconfig bat0 192.168.50.218 up batctl gw client ip route del default ip route add default via 192.168.50.1 On the node serving as gateway through its eth0, I had the additional lines for Network Address Translation. sysctl net.ipv4.ip_forward=1 iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE iptables --append FORWARD --in-interface bat0 -j ACCEPT You could add an @reboot line in /etc/crontab that calls your startbatman.sh on reboot every time. I have not updated this since the switch to 3.8 kernel, but I am pretty sure it would work on the current Debian image. I would recommend you use the 3.14 kernel to benefit from the more reliable USB. George On Fri, Sep 26, 2014 at 2:30 PM, Brian Anderson b...@nwlink.com mailto:b...@nwlink.com wrote: Hi all, I am interested in setting up a wireless mesh network using a collection of BBBs (and possibly other devices). Does anyone have experience setting up a wireless mesh network using BBB? I am not really interested in a so-called wireless distribution system that is used to extend an SSID across a wide area using wireless mesh networking. I am much more interested in setting up a network of cooperating nodes that talk with each other (and to the internet via a gateway/mesh portal connected simultaneously to the internet and the mesh). In particular, I'm interested in: * What distro and kernel are you using? * Ideally this would be with one of RCNs Debian images, but if not, I'm interested in what you might have used. * If you have done something with a Linux based system other than a BBB, I'd like to know about that too. * What mesh routing protocol was used? Batman, Babel/AHCP, HWMP, OLSR, ... * Steps to configure the mesh network and gateway. * Did you use 802.11s? If so, presumably using the 802.11s support in the kernel? * WiFi chipset that was used (presumably supporting mesh mode). SOFTMAC or HARDMAC? I have researched the topic fairly extensively and can probably set something up via trial and error myself. Prior to diving into that, I wanted to see if anyone has already done some work with wireless mesh networking and BBB (or something else) and would be willing to share their experience and knowledge! Thanks in advance. Cheers, ba -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. Nice work there! You could also look into cjdns it may fit your needs -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups
Re: [beagleboard] startup process error
Good suggestion and it works. Couldn't make it with systemd however and I'm curious why. It is a GUI application and possibly I made some syntax error. my bap.service file is: [Unit] Description=Ball and Plate [Service] WorkingDirectory=/opt/bap ExecStart=/opt/bap runbap SyslogIdentifier=bap and my /opt/bap/bap.sh is #! /bin/bash echo waiting... sleep 20 echo changing cpufreq sudo cpufreq-set -g performance sudo cpufreq-info ./bap The service is installed, but fails on execution. On Friday, September 26, 2014 1:38:02 PM UTC+10, Wulf Man wrote: Can't start in in a cron job ? On 9/25/2014 8:20 PM, janszyma...@gmail.com javascript: wrote: Hi, I want to autostart the program on boot on BBB debian. My executable is located in /opt/bap and I can start it from terminal by ./bap Following the instruction from here http://stackoverflow.com/questions/11152657/angstrom-start-up-processes-beaglebone the file bap.service in /lib/systemd/system/ has the content: [Unit] Description=ball and plate After=syslog.target network.target [Service] WorkingDirectory=/opt/bap Type=simple ExecStart=/opt/bap ./bap [Install] WantedBy=multi-user.target then I did: systemctl enable bap.servicesystemctl start bap.service All was good, but debian@beaglebone:/opt/bap$ sudo systemctl status bap.service bap.service - ball and plate Loaded: loaded (/lib/systemd/system/bap.service; enabled) Active: failed (Result: exit-code) since Fri, 26 Sep 2014 03:03:42 +; 4s ago Process: 6515 ExecStart=/opt/bap ./bap (code=exited, status=203/EXEC) CGroup: name=systemd:/system/bap.service Sep 26 03:03:42 beaglebone (bap)[6515]: Failed at step EXEC spawning /opt/ba...d debian@beaglebone:/opt/bap$ How to fix it? Jan -- 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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] Beagle Bone Black Dog Standoff Dog Feet
https://www.shapeways.com/model/2670740/dogfeet11.html?materialId=6 I created some dog feet standoffs for my beagle board black. Made them available at shapeways if anyone wants a set. I think they are cute. Thanks -- 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.
