[beagleboard] BBB pull contention

On 9 February 2016 at 17:46, Gerald Coley wrote: > If you don't run SW, that fixes a contention issue in the processor and > let it sit, you will void the warranty and damage the processor after about > 120 hours of operation.. Speaking of contention, I reported one in

[beagleboard] Re: BBB pull contention

On 12 February 2016 at 15:07, Robert Nelson wrote: > Nah, that one is my fault.. That bug report must be bad luck, as > every time i started looking at it, something at the day job pulled me > away.. > OK, thing is, although it didn't seem particularly important to me

Re: [beagleboard] Codec drivers and alsa support for custom cape with sta321mp

Hi Pablo, Any progress with your board ? Also, to answer your question, I got the alsamixer working. You have to add a number of macros for predefined controls corresponding to register to update in the codec. You can see it directly in my code:

[beagleboard] lcd4 driver for beaglebone black.

I believe you will have to modify and recompile the kernel. Otherwise this link might be useful: http://papermint-designs.com/community/node/331 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

[beagleboard] Re: BBB pull contention

On Fri, Feb 12, 2016 at 7:18 AM, Matthijs van Duin wrote: > On 9 February 2016 at 17:46, Gerald Coley wrote: >> >> If you don't run SW, that fixes a contention issue in the processor and >> let it sit, you will void the warranty and damage the

[beagleboard] Re: BBB pull contention

On Fri, Feb 12, 2016 at 10:35 AM, Matthijs van Duin wrote: > On 12 February 2016 at 16:37, Robert Nelson wrote: >> >> So, P9.15, gpmc_a0 is setup as: >> >> {OFFSET(gpmc_ad0), (MODE(1) | RXACTIVE | PULLUP_EN)}, /* MMC1_DAT0 */ > > > Those are

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

On Fri, Feb 12, 2016 at 11:11 AM, Rafael Vega wrote: > Hi. > > I have the following DTO that I've been using successfully in kernel 3.8 to > use pin P9_41 as an input: > > ... > P9_41A_i: P9_41A_in{pinctrl-single,pins = <0x1B4 0x37>;}; >

[beagleboard] Using P9_41 as an input using 4.1 kernel.

Hi. I have the following DTO that I've been using successfully in kernel 3.8 to use pin P9_41 as an input: ... P9_41A_i: P9_41A_in{pinctrl-single,pins = <0x1B4 0x37>;}; P9_41A_o: P9_41A_out{pinctrl-single,pins = <0x1B4 0x0F 0x1A8 0x37 >;}; ...

[beagleboard] RS485 support for BBB

I would like to use RS485 with the BBB. root@beaglebone:~/test# uname -a Linux beaglebone 4.1.15-ti-r40 #1 SMP PREEMPT Thu Jan 7 23:32:17 UTC 2016 armv7l GNU/Linux I am using the kernel above. Its source code is at https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.1.15-ti-rt-r40 ...

Re: [beagleboard] RS485 support for BBB

On 12 February 2016 at 16:04, arsi wrote: > Hi, > > Use MAX13487EESA+ It has an automatic direction control.. Thanks, Arsi. That is interesting. I am using a prototype board designed by our hardware department that uses another Maxim RS485 driver which is pin compatible with the

[beagleboard] Re: BBB pull contention

On 12 February 2016 at 16:37, Robert Nelson wrote: > So, P9.15, gpmc_a0 is setup as: > > {OFFSET(gpmc_ad0), (MODE(1) | RXACTIVE | PULLUP_EN)}, /* MMC1_DAT0 */ > Those are different pins. The only useful purpose of pin 16 ("gpmc_a0") on a BBB is as pwm 1 tripzone input.

[beagleboard] Re: BBB pull contention

On Fri, Feb 12, 2016 at 9:11 AM, Matthijs van Duin wrote: > On 12 February 2016 at 15:07, Robert Nelson wrote: >> >> Nah, that one is my fault.. That bug report must be bad luck, as >> every time i started looking at it, something at the day

Re: [beagleboard] RS485 support for BBB

On Fri, Feb 12, 2016 at 9:33 AM, Taceant Omnes wrote: > I would like to use RS485 with the BBB. > > root@beaglebone:~/test# uname -a > Linux beaglebone 4.1.15-ti-r40 #1 SMP PREEMPT Thu Jan 7 23:32:17 UTC > 2016 armv7l GNU/Linux > > I am using the kernel above. Its source code

Re: [beagleboard] RS485 support for BBB

