[beagleboard] debian jessie: device-tree-compiler: upgrade for v4.1.x+ kernel's..
I think it's time we say good bye to that old 3.8.x based kernel, it's served thing well.. (for jessie+) What i'm planning to do, push a "device-tree-compiler" package update, which will break "3.8.x dtbo's" * (and therefore support v4.1.x+) For building "external" *.dtbo's on target... 3.8.13 users on jessie can still use: https://github.com/RobertCNelson/tools/blob/master/pkgs/dtc.sh to get the "dtc compiler for 3.8.x".. This is the first step in packaging the "bb.org-overlays" repo, and allow "console" users a small base image and get the v4.1.x overlay *.dtbo's.. Any last minute thoughts? * wheezy/trusty users WILL NOT be affected, that will support 3.8.13 till the end of time. Only jessie+ (and therefore xenial) Regards -- Robert Nelson https://rcn-ee.com/ -- 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: Dropbear Ignoring "-w" Disable SSH Root Login on BeagleBone Black
Hi, This is obviously a pretty old topic - but there wasn't an answer, does anyone know what the solution to this is? On Saturday, September 7, 2013 at 9:26:46 PM UTC+1, jhar...@gmail.com wrote: > > Hey everyone, > > I have a BeagleBone Black board and I am trying to disable SSH root login. > The board is running the newest Angstrom Linux build, but other than that > the rest of the settings are stock. > > I created a new user w/ password and added a password to the root user. I > am able to SSH into the board through Putty, as either the user or root, > but I want to disable being able to login as root. > > I updated /etc/init.d/dropbearand added a "-w" to the > "DROPBEAR_EXTRA_ARGS=" line, and rebooted, but I could still login as root. > > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin >> DAEMON=/usr/sbin/dropbear >> NAME=dropbear >> DESC="Dropbear SSH server" >> DROPBEAR_PORT=22 >> DROPBEAR_EXTRA_ARGS= >> *"-w"*NO_START=0 >> set -e > > > I also checked the K10dropbear files in the rc*.d directories and the > "-w" was in all 6 files. > > I then saw that it says at the top of the file " # Do not configure this > file. Edit /etc/default/dropbear instead! ", but the "dropbear" file does > not exist in my /etc/default/ folder. > So my next attempt I reverted the file in init.d back to the original and > I created a new "dropbear" file in /etc/default and put the following info > inside. (which I found from a google search) > > /etc/default/dropbear... > > #any additional arguments for Dropbear >> DROPBEAR_EXTRA_ARGS="-w" >> > > I then rebooted again and still no luck, I can still login as root through > putty. I'm not sure what I am missing here... > > Thank you in advanced. > > > > > -- 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] CVE-2015-7547 glibc bug
The whole story: vigil@VE1cba8ca9e5fb:~$ ldd --version ldd (Ubuntu EGLIBC 2.19-0ubuntu6) 2.19 Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper But at this point I don't care too much, it's now merely academic curiosity and is not getting in the way of getting anything done. On Tuesday, February 23, 2016 at 2:33:41 PM UTC-8, Peter Hurley wrote: > > On 02/23/2016 01:15 PM, mickeyf wrote: > > I don't get that on my BBBs ( which have ubuntu 14.04, if that matters). > > It's beyond my power to see what you actually do get for output if you > don't post it. > And I pulled that 'ldd --version' output from a 14.04 bbb as well. > > > > I'm speculating that since what ldd is actually showing, as I understand > it, is the version number and dependencies of ldd itself, it is showing the > version number of what it requires, i.e. any libc6, not the one actually in > use, i.e. libc6.7. Or maybe more likely, libc6 is actually a link to > libc6.x, and that's what ldd is reporting? Pure speculation, tho'. I'd live > to hear to the real story. > > > > On Tuesday, February 23, 2016 at 11:41:30 AM UTC-8, Peter Hurley wrote: > > > > On 02/23/2016 10:47 AM, mickeyf wrote: > > > Bingo! 'dpkg-query --show libc6 ' does show 6.7. > > > > > > Curious why ldd does not. > > > > ?? > > > > peter@black:~$ ldd --version > > ldd (Ubuntu EGLIBC 2.19-0ubuntu6.7) 2.19 > >^^^ > > -- 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] CVE-2015-7547 glibc bug
On 02/23/2016 01:15 PM, mickeyf wrote: > I don't get that on my BBBs ( which have ubuntu 14.04, if that matters). It's beyond my power to see what you actually do get for output if you don't post it. And I pulled that 'ldd --version' output from a 14.04 bbb as well. > I'm speculating that since what ldd is actually showing, as I understand it, > is the version number and dependencies of ldd itself, it is showing the > version number of what it requires, i.e. any libc6, not the one actually in > use, i.e. libc6.7. Or maybe more likely, libc6 is actually a link to > libc6.x, and that's what ldd is reporting? Pure speculation, tho'. I'd live > to hear to the real story. > > On Tuesday, February 23, 2016 at 11:41:30 AM UTC-8, Peter Hurley wrote: > > On 02/23/2016 10:47 AM, mickeyf wrote: > > Bingo! 'dpkg-query --show libc6 ' does show 6.7. > > > > Curious why ldd does not. > > ?? > > peter@black:~$ ldd --version > ldd (Ubuntu EGLIBC 2.19-0ubuntu6.7) 2.19 >^^^ -- 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] osx 10.11.3 connectivity problem - HoRNDIS?
I have resisted putting on El Capitan. Because of all the connectivity problems it has had, and apparently STILL has. I am still at Yosemite for this reason. -- Extra Ham Operator: K7AZJ Registered Linux User: 275424 Raspberry Pi and Arduino developer *The most exciting phrase to hear in science - the one that heralds new discoveries - is not "Eureka!" but "That's funny...".*- Isaac. Asimov *I* *f you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. *- Anonymous *If writing good code requires very little comments, then writing really excellent code requires no comments at all!*- Ken Thompson On Tue, Feb 23, 2016 at 3:00 PM, William Hermans wrote: > *Has anyone else had problems with El Capitan?* >> > > It has been a known issues for many months now, that do not apply only to > this hardware. It applies to any hardware that uses USB as an ethernet > device ( g_ether ). So Android phones, embedded hardware, etc are all > effected. > > On Tue, Feb 23, 2016 at 2:30 PM, Fred Patrick > wrote: > >> I have been using OSX 10.11.3 for several months. I had a problem with my >> BeagleBone Black and had to replace it. When I went to boot using USB >> connection, it seemed to work several times. Then it stopped connecting and >> the Mac no longer sees 192.168.7.2. I found website of Joshua Wise in which >> he describes problems with HoRNDIS driver (apparently he maintains it) with >> El Capitan. >> >> Has anyone else had problems with El Capitan? >> >> -- >> 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. > -- 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] osx 10.11.3 connectivity problem - HoRNDIS?
> > *Has anyone else had problems with El Capitan?* > It has been a known issues for many months now, that do not apply only to this hardware. It applies to any hardware that uses USB as an ethernet device ( g_ether ). So Android phones, embedded hardware, etc are all effected. On Tue, Feb 23, 2016 at 2:30 PM, Fred Patrick wrote: > I have been using OSX 10.11.3 for several months. I had a problem with my > BeagleBone Black and had to replace it. When I went to boot using USB > connection, it seemed to work several times. Then it stopped connecting and > the Mac no longer sees 192.168.7.2. I found website of Joshua Wise in which > he describes problems with HoRNDIS driver (apparently he maintains it) with > El Capitan. > > Has anyone else had problems with El Capitan? > > -- > 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] osx 10.11.3 connectivity problem - HoRNDIS?
I have been using OSX 10.11.3 for several months. I had a problem with my BeagleBone Black and had to replace it. When I went to boot using USB connection, it seemed to work several times. Then it stopped connecting and the Mac no longer sees 192.168.7.2. I found website of Joshua Wise in which he describes problems with HoRNDIS driver (apparently he maintains it) with El Capitan. Has anyone else had problems with El Capitan? -- 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] CVE-2015-7547 glibc bug
I don't get that on my BBBs ( which have ubuntu 14.04, if that matters). I'm speculating that since what ldd is actually showing, as I understand it, is the version number and dependencies of ldd itself, it is showing the version number of what it requires, i.e. any libc6, not the one actually in use, i.e. libc6.7. Or maybe more likely, libc6 is actually a link to libc6.x, and that's what ldd is reporting? Pure speculation, tho'. I'd live to hear to the real story. On Tuesday, February 23, 2016 at 11:41:30 AM UTC-8, Peter Hurley wrote: > > On 02/23/2016 10:47 AM, mickeyf wrote: > > Bingo! 'dpkg-query --show libc6 ' does show 6.7. > > > > Curious why ldd does not. > > ?? > > peter@black:~$ ldd --version > ldd (Ubuntu EGLIBC 2.19-0ubuntu6.7) 2.19 >^^^ > > > -- 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] BBB, Mysql, systemd and halt/reboot
> > *Using Wheezy on the BBB (2015.03 console image). The mysql package is in > the in-between state of apparently using both mysqld-safe and systemd.* > Wheezy is technically not a systemd debian. It was added by Robert, and in fact it can be disabled. IF that is what you want. So my limited understanding of systemd is that you create services files, with targets, rules, etc. What it seems you need to do is write a service script that must be run before any of those system power options are engaged. As to how, I'm not exactly sure, but pretty sure a google session would be fruitful. On Tue, Feb 23, 2016 at 10:52 AM, Jonathan Ross wrote: > Using Wheezy on the BBB (2015.03 console image). The mysql package is in > the in-between state of apparently using both mysqld-safe and systemd. > If I run "service mysql stop", the systemd mysql service stops seemingly > happily and in /var/log/syslog I see the shutdown of mysql logged from > mysqld. > However, if I issue a system "halt" or "reboot" or even a systemctl > poweroff, I see no evidence of a clean mysql shutdown in the syslog. > I'm unsure if mysql is being halted cleanly upon system halt/reboot and > just not logged, or if the process is just being killed (leading to the > possibility of data corruption). > Cheers for any pointers / debugging ideas. > Jon Ross > > -- > 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] BBB making connection to 82.165.8.211 on port 80
On Tue, Feb 23, 2016 at 2:37 PM, Robert Nelson wrote: > On Tue, Feb 23, 2016 at 2:18 PM, wrote: >> Hi, my BBB is attempting to make a connection to 82.165.8.211 on port 80. >> Any idea which service is doing this and it's purpose for doing so? > > connman: > > http://ipv4.connman.net.dnstree.com/ details: https://01.org/jira/browse/CM-657 Regards, -- Robert Nelson https://rcn-ee.com/ -- 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] BBB making connection to 82.165.8.211 on port 80
On Tue, Feb 23, 2016 at 2:18 PM, wrote: > Hi, my BBB is attempting to make a connection to 82.165.8.211 on port 80. > Any idea which service is doing this and it's purpose for doing so? connman: http://ipv4.connman.net.dnstree.com/ Regards, -- Robert Nelson https://rcn-ee.com/ -- 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] EHRPWM1A and 1B in Debian Jessie 4.1
Hello All, I'm using Kernel 4.1.18-bone-19 in Debian Jessie. I've got my LCD cape running currently and I'm happy with how the backlight is functioning on EHRPWM1A. I currently have a piezo buzzer attached to EHRPWM1B, and I can't for the life of me figure out how to get the PWM to work on the second channel. I've been using the cape-universal overlay that has been modified to remove the pins that I'm using for my UART2 cape and my LCD4 cape. The trouble with this approach is that it exports all PWM options, and I'm not sure which one I need to use. My guess for the PWM chip to use is pwmchip4. This is because when I try to export pwm0 it tells me it is in use, but it will allow me to export pwm1. This is pure speculation that I'm even using the right channel. I don't know enough about this OS to find out which pin is mapped where (still new to this environment). I've been following the instructions here: https://groups.google.com/d/msg/beagleboard/dkS51WbicTo/tZ13PZChCgAJ to try different PWM channels. I've been through all of the pwmchips (0, 1, 2, 4, 6) and none of them trigger my piezo buzzer. pwm1 in pwmchip4 is particularly nasty, it won't let me export a period or a duty cycle, it just says that the arguments are invalid. There don't appear to be many tutorials on how to use PWM in the 4.1 kernel, and even fewer examples on how to use EHRPWM1A and EHRPWM1B simultaneously, although from what I've been reading it should be possible. Any thoughts/pointers/help is appreciated. -- 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] BBB making connection to 82.165.8.211 on port 80
Hi, my BBB is attempting to make a connection to 82.165.8.211 on port 80. Any idea which service is doing this and it's purpose for doing so? 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] Backlight not working using the 4dcape-43 lcd
I need help enabling the pwm when using the 4dcape-43. P9_14 is the pin needed for the displays backlight according to the instructions. When I enable it I get a conflict with the display. Since I'm getting a conflict I assume it's being setup but I'm not sure how to access it. Using the backlight max_brightness is not working. In /sys/devices/ocp.3 I do see '48302000.epwmss' so I believe there is a pmw being setup. but how do I use it? Not really sure what to do next or how to resolve the conflict. The Kernel version is 3.8.13 Thanks, Rob root@beaglebone:/sys/devices/bone_capemgr.9# more slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:P---L 4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS ,BB-BONE-LCD4 -01 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 Adding the following to the uEnv.txt: root@beaglebone:~# echo am33xx_pwm > /sys/devices/bone_capemgr.9/slots root@beaglebone:~# echo bone_pwm_P9_14 > /sys/devices/bone_capemgr.9/slots [ 7558.435733] bone-capemgr bone_capemgr.9: part_number 'bone_pwm_P9_14', version 'N/A' [ 7558.449098] bone-capemgr bone_capemgr.9: slot #10: generic override [ 7558.455749] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 10 [ 7558.463871] bone-capemgr bone_capemgr.9: slot #10: 'Override Board Name,00A0,Override Manuf,bone pwm_P9_14' [ 7558.478213] bone-capemgr bone_capemgr.9: slot #10: Requesting part number/version based 'bone_pwm_P9_14-00A0.dtbo [ 7558.492824] bone-capemgr bone_capemgr.9: slot #10: Requesting firmware 'bone_pwm_P9_14-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 7558.510830] bone-capemgr bone_capemgr.9: slot #10: dtbo 'bone_pwm_P9_14-00A0.dtbo' loaded; converting to live tree [ 7558.525956] bone-capemgr bone_capemgr.9: slot #10: bone_pwm_P9_14 conflict P9.14 (#3:BB-BONE-LCD4-01) [ 7558.535801] bone-capemgr bone_capemgr.9: slot #10: Failed verification -sh: echo: write error: File exists The backlight brightness is shown at 100. cat /sys/class/backlight/blacklight.11/max_brightness = 100 -- 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] Enable P9_14 with 4DCape
On Tue, Feb 23, 2016 at 1:41 PM, wrote: > I need help enabling the pwm when using the 4dcape-43. P9_14 is the pin > needed for the display according to the instructions. When I enable it I get > a conflict with the display. Not really sure what to do next or how to > resolve the conflict. The Kernel version is 3.8.13 > Thanks, > Rob > > root@beaglebone:/sys/devices/bone_capemgr.9# more slots > 0: 54:PF--- > 1: 55:PF--- > 2: 56:PF--- > 3: 57:P---L 4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS > ,BB-BONE-LCD4 -01 > 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 > > > Adding the following to the uEnv.txt: > root@beaglebone:~# echo am33xx_pwm > /sys/devices/bone_capemgr.9/slots > root@beaglebone:~# echo bone_pwm_P9_14 > /sys/devices/bone_capemgr.9/slots Well, "P9_14" is the pin used for the pwm backlight control for the 4D cape. So if you don't want it to conflict, remove the lcd... Regards, -- Robert Nelson https://rcn-ee.com/ -- 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] Enable P9_14 with 4DCape
I need help enabling the pwm when using the 4dcape-43. P9_14 is the pin needed for the display according to the instructions. When I enable it I get a conflict with the display. Not really sure what to do next or how to resolve the conflict. The Kernel version is 3.8.13 Thanks, Rob root@beaglebone:/sys/devices/bone_capemgr.9# more slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:P---L 4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS ,BB-BONE-LCD4 -01 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 Adding the following to the uEnv.txt: root@beaglebone:~# echo am33xx_pwm > /sys/devices/bone_capemgr.9/slots root@beaglebone:~# echo bone_pwm_P9_14 > /sys/devices/bone_capemgr.9/slots [ 7558.435733] bone-capemgr bone_capemgr.9: part_number 'bone_pwm_P9_14', version 'N/A' [ 7558.449098] bone-capemgr bone_capemgr.9: slot #10: generic override [ 7558.455749] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 10 [ 7558.463871] bone-capemgr bone_capemgr.9: slot #10: 'Override Board Name,00A0,Override Manuf,bone pwm_P9_14' [ 7558.478213] bone-capemgr bone_capemgr.9: slot #10: Requesting part number/version based 'bone_pwm_P9_14-00A0.dtbo [ 7558.492824] bone-capemgr bone_capemgr.9: slot #10: Requesting firmware 'bone_pwm_P9_14-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 7558.510830] bone-capemgr bone_capemgr.9: slot #10: dtbo 'bone_pwm_P9_14-00A0.dtbo' loaded; converting to live tree [ 7558.525956] bone-capemgr bone_capemgr.9: slot #10: bone_pwm_P9_14 conflict P9.14 (#3:BB-BONE-LCD4-01) [ 7558.535801] bone-capemgr bone_capemgr.9: slot #10: Failed verification -sh: echo: write error: File exists The backlight brightness is shown at 100. cat /sys/class/backlight/blacklight.11/max_brightness = 100 . -- 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] CVE-2015-7547 glibc bug
On 02/23/2016 10:47 AM, mickeyf wrote: > Bingo! 'dpkg-query --show libc6 ' does show 6.7. > > Curious why ldd does not. ?? peter@black:~$ ldd --version ldd (Ubuntu EGLIBC 2.19-0ubuntu6.7) 2.19 ^^^ -- 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] What is special about SPI0 ?
Hello, I was working a DT Overlay for my touchscreen and ran to issues trying to load it. It can successfully load it via cape_enable=bone_capemgr.enable_partno=BB-ADS7846 (so I know the overlays works) but I don't get the same results (not working) via the command line. Investigating this further I noticed similar points with the SPI0 (BB-SPIDEV0-00A0.dts) and discovered it not setting the pin mux via the command line as I would expect. (SPIDEV0 also works via capemgr in uEnv.txt) I'm using the bog-standard BB-SPIDEV0-00A0.dts overlay from bb.org-overlays/src/arm. Everything else looks like it is working properly in dmesg. I can move forward using bone_capemgr.enable in uEnv.txt so this is not a critical issue but more a point of understanding what is going on (or not, as the case may be) and efficiency. I've googled around but could not find anything related to the newer 4.x kernels. Thanks in advance for any clues or assistance. *Environment:* root@beaglebone:~# uname -r; cat /etc/dogtag; dtc --version; cat /proc/cmdline 4.4.1-bone5 BeagleBoard.org Debian Image 2016-01-31 Version: DTC 1.4.1-g1e75ebc9 console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet .../boot/uEnv.txt ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: dtb=am335x-boneblack-overlay.dtb results do not vary if I use cape_universal=enable or not . I also tried the 4.1.16-ti-rt-r44 kernel …..noob-ish *Test* Following the instructions on William's website for loading an overlay UART1 (working as expected) http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/ *before* root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins | grep 'pin 96\|pin 97' pin 96 (44e10980.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 97 (44e10984.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep 'pin 96\|pin 97' pin 96 (44e10980.0) *0037 *pinctrl-single pin 97 (44e10984.0) *0037* pinctrl-single *load overlay* root@beaglebone:~# sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots" *(ignore the sudo part with root – just a copy & paste point !!!)* *after* root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins | grep 'pin 96\|pin 97' pin 96 (44e10980.0): 48022000.serial (GPIO UNCLAIMED) *function pinmux_bb_uart1_pins group pinmux_bb_uart1_pins * pin 97 (44e10984.0): 48022000.serial (GPIO UNCLAIMED) *function pinmux_bb_uart1_pins group pinmux_bb_uart1_pins * root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep 'pin 96\|pin pin 96 (44e10980.0) *0028* pinctrl-single pin 97 (44e10984.0) *0008* pinctrl-single root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-UART1 97' *unload* sudo sh -c "echo '-4' > /sys/devices/platform/bone_capemgr/slots" *same procedure for SPI0* *before* root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins | grep 'pin 84\|pin 85\|pin 86\|pin 87' pin 84 (44e10950.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 85 (44e10954.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 86 (44e10958.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 87 (44e1095c.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep 'pin 84\|pin 85\|pin 86\|pin 87' pin 84 (44e10950.0) *0037* pinctrl-single pin 85 (44e10954.0) *0037* pinctrl-single pin 86 (44e10958.0) *0037* pinctrl-single pin 87 (44e1095c.0) *0037* pinctrl-single *load overlay* sudo sh -c "echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots" *after* root@beaglebone:~# dmesg [ 3283.995279] bone_capemgr bone_capemgr: part_number 'BB-SPIDEV0', version 'N/A' [ 3283.995309] bone_capemgr bone_capemgr: slot #5: override [ 3283.995324] bone_capemgr bone_capemgr: Using override eeprom data at slot 5 [ 3283.995339] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-SPIDEV0' [ 3284.006848] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-SPIDEV0-00A0.dtbo' loaded; overlay id #0 root@beaglebone:~# ls /dev/spi* /dev/spidev1.0 /dev/spidev1.1 root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins | grep 'pin 84\|pin 85\|pin 86\|pin 87' pin 84 (44e10950.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 85 (44e10954.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 86 (44e10958.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 87 (44e1095c.0): (MUX UNCLAIMED) (GPIO UNCLAIMED) root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins | grep 'pin 84\|pin 85\|pin 86\|pin 87' pin 84 (44e10950.0) *0037* pinctrl-single pin 85 (44e10954.0) *0037* pinctrl-single pin 86 (44e10958.0
Re: [beagleboard] CVE-2015-7547 glibc bug
Bingo! 'dpkg-query --show libc6 ' does show 6.7. Curious why ldd does not. Thanks! On Tuesday, February 23, 2016 at 10:33:30 AM UTC-8, Peter Hurley wrote: > > On 02/23/2016 10:14 AM, mickeyf wrote: > > So if I updated today, that should be what I get. But as I said, what I > actually see is not "2.19-0ubuntu6.7" but "2.19-0ubuntu6" ( no ".7"). > > $ dpkg-query --show libc6 > > > -- 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] Slew rate when toggling Enhanced GPIO pins in the PRU?
First of all, Thank you all for your help and suggestions. It turns out it was the fault of the oscilloscope. I found a better model and found my rates to be ~1.5ns. In case anybody was curious, this is being designed to control a radioactive electron measurement ASIC. On Wednesday, February 17, 2016 at 12:10:00 AM UTC-5, lb...@basisvector.com wrote: > > The PRU rise and fall times are 1.00 - 3.00 nSec. Your scope probe or > application circuit may be limiting the slew rate. Another possibility is > your oscilloscope input is bandwidth limited. If you are using a 1X scope > probe it will contribute significant capacitive loading and slow the edges > way down. > > Keep us informed with your progress and good luck. > > Cheers, > > Lowell Bohn > Chief Engineer > Basis Vector LLC > (303) 249-3763 > > > -Original Message- > *From:* Przemek Klosowski [mailto:przemek@gmail.com ] > *Sent:* Tuesday, February 16, 2016 10:53 PM > *To:* beagl...@googlegroups.com > *Subject:* Re: [beagleboard] Slew rate when toggling Enhanced GPIO pins > in the PRU? > > On Tue, Feb 16, 2016 at 4:08 PM, John M > > wrote: > >> I'm trying to create a clock using the PRU, and I have it working to an >> extent, but I am noticing a discrepancy between what I read in the TRM and >> what I'm seeing. When I use a series of SET CLR SET CLR commands on a pin, >> they do not resolve completely before the next command. When I seperate >> each command by a delay, the rising edge of the clock takes ~90ns to go >> from 0V to 3.3V. I was under the impression that this operation would be >> performed at around ~5ns. >> > > Straight out Set/Clear would theoretically run at 100MHz (two > instructions of 5ns each), but when you connect them to the chip I/O, there > are effects of interconnect between the PRU and the I/O resources, Charles > Steinkuehler wrote it up in > https://github.com/machinekit/machinekit/blob/master/src/hal/drivers/hal_pru_generic/pru_generic.p > > > However, the rise time of the signal as seen by your oscilloscope is > totally unrelated to that: the signal on a pin should change within a IO > clock cycle and the skew you're seeing must be due to the RC(L) delays due > to factors such as the state of the pullup on the IO pin, capacitances and > inductances within the package, on your board and in your oscilloscope > probe and cable. > > > -- > 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.
Re: [beagleboard] CVE-2015-7547 glibc bug
On 02/23/2016 10:14 AM, mickeyf wrote: > So if I updated today, that should be what I get. But as I said, what I > actually see is not "2.19-0ubuntu6.7" but "2.19-0ubuntu6" ( no ".7"). $ dpkg-query --show libc6 -- 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] CVE-2015-7547 glibc bug
So if I updated today, that should be what I get. But as I said, what I actually see is not "2.19-0ubuntu6.7" but "2.19-0ubuntu6" ( no ".7"). Am I checking incorrectly, or is ldd under-reporting, or is there some other relatively painless way to confirm which version is actually present? On Tuesday, February 23, 2016 at 9:48:17 AM UTC-8, RobertCNelson wrote: > > On Tue, Feb 23, 2016 at 11:38 AM, mickeyf > wrote: > > We have a number of BBB that are running Ubuntu 14.04. Everything I've > found > > on this bug/patch indicates that 'ldd --version' should show the > vulnerable > > version of libc as 2.19-0ubuntu6.6, and the patched one as > 2.19-0ubuntu6.7. > > Both before and after running 'apt-get install libc6' all I see is > > '2.19-0ubuntu6', with no minor version number. > > > > I don't know if this is because this is the ARMHF build, or for some > other > > reason, but the bottom line is I don't know whether these BBBs are > > vulnerable or not. Can someone suggest a simple alternate way of > confirming > > which libc6 is installed, or shed light on this? > > According to: > > http://packages.ubuntu.com/trusty/libc6 > > & > > http://ports.ubuntu.com/pool/main/e/eglibc/ > > 2.19-0ubuntu6.7 was pushed out: 16-Feb-2016 > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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] BBB, Mysql, systemd and halt/reboot
Using Wheezy on the BBB (2015.03 console image). The mysql package is in the in-between state of apparently using both mysqld-safe and systemd. If I run "service mysql stop", the systemd mysql service stops seemingly happily and in /var/log/syslog I see the shutdown of mysql logged from mysqld. However, if I issue a system "halt" or "reboot" or even a systemctl poweroff, I see no evidence of a clean mysql shutdown in the syslog. I'm unsure if mysql is being halted cleanly upon system halt/reboot and just not logged, or if the process is just being killed (leading to the possibility of data corruption). Cheers for any pointers / debugging ideas. Jon Ross -- 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] CVE-2015-7547 glibc bug
On Tue, Feb 23, 2016 at 11:38 AM, mickeyf wrote: > We have a number of BBB that are running Ubuntu 14.04. Everything I've found > on this bug/patch indicates that 'ldd --version' should show the vulnerable > version of libc as 2.19-0ubuntu6.6, and the patched one as 2.19-0ubuntu6.7. > Both before and after running 'apt-get install libc6' all I see is > '2.19-0ubuntu6', with no minor version number. > > I don't know if this is because this is the ARMHF build, or for some other > reason, but the bottom line is I don't know whether these BBBs are > vulnerable or not. Can someone suggest a simple alternate way of confirming > which libc6 is installed, or shed light on this? According to: http://packages.ubuntu.com/trusty/libc6 & http://ports.ubuntu.com/pool/main/e/eglibc/ 2.19-0ubuntu6.7 was pushed out: 16-Feb-2016 Regards, -- Robert Nelson https://rcn-ee.com/ -- 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] CVE-2015-7547 glibc bug
We have a number of BBB that are running Ubuntu 14.04. Everything I've found on this bug/patch indicates that 'ldd --version' should show the vulnerable version of libc as 2.19-0ubuntu6.6, and the patched one as 2.19-0ubuntu6.7. Both before and after running 'apt-get install libc6' all I see is '2.19-0ubuntu6', with no minor version number. I don't know if this is because this is the ARMHF build, or for some other reason, but the bottom line is I don't know whether these BBBs are vulnerable or not. Can someone suggest a simple alternate way of confirming which libc6 is installed, or shed light on this? 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] LCD touch screen is not saved after reboot
Hello there, I am using BeagleBone Black with 4D LCD touch screen. When I do the calibration, it works alright but after reboot I have to redo it, its not being save. Could you please tell me how can I save it so it wont be lost after reboot? I would appreciate all help! -- 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.
