The battery at the link you provided has a TX60 connector for the power leads.
I do not know where you are located but you could order the following from
Pololu and make a cable that splits the power with a pair (red and black) going
to a new TX60 connector which mates with your drone motors
I'm kind of at a standstill. I found a circuit design to use a transistor
to take a 3.3v input, and switch on the 5v for the GPS but then while doing
more reading someone said that was a really bad idea because they weren't
opto-isolated. I didn't really know what that was, but after reading it
Hi,
I am currently working on fabricating a PocketBeagle board with OSH Park
PCB's and the components
listed on the pocketbeagle github page.
https://github.com/beagleboard/pocketbeagle
There is one part that I had a hard time finding on digikey or another
supplier.
It is the SD card
Hey Man,
Seth here. Did you ever figure out the issue w/ setting up a GPIO pin to
control the 5v for your GPS?
Seth
On Sunday, February 10, 2019 at 12:38:52 AM UTC-6, Dan Hammans wrote:
>
> No apologies needed, I'm just trying to figure this out. What I meant was
> using a GPIO pin to
Robert:
Thanks for the quick reply. It turns out the resolution is working
fine. It's the backlight that isn't working.
--Mark
On Wednesday, February 13, 2019 at 5:30:11 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Feb 13, 2019 at 4:09 PM Mark A. Yoder > wrote:
> >
> > I have this nice new
On Wed, Feb 13, 2019 at 4:09 PM Mark A. Yoder wrote:
>
> I have this nice new HDMI display[1] for my x15, but when I hook it up,
> nothing displays. How do I change the default resolution on the x15?
>
> --Mark
>
> [1]
>
I have this nice new HDMI display[1] for my x15, but when I hook it up,
nothing displays. How do I change the default resolution on the x15?
--Mark
[1]
http://www.wiki.52pi.com/index.php?title=5-Inch-800x480-Capacitive-Touch-Screen_SKU:_EP-0081
--
For more options, visit
Search for the following two discussion topics on this forum:
BBB without reserved I2C addresses (Apr 17 2017)
Set up Cape's EEPROM i2c-2 BeagleBoneBlack Rev-C
--- Graham
On Wednesday, February 13, 2019 at 6:51:41 AM UTC-6, bruce...@yahoo.com
wrote:
>
> How can I
The charge balance connectors are typically JST PH connectors on a 0.1"
pitch (though might be 2mm - it think that's JST XH). They bring out the
two ends of the battery pack (the same as the high current connector) and
every junction between cells. So the 2s charger on the BBBlue has 2+1 pins
and
I used to be able to power my servo and DC motors with the 2 cell lipo
input. Now, I can't power the BB on at all through the lipo input and for
rc_test_adc (using 9V plugged into the wall - this is the only way I can
power on the board) I'm getting the following:
adc_0 | adc_1 | adc_2 | adc_3
I am a bit unsure on how to connect the 4s battery to the dc jack. It is
using the battery connector found on this
jack
https://www.unmannedtechshop.co.uk/product/tattu-1800mah-14-8v-45c-4s1p-lipo-battery-pack/.
Is there some component I can by which I can solder on the end of the
battery
I ran into this problem. I was able to fix it by re-imaging the BeagleBone
Black.
https://beagleboard.org/getting-started#update
The "IoT" image (without graphical desktop) is probably what you want. It
uses less space, and you'll need to get used to using a terminal emulator,
like PuTTY,
On Wed, Feb 13, 2019 at 1:25 PM wrote:
>
>
> Hi
> I have an old BBB that used to run a lasersaur, it still has the ubuntu
> /lasersaur software on it. I want to flash it with the latest debian, I have
> tried o many times it i ridiculous.
> I have used both dd and etcher to copy the image
Yesterday, my BeagleBone Black (Rev C) was working fine. Today, when I
powered up the system eth0 is not coming up.
$ ip addr show eth0
2: eth0: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether c8:df:84:d7:07:a6 brd ff:ff:ff:ff:ff:ff
How do I get eth0 to come up again?
I'm seeing the same behavior on a newer 4.14 kernel beaglebone image. If
the Beaglebone is already booted up and connected to a Chromebook, then the
USB device will properly be assigned the 192.168.7.1 address. If the
Beaglebone is powered over USB, though, the Chromebook seems to not see a
Hi
I have an old BBB that used to run a lasersaur, it still has the ubuntu
/lasersaur software on it. I want to flash it with the latest debian, I
have tried o many times it i ridiculous.
I have used both dd and etcher to copy the image onto the disk, I have
edited the text file on the boot
On Wed, 13 Feb 2019 at 13:42, Roger Quadros wrote:
> On 13/02/19 13:57, Matthijs van Duin wrote:
> > +#ifdef CONFIG_ARCH_DAVINCI_DA850
> > if (pdata->sram_pool) {
> > gdev->sram_pool = pdata->sram_pool;
>
> What is this sram pool? Is it about MSMC/OCMC RAM?
No idea, the sram
I did. I even ran examples provided by TI, and the one for PRU1 does not
work.
Jacek.
On Wed, Feb 13, 2019 at 1:30 PM wrote:
> Did you change the interrupt numbers?
>
> /* The PRU-ICSS system events used for RPMsg are defined in the Linux
> device tre
> e
> * PRU0 uses system event 16 (To
Strangely the hotspot was set as DNS before, but it did not work back then.
Thank you all for your support.
.On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo wrote:
>
> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com
> wrote:
> > Is there a way of just replacing
Did you change the interrupt numbers?
/* The PRU-ICSS system events used for RPMsg are defined in the Linux
device tre
e
* PRU0 uses system event 16 (To ARM) and 17 (From ARM)
* PRU1 uses system event 18 (To ARM) and 19 (From ARM)
*/
#define TO_ARM_HOST 18
> Yes there is. Note that there is nothing wrong with connman.
> One more thing, connmanctl can connect to an Enterprise network. You
> need to prepare the corresponding file, just like you will need to with
> wpa_supplicant
I did. Then I used a standard sequence of operations from the tutorial
> Sorry, I'm still a bit lost here ;).
> How do I see the PRUSS kernel patches that you have picked up?
Okay for v4.19.x & v4.20.x, i've picked up RFC 1: (I need to backport
the am33xx-l4 dts changes to then backport RFC2..)
On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote:
> Is there a way of just replacing connmanm with wpa_supplicant using apt_get?
>
Yes there is. Note that there is nothing wrong with connman. You can
learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli.
One more
Is there a way of just replacing connmanm with wpa_supplicant using apt_get?
On Monday, February 11, 2019 at 6:18:56 PM UTC+1, ith...@gmail.com wrote:
>
> I use Beaglebone Blue which has no Ethernet port. Yes, internet sharing
> has many variables, but hotspots often work and if BBB had a
Robert,
On 13/02/19 18:04, Robert Nelson wrote:
> Hi Roger,
>
> On Wed, Feb 13, 2019 at 9:52 AM Roger Quadros wrote:
>>
>> Robert,
>>
>> On 28/01/19 21:15, Robert Nelson wrote:
>>> On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp wrote:
I tried to update our app image from the 4.14
Hi Roger,
On Wed, Feb 13, 2019 at 9:52 AM Roger Quadros wrote:
>
> Robert,
>
> On 28/01/19 21:15, Robert Nelson wrote:
> > On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp wrote:
> >>
> >>
> >> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
> >> kernel and ran into a
Robert,
On 28/01/19 21:15, Robert Nelson wrote:
> On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp wrote:
>>
>>
>> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
>> kernel and ran into a big problem: uio_pruss is not configured in as it is
>> with 4.14. Is this an
How can I free-up the addresses 0x54-57 on I2C bus 2 on my Beaglebone Black
? I can only access the lower half addr 0x50-53; the upper ones 0x54-57
show 'UU' when using i2cdetect. I need them for addressing the entire
contents of a 24C16 I2C EEPROM. Or if not possible then how else can I
How can I free-up the addresses 0x54-57 on I2C bus 2 on my Beaglebone Black
? I need them for addressing the entire contents of a 24C156 I2C EEPROM.
Or if not possible then how wlse can I control I2C at the range 0x50-57 ?
Another bus ? Perhaps a bit-banged bus ?
--
For more options,
I recall being able to run my motors (servos + DCs) fine with a 9V DC Jack
to the wall or a battery. Suddenly, everything stopped working. I'm getting
the error "ERROR: battery disconnected or insufficiently charged to drive
servos\n" with rc_test_servos and rc_test_motors just isn't making
On 13/02/19 13:57, Matthijs van Duin wrote:
> Since I just noticed a bunch of people were added to the Cc... Just for
> context, this is the patch set I made to get uio-pruss for the am335x and
> dra7/am57xx working again on the 4.19-ti series kernel:
>
Since I just noticed a bunch of people were added to the Cc... Just for
context, this is the patch set I made to get uio-pruss for the am335x and
dra7/am57xx working again on the 4.19-ti series kernel:
On Wed, 13 Feb 2019 at 12:20, Roger Quadros wrote:
> I see that uio_pruss is important for the bone community. We will need
> to work together to make sure that it continues to operate
>
Fortunately uio_pruss is a pretty simple driver that's easy to forward-port.
> Meanwhile, I'd like to
+David, Tony, Suman.
Robert, Matthijs, Daniel,
On 28/01/19 21:15, Robert Nelson wrote:
> On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp wrote:
>>
>>
>> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
>> kernel and ran into a big problem: uio_pruss is not configured in
OK, shame on me for just testing everything works on bbx15 and merely
checking the devices show up on beaglebone and *assuming* they work. They
really didn't. I had overlooked that the ti,deassert-hard-reset DT property
is a non-standard thing added by the original uio-pruss patch. A better
Hello,
I have problems with receiving remoteproc messages on PRU1. The code works
fine when configured and executed on PRU0, but PRU1 never receives any
interrupts (event numbers set for each PRU accordingly).
I modified examples PRU_RPMsg_Echo_Interrupt0 and PRU_RPMsg_Echo_Interrupt1
to flip I/O
36 matches
Mail list logo
