Re: [beagleboard] Re: Blew up my BBB

> On Oct 25, 2015, at 07:36 , Graham wrote: > > I would think that your best bet (not the cheapest solution, but most likely > to yield results fast), is to buy another good BBB, then give that new one > and the bad one to someone that has BGA rework and re-balling

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

Thanks, William. Questions below > On Oct 26, 2015, at 15:56 , William Hermans wrote: > > Yes. > > cat /sys/bus/iio/devices/iio\:device0/in_voltageX_raw is single shot mode. If > you're running in continuous mode you need to read from /dev/iio:device. So > you get this

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

Thanks! On Monday, October 26, 2015 at 9:51:59 AM UTC-7, RobertCNelson wrote: > > On Sat, Oct 24, 2015 at 5:17 PM, Erik Stauber > wrote: > > Is there anything I need to do to make the power button work on the > latest > > Jessie images? It worked fine on 3.8.X. > >

Re: [beagleboard] How to update the latest image to eMMC?

On Mon, Oct 26, 2015 at 4:31 PM, Mian Tang wrote: >> First of all, I'm not using a 5volt 1 Amp power supply into the bbb's >> 5jolt jack, only with USB power supply. USB Flashing is not supported.. > > Second, the full image file name is: >

Re: [beagleboard] How to update the latest image to eMMC?

> > First of all, I'm not using a 5volt 1 Amp power supply into the bbb's > 5jolt jack, only with USB power supply. Second, the full image file name is: bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img. Third, so far I'm not sure which revision of the BBB I have. Could you please

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

Oh no! I will try building myself but failing that I can probably wait till Thursday. Will report back if the issue gets fixed. Lee On Mon, Oct 26, 2015 at 5:07 PM, Robert Nelson wrote: > On Mon, Oct 26, 2015 at 11:53 AM, Lee Armstrong

Re: [beagleboard] How to update the latest image to eMMC?

Do not use USB power to flash. It will fail. USB doe snot provide enough power for the flashing process. Gerald On Mon, Oct 26, 2015 at 4:31 PM, Mian Tang wrote: > First of all, I'm not using a 5volt 1 Amp power supply into the bbb's >> 5jolt jack, only with USB power

Re: [beagleboard] LCD and Capacitive touch drivers for Debian on BB black

On Mon, Oct 26, 2015 at 3:21 PM, wrote: > My company is building a product based on the Beaglebone black as a > reference design. We will be adding a touch screen with a capacitive touch > screen controller (Mitsubishi) using either a serial or USB protocol. The > LCD

Re: [beagleboard] How to update the latest image to eMMC?

> > OK. I'll try again with 5V power supply. And the revision is Rev C. Thank you for telling me. -- 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

[beagleboard] LCD and Capacitive touch drivers for Debian on BB black

