[beagleboard] heres a LOL moment
http://www.computerworld.com/article/2605093/laid-off-from-job-man-builds-tweeting-toilet.html You 2 can have your very own BBB toilet -- 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: BeagleBone Black switching to 3.14 kernel
Will the kernel have PREEMPT enabled as its now disabled for debian ? On Monday, August 18, 2014 6:56:34 AM UTC+5:30, Jason Kridner wrote: It is time to make another big software push for BeagleBone Black. We have several recent updates from Robert, including managing the kernel as Debian packages. To try out the new code, use one of the recent images from: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 Then, you'll need to switch to the 3.14 kernel: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 Report issues to one of these trackers: https://github.com/beagleboard/linux http://bugs.elinux.org/projects/debian-image-releases The device tree overlay support is still under development as is built-in 'config-pin/cape-universal' support, so static configuration of the .dtb is currently required. Your help is requested to make sure the default .dtb file includes as many configurations as possible that can be enabled from userspace. Update summary: * Repo moved to https://github.com/beagleboard/linux * Layout of Debian images now enable 'apt-get' updates to the kernel, but you need to grab a newer starting distro image * The false-start on the cape-firmware repo has been abandoned and device tree overlays are now part of the kernel tree * The kernel currently uses DMA for the USB and includes SGX support I've setup a buildbot hosted at http://builds.beagleboard.org, but I'm still working on getting it to handle pull requests, multiple branches, etc. like the MachineKit folks are doing, as well as pushing out the builds. After a bit more feedback, I'll push out some blog posts, etc. to get more people involved. Thanks for your 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.
[beagleboard] Beagle Bone Black PRU Cape
Hi, During my research, I discovered that there is a BeagleBone Black PRU CAPE. = http://www.ti.com/lit/df/tidr938/tidr938.pdf Do you know where I can buy it ? Thx you, Micka. -- 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: Beagle Bone Black PRU Cape
More info at: http://www.ti.com/lit/ug/tidu426/tidu426.pdf -- 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 bus recovery
This does not tell us strictly speaking if the canbus itself has issues, but we have a heartbeat device on the canbus. If we fail to hear from it (or any other traffic) for a set period of time, we reset the canbus as you described. In practice I've only seen this reset trigger when I've forgotten to specify or turn on a heartbeat device, or intentionally for testing. It was implemented as a safety net since the older generation windows based system (which was admittedly much larger, more complex, and used third party hardware and drivers) would sometimes fail for mysterious reasons. -- 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: Accessing BeagleBoard features through Mono runtime on Ubuntu for C# development
doesn't support? Doesn't come pre-installed, perhaps. What's not to support? On Wednesday, September 10, 2014 7:08:48 AM UTC-7, Peter Gregory wrote: What version of Ubuntu are you running? I believe 14.04 doesn't support mono. -- 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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
Hi Robert, I checked this morning and it's A3 [0.595611] bone-capemgr bone_capemgr.9: slot #0: '4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01' [0.689675] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMI [0.689690] bone-capemgr bone_capemgr.9: Skipping loading of disabled cape with part# BB-BONELT-HDMIN [0.689887] bone-capemgr bone_capemgr.9: loader: before slot-0 BB-BONE-LCD7-01:00A3 (prio 0) [0.689902] bone-capemgr bone_capemgr.9: loader: check slot-0 BB-BONE-LCD7-01:00A3 (prio 0) [0.689942] bone-capemgr bone_capemgr.9: initialized OK. [0.692709] bone-capemgr bone_capemgr.9: loader: after slot-0 BB-BONE-LCD7-01:00A3 (prio 0) [0.692732] bone-capemgr bone_capemgr.9: slot #0: Requesting part number/version based 'BB-BONE-LCD7-01-00A3.dtbo [0.692749] bone-capemgr bone_capemgr.9: slot #0: Requesting firmware 'BB-BONE-LCD7-01-00A3.dtbo' for board-name '4D 7.0 LCD CAPE- 4DCAPE-70T ', version '00A3' [0.692769] bone-capemgr bone_capemgr.9: slot #0: dtbo 'BB-BONE-LCD7-01-00A3.dtbo' loaded; converting to live tree Also got [ 12.306552] tilcdc 4830e000.fb: timeout waiting for framedone [ 24.290871] tilcdc 4830e000.fb: timeout waiting for framedone but everything is working fine. -- 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
On Saturday, August 30, 2014 12:01:18 PM UTC+1, 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.
The dts file I used (on a 3.8 kernel) was:
/*
** Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
**
** This program is free software; you can redistribute it and/or modify
** it under the terms of the GNU General Public License version 2 as
** published by the Free Software Foundation.
*/
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
part-number = BB-W1;
version = 00A0;
/* Resources used */
exclusive-use =
/* the pin header */
P8.11,
/* The first pin is the data pin. The second
** (optional) pin enables an external pull-up.
*/
gpio1_13;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
w1_pins: pinmux_w1_pins {
pinctrl-single,pins =
0x34 0x37 /* gpmc_ad13.gpio1_13 P8_11,
OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 */
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
onewire@0 {
compatible = w1-gpio;
pinctrl-names = default;
pinctrl-0 = w1_pins;
status = okay;
/* nb. gpio index is (resources index + 1) */
gpios = gpio2 13 0;
};
};
};
};
/*
** eof
*/
I built the dtbo file with:
#!/bin/bash
dtc -O dtb -o BB-W1-00A0.dtbo -b 0 -@ w1.dts
# Copy the dtbo file into /lib/firmware
and then loaded it with:
#!/bin/bash
echo BB-W1 /sys/devices/bone_capemgr.8/slots
I could then read the DS18B20 with:
#!/bin/bash
cat /sys/devices/w1_bus_master1/28-03e6b937/w1_slave
Good luck - Will
--
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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
On Thu, Sep 11, 2014 at 8:12 AM, Cedric Malitte cedric.mali...@gmail.com wrote: Hi Robert, I checked this morning and it's A3 [0.595611] bone-capemgr bone_capemgr.9: slot #0: '4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01' Ah, the 4dcape-70t, (i grabbed the wrong lcd this morning..) So this one was a little fun to get working, i don't remember if i pushed all the fixes to v3.15.x sudo apt-get update sudo apt-get install linux-image-3.14.17-ti-r19 sudo cp -v /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.dtb /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.bak sudo cp -v /boot/dtbs/3.14.17-ti-r19/am335x-boneblack-4dcape-70t.dtb /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.dtb sudo reboot Regards, -- Robert Nelson http://www.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] BeagleBone Black DDR3 RAM Voltage levels
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
javascript: wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
because initially it did.. It was designed this way because when it was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in eeprom:
262 /*
263 * Override what we have detected since we know if we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE
and MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1 but it never reached the rest of the world so it's more a happy
accident that should be corrected (and wouldn't be too hard to do, if
anyone out there is looking for a reason to get their feet wet ).
--
Tom
--
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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
I will try, but I'm checking diffs between 3.8.13 dts and 3.15.10, because using dtb from 3.14 is not really a solution for me as I also need pruss. Well I think :) Thanks Le jeudi 11 septembre 2014 10:02:28 UTC-4, RobertCNelson a écrit : On Thu, Sep 11, 2014 at 8:12 AM, Cedric Malitte cedric@gmail.com javascript: wrote: Hi Robert, I checked this morning and it's A3 [0.595611] bone-capemgr bone_capemgr.9: slot #0: '4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS ,BB-BONE-LCD7-01' Ah, the 4dcape-70t, (i grabbed the wrong lcd this morning..) So this one was a little fun to get working, i don't remember if i pushed all the fixes to v3.15.x sudo apt-get update sudo apt-get install linux-image-3.14.17-ti-r19 sudo cp -v /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.dtb /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.bak sudo cp -v /boot/dtbs/3.14.17-ti-r19/am335x-boneblack-4dcape-70t.dtb /boot/dtbs/3.14.17-ti-r19/am335x-boneblack.dtb sudo reboot Regards, -- Robert Nelson http://www.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] Re: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
On Thu, Sep 11, 2014 at 9:26 AM, Cedric Malitte cedric.mali...@gmail.com wrote: I will try, but I'm checking diffs between 3.8.13 dts and 3.15.10, because using dtb from 3.14 is not really a solution for me as I also need pruss. Well I think :) https://github.com/beagleboard/linux/commit/94f48ff05623afbfcf75ca211b4c4df23a66f82e starting with r18, we got pruss from ti.. Regards, -- Robert Nelson http://www.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] BeagleBone Black DDR3 RAM Voltage levels
On Thursday, September 11, 2014 10:23:40 AM UTC-4, Tom Rini wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
because initially it did.. It was designed this way because when it was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in
eeprom:
262 /*
263 * Override what we have detected since we know if we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE
and MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1 but it never reached the rest of the world so it's more a happy
accident that should be corrected (and wouldn't be too hard to do, if
anyone out there is looking for a reason to get their feet wet ).
Yeah, I was looking for DCDC1 and couldn't find it, so I'm working on
adding it now. Not sure how quick I'll get it posted, so I wouldn't mind
someone else chiming in with the fix.
--
Tom
--
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] BeagleBone Black DDR3 RAM Voltage levels
On Thu, Sep 11, 2014 at 9:23 AM, Tom Rini tom.r...@gmail.com wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
because initially it did.. It was designed this way because when it was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in eeprom:
262 /*
263 * Override what we have detected since we know if we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE and
MPU) voltage. I don't know what initial bring-up U-Boot was whacking DCDC1
but it never reached the rest of the world so it's more a happy accident
that should be corrected (and wouldn't be too hard to do, if anyone out
there is looking for a reason to get their feet wet ).
Well, the original v2013.04 patchset can be seen here:
https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/recipes-bsp/u-boot/u-boot-denx
The only thing that touches the pmic, is this hack:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-bsp/u-boot/u-boot-denx/0004-beaglebone-HACK-raise-USB-current-limit.patch
I don't have my tps decoder ring, so i'm not sure if that address is
more then just the usb current setting..
Regards,
--
Robert Nelson
http://www.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] CAN bus recovery
Brent, have you tried to use can-utils to dump traffic on the canbus when the NIC is found in that bad state? AFAIK, socketCAN implementation on linux does not utilize ID filtering on the can transceiver, it is done at the SocketCAN api level. You maybe able to see traffic. Also, what can transceiver are you using? -- 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 A6 B running slow, C ok
From dmesg: A6 - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 B - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone 60 - vdd-mpu 1325 mV, Bogomips 993 Also: A6 - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 B - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone47 - vdd-mpu 1325 mV, Bogomips 993 Do this mean that the A6 B boards are running at 500 or 600 MHz? -- 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 A6 B running slow, C ok
On Thu, Sep 11, 2014 at 10:23 AM, jstam...@gmail.com wrote: From dmesg: A6 - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 B - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone 60 - vdd-mpu 1325 mV, Bogomips 993 Also: A6 - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 B - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone47 - vdd-mpu 1325 mV, Bogomips 993 Do this mean that the A6 B boards are running at 500 or 600 MHz? With the little information you have shown. My guess, your Revision C is running a newer bootloader that enabled 1Ghz at bootup.. Regards, -- Robert Nelson http://www.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 A6 B running slow, C ok
What information would you like? What is the latest version of the bootloader for these boards? On Thu, Sep 11, 2014 at 11:27 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Sep 11, 2014 at 10:23 AM, jstam...@gmail.com wrote: From dmesg: A6 - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 B - Debian bone 60 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone 60 - vdd-mpu 1325 mV, Bogomips 993 Also: A6 - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 B - Angstrom 3.8.13 - vdd-mpu 1100 mV, Bogomips 545 C - Debian bone47 - vdd-mpu 1325 mV, Bogomips 993 Do this mean that the A6 B boards are running at 500 or 600 MHz? With the little information you have shown. My guess, your Revision C is running a newer bootloader that enabled 1Ghz at bootup.. Regards, -- Robert Nelson http://www.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. -- John Stampfl -- 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 A6 B running slow, C ok
On Thu, Sep 11, 2014 at 10:34 AM, John Stampfl jstam...@gmail.com wrote: What information would you like? What is the latest version of the bootloader for these boards? Well, since the C works.. Run the debian flasher on the A6/B http://beagleboard.org/latest-images Regards, -- Robert Nelson http://www.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 A6 B running slow, C ok
Ok, will do that tomorrow and report On Thu, Sep 11, 2014 at 11:37 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Sep 11, 2014 at 10:34 AM, John Stampfl jstam...@gmail.com wrote: What information would you like? What is the latest version of the bootloader for these boards? Well, since the C works.. Run the debian flasher on the A6/B http://beagleboard.org/latest-images Regards, -- Robert Nelson http://www.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. -- John Stampfl -- 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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
Le jeudi 11 septembre 2014 10:32:25 UTC-4, RobertCNelson a écrit :
On Thu, Sep 11, 2014 at 9:26 AM, Cedric Malitte
cedric@gmail.com javascript: wrote:
I will try, but I'm checking diffs between 3.8.13 dts and 3.15.10,
because
using dtb from 3.14 is not really a solution for me as I also need
pruss.
Well I think :)
https://github.com/beagleboard/linux/commit/94f48ff05623afbfcf75ca211b4c4df23a66f82e
starting with r18, we got pruss from ti..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Ok, so LCD7 is working now.
What I did:
in pinmux file:
bbcape_lcd7_pins: bbcape_lcd7_pins {
pinctrl-single,pins =
*0x150 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* spi0_sclk.gpio0_2, OUTPUT | MODE7
- AVDD_EN */*
0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */
*0xa3 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */*
0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */
0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */
0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */
0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */
0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */
0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */
0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */
0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */
0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */
0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */
0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */
0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */
0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */
0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */
0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */
0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */
0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */
0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en (lcd_en) */
;
};
in bone-panel-800x480
panel {
status = okay;
compatible = ti,tilcdc,panel;
pinctrl-names = default;
pinctrl-0 = *bbcape_lcd7_pins*;
panel-info {
ac-bias = 255;
ac-bias-intrpt= 0;
dma-burst-sz = 16;
bpp = 16;
fdd = 0x80;
sync-edge = 0;
sync-ctrl = 1;
raster-order = 0;
fifo-th = 0;
* tft-alt-mode = 0;*
* stn-565-mode = 0;*
};
display-timings {
native-mode = timing0;
/* Settings for ThreeFive S9700RTWV35TR / LCD7 cape: */
timing0: 800x480 {
clock-frequency = 3000;
hactive = 800;
vactive = 480;
hfront-porch = 40;
hback-porch = 40;
hsync-len = 48;
vback-porch = 29;
vfront-porch = 13;
vsync-len = 3;
hsync-active = 0;
vsync-active = 0;
};
};
};
Looks like the lcd.data1 which is used on 7 screens is not the same as on
4 ones.
As for Pruss, in 3.15 bone 6 I patched uio_pruss.c driver, and enabled it
in dts / Kernel config.
Will check for your remoteproc driver.
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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
On Thu, Sep 11, 2014 at 11:00 AM, Cedric Malitte
cedric.mali...@gmail.com wrote:
Le jeudi 11 septembre 2014 10:32:25 UTC-4, RobertCNelson a écrit :
On Thu, Sep 11, 2014 at 9:26 AM, Cedric Malitte
cedric@gmail.com wrote:
I will try, but I'm checking diffs between 3.8.13 dts and 3.15.10,
because
using dtb from 3.14 is not really a solution for me as I also need
pruss.
Well I think :)
https://github.com/beagleboard/linux/commit/94f48ff05623afbfcf75ca211b4c4df23a66f82e
starting with r18, we got pruss from ti..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Ok, so LCD7 is working now.
What I did:
in pinmux file:
bbcape_lcd7_pins: bbcape_lcd7_pins {
pinctrl-single,pins =
0x150 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* spi0_sclk.gpio0_2, OUTPUT | MODE7 -
AVDD_EN */
I think this was the fix ^..
I can do something simlar to:
https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-common-pinmux.dtsi#L66
which i did to make the lcd4 work..
0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */
0xa3 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */
I saw this too... 0xa3 is not a valid pin...
0xa8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data2.lcd_data2 */
0xac (PIN_OUTPUT | MUX_MODE0) /* lcd_data3.lcd_data3 */
0xb0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data4.lcd_data4 */
0xb4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data5.lcd_data5 */
0xb8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data6.lcd_data6 */
0xbc (PIN_OUTPUT | MUX_MODE0) /* lcd_data7.lcd_data7 */
0xc0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data8.lcd_data8 */
0xc4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data9.lcd_data9 */
0xc8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data10.lcd_data10 */
0xcc (PIN_OUTPUT | MUX_MODE0) /* lcd_data11.lcd_data11 */
0xd0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data12.lcd_data12 */
0xd4 (PIN_OUTPUT | MUX_MODE0) /* lcd_data13.lcd_data13 */
0xd8 (PIN_OUTPUT | MUX_MODE0) /* lcd_data14.lcd_data14 */
0xdc (PIN_OUTPUT | MUX_MODE0) /* lcd_data15.lcd_data15 */
0xe0 (PIN_OUTPUT | MUX_MODE0) /* lcd_vsync.lcd_vsync */
0xe4 (PIN_OUTPUT | MUX_MODE0) /* lcd_hsync.lcd_hsync */
0xe8 (PIN_OUTPUT | MUX_MODE0) /* lcd_pclk.lcd_pclk */
0xec (PIN_OUTPUT | MUX_MODE0) /* lcd_ac_bias_en.lcd_ac_bias_en (lcd_en) */
;
};
in bone-panel-800x480
panel {
status = okay;
compatible = ti,tilcdc,panel;
pinctrl-names = default;
pinctrl-0 = bbcape_lcd7_pins;
panel-info {
ac-bias = 255;
ac-bias-intrpt= 0;
dma-burst-sz = 16;
bpp = 16;
fdd = 0x80;
sync-edge = 0;
sync-ctrl = 1;
raster-order = 0;
fifo-th = 0;
tft-alt-mode = 0;
stn-565-mode = 0;
These last two are not in the driver...
Regards,
--
Robert Nelson
http://www.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] BeagleBone Black DDR3 RAM Voltage levels
On Thu, Sep 11, 2014 at 9:32 AM, Jason Kridner jkrid...@gmail.com wrote:
On Thursday, September 11, 2014 10:23:40 AM UTC-4, Tom Rini wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped somewhere
because initially it did.. It was designed this way because when it was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in
eeprom:
262 /*
263 * Override what we have detected since we know if we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE
and MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1 but it never reached the rest of the world so it's more a happy
accident that should be corrected (and wouldn't be too hard to do, if anyone
out there is looking for a reason to get their feet wet ).
Yeah, I was looking for DCDC1 and couldn't find it, so I'm working on adding
it now. Not sure how quick I'll get it posted, so I wouldn't mind someone
else chiming in with the fix.
Here's a fix for the dts..
debian@beaglebone:/opt/source/dtb-3.14-ti/src/arm$ git diff am335x-boneblack.dts
diff --git a/src/arm/am335x-boneblack.dts b/src/arm/am335x-boneblack.dts
index d594da5..c1420f3 100644
--- a/src/arm/am335x-boneblack.dts
+++ b/src/arm/am335x-boneblack.dts
@@ -26,6 +26,15 @@
pinctrl-0 = clkout2_pin;
};
+dcdc1_reg {
+ /* VDD_DDR3 voltage 1.35V */
+ regulator-name = vdd_ddr3;
+ regulator-min-microvolt = 135;
+ regulator-max-microvolt = 135;
+ regulator-boot-on;
+ regulator-always-on;
+};
+
#include am335x-boneblack-emmc.dtsi
/* spi0: */
debian@beaglebone:/opt/source/dtb-3.14-ti/src/arm$ dmesg | grep vdd
[3.216522] vdd_ddr3: 1350 mV
[3.219877] vdd_mpu: 925 -- 1375 mV at 1325 mV
[3.221770] vdd_core: 925 -- 1150 mV at 1125 mV
Regards,
--
Robert Nelson
http://www.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] BeagleBone Black DDR3 RAM Voltage levels
Here's a fix for the dts..
debian@beaglebone:/opt/source/dtb-3.14-ti/src/arm$ git diff
am335x-boneblack.dts
diff --git a/src/arm/am335x-boneblack.dts b/src/arm/am335x-boneblack.dts
index d594da5..c1420f3 100644
--- a/src/arm/am335x-boneblack.dts
+++ b/src/arm/am335x-boneblack.dts
@@ -26,6 +26,15 @@
pinctrl-0 = clkout2_pin;
};
+dcdc1_reg {
+ /* VDD_DDR3 voltage 1.35V */
+ regulator-name = vdd_ddr3;
+ regulator-min-microvolt = 135;
+ regulator-max-microvolt = 135;
+ regulator-boot-on;
+ regulator-always-on;
+};
+
#include am335x-boneblack-emmc.dtsi
/* spi0: */
debian@beaglebone:/opt/source/dtb-3.14-ti/src/arm$ dmesg | grep vdd
[3.216522] vdd_ddr3: 1350 mV
[3.219877] vdd_mpu: 925 -- 1375 mV at 1325 mV
[3.221770] vdd_core: 925 -- 1150 mV at 1125 mV
and u-boot (off head)
voodoo@hades:/opt/github/u-boot$ git diff
diff --git a/board/ti/am335x/board.c b/board/ti/am335x/board.c
index 0739e60..6b6dea0 100644
--- a/board/ti/am335x/board.c
+++ b/board/ti/am335x/board.c
@@ -300,6 +300,15 @@ void am33xx_spl_board_init(void)
return;
}
+ /* Set DCDC1 (DDR3) to 1.35V for Beaglebone Black. */
+ if (board_is_bone_lt(header)) {
+ if (tps65217_voltage_update(TPS65217_DEFDCDC1,
+
TPS65217_DCDC_VOLT_SEL_1350MV)) {
+ puts(tps65217_voltage_update failure\n);
+ return;
+ }
+ }
+
/*
* Set LDO3, LDO4 output voltage to 3.3V for Beaglebone.
* Set LDO3 to 1.8V and LDO4 to 3.3V for Beaglebone Black.
diff --git a/include/power/tps65217.h b/include/power/tps65217.h
index 297c4cb..008fd6d 100644
--- a/include/power/tps65217.h
+++ b/include/power/tps65217.h
@@ -68,6 +68,7 @@ enum {
#define TPS65217_DCDC_VOLT_SEL_1125MV 0x09
#define TPS65217_DCDC_VOLT_SEL_1275MV 0x0F
#define TPS65217_DCDC_VOLT_SEL_1325MV 0x11
+#define TPS65217_DCDC_VOLT_SEL_1350MV 0x12
#define TPS65217_LDO_MASK 0x1F
#define TPS65217_LDO_VOLTAGE_OUT_1_8 0x06
hopefully that's enough to fix some of the emi problems your fighting..
Regards,
--
Robert Nelson
http://www.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] Re: registering asynchronous events on kernel thread in user space
Hi John 1. You said that i can execute control functions / time critical functions using PRU, but how ? Is there any guide/sample code to using the PRU like in github ? 2. There is nothing described about using PRU in the TRM, except that its has 7 interrupt lines so are there application notes or guides or ready to use libraries. 3. Any reason why you suggested that i can use PRU for time critical operations and can generate a signal to the user-space reliably without that jitter you were referring to ? Thanks On Thursday, September 11, 2014 12:50:36 AM UTC+5:30, john3909 wrote: From: neo prag@gmail.com javascript: Reply-To: beagl...@googlegroups.com javascript: beagl...@googlegroups.com javascript: Date: Wednesday, September 10, 2014 at 5:13 AM To: beagl...@googlegroups.com javascript: beagl...@googlegroups.com javascript: Subject: Re: [beagleboard] Re: registering asynchronous events on kernel thread in user space Hi Brandon Thanks for the reply. I will summarize here what i found about controlling a GPIO and about using interrupts. 1. Using sysfs one can easily control the gpio and using threading can re-create pseudo-interrupt from user space. Found a useful project called libsoc https://github.com/jackmitch/libsoc. They use threading along with polling using poll(2) 2. Using mmap() one can import the memory space of the GPIO peripheral and with a combination of threads can re-create pseudo-interrupt from user space. Found useful project called BBBIOlib https://github.com/VegetableAvenger/BBBIOlib. 3. Using /dev/input/event for controlling GPIO from user space. 4. Using an LKM from kernel space where one can use request_irq() or request_threaded_irq() and using some kind of buffering to transfer the data to userspace. Here one will be writing actual interrupts. Some bits can be found here http://processors.wiki.ti.com/index.php/GPIO_Driver_Guide#Sysfs_entries_configuration I have very good idea about 1 and 2. I am still working on 3- /dev/input and also on 4- about writing a real ISR. Although the above methods enable GPIO control I am not sure which will give me the highest performance. I read that using mmap() method gives faster switching on forums and the using sysfs gives the slowest switching rate. I am not sure about /dev/input method. The LKM method gives faster ISR and i am guessing that LKM in combination with mmap() will give faster response timings. Any thoughts on the above... You are on the right path. One thing to remember, whenever you are doing any I/O from user space, you are dealing with context switching and thread scheduling, which means that your application won’t respond to a GPIO event for anywhere from a few ms to 100mS. This is true because of both the interrupt latency in Linux and thread scheduler. In most cases, this is fine, because the user doesn’t know the difference. However, if you are attempting to do some sort of control, then you may want to consider the PRU. The PRU can still send events to your user space app. Another solution might be Xenomai which reduces to interrupt latency to about 50uS on the BBB, but you still have the context switch delay. Regards, John On Wednesday, September 10, 2014 8:20:18 AM UTC+5:30, Brandon I wrote: Before you jump into the kernel hole, is there a reason that you're not using the existing sysfs gpio interface ( https://www.kernel.org/doc/Documentation/gpio/sysfs.txt) for the interrupts? Using this, if you set the gpio up as an interrupt with the sysfs interface, you poll() the value file and it will block until there's an interrupt. When it unblocks, you can read the current value. Or, you can make the gpio look like an event/button: http://bec-systems.com/site/281/how-to-implement-an-interrupt-driven-gpio-input-in-linux Any sane way you do it will be the same at the low level. You'll have a read or ioctl function on the kernel device file that blocks in the kernel using a completion/semaphore, putting your process/thread to sleep. When the interrupt fires, the interrupt handler function is called to release the completion/semaphore, unblocking your process/thread and allowing it to continue executing. This unblocking is how the userspace program is signaled. So, if you *want* to reinvent the wheel, for understanding, then that's fine. But, there's an existing interface that exists, only a few lines of code away. --Brandon On Tue, Sep 9, 2014 at 7:10 PM, neo star prag@gmail.com wrote: Hi Brandon I read through the link, very informative thanks.I can create a thread to do the polling and signal me when its ready. But how to really write an ISR in arm. I see a lot of guides but they say that it will work in Intel processors but they are not sure about ARM. For sure from my readings i see that i need
[beagleboard] Re: Boards abilities
I would suggest looking at Dokeos or Moodle as a web-based platform to deliver your curriculum from either the Rpi or the BBB. They are both great tools. I've used both in hosted settings but haven't tried them on an embedded Linux platform yet... so I can't vouch for performance. -- 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: registering asynchronous events on kernel thread in user space
Hi Brandon 1. I agree with jitter involved with processing interrupts and 100% cpu usage during polling for the same, so is there no way to let the user-space know that interrupt has occurred apart from polling ? 2. The reason why i said pseudo-interrupt is because we are polling and waiting there which is same as watching a flag in a UART register for RX flag to set. 3. I am curious as to how interrupts for Ethernet and usb are written. I am guessing that the ISR will use the DMA to transfer bytes to user-space. But even in that case the userspace should know that a new data has arrived. Then hoe to synchronize the kernel space and user-space if there are to share a data ? Thanks... On Thursday, September 11, 2014 2:26:15 AM UTC+5:30, Brandon I wrote: pseudo-interrupt from user space There's nothing pseudo about it. Again, any usual way to have a userspace application respond to an interrupt will be the exact same. The kernel will block the userspace process until the interrupt is seen. The only real alternative is burning up the cpu with memory polling, which appears to be what the BBIOlib method uses. So, your latency is limited to your poll speed (which can be faster than interrupts). But, if you have a constant poll for minimum latency, lets hope you're not trying to do something important elsewhere since your cpu usage will be at 100%, and you'll be maximizing process to process context switching! For 4, The only difference between a userspace and kernel space interrupt handler is where the code is that responds to the interrupt. You will only benefit from writing your own interrupt handler if you put all of your code that does something with that interrupt in the kernel. Otherwise, you're back to process blocked by kernel, interrupt occurs, kernel unblocks process, process does something after seeing the interruptback to the sysfs/UIO method. I would try some benchmarks. See if the regular UIO/sysfs interrupt method gives you sufficient performance. And definitely keep in mind John's statement. You're going to see a massive amount of jitter for anything in userspace or kernel space (better jitter since you can disable interrupts and whatnot, but if you don't finish quickly in kernel space, you'll crash the kernel). If something like a precise timestamp is needed for an async event, then there are other ways to approach this. If you're looking for fixed low latency, you're doomed. On Wed, Sep 10, 2014 at 5:13 AM, neo prag@gmail.com javascript: wrote: pseudo-interrupt from user space -- 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: Purchase original Beaglebone (white)
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] Trying to use ttyO0 but I can't disable the console login.
I've got a RS232 micro cape http://www.logicsupply.com/components/beaglebone/capes/cbb-ttl-232/ that I need to use as a serial port. The problem is that by default /dev/ttyO0 is setup as a login console. I need to disable that so that I can use the port for my own purposes. I've found instructions for how to do it on Rasbian but I can't find anything for the Beaglebone. I found a line in /etc/inittab that looked like it was starting a getty session on /dev/ttyO0 and I commented it out but after a reboot, the login is still there. I found some references to inittab being obsolete because systemd doesn't use it but I can't find anything to configure systemd so it doesn't use ttyO0. Can anyone point me in the right direction? -- 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 bus recovery
You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- 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] Beaglebone black, Debian, Setting up Wifi access point.
Hi Colin, Have you figured out whether it is a config or dongle issue? Thanks! On Tuesday, July 8, 2014 3:21:34 PM UTC-7, Colin Bester wrote: i purchased Ralink5370 USB dongle and it is working as access point. I am having issues connecting with a windows client but am not yet sure on cause - whether its a config issue or USB wifi dongle issue. My hostapd.conf file ``` ### Default hostapd settings ## Wireless network name ###interface=wlan0 Set your bridge name bridge=br0#driverdriver=nl80211country_code=USssid=biocharger_defaultchannel=7hw_mode=g# # Static WPA2 key configuration# #1=wpa1, 2=wpa2, 3=bothwpa=3wpa_passphrase=apassword## Key management algorithms ##wpa_key_mgmt=WPA-PSK### Set cipher suites (encryption algorithms) TKIP = Temporal Key Integrity Protocol## CCMP = AES in Counter mode with CBC-MACwpa_pairwise=TKIP#rsn_pairwise=CCMP### Shared Key Authentication ##auth_algs=1## Accept all MAC address ###macaddr_acl=0#enables/disables broadcasting the ssidignore_broadcast_ssid=0# Needed for Windows clientseapol_key_index_workaround=0 ``` My udhcpd.conf file: ``` ### default udhcpd configuration file ###start 192.168.4.2end 192.168.4.9interface wlan0max_leases 8option subnet 255.255.255.248 ``` My /etc/network/interfaces file (pretty much everything commented out: ``` ###Default network interfaces, supporting eth0 and wlan0 configured as Access Pointauto loiface lo inet loopback# The primary network interfaceallow-hotplug eth0iface eth0 inet dhcp# WiFiallow-hotplug wlan0#iface wlan0 inet static# address 192.168.4.1#network 192.168.4.0#netmask 255.255.255.0#broadcast 192.168.4.255#hostapd /etc/hostapd/hostapd.conf ``` On Monday, July 7, 2014 2:18:37 AM UTC-5, chrich...@gmail.com wrote: I got the same Problems. Could you please tell me which dongle you bought and send me the conf-file? Thx, Heiko -- 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: Device Tree Compiler
Hi Robert,
I want to read/write data directly from the registers for SPI0.
1) I read the arm335X manual for this.
2) I am coding in C.
3) According to the manual I have to first soft reset the the module. For
this purpose I have to set the RESETDONE bit in the MCSPI_SYSCONFIG
register.
4) So I am first using mmap to map the device register.
5) then using the offset I am reaching to the particular register's address
6) As soon as I do any operation with the content of the register I get Bus
Error.
this is my code
#include stdio.h
#include stdlib.h
#include sys/stat.h
#include fcntl.h
#include unistd.h
#include sys/ioctl.h
#include linux/types.h
#include linux/spi/spidev.h
//Xenomai for mapping the register
#include sys/mman.h
#define SPI0_START_ADDR 0x4803 //mcspi0 data registers
#define SPI0_END_ADDR 0x48030FFF
#define SPI0_SIZE (SPI0_END_ADDR - SPI0_START_ADDR + 0x01) // 4KB
#define SPI1_START_ADDR 0x481A //mcspi1 data registers
#define SPI1_END_ADDR 0x481A0FFF
#define SPI1_SIZE (SPI1_END_ADDR - SPI1_START_ADDR + 0x01) // 4KB
//print_output(void *data) {
// unsigned int *my_data =
//}
int main (int *argc, int **argv)
{
printf(%d\n,sysconf(_SC_PHYS_PAGES));
mlockall (MCL_CURRENT | MCL_FUTURE);
int fd, outputfile;
struct stat attr;
void *spi0_addr = NULL;
//SPI Registers
volatile unsigned int *mcspi_revision = NULL;
volatile unsigned int *mcspi_sysconfig = NULL;
volatile unsigned int *mcspi_sysstatus = NULL;
volatile unsigned int *mcspi_irqstatus = NULL;
volatile unsigned int *mcspi_irqenable = NULL;
volatile unsigned int *mcspi_syst = NULL;
volatile unsigned int *mcspi_modulctrl = NULL;
volatile unsigned int *mcspi_ch0conf = NULL;
volatile unsigned int *mcspi_ch0stat = NULL;
volatile unsigned int *mcspi_ch0ctrl = NULL;
volatile unsigned int *mcspi_tx0 = NULL;
volatile unsigned int *mcspi_rx0 = NULL;
if ((fd = open(/dev/mem, O_RDWR | O_SYNC)) 0) {
fprintf(stderr, can not open /dev/mem!\n);
exit(-1);
}
else {
printf(Mapping %x - %x (size: 0x%x bytes)\n,
SPI0_START_ADDR, SPI0_END_ADDR, SPI0_SIZE);
}
if (fstat(fd,attr) == -1) {
fprintf(stderr,Error while fstat\n);
}
//mapping the file /dev/mem
spi0_addr = mmap(NULL, 0x1000, PROT_READ | PROT_WRITE, MAP_PRIVATE,
fd, SPI0_START_ADDR);
if (spi0_addr == MAP_FAILED) {
printf(Mapping of the SPI0 failed!! \n);
exit(1);
}
else {
printf(/dev/mem file is mapped\n);
}
//fprintf(stdout, size of void* is : %d and size of volatile
unsigned int * is: %d\n,*((int *)spi0_addr),\
// sizeof(*mcspi_rx0));
//fprintf(stdout,Base address returned from the mmap is: %X and
size of value \
// returned is: %X \n,(unsigned)spi0_addr,
sizeof(*spi0_addr));
mcspi_revision = spi0_addr + 0x00;
mcspi_sysconfig = spi0_addr + 0x110;
mcspi_sysstatus = spi0_addr + 0x114;
mcspi_irqstatus = spi0_addr + 0x118;
mcspi_irqenable = spi0_addr + 0x11C;
mcspi_syst = spi0_addr + 0x124;
mcspi_modulctrl = spi0_addr + 0x128;
// spi0 channel
mcspi_ch0conf = spi0_addr + 0x12C;
mcspi_ch0stat = spi0_addr + 0x130;
mcspi_ch0ctrl = spi0_addr + 0x134;
mcspi_tx0 = spi0_addr + 0x138;
mcspi_rx0 = spi0_addr + 0x13C;
// Soft reset
*mcspi_sysconfig = ((*mcspi_sysconfig) | (0x2));//-this is
the point where I am getting an error as I am trying to acces the content
of the register.
int temp = (*mcspi_sysconfig 0x2);
printf(0x%02X\n,temp);
//checking if reset is done
//while (1) {
if (((*mcspi_sysstatus) (0x0001)) == 0x1) {
printf(reset is complete\n);
//break;
}
else {
printf(reset is going on\n);
}
//}
if ((outputfile = open(/home/ubuntu/dac/output_file.txt, O_RDWR |
O_APPEND))0) {
printf(could not open the file\n);
}
close(outputfile);
//mcspi_sysstatus = NULL;
//fprintf(stdout, ch0conf: %x\n, mcspi_sysstatus);
//fpirntf(stdout, ch0stat: %x\n, (unsigned int)mcspi_ch0stat);
//fprintf(stdout, ch0ctrl: %x\n, (unsigned int)mcspi_ch0ctrl);
//fprintf(stdout, tx0: %x\n, (unsigned int)mcspi_tx0);
//fpirntf(stdout, rx0: %x\n, (unsigned int)mcspi_rx0);
close(fd);
return 0;
}
Please give your suggestions about where I am going wrong.
*Best Regards,*
On 2 September 2014 19:24, John Syn john3...@gmail.com wrote:
From: Amit Sama amitsama@gmail.com
Reply-To:
[beagleboard] SDI 12 for beaglebone black
Hi, I want to read data from a sensor that uses SDI-12, i read about how the SDI-12 functions but I can't find a way to implement it in my Beaglebone Black. Any suggestions on how to do this? -- 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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
Le jeudi 11 septembre 2014 12:26:53 UTC-4, RobertCNelson a écrit :
On Thu, Sep 11, 2014 at 11:00 AM, Cedric Malitte
cedric@gmail.com javascript: wrote:
Le jeudi 11 septembre 2014 10:32:25 UTC-4, RobertCNelson a écrit :
On Thu, Sep 11, 2014 at 9:26 AM, Cedric Malitte
cedric@gmail.com wrote:
I will try, but I'm checking diffs between 3.8.13 dts and 3.15.10,
because
using dtb from 3.14 is not really a solution for me as I also need
pruss.
Well I think :)
https://github.com/beagleboard/linux/commit/94f48ff05623afbfcf75ca211b4c4df23a66f82e
starting with r18, we got pruss from ti..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Ok, so LCD7 is working now.
What I did:
in pinmux file:
bbcape_lcd7_pins: bbcape_lcd7_pins {
pinctrl-single,pins =
0x150 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* spi0_sclk.gpio0_2, OUTPUT |
MODE7 -
AVDD_EN */
I think this was the fix ^..
*Yes this is the fix :) *
I can do something simlar to:
https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-common-pinmux.dtsi#L66
which i did to make the lcd4 work..
0xa0 (PIN_OUTPUT | MUX_MODE0) /* lcd_data0.lcd_data0 */
0xa3 (PIN_OUTPUT | MUX_MODE0) /* lcd_data1.lcd_data1 */
I saw this too... 0xa3 is not a valid pin...
*Put it back to 0xa4 *
tft-alt-mode = 0;
stn-565-mode = 0;
These last two are not in the driver...
Nope but were in 3.8.13...
Another trouble is with keymap now.
If I enable keymap for the user buttons ( even if I do not need them for
now ) , the touchscreen is clicking by itself when I do a ts_calibrate.
Going to investigate :)
Cedric
--
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: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
in pinmux file:
bbcape_lcd7_pins: bbcape_lcd7_pins {
pinctrl-single,pins =
0x150 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* spi0_sclk.gpio0_2, OUTPUT |
MODE7 -
AVDD_EN */
I think this was the fix ^..
Yes this is the fix :)
Cool! i'll enable that by default...
Another trouble is with keymap now.
If I enable keymap for the user buttons ( even if I do not need them for now
) , the touchscreen is clicking by itself when I do a ts_calibrate.
Going to investigate :)
Make sure they are -1 compared with v3.8.13
https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-keymap0.dtsi
Regards,
--
Robert Nelson
http://www.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] BeagleBone Black DDR3 RAM Voltage levels
On Thursday, September 11, 2014 10:39:25 AM UTC-4, RobertCNelson wrote:
On Thu, Sep 11, 2014 at 9:23 AM, Tom Rini tom.r...@gmail.com wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped
somewhere
because initially it did.. It was designed this way because when it
was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA
and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in
eeprom:
262 /*
263 * Override what we have detected since we know if
we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE
and
MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1
but it never reached the rest of the world so it's more a happy accident
that should be corrected (and wouldn't be too hard to do, if anyone out
there is looking for a reason to get their feet wet ).
Well, the original v2013.04 patchset can be seen here:
https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/recipes-bsp/u-boot/u-boot-denx
The only thing that touches the pmic, is this hack:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-bsp/u-boot/u-boot-denx/0004-beaglebone-HACK-raise-USB-current-limit.patch
I don't have my tps decoder ring, so i'm not sure if that address is
more then just the usb current setting..
I believe the equivalent hack to set DCDC1 to 1.35V is
+/* 0x24 is the address of the PMIC */
+/* 0x0b is the password register */
+/* 0x0e is the DEFDCDC1 register */
+/* 0x73 is the password (register 0x0e ^ 0x7d) */
+/* 0x12 sets the DCDC1 to 1.35V */
+/* Sequence must be repeated twice for password protection */
#define CONFIG_BOOTCOMMAND \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
I'm just about to try this out, but don't mind if someone beats me to it.
:-)
Regards,
--
Robert Nelson
http://www.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] Re: Start QT Application on bootup on Beaglebone Black
Tim, Please look the this stackoverflow questions and response Start QT Application on bootup on an Embedded Linux Device (Beaglebone Black) http://stackoverflow.com/questions/25701662/start-qt-application-on-bootup-on-an-embedded-linux-device-beaglebone-black Based on this input I was able to resolve the issue. I will post my end solution in due course. * Mickae1 and Maxim I do understand Angstrom distribution is something in the past. Have a come across a good source to configure QT development for BBB/Debian on a Host Ubuntu. I used Derek Molloy suggestions and it worked well for QT development for BBB/Angstrom on Host Ubuntu. I do understand that I need to make the change BBB/Debian. Thank you for all the great input. On Wed, Sep 10, 2014 at 8:52 PM, Tim Cole timc...@rogers.com wrote: You've accomplished more than I've managed to do. Could you suggest some references I could check so I can figure out what silly mistakes I'm making? Cheers, Tim On Tuesday, September 9, 2014 3:57:58 AM UTC-4, Mickae1 wrote: you should switch to debian, you will have more help from the Debian community . I've a BBB under debian which start QT at bootup ! Micka, Le dimanche 7 septembre 2014 14:03:35 UTC+2, Mahendra Gunawardena a écrit : Below is picture of the display on bootup. Expected display output is overwritten by Angstrom screen https://lh6.googleusercontent.com/-0ZA2QPRpNi8/VAxGxNd11yI/ABs/lvJbktseYgY/s1600/IMG_3852.JPG Expected Display output https://lh4.googleusercontent.com/-6jEzdpYTOQ0/VAxG86ZQFzI/AB0/LcFlyIPkwfE/s1600/IMG_3853.JPG The expected display output briefly appears but is overwritten by the Angstrom text based image. But occasionally the expected display appears. Then the dynamic widgets update the screen but the static information is not visible. The issues appears to be timing, and if the BBB can be forced to start the QT application after complete bootup of BBB that would suffices the current needs. Application is been started as a service. Below is the content of the service file [Unit] Description=QTAccelerometer GUI After=systemd-user-sessions.service [Service] WorkingDirectory=/home/root/projects/qt-projects ExecStart=/home/root/projects/qt-projects/QTAccelerometer -qws SyslogIdentifier=QTAccelerometer Restart=on-failure RestartSec=5 [Install] Alias=display-manager.service Below are the other options tried without success [Install] WantedBy=multi-user.target WantedBy=graphical.target *References* - Creating Ångström System Services on BeagleBone Black http://mattrichardson.com/BeagleBone-System-Services/ I have also posted this question on Stackoverflow http://stackoverflow.com/questions/25701662/start-qt-application-on-bootup-on-an-embedded-linux-device-beaglebone-black . Thank you in advance Mahen -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/E6qDY9Eydc0/unsubscribe. To unsubscribe from this group and all its topics, 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] BeagleBone Black DDR3 RAM Voltage levels
On 9/11/14, 12:06 PM, Robert Nelson robertcnel...@gmail.com wrote:
On Thu, Sep 11, 2014 at 1:57 PM, Jason Kridner jkrid...@gmail.com wrote:
On Thursday, September 11, 2014 10:39:25 AM UTC-4, RobertCNelson wrote:
On Thu, Sep 11, 2014 at 9:23 AM, Tom Rini tom.r...@gmail.com wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley
ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped
somewhere
because initially it did.. It was designed this way because when
it
was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739
e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or
1800mA
and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in
eeprom:
262 /*
263 * Override what we have detected since we know
if
we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3
(CORE
and
MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1
but it never reached the rest of the world so it's more a happy
accident
that should be corrected (and wouldn't be too hard to do, if anyone
out
there is looking for a reason to get their feet wet ).
Well, the original v2013.04 patchset can be seen here:
https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/r
ecipes-bsp/u-boot/u-boot-denx
The only thing that touches the pmic, is this hack:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/r
ecipes-bsp/u-boot/u-boot-denx/0004-beaglebone-HACK-raise-USB-current-lim
it.patch
I don't have my tps decoder ring, so i'm not sure if that address is
more then just the usb current setting..
I believe the equivalent hack to set DCDC1 to 1.35V is
+/* 0x24 is the address of the PMIC */
+/* 0x0b is the password register */
+/* 0x0e is the DEFDCDC1 register */
+/* 0x73 is the password (register 0x0e ^ 0x7d) */
+/* 0x12 sets the DCDC1 to 1.35V */
+/* Sequence must be repeated twice for password protection */
#define CONFIG_BOOTCOMMAND \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
I'm just about to try this out, but don't mind if someone beats me to
it.
:-)
Is there an easy to access ddr3_vdd test point?
Probably the best place is L1 or R6 which is on the bottom of the board
close to the 5V connector
Regards,
John
Regards,
--
Robert Nelson
http://www.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.
--
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 A6 B running slow, C ok
*william@arm:~$ cat /proc/cpuinfo* processor : 0 model name : ARMv7 Processor rev 2 (v7l) BogoMIPS: *297.40* Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part: 0xc08 CPU revision: 2 Hardware: Generic AM33XX (Flattened Device Tree) Revision: Serial : *william@arm:~$ sudo cpufreq-info -p* 30 100 ondemand *william@arm:~$ sudo cpufreq-set -g performance* *william@arm:~$ sudo cpufreq-info -p* 30 100 performance *william@arm:~$ cat /proc/cpuinfo* processor : 0 model name : ARMv7 Processor rev 2 (v7l) BogoMIPS: *990.68* Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part: 0xc08 CPU revision: 2 Hardware: Generic AM33XX (Flattened Device Tree) Revision: Serial : *william@arm:~$ uname -a* Linux arm 3.8.13-bone64.1 #1 SMP Sun Aug 31 13:30:46 MST 2014 armv7l GNU/Linux *william@arm:~$ ps --pid 1 -f* UIDPID PPID C STIME TTY TIME CMD root 1 0 0 Sep10 ?00:00:18 init [2] This board is an A5A off the first production run I think. It came from Digi-key ? Not sure my buddy pre-ordered one for himself, and one for me ~2 months prior to release. Not sure init daemon matters, but there it is. On Thu, Sep 11, 2014 at 8:41 AM, John Stampfl jstam...@gmail.com wrote: Ok, will do that tomorrow and report On Thu, Sep 11, 2014 at 11:37 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Sep 11, 2014 at 10:34 AM, John Stampfl jstam...@gmail.com wrote: What information would you like? What is the latest version of the bootloader for these boards? Well, since the C works.. Run the debian flasher on the A6/B http://beagleboard.org/latest-images Regards, -- Robert Nelson http://www.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. -- John Stampfl -- 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 A6 B running slow, C ok
By the way. For what it is worth. While the CPU profile is set to ondemand, the processor will stay at 300MHz until CPU utilization goes above 60%. I tested this early on last year with a simple load test application that I wrote. Which I think I may have even posted the code on these groups . . . I dont remember. On Thu, Sep 11, 2014 at 12:39 PM, William Hermans yyrk...@gmail.com wrote: *william@arm:~$ cat /proc/cpuinfo* processor : 0 model name : ARMv7 Processor rev 2 (v7l) BogoMIPS: *297.40* Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part: 0xc08 CPU revision: 2 Hardware: Generic AM33XX (Flattened Device Tree) Revision: Serial : *william@arm:~$ sudo cpufreq-info -p* 30 100 ondemand *william@arm:~$ sudo cpufreq-set -g performance* *william@arm:~$ sudo cpufreq-info -p* 30 100 performance *william@arm:~$ cat /proc/cpuinfo* processor : 0 model name : ARMv7 Processor rev 2 (v7l) BogoMIPS: *990.68* Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part: 0xc08 CPU revision: 2 Hardware: Generic AM33XX (Flattened Device Tree) Revision: Serial : *william@arm:~$ uname -a* Linux arm 3.8.13-bone64.1 #1 SMP Sun Aug 31 13:30:46 MST 2014 armv7l GNU/Linux *william@arm:~$ ps --pid 1 -f* UIDPID PPID C STIME TTY TIME CMD root 1 0 0 Sep10 ?00:00:18 init [2] This board is an A5A off the first production run I think. It came from Digi-key ? Not sure my buddy pre-ordered one for himself, and one for me ~2 months prior to release. Not sure init daemon matters, but there it is. On Thu, Sep 11, 2014 at 8:41 AM, John Stampfl jstam...@gmail.com wrote: Ok, will do that tomorrow and report On Thu, Sep 11, 2014 at 11:37 PM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Sep 11, 2014 at 10:34 AM, John Stampfl jstam...@gmail.com wrote: What information would you like? What is the latest version of the bootloader for these boards? Well, since the C works.. Run the debian flasher on the A6/B http://beagleboard.org/latest-images Regards, -- Robert Nelson http://www.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. -- John Stampfl -- 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: registering asynchronous events on kernel thread in user space
OK, one more time. All userspace interrupts work the same, pru, network driver, *anything*. The process blocks until the interrupt handler unblocks the process with a semaphore or completion in the kernel. For example, when you read data for a socket connection, it blocks. When data comes in, the data is copied to userspace, the read function unblocks. Again, this is all explained in that LDD3 chapter I linked. There's no other way to do it, except going around the kernel and polling memory. 1. This isn't a realtime kernel. You will always have jitter. Does it matter? I don't know what you're doing. You don't need to use polling. UIO and select doesn't use polling. 2. Using select (and even poll() since it's just a wrapper for select()) on the gpio doesn't poll. It's interrupt driven. Same method as described. 3. Same method as described. If you use the PRU, it will be the same method to notify your userspace application with the same shortcomings, unless you put all of your code into the pru. If you want deterministic timing, you either need a realtime kernel, or put all your code on the pru. But, I can guarantee you don't need deterministic timing, and I can guess that you're worrying about nothing Seriously, do some benchmarks with sysfs. It's only a few lines of code. And, there are all sorts of userspace hardware drivers that use userspace interrupts out there including graphics and network. If you only need to know when a gpio event happened, and process it later (it will always be later since this isn't a realtime kernel or in the pru), you can timestamp the event. I believe you can do this with the enhanced timers, and I know you can do this in the pru. So it would go, event happens, pru/etimer hardware timestamps the event, sends interrupt, userspace gets interupt using the only way possible, userspace reads timestamp from hardware, pretends that the event happened at the timestamp for any calculations. If you explained what you were doing, we could advise you better. Good luck! On Thursday, September 11, 2014, neo prag.in...@gmail.com wrote: Hi Brandon 1. I agree with jitter involved with processing interrupts and 100% cpu usage during polling for the same, so is there no way to let the user-space know that interrupt has occurred apart from polling ? 2. The reason why i said pseudo-interrupt is because we are polling and waiting there which is same as watching a flag in a UART register for RX flag to set. 3. I am curious as to how interrupts for Ethernet and usb are written. I am guessing that the ISR will use the DMA to transfer bytes to user-space. But even in that case the userspace should know that a new data has arrived. Then hoe to synchronize the kernel space and user-space if there are to share a data ? Thanks... On Thursday, September 11, 2014 2:26:15 AM UTC+5:30, Brandon I wrote: pseudo-interrupt from user space There's nothing pseudo about it. Again, any usual way to have a userspace application respond to an interrupt will be the exact same. The kernel will block the userspace process until the interrupt is seen. The only real alternative is burning up the cpu with memory polling, which appears to be what the BBIOlib method uses. So, your latency is limited to your poll speed (which can be faster than interrupts). But, if you have a constant poll for minimum latency, lets hope you're not trying to do something important elsewhere since your cpu usage will be at 100%, and you'll be maximizing process to process context switching! For 4, The only difference between a userspace and kernel space interrupt handler is where the code is that responds to the interrupt. You will only benefit from writing your own interrupt handler if you put all of your code that does something with that interrupt in the kernel. Otherwise, you're back to process blocked by kernel, interrupt occurs, kernel unblocks process, process does something after seeing the interruptback to the sysfs/UIO method. I would try some benchmarks. See if the regular UIO/sysfs interrupt method gives you sufficient performance. And definitely keep in mind John's statement. You're going to see a massive amount of jitter for anything in userspace or kernel space (better jitter since you can disable interrupts and whatnot, but if you don't finish quickly in kernel space, you'll crash the kernel). If something like a precise timestamp is needed for an async event, then there are other ways to approach this. If you're looking for fixed low latency, you're doomed. On Wed, Sep 10, 2014 at 5:13 AM, neo prag@gmail.com wrote: pseudo-interrupt from user space -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/eNX0CU7-noE/unsubscribe.
Re: [beagleboard] Re: Kernel 3.15.10 bone 8 + 4D LCD7 cape failed on BBB
About Touchscreen forget all I said :) My very own fault, I had leftover TS things in /etc/profile pointing to /dev/input/event1 instead of /dev/input/event2 So back to my sandbox for a bit more games :) -- 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] BeagleBone Black DDR3 RAM Voltage levels
On Thu, Sep 11, 2014 at 1:57 PM, Jason Kridner jkrid...@gmail.com wrote:
On Thursday, September 11, 2014 10:39:25 AM UTC-4, RobertCNelson wrote:
On Thu, Sep 11, 2014 at 9:23 AM, Tom Rini tom.r...@gmail.com wrote:
On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley ger...@beagleboard.org
wrote:
SW is supposed to set it to 1.35V. Sounds like it got dropped
somewhere
because initially it did.. It was designed this way because when it
was
designed, the PMIC defaulted to 1.5V. Since the design there is a
TPS65217D
that was release later that supports the 1.35V initial setting.
It should be set here:
http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
269 /*
270 * Increase USB current limit to 1300mA or 1800mA
and
set
271 * the MPU voltage controller as needed.
272 */
273 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
274 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
275 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
276 } else {
277 usb_cur_lim =
TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
278 mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
279 }
But that only happens if you have the beaglebone black header in
eeprom:
262 /*
263 * Override what we have detected since we know if
we
have
264 * a Beaglebone Black it supports 1GHz.
265 */
266 if (board_is_bone_lt(header))
So you'll have to override that check.
Note that the question was about DCDC1 and DDR voltage not DCDC2/3 (CORE
and
MPU) voltage. I don't know what initial bring-up U-Boot was whacking
DCDC1
but it never reached the rest of the world so it's more a happy accident
that should be corrected (and wouldn't be too hard to do, if anyone out
there is looking for a reason to get their feet wet ).
Well, the original v2013.04 patchset can be seen here:
https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/recipes-bsp/u-boot/u-boot-denx
The only thing that touches the pmic, is this hack:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-bsp/u-boot/u-boot-denx/0004-beaglebone-HACK-raise-USB-current-limit.patch
I don't have my tps decoder ring, so i'm not sure if that address is
more then just the usb current setting..
I believe the equivalent hack to set DCDC1 to 1.35V is
+/* 0x24 is the address of the PMIC */
+/* 0x0b is the password register */
+/* 0x0e is the DEFDCDC1 register */
+/* 0x73 is the password (register 0x0e ^ 0x7d) */
+/* 0x12 sets the DCDC1 to 1.35V */
+/* Sequence must be repeated twice for password protection */
#define CONFIG_BOOTCOMMAND \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
+ i2c mw 0x24 0x0b 0x73; \
+ i2c mw 0x24 0x0e 0x12; \
So I got this to work via this sequence in the terminal..
i2c dev 0;
i2c mw 0x24 0x0b 0x73; /* Password unlock 1 */
i2c mw 0x24 0x0e 0x12; /* Set DCDC1 to 1.35V */
i2c mw 0x24 0x0b 0x73; /* Password unlock 2 */
i2c mw 0x24 0x0e 0x12; /* Set DCDC1 to 1.35V */
i2c mw 0x24 0x0b 0x6c; /* Password unlock 1 */
i2c mw 0x24 0x11 0x86; /* Apply DCDC changes */
i2c mw 0x24 0x0b 0x6c; /* Password unlock 2 */
i2c mw 0x24 0x11 0x86; /* Apply DCDC changes */
The L1/R6 test point is showing 1.35v
Regards,
--
Robert Nelson
http://www.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] Re: custom cape i2c bus
Then it appears your cape is working and the chips are at least visible to the bus. You should be able to use the smbus system calls to talk to them. Might be able to do something with i2cget. -- 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: Start QT Application on bootup on Beaglebone Black
Thanks! That's more grist for my slowly grinding mental mill On Thursday, September 11, 2014 3:29:15 PM UTC-4, Mahendra Gunawardena wrote: Tim, Please look the this stackoverflow questions and response Start QT Application on bootup on an Embedded Linux Device (Beaglebone Black) http://stackoverflow.com/questions/25701662/start-qt-application-on-bootup-on-an-embedded-linux-device-beaglebone-black Based on this input I was able to resolve the issue. I will post my end solution in due course. * Mickae1 and Maxim I do understand Angstrom distribution is something in the past. Have a come across a good source to configure QT development for BBB/Debian on a Host Ubuntu. I used Derek Molloy suggestions and it worked well for QT development for BBB/Angstrom on Host Ubuntu. I do understand that I need to make the change BBB/Debian. Thank you for all the great input. On Wed, Sep 10, 2014 at 8:52 PM, Tim Cole tim...@rogers.com javascript: wrote: You've accomplished more than I've managed to do. Could you suggest some references I could check so I can figure out what silly mistakes I'm making? Cheers, Tim On Tuesday, September 9, 2014 3:57:58 AM UTC-4, Mickae1 wrote: you should switch to debian, you will have more help from the Debian community . I've a BBB under debian which start QT at bootup ! Micka, Le dimanche 7 septembre 2014 14:03:35 UTC+2, Mahendra Gunawardena a écrit : Below is picture of the display on bootup. Expected display output is overwritten by Angstrom screen https://lh6.googleusercontent.com/-0ZA2QPRpNi8/VAxGxNd11yI/ABs/lvJbktseYgY/s1600/IMG_3852.JPG Expected Display output https://lh4.googleusercontent.com/-6jEzdpYTOQ0/VAxG86ZQFzI/AB0/LcFlyIPkwfE/s1600/IMG_3853.JPG The expected display output briefly appears but is overwritten by the Angstrom text based image. But occasionally the expected display appears. Then the dynamic widgets update the screen but the static information is not visible. The issues appears to be timing, and if the BBB can be forced to start the QT application after complete bootup of BBB that would suffices the current needs. Application is been started as a service. Below is the content of the service file [Unit] Description=QTAccelerometer GUI After=systemd-user-sessions.service [Service] WorkingDirectory=/home/root/projects/qt-projects ExecStart=/home/root/projects/qt-projects/QTAccelerometer -qws SyslogIdentifier=QTAccelerometer Restart=on-failure RestartSec=5 [Install] Alias=display-manager.service Below are the other options tried without success [Install] WantedBy=multi-user.target WantedBy=graphical.target *References* - Creating Ångström System Services on BeagleBone Black http://mattrichardson.com/BeagleBone-System-Services/ I have also posted this question on Stackoverflow http://stackoverflow.com/questions/25701662/start-qt-application-on-bootup-on-an-embedded-linux-device-beaglebone-black . Thank you in advance Mahen -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/E6qDY9Eydc0/unsubscribe. To unsubscribe from this group and all its topics, 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: CAN bus recovery
Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai devan@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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: Trying to use ttyO0 but I can't disable the console login.
Some reason you can't just use one of the other UARTs? It's very handy to have a serial console for debugging. On Thursday, September 11, 2014 10:29:48 AM UTC-7, jgold wrote: I've got a RS232 micro cape http://www.logicsupply.com/components/beaglebone/capes/cbb-ttl-232/ that I need to use as a serial port. The problem is that by default /dev/ttyO0 is setup as a login console. I need to disable that so that I can use the port for my own purposes. I've found instructions for how to do it on Rasbian but I can't find anything for the Beaglebone. I found a line in /etc/inittab that looked like it was starting a getty session on /dev/ttyO0 and I commented it out but after a reboot, the login is still there. I found some references to inittab being obsolete because systemd doesn't use it but I can't find anything to configure systemd so it doesn't use ttyO0. Can anyone point me in the right direction? -- 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] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu
Ok, where does one get qtwayland? It is not a part of the normal distribution repositories Nor is it in ubuntu-sdk-team/ppa I saw some references on how to download and compile it. Is that my only option? Do any of the desktops in the normal distribution work or are they all X desktops? ubuntu-desktop (mouse locks it up) lubuntu-desktop (mouse locks it up) ubuntu-desktop-mir (didn't work for me) xubuntu-desktop -- 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: color ball tracking with opencv on BBB
I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical-computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com javascript: wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com javascript: wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB camera (Logitech C920) I need a resolution of 640x480. The problem is with a speed on BBB, having a significant delay. It's good on a desktop PC. I would like to ask for advice how to improve the performance on BBB if possible. Jan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/fTan4VKv1no/unsubscribe. To unsubscribe from this group and all its topics, 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] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu
From: Peter Gregory talkto...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:33 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Cc: wingli...@163.com Subject: Re: [beagleboard] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu Ok, where does one get qtwayland? You have to build It from source: http://download.qt-project.org/official_releases/qt/5.3/5.3.1/single/ Or you can use archlinux for arm as I believe they have qtwayland already packaged. I haven¹t used archlinux myself, but from what I have learned it looks pretty good. Regards, John It is not a part of the normal distribution repositories Nor is it in ubuntu-sdk-team/ppa I saw some references on how to download and compile it. Is that my only option? Do any of the desktops in the normal distribution work or are they all X desktops? ubuntu-desktop (mouse locks it up) lubuntu-desktop (mouse locks it up) ubuntu-desktop-mir (didn't work for me) xubuntu-desktop -- 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: color ball tracking with opencv on BBB
From: janszymanski12...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:35 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 300 MHz. cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: sudo cpufreq-set -g performance Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical-computing-o n-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com javascript: wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com javascript: wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB camera (Logitech C920) I need a resolution of 640x480. The problem is with a speed on BBB, having a significant delay. It's good on a desktop PC. I would like to ask for advice how to improve the performance on BBB if possible. Jan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/fTan4VKv1no/unsubscribe. To unsubscribe from this group and all its topics, 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. -- 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] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu
On Thu, Sep 11, 2014 at 5:33 PM, Peter Gregory talkto...@gmail.com wrote: Ok, where does one get qtwayland? It is not a part of the normal distribution repositories Nor is it in ubuntu-sdk-team/ppa I saw some references on how to download and compile it. Is that my only option? Do any of the desktops in the normal distribution work or are they all X desktops? ubuntu-desktop (mouse locks it up) lubuntu-desktop (mouse locks it up) ubuntu-desktop-mir (didn't work for me) xubuntu-desktop check your xorg.conf: http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-HDMI modesetting has a tendency to lockup Regards, -- Robert Nelson http://www.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] Re: color ball tracking with opencv on BBB
$ cpufreq-set --help. You may need to set you profile limits/ performance is default 300MHz to 1Ghz just like ondemand, but for some reason it is always 1GHz whenever I look. On Thu, Sep 11, 2014 at 3:47 PM, John Syn john3...@gmail.com wrote: From: janszymanski12...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:35 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: *sudo cpufreq-set -g performance* Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical- computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/ 02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB camera (Logitech C920) I need a resolution of 640x480. The problem is with a speed on BBB, having a significant delay. It's good on a desktop PC. I would like to ask for advice how to improve the performance on BBB if possible. Jan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/beagleboard/fTan4VKv1no/unsubscribe. To unsubscribe from this group and all its topics, 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
Re: [beagleboard] Re: color ball tracking with opencv on BBB
From memory setting profile limits would be like this You change to a profile via $ sudo cpufreq-set -g govenor_name Check profile limits $ sudo cpufreq-info -p Change minimum profile range $ cpufreq-set -d 100 /*set minimum processor freq for active profile to 1 GHz */ I do not know if these setting persist across reboots, but I think not. At least it did not see that was for me. Also settings seem to be a bit quirky. On one of my Linux support system for instance, manually changing anything did not work as expected. I could change profiles, governors etc, but actual frequency always stayed the same. Then with BBB when you set minimum ondemand profile to 1Ghz, it does not take. But when changing to performance profile, minimum freq is 300Mhz, but when you check actual processor freq it is 1Ghz . . . So yeah, anyhow the program is quirky. On Thu, Sep 11, 2014 at 4:26 PM, William Hermans yyrk...@gmail.com wrote: $ cpufreq-set --help. You may need to set you profile limits/ performance is default 300MHz to 1Ghz just like ondemand, but for some reason it is always 1GHz whenever I look. On Thu, Sep 11, 2014 at 3:47 PM, John Syn john3...@gmail.com wrote: From: janszymanski12...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:35 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: *sudo cpufreq-set -g performance* Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical- computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/ 02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB camera (Logitech C920) I need a resolution of 640x480. The problem is with a speed on BBB, having a significant delay. It's good on a desktop PC. I would like to ask for advice how to improve the performance on BBB if possible. Jan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic,
Re: [beagleboard] Re: color ball tracking with opencv on BBB
Oh, and for the uninitiated . . . setting your governor to performance / 1Ghz _all_the_time_ may not be a very good idea. For instance it has been in the mid to upper 80's F outdoor ambient here, and I've noticed my BBB getting pretty warm. On Thu, Sep 11, 2014 at 4:34 PM, William Hermans yyrk...@gmail.com wrote: From memory setting profile limits would be like this You change to a profile via $ sudo cpufreq-set -g govenor_name Check profile limits $ sudo cpufreq-info -p Change minimum profile range $ cpufreq-set -d 100 /*set minimum processor freq for active profile to 1 GHz */ I do not know if these setting persist across reboots, but I think not. At least it did not see that was for me. Also settings seem to be a bit quirky. On one of my Linux support system for instance, manually changing anything did not work as expected. I could change profiles, governors etc, but actual frequency always stayed the same. Then with BBB when you set minimum ondemand profile to 1Ghz, it does not take. But when changing to performance profile, minimum freq is 300Mhz, but when you check actual processor freq it is 1Ghz . . . So yeah, anyhow the program is quirky. On Thu, Sep 11, 2014 at 4:26 PM, William Hermans yyrk...@gmail.com wrote: $ cpufreq-set --help. You may need to set you profile limits/ performance is default 300MHz to 1Ghz just like ondemand, but for some reason it is always 1GHz whenever I look. On Thu, Sep 11, 2014 at 3:47 PM, John Syn john3...@gmail.com wrote: From: janszymanski12...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:35 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: *sudo cpufreq-set -g performance* Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical- computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/ 02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB camera (Logitech C920) I need a resolution of 640x480. The problem is with a speed on BBB, having a
Re: [beagleboard] Re: Trying to use ttyO0 but I can't disable the console login.
ttyo0 has to be disabled in uEnv.txt, and also the board device tree file I believe ( could be wrong on the last part ). Also, systemd may have a service profile for it. I have not looked, and currently am not running systemd. Maybe I'll check later once I get this rootfs working good, and backed up. On Thu, Sep 11, 2014 at 3:02 PM, Lee Crocker l...@ansync.com wrote: Some reason you can't just use one of the other UARTs? It's very handy to have a serial console for debugging. On Thursday, September 11, 2014 10:29:48 AM UTC-7, jgold wrote: I've got a RS232 micro cape http://www.logicsupply.com/ components/beaglebone/capes/cbb-ttl-232/ that I need to use as a serial port. The problem is that by default /dev/ttyO0 is setup as a login console. I need to disable that so that I can use the port for my own purposes. I've found instructions for how to do it on Rasbian but I can't find anything for the Beaglebone. I found a line in /etc/inittab that looked like it was starting a getty session on /dev/ttyO0 and I commented it out but after a reboot, the login is still there. I found some references to inittab being obsolete because systemd doesn't use it but I can't find anything to configure systemd so it doesn't use ttyO0. Can anyone point me in the right direction? -- 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 bus recovery
Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent.s...@gmail.com wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai devan@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu
Thanks for all the great info. I was in the process of testing lxde (Lightweight X11 desktop environment) as of my last post It works quite well. I installed bone-ubuntu-14.04-console-armhf-2014-08-13-2gb.img.xz onto a SD card I installed the SGX drivers as described at http://elinux.org/BeagleBoardUbuntu I installed lxde (sudo apt-get install lxde) I have a desktop that takes up about 1.3gb on my SD drive. Mouse HDMI work well. I'm going to develop some quick apps transfer to flash test headless execution -- 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] Beaglebone Black rev B - Embedded QT and X Sever - Deployment OS Ubuntu
How about performance ? I'd expect it would run sluggish.I wonder how well xcompmgr + cairo-dock would run on it heh. I recently installed Lubuntu 14.04 on an older laptop, and have to say I'm impressed with it. Aesthetically it looks very nice, and otherwise is just Ubuntu, except it runs faster, and looks better. On Thu, Sep 11, 2014 at 4:44 PM, Peter Gregory talkto...@gmail.com wrote: Thanks for all the great info. I was in the process of testing lxde (Lightweight X11 desktop environment) as of my last post It works quite well. I installed bone-ubuntu-14.04-console-armhf-2014-08-13-2gb.img.xz onto a SD card I installed the SGX drivers as described at http://elinux.org/BeagleBoardUbuntu I installed lxde (sudo apt-get install lxde) I have a desktop that takes up about 1.3gb on my SD drive. Mouse HDMI work well. I'm going to develop some quick apps transfer to flash test headless execution -- 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 bus recovery
Well, I'm not reading a guide, but I'll share a few links that helped me get started. I have a Qt application and I use the SocketCAN to read/write CAN messages. This will work with J1939 as well. https://www.kernel.org/doc/Documentation/networking/can.txt http://en.wikipedia.org/wiki/SocketCAN http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent...@gmail.com javascript: wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai deva...@gmail.com javascript: wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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] Re: Trying to use ttyO0 but I can't disable the console login.
The micro cape I purchased can be either UART0 or UART4 but to change it you have to solder some bridges across some little bitty pads. It looked too delicate for my fat fingers so with this setup, I'm kinda stuck with UART0. On Thursday, September 11, 2014 3:02:34 PM UTC-7, Lee Crocker wrote: Some reason you can't just use one of the other UARTs? It's very handy to have a serial console for debugging. On Thursday, September 11, 2014 10:29:48 AM UTC-7, jgold wrote: I've got a RS232 micro cape http://www.logicsupply.com/components/beaglebone/capes/cbb-ttl-232/ that I need to use as a serial port. The problem is that by default /dev/ttyO0 is setup as a login console. I need to disable that so that I can use the port for my own purposes. I've found instructions for how to do it on Rasbian but I can't find anything for the Beaglebone. I found a line in /etc/inittab that looked like it was starting a getty session on /dev/ttyO0 and I commented it out but after a reboot, the login is still there. I found some references to inittab being obsolete because systemd doesn't use it but I can't find anything to configure systemd so it doesn't use ttyO0. Can anyone point me in the right direction? -- 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 bus recovery
Thank Brent, However I was more curious about the bring up of the hardware on the BBB. IS there cape file I have not noticed yet ? If so I can probably figure it out on my own. On Thu, Sep 11, 2014 at 4:52 PM, Brent brent...@hotmail.com wrote: Well, I'm not reading a guide, but I'll share a few links that helped me get started. I have a Qt application and I use the SocketCAN to read/write CAN messages. This will work with J1939 as well. https://www.kernel.org/doc/Documentation/networking/can.txt http://en.wikipedia.org/wiki/SocketCAN http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent...@gmail.com wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai deva...@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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: Trying to use ttyO0 but I can't disable the console login.
I found the answer here; http://stackoverflow.com/questions/21596384/cannot-disable-systemd-serial-getty-service My port is at ttyO0. so in my case I entered systemctl mask serial-getty@ttyO0.service. I was able to confirm the device name by typing systemctl --full. My device was in the list. Once I typed the command above and rebooted, I could use the serial port in my program. On Thursday, September 11, 2014 4:42:31 PM UTC-7, William Hermans wrote: ttyo0 has to be disabled in uEnv.txt, and also the board device tree file I believe ( could be wrong on the last part ). Also, systemd may have a service profile for it. I have not looked, and currently am not running systemd. Maybe I'll check later once I get this rootfs working good, and backed up. On Thu, Sep 11, 2014 at 3:02 PM, Lee Crocker l...@ansync.com javascript: wrote: Some reason you can't just use one of the other UARTs? It's very handy to have a serial console for debugging. On Thursday, September 11, 2014 10:29:48 AM UTC-7, jgold wrote: I've got a RS232 micro cape http://www.logicsupply.com/ components/beaglebone/capes/cbb-ttl-232/ that I need to use as a serial port. The problem is that by default /dev/ttyO0 is setup as a login console. I need to disable that so that I can use the port for my own purposes. I've found instructions for how to do it on Rasbian but I can't find anything for the Beaglebone. I found a line in /etc/inittab that looked like it was starting a getty session on /dev/ttyO0 and I commented it out but after a reboot, the login is still there. I found some references to inittab being obsolete because systemd doesn't use it but I can't find anything to configure systemd so it doesn't use ttyO0. Can anyone point me in the right direction? -- 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: CAN bus recovery
Ah, yes. The TT3201 cape has three CAN channels, but two of them are over SPI. This should help you out... https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/TT3201-001-01.dts On Thu, Sep 11, 2014 at 8:00 PM, William Hermans yyrk...@gmail.com wrote: Thank Brent, However I was more curious about the bring up of the hardware on the BBB. IS there cape file I have not noticed yet ? If so I can probably figure it out on my own. On Thu, Sep 11, 2014 at 4:52 PM, Brent brent...@hotmail.com wrote: Well, I'm not reading a guide, but I'll share a few links that helped me get started. I have a Qt application and I use the SocketCAN to read/write CAN messages. This will work with J1939 as well. https://www.kernel.org/doc/Documentation/networking/can.txt http://en.wikipedia.org/wiki/SocketCAN http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent...@gmail.com wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai deva...@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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] Will the watchdog reset if the kernel panics?
Does anyone know that if the watchdog timer is enabled, will a kernel panic still allow the watchdog to reset? Since it's not an external watchdog, I wasn't sure what would happen. I've seen some cases where the kernel will panic and completely brick my device until it is manually rebooted. I haven't had a chance to debug why the kernel panics at what seems like random times, so I need to do some investigation. However, my band-aid to the problem would be to enable the watchdog timer so that it will automatically reboot. I would just try it, but I'm having a hard time reproducing a kernel panic. Also, on a side note, how do you change the default duration of 60 seconds? It seems like this info would be all over the internet, but I haven't found anywhere that talks about this. -- 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: color ball tracking with opencv on BBB
Or, cpufreq-set -f 1GHz On Thu, Sep 11, 2014 at 4:39 PM, William Hermans yyrk...@gmail.com wrote: Oh, and for the uninitiated . . . setting your governor to performance / 1Ghz _all_the_time_ may not be a very good idea. For instance it has been in the mid to upper 80's F outdoor ambient here, and I've noticed my BBB getting pretty warm. On Thu, Sep 11, 2014 at 4:34 PM, William Hermans yyrk...@gmail.com wrote: From memory setting profile limits would be like this You change to a profile via $ sudo cpufreq-set -g govenor_name Check profile limits $ sudo cpufreq-info -p Change minimum profile range $ cpufreq-set -d 100 /*set minimum processor freq for active profile to 1 GHz */ I do not know if these setting persist across reboots, but I think not. At least it did not see that was for me. Also settings seem to be a bit quirky. On one of my Linux support system for instance, manually changing anything did not work as expected. I could change profiles, governors etc, but actual frequency always stayed the same. Then with BBB when you set minimum ondemand profile to 1Ghz, it does not take. But when changing to performance profile, minimum freq is 300Mhz, but when you check actual processor freq it is 1Ghz . . . So yeah, anyhow the program is quirky. On Thu, Sep 11, 2014 at 4:26 PM, William Hermans yyrk...@gmail.com wrote: $ cpufreq-set --help. You may need to set you profile limits/ performance is default 300MHz to 1Ghz just like ondemand, but for some reason it is always 1GHz whenever I look. On Thu, Sep 11, 2014 at 3:47 PM, John Syn john3...@gmail.com wrote: From: janszymanski12...@gmail.com Reply-To: beagleboard@googlegroups.com beagleboard@googlegroups.com Date: Thursday, September 11, 2014 at 3:35 PM To: beagleboard@googlegroups.com beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: *sudo cpufreq-set -g performance* Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical- computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/ 02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a error message of not enough memory. Jan On Tuesday, September 9, 2014 11:03:58 AM UTC+10, janszyma...@gmail.com wrote: Hi, I need to implement tracking of color ball with opencv on BBB. I have a rev.C BBB with latest (default Debian) including opencv 2.3.1 On my desktop Ubuntu I have installed opencv 2.4.9 To check the initial performance I used the example webcam program from the book Practical OpenCV listing 4-4 p.34 playing the video from USB
Re: [beagleboard] Re: color ball tracking with opencv on BBB
That works. Another question is how to clone or replicate BBBs eMMC? How to move it into microSD card and vice versa? If I need to have exactly the same image on another BBB as the one I am currently working on (when it's finished) what is the procedure then? On Friday, 12 September 2014 12:45:15 UTC+10, Brandon I wrote: Or, cpufreq-set -f 1GHz On Thu, Sep 11, 2014 at 4:39 PM, William Hermans yyr...@gmail.com javascript: wrote: Oh, and for the uninitiated . . . setting your governor to performance / 1Ghz _all_the_time_ may not be a very good idea. For instance it has been in the mid to upper 80's F outdoor ambient here, and I've noticed my BBB getting pretty warm. On Thu, Sep 11, 2014 at 4:34 PM, William Hermans yyr...@gmail.com javascript: wrote: From memory setting profile limits would be like this You change to a profile via $ sudo cpufreq-set -g govenor_name Check profile limits $ sudo cpufreq-info -p Change minimum profile range $ cpufreq-set -d 100 /*set minimum processor freq for active profile to 1 GHz */ I do not know if these setting persist across reboots, but I think not. At least it did not see that was for me. Also settings seem to be a bit quirky. On one of my Linux support system for instance, manually changing anything did not work as expected. I could change profiles, governors etc, but actual frequency always stayed the same. Then with BBB when you set minimum ondemand profile to 1Ghz, it does not take. But when changing to performance profile, minimum freq is 300Mhz, but when you check actual processor freq it is 1Ghz . . . So yeah, anyhow the program is quirky. On Thu, Sep 11, 2014 at 4:26 PM, William Hermans yyr...@gmail.com javascript: wrote: $ cpufreq-set --help. You may need to set you profile limits/ performance is default 300MHz to 1Ghz just like ondemand, but for some reason it is always 1GHz whenever I look. On Thu, Sep 11, 2014 at 3:47 PM, John Syn john...@gmail.com javascript: wrote: From: janszyma...@gmail.com javascript: Reply-To: beagl...@googlegroups.com javascript: beagl...@googlegroups.com javascript: Date: Thursday, September 11, 2014 at 3:35 PM To: beagl...@googlegroups.com javascript: beagl...@googlegroups.com javascript: Subject: Re: [beagleboard] Re: color ball tracking with opencv on BBB I was able to build and install the same version of openCV (2.4.9) on BBB debian as on my desktop Ubuntu by using an external USB memory stick. Now I have a problem with changing CPU frequency (as I would like to increase it from 300MHz to 1GHz) debian@beaglebone:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpu...@vger.kernel.org javascript:, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor ondemand may decide which speed to use within this range. * current CPU frequency is 300 MHz.* cpufreq stats: 300 MHz:97.20%, 600 MHz:0.20%, 800 MHz:0.06%, 1000 MHz:2.55% (35) debian@beaglebone:~$ sudo cpufreq-set -g GOV *Error setting new values*. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? debian@beaglebone:~$ William just explained how to do this earlier today: *sudo cpufreq-set -g performance* Regards, John What am I doing wrong? Jan On Wednesday, 10 September 2014 12:52:11 UTC+10, Brandon I wrote: And, here are some compile flags you'll want to include/force: http://www.eliteraspberries.com/blog/2013/09/cflags-for-numerical- computing-on-the-beaglebone-black.html On Tue, Sep 9, 2014 at 7:16 PM, Brandon I brando...@gmail.com wrote: I'm not sure that newer open cv can be compiled on the raspberry or beaglebone due to the limited ram. You'll probably have to cross compile. On Tue, Sep 9, 2014 at 5:56 PM, janszyma...@gmail.com wrote: Thanks for that link, it is very usefull. In a meantime my attempt to install a newer version of opencv (following the instructions from here http://robertcastle.com/2014/ 02/installing-opencv-on-a-raspberry-pi/0) has failed firstly with cmake-curses-gui not working (empty database?) and after that (using command line cmake) the building stopped with a
[beagleboard] Re: Will the watchdog reset if the kernel panics?
I figured out how to change the watchdog duration. The example program is here: http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/ And a good description of the available commands is here: https://github.com/shengchao/beaglebone-angstrom-xenomai/blob/master/Documentation/watchdog/watchdog-api.txt However, my first question regarding the kernel panic still remains. Also, if I do get a kernel panic, how do I record the error message/code so that I can debug it later? On Thursday, September 11, 2014 9:15:02 PM UTC-4, Brent wrote: Does anyone know that if the watchdog timer is enabled, will a kernel panic still allow the watchdog to reset? Since it's not an external watchdog, I wasn't sure what would happen. I've seen some cases where the kernel will panic and completely brick my device until it is manually rebooted. I haven't had a chance to debug why the kernel panics at what seems like random times, so I need to do some investigation. However, my band-aid to the problem would be to enable the watchdog timer so that it will automatically reboot. I would just try it, but I'm having a hard time reproducing a kernel panic. Also, on a side note, how do you change the default duration of 60 seconds? It seems like this info would be all over the internet, but I haven't found anywhere that talks about this. -- 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.
