Re: [beagleboard] Driving a Multiplexed LED matrix directly from gpio

OK so yes, seeing your code would help us understand what you're bottleneck but I've a pretty good idea why you're LCD matrix refresh is so slow. It has to do with userspace communicating with kernel space, and you're either invoking some system API calls ( which are notoriously slow ), or you're

Re: [beagleboard] Driving a Multiplexed LED matrix directly from gpio

Show us some code. On Sun, Mar 20, 2016 at 6:28 PM, David Good wrote: > Hi All, > > I've been experimenting with embedded linux and matrixed LED displays. I > started on a Raspberry pi user space program, but could see visual > artifacts on the display due to

Re: [beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

Reading this made me laugh. On 3/20/2016 3:49 PM, William Hermans wrote: > > /Trying to update the flash to Debian 8.3 and initially I get the > back and forth Knight Rider pattern. Then, after a bit I get just > 4 double blink leds every half second or so. Looks like a few >

[beagleboard] Driving a Multiplexed LED matrix directly from gpio

Hi All, I've been experimenting with embedded linux and matrixed LED displays. I started on a Raspberry pi user space program, but could see visual artifacts on the display due to inconsistent timing of my sleep command. So, I figured that moving the basic row scanning into the kernel would help

Re: [beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

> > *Trying to update the flash to Debian 8.3 and initially I get the back and > forth Knight Rider pattern. Then, after a bit I get just 4 double blink > leds every half second or so. Looks like a few others have seen this, but > no conversation around the issue or possible solutions.* > > *My

Re: [beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

On 21 Mar 2016 06:28, "Karl Easterly" wrote: > Mine are going in the trash Seriously? Don't trash em. Send em to me. Email me your details and I'll pay for shipping if you like. PO Box 195 Lindisfarne Tasmania AUSTRALIA 7015 P. -- For more options, visit

Re: [beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

Quoting Robert Nelson : On Mar 20, 2016 2:28 PM, "Karl Easterly" wrote: It's clear that the BBB is a dead product. There is no meaningful resources for issues, and when the system simply won't 'reset from a new image from their site'...

Re: [beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

On Mar 20, 2016 2:28 PM, "Karl Easterly" wrote: > > Trying to update the flash to Debian 8.3 and initially I get the back and forth Knight Rider pattern. Then, after a bit I get just 4 double blink leds every half second or so. Looks like a few others have seen this, but

[beagleboard] looks like the BeagleBone Black and this community is dead. Cannot even flash 8.3.

Trying to update the flash to Debian 8.3 and initially I get the back and forth Knight Rider pattern. Then, after a bit I get just 4 double blink leds every half second or so. Looks like a few others have seen this, but no conversation around the issue or possible solutions. My raspberry pi's

[beagleboard] BBB based board power-off

Hello, We have a custom, BBB based board, which, when all relevant patches and PMIC settings have been applied, will power-cycle when poweroff is issued (remains off for a couple of seconds, and powers on again. The strange thing is that if we have the UART0 Tx pin connected to a PC, when

Re: [beagleboard] Debugging with beaglebone black

https://www.google.com/search?q=how+to+debug+linux+kernel+modules Just like you would on any platform. On Thu, Mar 17, 2016 at 8:46 PM, John Syne wrote: > To debug kernel modules with JTAG, you have to have a debugger which is > kernel aware like Lauterbach. If you don’t

[beagleboard] Terminal Block Wiring Options

Hey guys, I'm currently designing a greenhouse automation control unit utilizing the BBB as the brain. In order to create industrial strength wiring I'd like to use terminal block connections to each connector on the P8 and P9 headers. To give you a visual of what I'd like to do check out a

[beagleboard] Re: All the Leds remain lit.

Have you tried to boot it fro ma system that is located on external microSD-card? E.g. a Ubuntu-version? Am Freitag, 11. März 2016 17:25:57 UTC+1 schrieb Anh Le Tuan: > > It is a BeagleBone Black which was successfully flashed. I tried to > upgrade the kernel. However failed. I reboot the

Re: [beagleboard] bbb Internal ADC configuration settings?

What is your kernel version? Regards, John > On Mar 18, 2016, at 1:22 PM, Audrey wrote: > > It says: > root@beaglebone:/# echo 1 > > /sys/bus/iio/devices/iio:device0/scan_element/in_voltage0_en > -bash: /sys/bus/iio/devices/iio:device0/scan_element/in_voltage0_en: No such

[beagleboard] Cape Manager question- What installs config-pin command?

I've successfully ran Robert Nelson's scripts (https://eewiki.net/display/linuxonarm/BeagleBone) which compile a kernel image, u-boot, installed root file system etc. and installed on microSD card. It boots perfectly, I can use the serial device or SSH into a Beagleboard Green and all looks

[beagleboard] Re: PWM Pin Error on Boot

I should clarify that it is every time I start my node.js server file that a has a required module that uses P9_14. I can manually change the polarity to 0 but it resets every time I reboot. On Saturday, March 19, 2016 at 11:30:58 PM UTC-7, M House wrote: > > I'm doing a project right now that

[beagleboard] PWM Pin Error on Boot

I'm doing a project right now that involves using a micro servo. One is on port P8_13 and another on P9_14. Everytime I boot the beaglebone it gives me - error: Error enabling PWM controls: Error: ENOENT, no such file or directory '/sys/devices/ocp.3/bs_pwm_test_P9_14.15/polarity' When I