For the pure asm part of this
You can look at the FPP PRU code:
https://github.com/FalconChristmas/fpp/tree/master/src/pru
and the sh scripts in there used to compile the asm.The FPP PRU code is
all hand tuned assembly and does NOT use the C runtime/stack at all. Thus,
the entire me
That error you are seeing appears to come from your USB to Serial interface.
Note:
http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
Jon
On Tue, Jul 21, 2020 at 6:48 AM wrote:
> I got to know that the driver is no longer supported when I first
> connected the cable. The driver sti
The PRU Cookbook[1] has an example of using the UART and printf on the
PRU[2]. Maybe it will help.
--Mark
[1] https://github.com/MarkAYoder/PRUCookbook
[2] https://markayoder.github.io/PRUCookbook/04debug/debug.html#_uart
On Monday, July 20, 2020 at 12:15:42 PM UTC-4 sreeko...@gmail.com wrote:
What to look into it?
PGOOD signal is low and it seems to be PMIC programming issue.
I had re-used SSD card from original working board.
What to do look into? where?
BR
kisub
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
I got to know that the driver is no longer supported when I first connected
the cable. The driver still seems to work though.
[image: PL2303HXA-driver-properties.png]
Also, I added filters in the VM's settings and that is how picocom was able
to connect to /dev/ttyUSB0.
Hi everyone,
I was just wondering if it was possible to get a debug serial console on an
UART different than UART0
I'm working on a BBB Wireless, kernel version 4.14.71-ti-r80
Thanks in advance,
Patricia
--
For more options, visit http://beagleboard.org/discuss
---
You received this mess
I did try using MobaXterm on Windows to connect to the serial port. That
didn't work.
I got the below error:
[image: MobaXterm-serial-error.png]
I am indeed plugging both cables to my PC. Sadly, I do not have a USB hub
or a power supply for the BBW.
On Monday, July 20, 2020 a
Hi Dennis,
Thanks for the reply. I forgot to mention that I get linker erros if i use
printf() statements.
On Monday, 20 July 2020 14:53:10 UTC-4, Dennis Bieber wrote:
>
> On Mon, 20 Jul 2020 09:03:34 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user
> sreekodakkad-re5jqeeqqe8avxtiumw...@
Very much in production, but we changed manufacturers from Embest to Seeed.
Distributors are transitioning stock.
btw, I put the support/community list in copy on my response and removed
your name.
https://www.digikey.com/product-detail/en/beagleboard-by-seeed-studio/102110423/1597-102110423-ND/
2020년 7월 20일 월요일 오전 4시 10분 40초 UTC+9, Raul Rathmann 님의 말:
>
>
> Hi,
>
> I've got a custom board where I need/want to use the MCSPI3 CS0, CS2 and
> CS3 hw lines for SPI.
>
> When I configure and enable mcspi3 in a custom DTS for the Linux image,
> with I get the following message viewable with
I am creating an application using /dev/spidev1.0 /dev/spidev1.1.
However, the signals such as spi clcok, MISO, MOSI, and SPI_CS are not
high/low, regardless of what is used.
For the BeagleBone AI
P9.28 -SPI3_SS1
P9.29 -SPI3_MISO
P9.30 SPI3_MOSI
P9.31 SPI3_SCK
Why can't I do SPI communication wi
11 matches
Mail list logo