[beagleboard] Re: Problems reading PRU data RAM from host side on beaglebone black

[Daniel Kulp]

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 memory blocks are available to the pru assembly code.   

You basically need to get the "ResourceTable.asm" included, set the "main" 
section text segment, and then pass the right flags to clpru.  The results 
"out" can then be loaded via rproc.

Dan


On Monday, July 20, 2020 at 4:58:13 PM UTC-4 hans...@gmail.com wrote:

>
> Another option I am trying is to have the PRUs write data to DRAM memory 
> directly.  I really want to do this in assembly because my PRU code has 
> some tight timing.  I couldn't find any examples online to do this with the 
> rproc driver however. Any ideas?
>

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/75b11b9a-85e8-4b4d-a13a-e8004bff78ccn%40googlegroups.com.

Re: [beagleboard] Re: BBW not booting when serial to USB cable connected

[jonnymo]

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=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 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.
>
>
> On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:
>
>> On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in
>> gmane.comp.hardware.beagleboard.user Rishabh
>>  wrote:
>>
>> >I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows
>> >10. I am trying to use a PL2303HXA serial to USB cable to get the serial
>> >output to my terminal in Ubuntu. I am doing this to view U-Boot.
>> >
>>
>> Wonder if Win10 may be getting in the way... The driver for the
>> HXA is
>> no longer supported in Win10.
>> http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225=41
>> """
>>  NOTE:
>>
>> Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL
>> chip
>> versions.
>> """
>>
>> I don't know how VirtualBox handles USB devices -- if they pass
>> through
>> to the guest OS as raw devices, or if VBox is intercepting the guest I/O
>> and mapping through the host OS...
>>
>> https://www.google.com/search?q=PL2303HXA+=PL2303HXA
>>
>>
>> --
>> Dennis L Bieber
>>
>>
> --
> 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 stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/590f7b0d-7cfb-4e0f-99e6-0efe7deb3c4fo%40googlegroups.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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAG99bkr%2BfOS8VF3p8t9%2BCehD75uRAkQjjE_omfe%3D%3DtWLshBCWg%40mail.gmail.com.

[beagleboard] Re: printf support when you program PRUs in beagle board AI

[Mark A. Yoder]

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:

> Hi
>
> I am just trying to print some values to check if the condition meets the 
> requirement in beagle bone AI board. But it is not happening when I program 
> PRUs.
>
> Do I have to configure UART in PRU to achieve this capability?
>
> please help me crack this, help would be appreciated,
>
> thank you'
> sreekanth m.
>

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3f00cc45-b545-44c4-9851-c0564855b018n%40googlegroups.com.

[beagleboard] I had duplicated beagle AI and LED is not on.

[kisub Jung]

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 Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5dd76594-0725-4658-b19d-3f1883fc7299o%40googlegroups.com.

[beagleboard] Re: BBW not booting when serial to USB cable connected

[rishabh . gupta777]

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.


On Monday, July 20, 2020 at 2:51:55 AM UTC+2, Dennis Bieber wrote:

> On Sun, 19 Jul 2020 12:15:09 -0700 (PDT), in 
> gmane.comp.hardware.beagleboard.user Rishabh 
> > 
> wrote: 
>
> >I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
> >10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
> >output to my terminal in Ubuntu. I am doing this to view U-Boot. 
> > 
>
> Wonder if Win10 may be getting in the way... The driver for the 
> HXA is 
> no longer supported in Win10. 
> http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225=41 
> """ 
>  NOTE: 
>
> Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip 
> versions. 
> """ 
>
> I don't know how VirtualBox handles USB devices -- if they pass 
> through 
> to the guest OS as raw devices, or if VBox is intercepting the guest I/O 
> and mapping through the host OS... 
>
> https://www.google.com/search?q=PL2303HXA+=PL2303HXA 
>
>
> -- 
> Dennis L Bieber 
>
>

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/590f7b0d-7cfb-4e0f-99e6-0efe7deb3c4fo%40googlegroups.com.

[beagleboard] Debug console on different UART

[p.lafond75 via BeagleBoard]

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 message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5a2bb32b-e55c-4da9-87f0-ccfdc6608752o%40googlegroups.com.

