mulate audio on hdmi, etc...
>
> PRU are amazing!
>
> On Thu, Nov 21, 2019 at 5:24 PM Dan Julio wrote:
>
>> Very neat Tomas!
>>
>> A PRU is capturing the write to the video memory? Are you reading the
>> data in via a parallel interface or serializing it?
>>
Very neat Tomas!
A PRU is capturing the write to the video memory? Are you reading the data
in via a parallel interface or serializing it?
Cheers, Dan
On Wednesday, November 20, 2019 at 9:19:44 AM UTC-7, Tomas Espeleta wrote:
>
> Helllo Guys,
> I just wanted to share the first steps of my
Hi Stuart,
I tried to use the PocketBeagle with the battery and also found the extra
current draw. Ultimately I communicated with Octavo and got the following
reply. The OSD3358-SM SiP used on the pocketbeagle internally connects the
LDO1 regulator to both the RTC clock input (VDDS_RTC) as
, and see if I can drive an RGB LCD. I really don't want
> to go to SPI LCD's for now, maybe just to try.
>
> Have a good weekend.
>
> Best regards,
>
>
> Em sábado, 6 de julho de 2019 16:43:17 UTC+2, Dan Julio escreveu:
>>
>> Although it isn't the 4.3" CA
Although it isn't the 4.3" CAPE, I have gotten a generic and inexpensive
2.8" ILI9348-based SPI display to work with the Pocketbeagle (and
Beaglebone black). It seems reasonably fast although I'm sure not as fast
as the parallel display. I haven't yet gotten the built-in TSC2046
resistive
Your PRU isn't running code so remoteproc has nothing to control. Either
the firmware file is missing from /lib/firmware or it isn't valid code.
On Sunday, March 10, 2019 at 10:27:40 AM UTC-6, gw wrote:
>
>
> [ 1864.134156] remoteproc remoteproc1: powering up 4a334000.pru
> [ 1864.134336]
Programming PRUs is a bit of a moving target as the mechanisms have changed
and evolved and a lot of documentation is out-of-date. I used some of
Mark's stuff and well as the cut method too.
I'm not using the scratchpad but I did write an application that moves data
between PRUs using a
Yes, T11 is connected to P2.12 on pocketbeagle.
On Monday, February 25, 2019 at 7:47:15 AM UTC-7, Hans Leeuw wrote:
>
> Dear community,
>
> Does anyone know if one of the pins on the pocket beagle connects to the
> start button pin pmic_PB_in? Also called T11 as I can see it in the
>
to challenge the clock down.
>
> After reading the datasheet of the PMIC, I would like to add a resistor to
> charge it and add a capacitor as needed.
> http://www.ti.com/lit/ds/symlink/tps65217.pdf
>
> 2019年2月3日日曜日 1時55分29秒 UTC+9 Dan Julio:
>>
>> IIRC, the pock
IIRC, the pocketbeagle can see current spikes over 200 mA from the battery
while it is booting, although it takes less power after it is booted and
idling. Probably one of two things is happening. The battery voltage
droops and either its own protection circuitry cuts off the power or the
It should be possible to move to the Pocketbeagle. I moved a moderately
complex application from the black to the pocketbeagle. I use GPIO, both
SPIs, I2C and USB. Here's what I found (4.14-based beaglebone debian
distro):
1. SPI and I2C devices should be ok providing you are using the
To close this thread out, I heard back from Octavo systems. The OSD3358-SM
SiP used on the pocketbeagle internally connects the LDO1 regulator (I
misspoke above) to both the RTC clock input (VDDS_RTC) as well as the VDDS
input. The extra current is taken by the connection to the VDDS power
I have done some further research. It seems that the tps65217.c mfd driver
in the kernel sets the OFF bit (bit 7) in the PMIC STATUS register (offset
0xA) in order to make sure it shuts down all output voltages (including the
RTC 1.8V supply from LDO2) when the system executes a power-down.
Hey Fred,
Here are some answers to your questions:
1. I have attached a LiPo battery from a Pentax camera that has a built-in
10K thermistor and I put a 75k resistor across the T signal and ground on
the pocketbeagle. I also added a 10 uF electrolytic cap between Vbatt and
ground on the
Thanks for those helpful pointers, Jason. I will dig in.
It definitely stops charging for me and as you see in the response to Fred,
I definitely see it charging while the system is booted. Could some other
piece of code tell the driver to disable charging on the way down?
--
For more
I've configured my pocketbeagle with a 3.7v Li-ION battery and it works
fine. It also charges when I power the pocketbeage via the USB connector
(and switches seamlessly as USB power comes and goes) . However it won't
charge the battery when the computer shuts down. I suspect something
16 matches
Mail list logo
