If you understand device trees, you should be able to turn off I2C2 on
p9-19 and P9-20 and enable on P9-21 and P9-22 (as Mode 4). I doubt that
you can route the I2C2 out to two separate pin-outs at the same time.
If you don't understand how to make all of that work, then I would put some
very
Oh, and by the way, this hardware and community is 100% open source. If
you've got a problem that us supposedly crapper community helpers can help
you with. Go download the schematics, or source code and figure it out for
yourself. Unles of course as I suspect you're not a real engineer, but some
Yeah well those Rabbit semi boards actually are not bad, its the software
stack you're forced to use with them that is horrible. Wulf and I built an
ethernet connected lead acid charge controller using one of these and the
crappy compiler you're forced to use introduced random bugs that where hard
For someone who has been "working with products like this for 18 years", you
would think he would be able to help himself by now. Yet he still thinks he is
smarter than the rest of us, advising us to “leave this BBB”. Well, Karl, there
are many more smarter people here who think BBB is way
Source has been noted.
Gerald
On Mar 22, 2016 6:52 PM, "evilwulfie" wrote:
> Nobody has forced you to use the BBB.
> Nobody has forced you to even LIKE the BBB
>
> As long as you feel that way remove yourself from the list and we will not
> be bothered
> by you anymore.
>
Nobody has forced you to use the BBB.
Nobody has forced you to even LIKE the BBB
As long as you feel that way remove yourself from the list and we will
not be bothered
by you anymore.
On 3/22/2016 4:42 PM, Karl Easterly wrote:
>
> to be a bit more nice about my grandious statement that the BBB
to be a bit more nice about my grandious statement that the BBB is dead..
here is a bit of history.
I have been working with products like this for about 18 years. Small form
factor boards like the basic stamps and zworld jack rabbits to todays rasp
pi's and bbb's and the banana pros and such and
SPI1 shows the same 1.8v output. I will attempt to move to another BBB (a
BBG actually) and if things work there then I'll assume I toasted the SPI
on this board.
On Tuesday, March 22, 2016 at 1:07:43 PM UTC-4, Walker Archer wrote:
>
> I suspect you're exactly right Wulf Man. I was not really
My experience has been quite different. Pretty much all the progress I've
made with the BBB was enabled by various forum posts and code
repositories. And every time I think I have an original question or
observation, a little searching online finds the answer or a similar
developer
Ya.. I didn't ask for help.. as you noticed :)
The point is the community for the beagle board is so sparse self help is
not an option. A sparse community around this type of product equals a dead
product.
On Sun, Mar 20, 2016 at 4:32 PM, Robert P. J. Day
wrote:
>
Hi Mike,
On Tue, Mar 22, 2016 at 2:51 PM, Mike wrote:
> root@beaglebone:/boot# grep NTP config-4.1.18-ti-rt-r52
> # CONFIG_NTP_PPS is not set
> root@beaglebone:/boot#
>
> Any chance we can get this enabled?
>
> Been chasing my tail for too long now trying to figure out why
root@beaglebone:/boot# grep NTP config-4.1.18-ti-rt-r52
# CONFIG_NTP_PPS is not set
root@beaglebone:/boot#
Any chance we can get this enabled?
Been chasing my tail for too long now trying to figure out why ntpd
doesn't see my pps signal.
Thanks
Mike
--
For more options, visit
Hi Lucas,
This seems to work just fine for me. What kernel version are you using?
I’m using V4.1.13-ti-r33. As you can see, all remoteproc/rpmsg kernel modules
are loaded automatically at boot time.
[ 16.251480] pruss-rproc 4a30.pruss: 8 PRU interrupts parsed
I suspect you're exactly right Wulf Man. I was not really paying attention
to the order I applied the power and I was assuming that the POT voltage
would be isolated from the digital control side of the chip. But I also
assumed that if I blew the drivers that I would no longer get any signal
Only specific video modes of the HDMI framer device support audio. See the wiki
page.
> On Mar 22, 2016, at 10:44 AM, yolc...@gmail.com wrote:
>
> After work with a multitouch screen for the BeagleBone Black, now I just want
> to play audio/sounds through the HDMI connection as the multitouch
There are no other SPI chips on that bus. Since the AD5206 is permanently
a slave on the SPI bus I would think it would not try to drive the line.
On Tuesday, March 22, 2016 at 10:55:49 AM UTC-4, Harvey White wrote:
>
> On Tue, 22 Mar 2016 05:47:19 -0700 (PDT), you wrote:
>
> >I've been
On Tue, Mar 22, 2016 at 11:31 AM, wrote:
> Adding new information about the issue:
> filename: /lib/modules/4.1.16-bone18/kernel/sound/core/snd.kp
>
HDMI audio is in patch hell on mainline, if you want to use "4.1.x"
with hdmi audio you need to use the ti branch:
cd
Adding new information about the issue:
'lsmod':
snd 56846 6 snd_soc_core, snd_timer, snd_pcm, snd_seq,
snd_seq_device, snd_comp
'modinfo snd':
filename: /lib/modules/4.1.16-bone18/kernel/sound/core/snd.kp
alias: char-major-116-*
license:
Le mardi 22 mars 2016 14:28:48 UTC+1, RobertCNelson a écrit :
>
> On Tue, Mar 22, 2016 at 5:40 AM, Le Costaouec Vincent
> wrote:
> > Hi,
> >
> > I'm currently trying to configure and test UART4 on the BBB.
> > So I my point is to connect the two pins and try to
After work with a multitouch screen for the BeagleBone Black, now I just
want to play audio/sounds through the HDMI connection as the multitouch
screen has a speaker.
First of all, I just copied an audio sample, and try to reproduce it by
'vlc', but next message is shown:
"*Audio
As stated in the topic's subject, I am currently trying to expose I2C2 (The
I2C bus that's normally connected to P9_19, P9_20) to pins P9_21 and P9_22.
Since the documentation for the Beaglebone Black/Green show that pins 21
and 22 can be used for I2C2 it must be possible, I just can't find a
Power sequencing is the key. How are you doing this?
If you are applying the 5v to the pots first you may be causing the
issue and blowing the processor pins.
All pins on the processor need to be isolated from everything until
power rails are stable.
Drive a input pin when the processor is not
On Tue, Mar 22, 2016 at 9:58 AM, Karina Bond wrote:
> A question about Robert's commentsmy USB devices are powered with their
> own supply though. In this case neither of the devices should be requesting
> the full 500mA.
>
> Anything I try To make this work with an
A question about Robert's commentsmy USB devices are powered with their own
supply though. In this case neither of the devices should be requesting the
full 500mA.
Anything I try To make this work with an unpowered USB HUB?
-Karina
Sent from my iPhone
> On Mar 22, 2016, at 7:18 AM,
On Tue, 22 Mar 2016 05:47:19 -0700 (PDT), you wrote:
>I've been building a custom cape for a robotics project and one of the
>chips I'm using is controlled via SPI. I've used an oscilloscope to
>validate that the SPI is working as expected. However, two days ago I
>noticed that the chip
I am trying to use rpmsg from user space. I am following the PRU training
of TI
(http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#Part_1:_Linux_Command_Line_LED_Toggling)
I use the latest beaglebone black image (Debian 8.3 2016-01-24
from
Forgot to add info about how the cape is powered. The chip I'm using on
the cape is an AD5206 digital potentiometer (10k). I'm using the 3.3v rail
to power the SPI side and an external 5v (4.9v measured) supply powers the
pots. However, I've been getting voltages from the pots that aren't
Thanks for responding Gerald. The scope capture above was done with no
cape. It was taken from SPI0. The chip has one-way communication so I'm
only using SPID1 (P9_18 from memory). The clock is coming from P9_22.
Chip select is P9_17. When I get home tonight I'll try the same from SPI1
On Tue, Mar 22, 2016 at 8:56 AM, Karina Bond wrote:
>
> So the hub in my setup is unpowered. But I have tried powering up the USB
> devices first. Then powering up the beagle bone . In this case the two USB
> show up in the output of 'lsusb'.
>
> I am working on finding a
So the hub in my setup is unpowered. But I have tried powering up the USB
devices first. Then powering up the beagle bone . In this case the two USB show
up in the output of 'lsusb'.
I am working on finding a powered USB hub to try this with. But ideally I'd
like to use an unpowered hub.
On Tue, Mar 22, 2016 at 2:58 AM, wrote:
> hello,
> almost the same problem with me but as i am following the link:
> https://eewiki.net/display/linuxonarm/BeagleBone+Black
> after downloading the boot loader and linux kernel for "am33x-v4.5 (Stable)"
> i.e git checkout
Hi,
I'm currently trying to configure the UART4 of the BBB.
In addition my test is simply to connect the RX and TX pins and try to
received the message through minicom.
However after my configuration I didn't succeed to make it work. I don't
really understand why.
I use the following dtb
you can just package it from the IDE in the jar and use default jssc jar
2.8 version.
On Tuesday, July 29, 2014 at 10:01:03 PM UTC+3, RobertCNelson wrote:
>
> On Tue, Jul 29, 2014 at 9:40 AM,
> wrote:
> > I'm having problems using jSSC on my BBB Rev C running Debian.
hello,
almost the same problem with me but as i am following the link:
https://eewiki.net/display/linuxonarm/BeagleBone+Black
after downloading the boot loader and linux kernel for "am33x-v4.5
(Stable)" i.e git checkout origin/am33x-v4.5 -b tmp, the build_kernel.sh
script is not running and is
No way for me to tell what you may have done, but 1.8V is not good. Any
chance you can provide more information like the pin number and connector
you are using?
What do you have connected to this pin?
How is that device powered?
Gerald
On Tue, Mar 22, 2016 at 6:47 AM, Walker Archer
David,
William's suggestion of the PRU is a really good one.
I know there are examples on the forum for using them - even though I
personally haven't looked at them.
You should be able to do everything inside the PRU - You only need 144
bytes per buffer (assuming 1 color / 1 bpp).
So even
On Tue, Mar 22, 2016 at 5:40 AM, Le Costaouec Vincent
wrote:
> Hi,
>
> I'm currently trying to configure and test UART4 on the BBB.
> So I my point is to connect the two pins and try to communicate with them
> through minicom.
> However I haven't any response from
I've been building a custom cape for a robotics project and one of the
chips I'm using is controlled via SPI. I've used an oscilloscope to
validate that the SPI is working as expected. However, two days ago I
noticed that the chip stopped responding and after scoping the SPI signal I
can see
Hi,
I'm currently trying to configure and test UART4 on the BBB.
So I my point is to connect the two pins and try to communicate with them
through minicom.
However I haven't any response from the board.
for my dts i'm using this one :
On Tuesday, March 22, 2016, Karina wrote:
> Hi,
>
> I have a unpowered 2-port USB hub that I have connected to the BeagleBone
> Black (Rev C). I have two (serial over ) USB devices connected to the two
> port of the USB hub. They are are not powered to begin with. When i
So... I have a BBB rev C with a wifi dongle. I downloaded the 8.3 disk
image, started it, no channels blocked by rfkill when I first started
with the new image. I was able to modify /etc/network/interfaces and
connect to wifi. I then ran the apt-get update/upgrade combo. After
that, I rebooted...
41 matches
Mail list logo