Re: [beagleboard] BBW not booting when serial to USB cable connected

[rishabh . gupta777]

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 at 5:21:20 AM UTC+2, lazarman wrote:

> Did you  try this using a Windows serial terminal as well?
> Your fatal error is in linux terminal in virtual machine
> Let us know if there  is a difference and use a powered hub or power 
> supply  as was suggested 
>
> Sent from Yahoo Mail on Android 
> 
>
> On Sun, Jul 19, 2020 at 2:54 PM, Rishabh
> > wrote:
> Hi,
>
> I am running Ubuntu 18.04 inside a VM using VirtualBox hosted on Windows 
> 10. I am trying to use a PL2303HXA serial to USB cable to get the serial 
> output to my terminal in Ubuntu. I am doing this to view U-Boot.
>
> Whenever the serial to USB is connected, the board doesn't boot up.  
>
> When the serial to USB cable is connected and I run 
>
> picocom -b 115200 /dev/ttyUSB0 
>
> the terminal waits for data on the port. As soon as I try to power up the 
> board with the micro-USB cable, I get a fatal error and the serial port 
> connection gets lost.
>
> picocom v2.2
>
> port is: /dev/ttyUSB0
> flowcontrol: none
> baudrate is: 115200
> parity is  : none
> databits are   : 8
> stopbits are   : 1
> escape is  : C-a
> local echo is  : no
> noinit is  : no
> noreset is : no
> nolock is  : no
> send_cmd is: sz -vv
> receive_cmd is : rz -vv -E
> imap is: 
> omap is: 
> emap is: crcrlf,delbs,
>
> Type [C-a] [C-h] to see available commands
>
> Terminal ready
>
> FATAL: term closed
>
>
> The board boots up only when the serial to USB cable is disconnected from 
> the PC.
>
> I tried to connect the serial to USB after powering up the board and that 
> powers off the board. I am not sure why but the two connections (serial to 
> USB and micro-USB power cable) seem to be mutually exclusive. I would 
> appreciate any suggestions on how to resolve this issue.
>
> Thanks,
> Rishabh
>
> -- 
> 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 stop receiving emails from it, send an 
> email to beagl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/cbdb43e6-b279-4aa2-aa38-d1a02468e574o%40googlegroups.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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7315c84d-af64-4941-8758-cf64d9b1aa65o%40googlegroups.com.

[beagleboard] Re: printf support when you program PRUs in beagle board AI

