[beagleboard] lcd4 driver for beaglebone black.

Hi, I have a 4D systems 4.3" lcd cape (this one ). I wan't to keep the size of the system that I am making as small as possible, So I thought of using the LCD from the cape, along with the adafruit LCD firend

[beagleboard] Re: Does your BB Prus support multitasking in forth?

Did you find https://github.com/biocode3D/prufh ? On Mon, Feb 8, 2016 at 3:11 AM wrote: > I love forth. > > Currently, I am developing a series of cnc closed loop controlled maker > machines that are dirt cheap and smart. > > I need multiple task to capture and process video and other encoder dat

[beagleboard] tilcdc FIFO underflow

Hi there, i was able to get my 10.1 custom Display to work with the RGB Pins on the beaglebone black. I am using the latest Debian Jessie image from beagleboard.org and the X11 Desktop has the right colors and the right size. So i assume that the Timings from my display are correct. panel

Re: [beagleboard] Pure server version for BBB?

There are “console" images for Ubuntu as well: http://elinux.org/BeagleBoardUbuntu#raw_microSD_img -hilmar > On Feb 6, 2016, at 6:43 PM, Rick Mann wrote: > > I think you're looking for the "Console" versions. They're Debian, tho. > >> On Feb 6, 2016, at 00:09 , georges.heine...@gmail.com wrot

[beagleboard] BeagleBoard.org host moved machines

I've moved the AWS machine that is hosting BeagleBoard.org and added https:// support. Please let me know if you have any difficulties with the website. This includes https://debian.beagleboard.org (was previously hosted on S3), https://beagleboard.org, and https://builds.beagleboard.org. I'm still

[beagleboard] Can't copy uSD to emmc

Some month ago, I've made a backup of a emmc to an sd, with dd. Now I've restored the .img to a new uSD. If I put the uSD in the BBB the system start and I can login in it and everything seems fine... but I cannot move the system from uSD to emmc. I've tried to ssh and dd the image to emmc, but

[beagleboard] Re: Protect eMMC/eMMC flasher Data

Hello, I up the post, nobody has a solution for encrypting an image ? I see more solution for the raspberry but i don't find a same solution for BBB... I tested with encfs but the password must be typed or in a script. For automount folder at startup this is not secure. And i think with encFS

[beagleboard] Re: Protect eMMC/eMMC flasher Data

Hello, I up the post, nobody has a solution for encrypting an image ? I see more solution for the raspberry but i don't find a same solution for BBB... I tested with encfs but the password must be typed or in a script. For automount folder at startup this is not secure. And i think with encFS

[beagleboard] Re: Use GPIO as non-root user?

Hi Drew! Am Freitag, 5. Februar 2016 23:13:34 UTC+1 schrieb Drew Fustini: > > ... to provide a way for non-root users to access GPIO: > ... > Anyone have ideas/plans? > You could use libpruio to acce

Re: [beagleboard] Re: Protect eMMC/eMMC flasher Data

On Mon, 2016-02-08 at 08:47 -0800, Julien wrote: > Hello, > > I up the post, nobody has a solution for encrypting an image ? > > I see more solution for the raspberry but i don't find a same > solution for BBB... I'm not sure what solution would work for the pi that can't also be used for the BB

Re: [beagleboard] Use GPIO as non-root user?

This is John, the guy with the question Drew to above on the Adafruit board. (Thanks Drew for starting this conversation here.) The problem is, this is part of a commercial application. My code will be reading and writing to the GPIOs and doing various things, communicating data to remote syste

Re: [beagleboard] Re: Protect eMMC/eMMC flasher Data

Hi Julien It's illegal to encrypt a Linux image (and sell it)! Please read the GPL in detail! http://www.gnu.org/licenses/gpl-3.0.en.html But, if your software is strictly your software, _and_ not depending on any GPL'd libraries, (LGPL might work, I am no lawyer;) Then it might work with a user wi

Re: [beagleboard] Re: Protect eMMC/eMMC flasher Data

On 2016-02-08 at 21:21:45 +0100, Dieter Wirz wrote: > Hi Julien > It's illegal to encrypt a Linux image (and sell it)! Please read the > GPL in detail! http://www.gnu.org/licenses/gpl-3.0.en.html the Linux kernel is released under GPLv2, not v3 -- Elena ``of Valhalla'' -- For more options, vis

[beagleboard] Reload a new PRU program in the PRU using pruss_remoteproc

Hello all, first post hoping you can help me. I have finally got my PRU working on my BBB Debian 4.1.17-ti-rt-r46. I used the PRU_gpioToggle example from https://git.ti.com/pru-software-support-package/pru-software-support-package/trees/master/examples/am335x/PRU_gpioToggle which I compiled w

[beagleboard] debian testing: 2016-02-07 (WiFi AP)