On 12 February 2016 at 15:41, Robert Nelson wrote: > On Fri, Feb 12, 2016 at 9:33 AM, Taceant Omnes wrote: >> I would like to use RS485 with the BBB. >> >> root@beaglebone:~/test# uname -a >> Linux beaglebone 4.1.15-ti-r40 #1 SMP PREEMPT Thu Jan 7

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

> I think i've seen enough, and i'm just going to remove the default > clock2 setting and re-enable P9_41 in the overlays.. > > > That's great, thanks! How would I disable the default overlays that you linked? How soon would your changes reach the repos as a new version of the kernel (no

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

On Fri, Feb 12, 2016 at 11:15 AM, Robert Nelson wrote: > On Fri, Feb 12, 2016 at 11:11 AM, Rafael Vega wrote: >> Hi. >> >> I have the following DTO that I've been using successfully in kernel 3.8 to >> use pin P9_41 as an input: >> >> ...

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

> > > P9_41 is used by audio, so make sure you are using the > > *-nhdmi-overlay.dtb, *-emmc-overlay.dtb or *-overlay.dtb > > I have dtb=am335x-boneblack-emmc-overlay.dtb in /boot/uEnv.txt so it should be fine (?) > ah p9_41.. so on mainline it's setup as clkout2_pin: > > >

[beagleboard] Re: pinctrl for P8_10 and P9_41 with 4.1.12-ti-r26

In case someone reads this: https://groups.google.com/forum/#!topic/beagleboard/e1do4oyo6RM On Friday, February 12, 2016 at 5:42:27 PM UTC+1, Rafael Vega wrote: > > Hey, did you manage to use P9_41 on 4.1 kernel? > > On Saturday, October 31, 2015 at 11:56:33 PM UTC+1, Erik Stauber wrote: >> >>

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

On Fri, Feb 12, 2016 at 12:03 PM, Rafael Vega wrote: >> >> >> > P9_41 is used by audio, so make sure you are using the >> > *-nhdmi-overlay.dtb, *-emmc-overlay.dtb or *-overlay.dtb >> > > I have dtb=am335x-boneblack-emmc-overlay.dtb in /boot/uEnv.txt so it should > be fine

[beagleboard] Re: BeagleBone Black won't startup (USR2 LED, always on)

new image 8.3 works well On Wednesday, 4 November 2015 21:21:53 UTC+5:30, Felix Müller-Irion wrote: > > Step by step: > I plug in a power supply or the USB cable, doesn't matter. > PWR LED comes on. > USR 0, USR 1, USR 2, USR 3 come on in that order, then USR 1 and 3 flash, > then USR 0 gives

Re: [beagleboard] How do you enable analog on Beaglebone Black?

Yeah, William did a nice job with this document. Regards, John > On Feb 12, 2016, at 3:38 PM, Gunnar wrote: > > Ok, I followed William's instructions, and the sample code is working, so I > think I am good to go. > > Thanks for the help! > > Gunnar > > On

Re: [beagleboard] How to build Os to beaglebone with hardcoding some of the GPIOs of beaglebone?

> > *When I refer, Beaglebone Black P8 Header, the GPIO 38, 39 (GPIO1[6], > GPIO1[7]) are having note as "Used on Board (Group: pinmux_emmc2_pins). > There are more other PINs having same note.* > The bolded text in the quote above should make it obvious as to why your attempt as using these pins

Re: [beagleboard] Using P9_41 as an input using 4.1 kernel.

On Fri, Feb 12, 2016 at 12:18 PM, Rafael Vega wrote: > >> I think i've seen enough, and i'm just going to remove the default >> clock2 setting and re-enable P9_41 in the overlays.. Yeah, it's tied to audio:

Re: [beagleboard] How do you enable analog on Beaglebone Black?

Ok, I followed William's instructions, and the sample code is working, so I think I am good to go. Thanks for the help! Gunnar On Thursday, February 11, 2016 at 7:13:58 PM UTC-8, john3909 wrote: > > Agreed. > > Regards, > John > > > > > On Feb 11, 2016, at 6:04 PM, William Hermans

[beagleboard] Re: Read voltage from ADC using an external power supply

Chelsea, As was mentioned, the BBB input pins can't be more than 1.8V so you will need a voltage divider to take your power supply voltage down between 0 and 1.8V. This page might help you: http://www.alfonsomartone.itb.it/hclbmf.html And it is possible you have already damaged that pin if you