My company is building a product based on the Beaglebone black as a reference design. We will be adding a touch screen with a capacitive touch screen controller (Mitsubishi) using either a serial or USB protocol. The LCD display will be wired to the BB similarly to the BB-VIEW cap (24 bit

[beagleboard] How do I get rid of of the Windows security pop-ups when installing the drivers

We have client software that installs the BONE_D64.exe driver on a first time installation on a client computer. I'd like to get rid of this experience for the customer - I assume the files are not certified - how can I get this resolved?

Re: [beagleboard] Source repo for 3.18.13-bone72?

Sorry, I need both 3.18.13-bone72 ande 3.18.13-bone68 Thanks, > On Oct 26, 2015, at 18:26 , Rick Mann wrote: > > Where do I find the branch/tag for 3.18.13-bone72? > > Thanks, > > -- > Rick Mann > rm...@latencyzero.com > > > -- > For more

Re: [beagleboard] Source repo for 3.18.13-bone72?

On Mon, Oct 26, 2015 at 8:26 PM, Rick Mann wrote: > Where do I find the branch/tag for 3.18.13-bone72? Pick one: https://github.com/beagleboard/linux/tree/3.8.13-bone72 https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/3.8.13-bone72

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

> > *I don't need ADC faster than 100 Hz (on each of up to three channels). > I'd love to move it to the PRU, but right now I'm using a library that > downloads firmware to both PRU cores to bitbang LED control. I'll have to > modify that to add my own ADC needs, and I'm not ready to do that right

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

> On Oct 26, 2015, at 17:05 , William Hermans wrote: > >> I'm using it the same way I always have. On my other BBB running a >> 3.8.13-bone68 kernel and an older Debian, I'm able to read it just fine with >> the BB-ADC dtbo loaded. As far as I know, I've never set anything

Re: [beagleboard] Re: Blew up my BBB

If the goal is to recover data, it might be easier to get the eMMC mounted on an adapter board (instead of risking another BeagleBone) so it can be read from a PC or another card reader. Or for the really adventureous - remove the eMMC and do a dead wiring to a disassembled uSD to SD adapter.

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

Yes. cat /sys/bus/iio/devices/iio\:device0/in_voltageX_raw is single shot mode. If you're running in continuous mode you need to read from /dev/iio:device. So you get this "error" when attempting to use single shot channel files, when the ADC is operating in continuous mode. If I were you, I'd

[beagleboard] Source repo for 3.18.13-bone72?

Where do I find the branch/tag for 3.18.13-bone72? Thanks, -- Rick Mann rm...@latencyzero.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

[beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

Anyone have any advice on why I can't seem to read the ADC? Thanks! -- What am I missing here? # uname -r 3.8.13-bone72 # pwd /sys/bus/iio/devices/iio:device0 # ls dev in_voltage0_raw in_voltage1_raw in_voltage2_raw name power/ subsystem@ uevent # cat in_voltage0_raw

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

> > *I'm using it the same way I always have. On my other BBB running a > 3.8.13-bone68 kernel and an older Debian, I'm able to read it just fine > with the BB-ADC dtbo loaded. As far as I know, I've never set anything to > be continuous (or one-shot, for that matter).* > You can check the mode

Re: [beagleboard] Re: Blew up my BBB

Just request an RMA. Note that you want to save the eMMC contents. They should be able to handle that. There is no need to replace the eMMC. They just need to be sure and not re-flash it. Gerald On Mon, Oct 26, 2015 at 5:12 PM, wrote: > If the goal is to recover data, it

Re: [beagleboard] Re: Blew up my BBB

Thanks, Gerald, that's awesome. I'll try that. Erm...where do I send the request? Element 14? > On Oct 26, 2015, at 17:32 , Gerald Coley wrote: > > Just request an RMA. Note that you want to save the eMMC contents. They > should be able to handle that. There is no need

Re: [beagleboard] Re: Blew up my BBB

Well, if you bought it from Element 14, well, I am not sure they can save the eMMC. We can. But, you bought it from Element 14 so you need to ask them what they are capable of doing. Gerald On Mon, Oct 26, 2015 at 7:38 PM, Rick Mann wrote: > Thanks, Gerald, that's

Re: [beagleboard] Re: Beaglebone Black Kernel 4.1 PWM and OCP?

Chris, This is a custom overlay that I created based on other overlays. I have not tested this *exact* overlay, since it is extracted from the larger overlay that matches my additional hardware (about 20 discrete inputs and 2 quadrature encoders). In the end, I think the standard overlays

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

Oh, and in case it's pertinent $ cat /etc/dogtag BeagleBoard.org Debian Image 2015-03-01 Wheezy 7.8 rootfs, and I'm using the pru's without remoteproc / rpmsg. On Mon, Oct 26, 2015 at 8:50 PM, William Hermans wrote: > I have it working Rick on . . . > $ uname -a > Linux

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

Hi John, Did you ever resolve this? > On Oct 19, 2015, at 11:08 , John Syne wrote: > > Hi Rich, > > I have this working on BBB using V4.1.6-bone15, but I should receive an x15 > sometime today and it will take me a few days to do testing. There is however > one hick-up

Re: [beagleboard] Source repo for 3.18.13-bone72?

On Mon, Oct 26, 2015 at 8:32 PM, Rick Mann wrote: > >> On Oct 26, 2015, at 18:29 , Robert Nelson wrote: >> >> Pick one: >> >> https://github.com/beagleboard/linux/tree/3.8.13-bone72 > > Weird. That's the first place I went, but I don't see

Re: [beagleboard] Blew up my BBB

Honestly, I've bought several from various places (Digikey, Adafruit, Sparkfun, etc). Who is "we?" > On Oct 26, 2015, at 19:00 , Gerald Coley wrote: > > Well, if you bought it from Element 14, well, I am not sure they can save the > eMMC. We can. But, you bought it

Re: [beagleboard] Blew up my BBB

Thanks! > On Oct 26, 2015, at 19:07 , Robert Nelson wrote: > > On Mon, Oct 26, 2015 at 9:02 PM, Rick Mann wrote: >> Honestly, I've bought several from various places (Digikey, Adafruit, >> Sparkfun, etc). > > http://beagleboard.org/support/RMA

Re: [beagleboard] Source repo for 3.18.13-bone72?

> On Oct 26, 2015, at 18:29 , Robert Nelson wrote: > > Pick one: > > https://github.com/beagleboard/linux/tree/3.8.13-bone72 Weird. That's the first place I went, but I don't see "3.8.13-bone72" show up in the branch/tag menu. If I start typing "3.8", it shows

Re: [beagleboard] Reading ADC, get "cat: in_voltage0_raw: Device or resource busy"

So, I tried making the same changes as that patch in my 3.8 kernel. It was straightforward, but had no effect. Both the -bone68 and -bone72 have identical code that patch changes, so I know that's not it, because it works fine on the -bone68 board. I tried enabling all the channels (I was only

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

I have it working Rick on . . . $ uname -a Linux beaglebone 4.1.9-bone-rt-r16 #1 Thu Oct 1 06:19:41 UTC 2015 armv7l GNU/Linux This kernel was just an apt-get install. But, it's not a TI specific kernel if that's what you're wanting. As far as I can tell though, it's identical except that the pru

Re: [beagleboard] Blew up my BBB

On Mon, Oct 26, 2015 at 9:02 PM, Rick Mann wrote: > Honestly, I've bought several from various places (Digikey, Adafruit, > Sparkfun, etc). http://beagleboard.org/support/RMA "Important! If your board has the text "element14" on it or was "Made in China" or "Made in

Re: [beagleboard] Blew up my BBB

We is BeagleBoard.org. r...@beagleboard.org Gerald On Mon, Oct 26, 2015 at 9:02 PM, Rick Mann wrote: > Honestly, I've bought several from various places (Digikey, Adafruit, > Sparkfun, etc). > > Who is "we?" > > > On Oct 26, 2015, at 19:00 , Gerald Coley

Re: [beagleboard] Cannot get audio over HDMI working

Correct. Gerald On Sun, Oct 25, 2015 at 9:14 AM, wrote: > Ok, but as I mentioned in my original post, I have tried both of those > resolutions and neither of them produced audio over the HDMI connection. > So there must be some other problem that I have to get

[beagleboard] Warm_reset

In a custom board similar to beagleboard Xm we have a problem: When we make a software reboot the Warm_reset output go down for 200uS but the nResPwron didn't change level. So could you give me a Tps65950 sequence for a complete boot after a WarmReset. Thank you in advance. -- For more

Re: [beagleboard] Problem with GPIO on P8_35 to 38

On Mon, Oct 26, 2015 at 7:57 AM, AndyS wrote: > Thank for your help so far guys. > ## Is this a comment? > # or is this a comment? The character '#' signifies a comment in u-boot's uEnv.txt files.. > I am guessing I need to take out these # to make my eEnv.txt

Re: [beagleboard] Problem with GPIO on P8_35 to 38

> > *This what cat slots looks like * > > *root@AndyBBB:/boot# cat $SLOTS* > * 0: 54:PF--- * > * 1: 55:PF--- * > * 2: 56:PF--- * > * 3: 57:PF--- * > * 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G* > * 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI* > * 6:

Re: [beagleboard] Problem with GPIO on P8_35 to 38

It looks like my $SLOTS look I assume the missing L for HDMI and HDMIL means that they are not loaded? root@AndyBBB:~# cat $SLOTS 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas

[beagleboard] Problems with CANBus at BBB

Hi out there, hope someone can help me to activate the CAN Bus interface at Beaglebone Black. I describe shortly what I have done so far Debain linux cat /etc/debian_version 8.2 uname -a Linux beaglebone 4.1.10-ti-r23 #1 SMP PREEMPT Fri Oct 16 23:55:32 UTC 2015 armv7l GNU/Linux I downloaded

Re: [beagleboard] Cannot get audio over HDMI working

Ok, but as I mentioned in my original post, I have tried both of those resolutions and neither of them produced audio over the HDMI connection. So there must be some other problem that I have to get solved in order to make this work. On Saturday, October 24, 2015 at 3:36:24 PM UTC-4, Gerald

[beagleboard] kernel 4.1 makes ti am335x touchscreen (common 4.3 inch 4D cape) unusable

Hi, I tested the latest jessie flasher image on my beaglebone black rev C and the anti-jitter algorithm that was probably swapped out in https://github.com/beagleboard/linux/commit/83edfdf30b6f8d0916e8283fb395589afb9bdacb is taking 100% CPU on my board (in the X process) and jitters like crazy

Re: [beagleboard] Problem with GPIO on P8_35 to 38

On Mon, Oct 26, 2015 at 8:06 AM, 'andrew stillie' via BeagleBoard wrote: > Is there a definite test I can do to verify that both capes are disabled? If you want both disabled: (/boot/uEnv.txt) ##Disable HDMI

Re: [beagleboard] Problem with GPIO on P8_35 to 38

Is there a definite test I can do to verify that both capes are disabled? On Mon, 26 Oct 2015 13:02 Robert Nelson wrote: > On Mon, Oct 26, 2015 at 7:57 AM, AndyS > wrote: > > Thank for your help so far guys. > > ## Is this a comment? > >

Re: [beagleboard] Problem with GPIO on P8_35 to 38

So that means ## is a comment, and # is a comment. Or, any line starting with a hash( # ) is a comment. @Robert, it seems like he wants both disabled. He's trying to use pins that are in use by the HDMI framer, as Per Charles. On Mon, Oct 26, 2015 at 6:01 AM, Robert Nelson

Re: [beagleboard] Problems with CANBus at BBB

On Sun, Oct 25, 2015 at 7:49 AM, wrote: > Hi out there, > > hope someone can help me to activate the CAN Bus interface at Beaglebone > Black. I describe shortly what I > have done so far The can interface works fine, what did you use to interface the bbb's pins to your

Re: [beagleboard] Problem with GPIO on P8_35 to 38

Thank for your help so far guys. ## Is this a comment? # or is this a comment? I am guessing I need to take out these # to make my eEnv.txt look like this? ##Audio Cape (needs HDMI Audio disabled) cape_disable=capemgr.disable_partno=BB-BONELT-HDMI

Re: [beagleboard] Problems with CANBus at BBB

You need to use a can transceiver, and properly terminate the can interface. Otherwise, the can interface will not work. in our case we're using the Logic supply serial / canbus cape. http://www.logicsupply.com/cbb-serial/ $ sudo ifconfig [sudo] password for william: can0 Link encap:UNSPEC

Re: [beagleboard] kernel 4.1 makes ti am335x touchscreen (common 4.3 inch 4D cape) unusable

> > *Hi,* > *I tested the latest jessie flasher image on my beaglebone black rev C and > the anti-jitter algorithm that was probably swapped out in > https://github.com/beagleboard/linux/commit/83edfdf30b6f8d0916e8283fb395589afb9bdacb >

Re: [beagleboard] Re: Blew up my BBB

Next time use an SD card much easier to transfer to a non defunct BBB. On 10/26/2015 1:53 AM, Rick Mann wrote: >> On Oct 25, 2015, at 07:36 , Graham wrote: >> >> I would think that your best bet (not the cheapest solution, but most likely >> to yield results fast), is to

[beagleboard] Re: Power Button doesn't work on 4.1.10-ti-r24

I've just seen this and having the same issue actually! On Saturday, October 24, 2015 at 11:17:34 PM UTC+1, Erik Stauber wrote: > > Is there anything I need to do to make the power button work on the latest > Jessie images? It worked fine on 3.8.X. > > Thanks, > Erik > > -- For more options,

Re: [beagleboard] Re: shutdown procedure required for beaglebone black ??

I have an Element14 BBB running 4.1.10-ti-r22 Kernel and Debian 8.1 Jessie. A momentary press of the PWR button does not have any effect and the manual suggests it should start a shut down command. Holding it down for >8 seconds causes it to reset like the reset button so I know the hardware

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

On Mon, Oct 26, 2015 at 11:53 AM, Lee Armstrong wrote: > Ah thanks Robert! > > Is there a way to get this update with one of the scripts built in like the > update_kernel.sh ? Well, r25's is eta'ed for thursday, can't really build it right now as i'm backed up on v4.3.0-rc7

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

Ah thanks Robert! Is there a way to get this update with one of the scripts built in like the update_kernel.sh ? I’d love to try this out but not really sure how to apply this! Lee On Mon, Oct 26, 2015 at 4:52 PM, Robert Nelson wrote: > On Sat, Oct 24, 2015

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

On Sat, Oct 24, 2015 at 5:17 PM, Erik Stauber wrote: > Is there anything I need to do to make the power button work on the latest > Jessie images? It worked fine on 3.8.X. Thanks, fixed in git..

Re: [beagleboard] How to update the latest image to eMMC?

> > Yes, I think I see the cylon led pattern. Four leds flash one by one and > back and forth for about 10 minutes. > And then, all leds flash together. So, I think the image has been burned > to eMMC. And then, I restart the board with SD card removed. > And I cannot connect my PC

Re: [beagleboard] How to update the latest image to eMMC?

On Mon, Oct 26, 2015 at 1:15 PM, Mian Tang wrote: >> Yes, I think I see the cylon led pattern. Four leds flash one by one and >> back and forth for about 10 minutes. > > >> >> And then, all leds flash together. So, I think the image has been burned >> to eMMC. And then, I