Howdy! So there's a little something new in this week's snapshot: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-02-07 Create AP access point on board via: sudo systemctl start create_ap (board is 192.168.8.1, haven't got "beaglebone.local" working over wifi like yet..) Or create a

Re: [beagleboard] Reload a new PRU program in the PRU using pruss_remoteproc

This is a known problem. Back on Oct 6, I wrote the following: I have pruss_remoteproc/virtio_rpmsg_bus working on V4.1 when I boot for the first time. However, when I uninstall the KO with rmmod -f pruss_remoteproc and then install the KO with modprobe pruss_remoteproc, I get a kernel exce

Re: [beagleboard] Cape Bacon & device tree issue on a BBB with 3.8.13 kernel

You are right, I've done a mess with the I/O, Cape Bacon is now up and running ! Many thanks for your help and for your amazing contribution to Linux for BBB. Kind regards, YA Le dimanche 7 février 2016 23:55:38 UTC+1, RobertCNelson a écrit : > > On Sun, Feb 7, 2016 at 4:34 PM, YA > > wrote:

Re: [beagleboard] Cape Bacon & device tree issue on a BBB with 3.8.13 kernel

> > *Many thanks for your help and for your amazing contribution to Linux for > BBB.* > Maybe nitpicking, and a point that perhaps Robert does not care to toot his own horn over . . . But Robert contributes to Linux for far more than just the BBB. In the context of beagle hardware, probably 5-6 bo

Re: [beagleboard] Cape Bacon & device tree issue on a BBB with 3.8.13 kernel

Hi Williams, I totally agree with you, thanks for your comment. Cheers, YA Le lundi 8 février 2016 22:54:56 UTC+1, William Hermans a écrit : > > *Many thanks for your help and for your amazing contribution to Linux for >> BBB.* >> > > Maybe nitpicking, and a point that perhaps Robert does not

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

I'm have trouble reproducing this. I'm running *cat /etc/dogtag* BeagleBoard.org Debian Image 2016-01-24 *cat $SLOTS * 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln Wire an LED to P9_14 and then: *cd /sys/cl

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 4:22 PM, Mark A. Yoder wrote: > I'm have trouble reproducing this. I'm running > > cat /etc/dogtag > BeagleBoard.org Debian Image 2016-01-24 > cat $SLOTS > 0: PF -1 > 1: PF -1 > 2: PF -1 > 3: PF -1 > 4: P-O-L- 0 Override Board Name,00A0,Override M

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Sorry, I left that out. *config-pin -q P9_14* P9_14 Mode: pwm It appears to be set right. --Mark On Monday, February 8, 2016 at 5:27:42 PM UTC-5, RobertCNelson wrote: > > On Mon, Feb 8, 2016 at 4:22 PM, Mark A. Yoder > wrote: > > I'm have trouble reproducing this. I'm running > > > > cat /

Re: [beagleboard] Use GPIO as non-root user?

> > *I call my success partial because I can get a test LED to turn on, but I > can't get it to flash using PWM.* > > *Any ideas why that would be?* > No . . . Because you've given no pertinent details. We'd need to know a few things, but kernel version used, method used for attempting to control

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Have the pins "shifted" in this kernel again ? On Mon, Feb 8, 2016 at 3:34 PM, Mark A. Yoder wrote: > Sorry, I left that out. > > *config-pin -q P9_14* > P9_14 Mode: pwm > > It appears to be set right. > > --Mark > > On Monday, February 8, 2016 at 5:27:42 PM UTC-5, RobertCNelson wrote: > >> On M

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 4:41 PM, William Hermans wrote: > Have the pins "shifted" in this kernel again ? or the pwm's moved and i didn't notice.. The only userspace pwm i've used is: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-BACONE-00A0.dts and accessed the pwm'

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 4:22 PM, Mark A. Yoder wrote: > I'm have trouble reproducing this. I'm running > > cat /etc/dogtag > BeagleBoard.org Debian Image 2016-01-24 > cat $SLOTS > 0: PF -1 > 1: PF -1 > 2: PF -1 > 3: PF -1 > 4: P-O-L- 0 Override Board Name,00A0,Override M

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Well /sys/class/pwm/pwmchip2/pwm0 worked! Thanks... So given the pin name (P9_14 for example) how do I find the pwm path? (I'm trying to port bonescript to Jessie.) --Mark On Monday, February 8, 2016 at 5:41:27 PM UTC-5, William Hermans wrote: > > Have the pins "shifted" in this kernel ag

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 5:36 PM, Mark A. Yoder wrote: > Well /sys/class/pwm/pwmchip2/pwm0 worked! Thanks... > > So given the pin name (P9_14 for example) how do I find the pwm path? (I'm > trying to port bonescript to Jessie.) For the pwm, I think it's load order (scary) not sure if we

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Well, they move around depending on which dts you boot under. P9_14 appears at /sys/class/pwm/pwmchip*2*/pwm0 with *cat $SLOTS * 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,*univ-emmc* But if you use: *cat $SLOTS * 0: PF

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

@Mark, Yes,and no. No, in that there is no way to differentiate which header the peripheral is physically attacked to. Yes, in that device tree "defines" usually define a device module as something similar to: device_tree_friendly_name@ In other words, we should be able to extrapolate which de

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

attached . . .but I figure you all knew that already ;) On Mon, Feb 8, 2016 at 5:13 PM, William Hermans wrote: > @Mark, > > Yes,and no. > > No, in that there is no way to differentiate which header the peripheral > is physically attacked to. > > Yes, in that device tree "defines" usually define

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Yup, here's the mappings depending on which dts file is used: # universaln # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 -> ../../devices/platform/ocp/4830.epwmss/48300200.ehrpwm/pwm/pwmchip0 # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip2 -> ../../devices/platform/ocp/48302000.epwms

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

You know this makes me cringe when I think about it. But perhaps Bonescript needs it's own dt overlay ? One needs consistency when using a certain thing, and based on what I'm seeing, you're not guaranteed that. What's more, there is no real way you can expect this either, considering difference ca

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 6:36 PM, Mark A. Yoder wrote: > Yup, here's the mappings depending on which dts file is used: > > # universaln > # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 -> > ../../devices/platform/ocp/4830.epwmss/48300200.ehrpwm/pwm/pwmchip0 > # 0 lrwxrwxrwx 1 root root 0 Feb

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

On Mon, Feb 8, 2016 at 6:50 PM, Robert Nelson wrote: > On Mon, Feb 8, 2016 at 6:36 PM, Mark A. Yoder wrote: >> Yup, here's the mappings depending on which dts file is used: >> >> # universaln >> # 0 lrwxrwxrwx 1 root root 0 Feb 8 19:32 pwmchip0 -> >> ../../devices/platform/ocp/4830.epwmss/48

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

> > *We could also add the alias to the am33xx.dtsi:* > > * > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi#n20 > * > > * like:* > > * > https

Re: [beagleboard] Enable PWM on BBB Debian 4.1 Jessie

Mark, Quite honestly, I have no idea how both of those capes you're showing data on work. Each peripheral module between the two have different base addresses. Offset width, I can understand being different, but device module base address ? . . .I'm confused. On Mon, Feb 8, 2016 at 5:58 PM, Willia

Re: [beagleboard] Use GPIO as non-root user?

(env) app@beaglebone:/opt/reactor_controller/src$ uname -a Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux (env) app@beaglebone:/opt/reactor_controller/src$ cat /etc/dogtag BeagleBoard.org Debian Image 2015-03-01 (env) app@beaglebone:/opt/reactor_controller/src$

Re: [beagleboard] X15 Availability

Is there any update on the shipping date? Are you still expecting to start shipping this month? On Thursday, December 24, 2015 at 10:24:32 AM UTC-6, Gerald wrote: > > Yes. We hope to start shipping in February. We had to make some design > changes in order to pass FCC. > > Gerald > > On Thu, Dec

Re: [beagleboard] Use GPIO as non-root user?

and when I do the above as root it blinks as it should. On Mon, Feb 8, 2016 at 4:44 PM John Stoner wrote: > (env) app@beaglebone:/opt/reactor_controller/src$ uname -a > Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l > GNU/Linux > (env) app@beaglebone:/opt/reactor_contr

Re: [beagleboard] X15 Availability

We are working to get about 150 of the current revision out in the next few weeks to one distributor. We had some of the Rev A2 versions PCBs still available so we are working to build those up. If you look at http://elinux.org/Beagleboard:BeagleBoard-X15 you will see the latest official update on

Re: [beagleboard] Use GPIO as non-root user?

OK, so assuming your issue doing the above - only works as root, and you'd like it to work as a regular user too . . . You need to figure out how the Adafruit_BBIO library accesses the pins, and go from there. Does it use sysfs, or /dev/mem/ ? If the library uses sysfs. Then I would think you'd n

Re: [beagleboard] Use GPIO as non-root user?

It seems as though their using sysfs: https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/source/c_pwm.c#L68-L77 On Mon, Feb 8, 2016 at 6:23 PM, William Hermans wrote: > OK, so assuming your issue doing the above - only works as root, and you'd > like it to work as a regular us

[beagleboard] Re: debian testing: 2016-02-07 (WiFi AP)

On Mon, Feb 8, 2016 at 3:16 PM, Robert Nelson wrote: > Howdy! > > So there's a little something new in this week's snapshot: > > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-02-07 > > Create AP access point on board via: > > sudo systemctl start create_ap > > (board is 192.168.8.1, ha