[sreekanth m]

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...@public.gmane.org  wrote: 
>
> >Hi 
> > 
> >I am just trying to print some values to check if the condition meets the 
> >requirement in beagle bone AI board. But it is not happening when I 
> program 
> >PRUs. 
> > 
>
> I'm actually surprised you don't get some link error if you are 
> using 
> printf() in a (C/C++) PRU program. The PRUs are not using an OS, so there 
> wouldn't be anything like STDOUT for a program running in a PRU. 
>
> >Do I have to configure UART in PRU to achieve this capability? 
>
> BB Black example at 
>
> http://exploringbeaglebone.com/chapter15/#High-Speed_Analog_to_Digital_Conversion_ADC_using_the_PRU-ICSS
>  
> appears to have the PRU write the data to shared RAM, and a program 
> running 
> in Linux reading the values for output. (NOTE: reference to "chapter 13" 
> applies to the first edition of the book -- it is chapter 15 in the 2nd) 
> (NOTE: Examples also seem to be using PRUSS driver, and not the newer 
> RemoteProc 
>
>
>
> https://processors.wiki.ti.com/index.php/PRU_Debugging#Place_.22printf.22_statements
>  
> Note that this also does not use printf() IN the PRU code, but rather in 
> whatever program was used to load/start the PRU, and it interfaces, again, 
> by monitoring shared memory into which the PRU has written. 
>
>
> -- 
> Dennis L Bieber 
>
>

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ccd0dab1-689b-48ba-a52a-051e253e9ca7o%40googlegroups.com.

[beagleboard] Re: BeagleBone Black Industrial?

[Jason Kridner]

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/12342853

https://www.mouser.com/ProductDetail/BeagleBoard-by-Seeed-Studio/102110423?qs=%2Fha2pyFaduhdfTYrXET7yAX9nICxVolfDXzHZgZ5%252BZBlGTrwuflCKNvMgxfxnagBnu435K2FoyA%3D

https://www.newark.com/element14/bbone-black-ind-4g/silicon-manufacturer-texas-instruments/dp/76Y2810?ost=beaglebone+black+industrial


Stock should arrive soon.

On Mon, Jul 20, 2020 at 9:57 AM someone wrote:

> Hi Jason,
>
> I’m trying to source the BeagleBone Black Industrial board (with increased
> temperature ratings) and I’m having trouble finding it.  Is this board
> still in production?  Any insights would be much appreciated.
>
> Thanks!
>
>
> --
https://beagleboard.org/about/jkridner - a 501c3 non-profit educating
around open hardware computing

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPkMpx%2BF%2BkLagrhDwoeMHGEMmQ4cAw2_u3veZ_Kz%2B3SZHw%40mail.gmail.com.

[beagleboard] Re: BBAI and HW MCSPI3 ch 0 (linux spidev 2.0) custom usage in Linux

[jisu . au]

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 dmesg:
> [ 1.189920] omap2_mcspi 480b8000.spi: chipselect 0 already in use
> [ 1.196085] spi_master spi2: spi_device register error 
> /ocp/spi@480b8000/channel@0
> [ 1.203721] spi_master spi2: Failed to create SPI device for 
> /ocp/spi@480b8000/channel@0
>
> So, channel 0 seems to be conflicting with some other driver or usage.
>
> I finally figured out that the "am5729-beagleboneai.dts" file has a 
> reference to mcspi3:
>  {
> status = "okay";
> ti,pindir-d0-out-d1-in;
>
> sn65hvs882: sn65hvs882@0 {
> compatible = "pisosr-gpio";
> gpio-controller;
> #gpio-cells = <2>;
>
> reg = <0>;
> spi-max-frequency = <100>;
> spi-cpol;
> };
> };
>
> My question is can I disable/override this usage?
>
> I don't know the system purpose of the "pisosr-gpio"/sn65hvs882 device and 
> what the effect will be if Linux access is disabled. Since I'll have a 
> custom device on linux spidev2.0, I don't want some other part of the 
> system trying to access that SPI bus/channel and causing problems with my 
> device.
>
> Thanks for any insights.
>
> Raul
>
>
>

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/91e97b66-5f2d-47ac-971b-41ff8c5e6bafo%40googlegroups.com.

[beagleboard] [BeagleBoneAI]i use spidev1.0 or spidev1.0, but application can not communicate to spi slave for BeagleBoneAI

[jisu . au]

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 with the slave?

Of course, /dev/spidev1.0 and /dev/spi1.1 were created normally by 
configuring the devicetree.

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5f28c5ae-d090-4208-871e-fb802088784ao%40googlegroups.com.

[beagleboard] Re: July 2020 GPIO Best Practices

[TJF]

Hi Dave!

Am Montag, 20. Juli 2020 15:30:56 UTC+2 schrieb dave m.:
>
> Is there a FAQ or compendium of current best practices?
>
 
There has been good documentations for Kernel 3.8. But the kernel changed 
and the docs got out of date.

 What about PRU -- I found some stuff about libpruio that looked promising, 
> but it seems to be out of date?  Is libgpiod preferable, if I don't need 
> the extra speed PRU appears to provide?
>

libpruio is not out of date. It builds and runs on each kernel since 3.8. 
And so does the users code compiled against libpruio.

The current BB repos don't contain the libpruio packages. They never 
contained libpruio packages (exept the LKM). So if you don't want to build 
from source, ask RCN or Jason Kridner. (Or switch back to Jessie for a 
comfortable binary installation by the package manager.)

libpruio provides extra execution speed. But the main advantage is the 
steep learning curve. It does all kind of pin-muxing. And if a pin is 
claimed by an other process it shows the process name in the error message. 
And if the user cannot (or temprary will not) resolve the conflict, 
libpruio can override the claim (admin privilegues).

Hardware configuration gets as easy as on the Arduino, but with the power 
of a full featured LINUX system.

Regards

-- 
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 stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7eed834a-fe44-4bc3-bb11-b7914d378cb2o%40googlegroups.com.