Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[Lucas SOLDA]

The setup I use should be correct since this is the one provided by QNX 
directly (MLO first, u-boot and image). Moreover, if my setup was 
incorrect, the prebuilt image could not work.

Yes i rebuilt all by following this 
https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/Bsp_650InstallationNotes
 but 
that does not work
Why does it say that I use QNX 6.5.0 (2010) whereas I compile with QNX 
6.5.0 SP1 (2012) ? I don't understand, we have been working on this for 3 
weeks

Le lundi 1 mars 2021 à 19:07:16 UTC+1, robert.sty...@gmail.com a écrit :

> I assumed you did rebuild all <
> https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/Bsp_650InstallationNotes
> >
>
> On Monday, 1 March 2021 at 17:02:25 UTC lazarman wrote:
>
>> I remember sd  card setup was important on Beagle board. your probably 
>> following old or incorrect instructions. What was on this board could be 
>> important. What instructions as well.
>> They used to have a forum before Blackberry bought them.
>>
>>
>> Sent from Yahoo Mail on Android 
>> 
>>
>> On Mon, Mar 1, 2021 at 10:52 AM, robert.sty...@gmail.com
>>  wrote:
>>
>> I vaguely remember the SP install being two manual steps, one being 
>> copying files from one place to another
>>
>> On Monday, 1 March 2021 at 16:02:15 UTC lucas...@gmail.com wrote:
>>
>> Hello,
>>
>> I would like to use QNX on my BeagleBone Black. I have downloaded the QNX 
>> Neutrino 6.5.0 SP1 BSP here:
>>
>>
>> https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone
>>
>> When I load the prebuilt image, it starts perfectly but when I try to 
>> build the BSP by myself, I have this : 
>>
>> *Jumping to QNX*
>>
>> *System page at phys:80011000 user:fc404000 kern:fc404000*
>> *Starting next program at vfe046604*
>> *cpu_startnext: cpu0 -> fe046604*
>> *VFPv3: fpsid=410330c3*
>> *coproc_attach(10): replacing fe07601c with fe0758bc*
>> *coproc_attach(11): replacing fe07601c with fe0758bc*
>> *Welcome to QNX Neutrino 6.5.0 SP1 on the Texas Instruments BeagleBone 
>> (ARMv7 Cortex-A8 core) - Board*
>>
>> *Shutdown[0,0] S/C/F=11/1/11 C/D=fe01c68c/fe099ff4 state(c0)= now lock*
>> *QNX Version 6.5.0 Release 2010/07/09-14:26:46EDT*
>> *[0]PID-TID=1-6? P/T FL=00019001/0502 "proc/boot/procnto-instr"*
>> *[0]ASPACE PID=2 PF=8012*
>> *armle context[effe8f4c]:*
>> *: 8ffb2000 8ffb2000 8ffb2c01 0181 effccbf8 0100  
>> fc004000*
>> *0020: fc004000 effdf47c 01072fff 0008  effe8f90 fe046878 
>> fe040e0c*
>> *0040: 6013*
>> *instruction[fe040e0c]:*
>> *06 30 98 e7 1c 20 94 e5 11 00 12 e3 00 70 94 15 18 20 9d 15 07 70 82 11 
>> 0c 00*
>> *stack[effe8f90]:*
>> *: effe8fbc e18a1000  efffb348 effca00c 003f 0a6e 
>> e1988160*
>> *0020: 8ffb2000 f000  0007 0040 effccbf8 fe099ff0 
>> 0100*
>> *0040: 00ff efff0090 0073 008d effca6e8 fe044744 effccbf8 
>> fe044ad0*
>> *0060: efffb348 fe069bac efffb348 fe071e30 effe9018   
>> ÿ*
>>
>>
>> As we can see, I have this message : *QNX Version 6.5.0 Release 
>> 2010/07/09-14:26:46EDT*
>> This means that I try to compile with QNX 6.5.0 and not QNX 6.5.0 SP1. I 
>> don't understand why i have this message because I have well installed QNX 
>> 6.5.0 SP1 :
>> [image: 1.png]
>>
>> [image: 2.jpg]
>> Do I miss something ? Do I have to activate someting somewhere ?
>>
>> Thank you for your help.
>>
>> -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>>
>> https://groups.google.com/d/msgid/beagleboard/84dc332e-7fc5-4b20-bf82-05224d394938n%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/a377588f-8ad6-44b8-a4c1-9c81f4c2eaf9n%40googlegroups.com.

RE: [beagleboard] POCKETBEAGLE: UART Help - Garbage data along with requisite data

[Graham Stott]

Which Pins are you using for UART4 rcv and have you set the PIN mux correctly 
for that PIN?

 

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Piyush Raj ae19m009
Sent: Monday, March 01, 2021 6:30 PM
To: BeagleBoard 
Subject: [beagleboard] POCKETBEAGLE: UART Help - Garbage data along with 
requisite data

 

I am implementing UART using Pocketbeagle wherein i am trying to send simple 
strings over UART . I have written a code for loopback testing of UART-4 in PB. 
for a logic Low on P2.1  i am sending String "LOW" and "HIGH" for vice versa. 
However i am getting garbage data along with the requisite strings. sometimes 
all the received data is missing or broken. I tried to work at various baud 
rates (600, 9600,115200) but of no help.

Am i doing any basic mistake. need guidance from community. (I worked with AVR 
and Arduino UART in the past and never faced such problem)

 

Further, i also tried to dump the received data in a text file( to rule out 
possibility of terminal baud rate mismatch), but results did not change.

 

My code is below:

 

 

#include

#include

#include 

#include 

#include 

#include //for usleep

#include"GPIO.h"

using namespace exploringBB;

using namespace std;

 

int main()

{

GPIO  outLogicSupply(60); outLogicSupply.setDirection(OUTPUT);  

GPIO  inLogicSupply(59); inLogicSupply.setDirection(INPUT);

 

int file,count;

char transmit[6];

char receive[10];

  int bytes_written,read_code;int count1=1;

 OPENING UART4 ON POCKETBEAGLE /

printf("UART: Transmission Started.\n");

if ((file = open("/dev/ttyO4", O_RDWR | O_NOCTTY | O_NDELAY))<0)

{

  perror("UART: Failed to open the device.\n");

  return -1;

}

else

{

printf("UART: Opened file successfully\n");

}

/

 

   ///SETTING UP UART OPTIONS  ///

  struct termios options;

   tcgetattr(file, );

   options.c_cflag = B9600 | CS8 | CREAD | CLOCAL;

   options.c_iflag = IGNPAR | ICRNL;

   tcflush(file, TCIFLUSH);

   fcntl(STDIN_FILENO, F_SETFL, O_NONBLOCK);  // make reads non-blocking

   tcsetattr(file, TCSANOW, );

  

   cout << "The value of the input is: "<< inLogicSupply.getValue() << endl;

 

 

   while(1)

{

  

if(inLogicSupply.getValue()==1)

   

{

strcpy(transmit,"HIGH\n");

 outLogicSupply.setValue(HIGH);



}

else



{

strcpy(transmit,"LOW\n");

 outLogicSupply.setValue(LOW);

}



bytes_written = write(file, ,6);

sleep(1);

read_code= read(file,receive,10);

if(bytes_written>0  && read_code>0  ) 

{

receiveFile .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/99530b73-a474-410b-8583-4d0327d32d35n%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/000201d70f2a%24edd15100%24c973f300%24%40comcast.net.

Re: [beagleboard] Re: GPIO, libpruio & dtbo Question

[set_]

Hello,

Are you using BBB_IO or Adafruit_BBIO? 

Either way, here is a start w/ Adafruit_BBIO:

*import serial *
*import Adafruit_BBIO.UART as UART *
*from time import sleep*
 

*UART.setup("UART2") *
*ser=serial.Serial("/dev/ttyS2", 9600) *

*class GPS: *
*def __init__(self)*

and then...

If you want to add a button, just use a GPIO from Adafruit_BBIO again. So, 
that example will look like this:

*import Adafruit_BBIO.GPIO as GPIO*
*from time import sleep*

*pinOne = 'P8_11'*
*GPIO.setup(pinOne, GPIO.IN)*

*while True:*
*if GPIO.input(pinOne):*
*print("The Button Shall get pressed Again or whatever...")*
*sleep(2)*

That is a simplistic approach. I got that source from an older book: 
"Getting Started with BeagleBone (Richardson 2013)."

There are some neat examples in that book but nothing too complicated. It 
would be a refresher to see what was then and what has changed.

Anyway, I hope that works for you. That button function should just work. 
You can always do better and make it on an edge. Falling, Rising, or Both 
w/ that same lib.

Seth



On Monday, March 1, 2021 at 7:14:01 PM UTC-6 set_ wrote:

> Hello,
>
> I am receiving errors w/ the .dtbo only. I am too far from outside to 
> communicate w/ my GPS and I am receiving no feedback w/ pyserial on my BBG 
> (BeagleBone Green). I tried installing a serial lib. w/ sudo apt install 
> python3-serial, also.
>
> I just downloaded/installed the docs in .epub/html format on my hard 
> drive. I am thinking it may or may not be Adafruit_BBIO. I am also thinking 
> that it may be or may not be pyserial. The intallation w/ apt was faulty 
> from the get-go.
>
> I can use config-pin p9.21 uart && config-pin p9.22 uart and have that 
> command turn successful.
>
> ...
>
> It may be a faulty effort in an update from pyserial but I am not sure 
> yet. If this means anything, please let me know:
>
> ^CTraceback (most recent call last):
>   File "./FirstGPS.py", line 87, in 
> myGPS.read()
>   File "./FirstGPS.py", line 47, in read
> while ser.inWaiting() == 0:
>   File 
> "/home/debian/.local/lib/python3.7/site-packages/serial/serialutil.py", 
> line 593, in inWaiting
> def inWaiting(self):
> KeyboardInterrupt
>
> The above error is only when I make no call to config-pin w/out a .dtbo 
> loaded. Also, pyserial is listed...
>
> Now...this source below is after making a config-pin call to P9.21/22 and 
> trying to exit my program:
>
> ^CTraceback (most recent call last):
>   File "./FirstGPS.py", line 87, in 
> myGPS.read()
>   File "./FirstGPS.py", line 47, in read
> while ser.inWaiting() == 0:
>   File 
> "/home/debian/.local/lib/python3.7/site-packages/serial/serialutil.py", 
> line 594, in inWaiting
> return self.in_waiting
>   File 
> "/home/debian/.local/lib/python3.7/site-packages/serial/serialposix.py", 
> line 549, in in_waiting
> s = fcntl.ioctl(self.fd, TIOCINQ, TIOCM_zero_str)
> KeyboardInterrupt
>
> Both...are screaming to me about pyserial and those specific locations. I 
> add print statements and receive nothing back. So, I think my source, which 
> is an update from Python2 (from utf-8 to bytes) to Python3, is faulty.
>
> I can show you in case you are wondering. I am just updating some source I 
> found a while back.
>
> Seth
>
>
> On Monday, March 1, 2021 at 6:47:56 PM UTC-6 donp...@gmail.com wrote:
>
>> You prompted me to recheck how I'm accessing the two peripherals I did 
>> get to install, the UART and the I2C. I'm only sending messages out over 
>> the UART using pyserial, although I do also use minicom to bi-directionally 
>> communicate with the board under test from the BBB Ubuntu command line. For 
>> the I2C I'm using the Adafruit char LCD library, which relies on busio from 
>> Circuit Python. Still an Adafruit product, but not technically the BBB_IO 
>> library, I guess.
>>
>> If anyone can give tips on how to do a button-based interrupt (abort) 
>> without BBB_IO, I'm all ears. I guess I could just start programming the 
>> BBB in C. I already program embedded microcontrollers in that language, so 
>> why not SBC?
>>
>>
>> --
>> Don Pancoe, P.E.
>> Industrial Designer, Electrical Engineer
>> DonPancoe.com 
>>
>> On Mon, Mar 1, 2021 at 4:27 PM set_  wrote:
>>
>>> Hello,
>>>
>>> I literally am havin' the same issue as you right now w/ a GPS module 
>>> working w/ BB-UART2-00A0.dtbo and a grove connector. This is my error:
>>>
>>> *py_setup_uart(UART2): set_pin_mode() failed for pin=P9_22Traceback 
>>> (most recent call last):*
>>> *  File "FirstGPS.py", line 5, in *
>>> *UART.setup("UART2")*
>>> *ValueError: Set pin mode failed for uart channel.*
>>>
>>> I think things are changing at some point in some way at some level. 
>>> Vague...yes. I can set up my source w/out the .dtbo and use config-pin to 
>>> set my uart2 pins to have my source 'work.'
>>>
>>> Anyway, I will be following 

[beagleboard] POCKETBEAGLE: UART Help - Garbage data along with requisite data

[Piyush Raj ae19m009]

I am implementing UART using Pocketbeagle wherein i am trying to send 
simple strings over UART . I have written a code for loopback testing of 
UART-4 in PB. for a logic Low on P2.1  i am sending String "LOW" and "HIGH" 
for vice versa. However i am getting garbage data along with the requisite 
strings. sometimes all the received data is missing or broken. I tried to 
work at various baud rates (600, 9600,115200) but of no help.
Am i doing any basic mistake. need guidance from community. (I worked with 
AVR and Arduino UART in the past and never faced such problem)

Further, i also tried to dump the received data in a text file( to rule out 
possibility of terminal baud rate mismatch), but results did not change.

My code is below:


#include
#include
#include 
#include 
#include 
#include //for usleep
#include"GPIO.h"
using namespace exploringBB;
using namespace std;

int main()
{
GPIO  outLogicSupply(60); outLogicSupply.setDirection(OUTPUT);  
GPIO  inLogicSupply(59); inLogicSupply.setDirection(INPUT);

int file,count;
char transmit[6];
char receive[10];
  int bytes_written,read_code;int count1=1;
 OPENING UART4 ON POCKETBEAGLE /
printf("UART: Transmission Started.\n");
if ((file = open("/dev/ttyO4", O_RDWR | O_NOCTTY | O_NDELAY))<0)
{
  perror("UART: Failed to open the device.\n");
  return -1;
}
else
{
printf("UART: Opened file successfully\n");
}
/

   ///SETTING UP UART OPTIONS  ///
  struct termios options;
   tcgetattr(file, );
   options.c_cflag = B9600 | CS8 | CREAD | CLOCAL;
   options.c_iflag = IGNPAR | ICRNL;
   tcflush(file, TCIFLUSH);
   fcntl(STDIN_FILENO, F_SETFL, O_NONBLOCK);  // make reads non-blocking
   tcsetattr(file, TCSANOW, );
  
   cout << "The value of the input is: "<< inLogicSupply.getValue() << endl;
 

   while(1)
{
  
if(inLogicSupply.getValue()==1)
   
{
strcpy(transmit,"HIGH\n");
 outLogicSupply.setValue(HIGH);

}
else

{
strcpy(transmit,"LOW\n");
 outLogicSupply.setValue(LOW);
}

bytes_written = write(file, ,6);
sleep(1);
read_code= read(file,receive,10);
if(bytes_written>0  && read_code>0  ) 
{
receiveFile

Re: [beagleboard] Re: GPIO, libpruio & dtbo Question

[set_]

Hello,

I am receiving errors w/ the .dtbo only. I am too far from outside to 
communicate w/ my GPS and I am receiving no feedback w/ pyserial on my BBG 
(BeagleBone Green). I tried installing a serial lib. w/ sudo apt install 
python3-serial, also.

I just downloaded/installed the docs in .epub/html format on my hard drive. 
I am thinking it may or may not be Adafruit_BBIO. I am also thinking that 
it may be or may not be pyserial. The intallation w/ apt was faulty from 
the get-go.

I can use config-pin p9.21 uart && config-pin p9.22 uart and have that 
command turn successful.

...

It may be a faulty effort in an update from pyserial but I am not sure yet. 
If this means anything, please let me know:

^CTraceback (most recent call last):
  File "./FirstGPS.py", line 87, in 
myGPS.read()
  File "./FirstGPS.py", line 47, in read
while ser.inWaiting() == 0:
  File 
"/home/debian/.local/lib/python3.7/site-packages/serial/serialutil.py", 
line 593, in inWaiting
def inWaiting(self):
KeyboardInterrupt

The above error is only when I make no call to config-pin w/out a .dtbo 
loaded. Also, pyserial is listed...

Now...this source below is after making a config-pin call to P9.21/22 and 
trying to exit my program:

^CTraceback (most recent call last):
  File "./FirstGPS.py", line 87, in 
myGPS.read()
  File "./FirstGPS.py", line 47, in read
while ser.inWaiting() == 0:
  File 
"/home/debian/.local/lib/python3.7/site-packages/serial/serialutil.py", 
line 594, in inWaiting
return self.in_waiting
  File 
"/home/debian/.local/lib/python3.7/site-packages/serial/serialposix.py", 
line 549, in in_waiting
s = fcntl.ioctl(self.fd, TIOCINQ, TIOCM_zero_str)
KeyboardInterrupt

Both...are screaming to me about pyserial and those specific locations. I 
add print statements and receive nothing back. So, I think my source, which 
is an update from Python2 (from utf-8 to bytes) to Python3, is faulty.

I can show you in case you are wondering. I am just updating some source I 
found a while back.

Seth


On Monday, March 1, 2021 at 6:47:56 PM UTC-6 donp...@gmail.com wrote:

> You prompted me to recheck how I'm accessing the two peripherals I did get 
> to install, the UART and the I2C. I'm only sending messages out over the 
> UART using pyserial, although I do also use minicom to bi-directionally 
> communicate with the board under test from the BBB Ubuntu command line. For 
> the I2C I'm using the Adafruit char LCD library, which relies on busio from 
> Circuit Python. Still an Adafruit product, but not technically the BBB_IO 
> library, I guess.
>
> If anyone can give tips on how to do a button-based interrupt (abort) 
> without BBB_IO, I'm all ears. I guess I could just start programming the 
> BBB in C. I already program embedded microcontrollers in that language, so 
> why not SBC?
>
>
> --
> Don Pancoe, P.E.
> Industrial Designer, Electrical Engineer
> DonPancoe.com 
>
> On Mon, Mar 1, 2021 at 4:27 PM set_  wrote:
>
>> Hello,
>>
>> I literally am havin' the same issue as you right now w/ a GPS module 
>> working w/ BB-UART2-00A0.dtbo and a grove connector. This is my error:
>>
>> *py_setup_uart(UART2): set_pin_mode() failed for pin=P9_22Traceback (most 
>> recent call last):*
>> *  File "FirstGPS.py", line 5, in *
>> *UART.setup("UART2")*
>> *ValueError: Set pin mode failed for uart channel.*
>>
>> I think things are changing at some point in some way at some level. 
>> Vague...yes. I can set up my source w/out the .dtbo and use config-pin to 
>> set my uart2 pins to have my source 'work.'
>>
>> Anyway, I will be following along to see how far you get b/c right now, I 
>> am a  little stumped as to why what has worked no longer is viable.
>>
>> Seth
>>
>> On Monday, March 1, 2021 at 12:27:01 PM UTC-6 donp...@gmail.com wrote:
>>
>>> Hello all,
>>>
>>> I have a BBB Python application (PCBA test fixture) where I am using 
>>> libpruio, specifically for access to the eCAP pins. Libpruio requires that 
>>> the universal cape be disabled, but when I needed a UART and I2C, I was 
>>> able to add those back in using the existing dtbo files from /lib/firmware 
>>> (shown below) in my uEnv.txt.
>>>
>>> uboot_overlay_addr0=/lib/firmware/BB-I2C1-00A0.dtbo
>>> uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
>>> uboot_overlay_addr2=/lib/firmware/DP-GPIO-PCBATest-00A0.dtbo (I talk 
>>> about this below)
>>>
>>>
>>> Now I want to add an "abort" button to the test fixture since the 
>>> technicians have reported it takes a lot of time to reset if the board 
>>> under test locks up. I expect that wiring a pushbutton to a GPIO with an 
>>> interrupt is the way to handle this, and I've been thinking that there are 
>>> two ways to get there.
>>>
>>>1. Include another dtbo file to add a single GPIO that I can then 
>>>access with Adafruit_BBIO (this is where my efforts have focused so 
>>> far), or
>>> 

Re: [beagleboard] Re: PRU RemoteProc documentation

['Mark Lazarewicz' via BeagleBoard]

Hello Fischer 

This file looks like it's processing the resource table 
https://docs.huihoo.com/doxygen/linux/kernel/3.7/remoteproc__core_8c_source.html




* 804  * take a firmware and boot a remote processor with it. 805  */ 806 
static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw) 807 {


I'm no kernel internals guy but I'm pretty sure dev_info below in a working 
load gets displayed look at the output in Linux to DSP IPC SDK documents. Have 
you seen it? It's helped me if you have not let me know it also discussed M3 I 
know you are doing OUR

817  dev_info(dev, "Booting fw image %s, size %zd\n", name, fw->size);
Perhaps what you need is to recompile kernel with debug level for appropriate 
driver verbose mode.I'm sure it's possible but I'm not the right guy maybe it's 
a defconfigoption.

You'd want to make sure dev_dbg below spits out useful info is my guess 
If unable to actually talk to somebody who writes code like this us mere 
mortals are left to study the source code.
I been there I feel your pain. Have you located the file Din pointed to and the 
corresponding c files ???
701  /* make sure table isn't truncated */ 702  if (avail < 0) { 703  
dev_err(dev, "rsc table is truncated\n"); 704  return -EINVAL; 705  } 706  707  
dev_dbg(dev, "rsc: type %d\n", hdr->type); 708  709  
I remember that IPC document also talking about disabling interrupts in an 
example as well.
And lastly I've got the sneaky feeling that this whole remoteoroc falls apart 
rather quickly when the DSP, M3 or PRU examples get complex.My interest is DSP 
I need more modern HW or I'd be in there with you deciphering what it takes to 
use complex example on the DSP only my interest is using JTAG.
That L3 message looks like the ones the kernel spits out processing the image 
but again Im not a Linux guy.
 Also that IPC DSP doc lists addresses for all the cores you should be able to 
find At Address: 0x00806664 


[ 2393.327706] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 
370028[ 2393.327762] [ cut here ][ 2393.327782] 
WARNING: CPU: 0 PID: 1810 at drivers/bus/omap_l3_noc.c:147 
l3_interrupt_handler+0x368/0x3a4[ 2393.327790] 4400.ocp:L3 Standard Error: 
MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in 
Supervisor mode during Functional access


Keep us posted I'm interested if you find more data I think we will be seeing 
many more questions about remoteproc once people start running DSP and M4 code 
especially about resource tables 
Mark 






Sent from Yahoo Mail on Android 
 
  On Sun, Feb 28, 2021 at 11:46 PM, Fisher Grubb wrote: 
  Hi all,
I solved my issue in the end of it not booting, or causing errors with 
"L3_main" in the title from remoteProc to dmesg.
The issue turned out to be both having interrupts from the IEP timer, and that 
C++ needs .init_array in the linker command file to actually initialise the 
constructors.The linker did add the .init_array section at the end of the 
binary, but I don't think actually got the code to jump to the needed addresses 
without that section specifically put into the linker file.
I assume the interrupt issue may be been due to using an empty resource_table, 
so the kernel module didn't set anything up to receive them on the Linux side, 
but then the timer sent them.I'm not fully sure about that because I believe 
I've also left them enabled, and not had dmesg errors.
I still can't find any RemoteProc documentation of the possible config options, 
or how to get extra info out of the kernel modules, such as what it's doing as 
it processes the resource_table.
Fisher

On Friday, 12 February 2021 at 02:29:00 UTC+10 din...@gmail.com wrote:

The error message is emitted from the system bus driver 
(drivers/bus/omap_l3_noc.c ). 

I interpret it as a bug in your PRU firmware. When issue occurs, please try to 
inspect the PRU state. See 
https://zeekhuge.me/post/ptp_docs_commands_and_tools/ , or use JTAG.
Regards,DimitarOn Thursday, February 11, 2021 at 7:30:58 AM UTC+2 Fisher Grubb 
wrote:

Hi Dimitar,
Thanks for your reply, yes, I don't understand that as its code to flash 
lights.  Its built with different states, which makes it more complicated, but 
only flashes LEDs.
How can I know what the kernel module is doing so I can see more details and 
know where to look?  Such as, is this happening when the firmware is being 
processed by the module, or is this the module giving the error once the code 
is trying to run on the PRU?
Thanks,Fisher
On Thursday, 11 February 2021 at 02:58:57 UTC+10 din...@gmail.com wrote:

Looks like PRU attempts to access PCIE1 address space. I suspect it's a bug in 
your PRU firmware.

MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664

TI has tutorials how to use JTAG to debug PRU. Another option is 
https://markayoder.github.io/PRUCookbook/04debug/debug.html

Regards,Dimitar

On Wednesday, February 10, 2021 at 2:27:01 PM UTC+2 Fisher Grubb wrote:

Re: [beagleboard] Re: GPIO, libpruio & dtbo Question

[Don Pancoe]

You prompted me to recheck how I'm accessing the two peripherals I did get
to install, the UART and the I2C. I'm only sending messages out over the
UART using pyserial, although I do also use minicom to bi-directionally
communicate with the board under test from the BBB Ubuntu command line. For
the I2C I'm using the Adafruit char LCD library, which relies on busio from
Circuit Python. Still an Adafruit product, but not technically the BBB_IO
library, I guess.

If anyone can give tips on how to do a button-based interrupt (abort)
without BBB_IO, I'm all ears. I guess I could just start programming the
BBB in C. I already program embedded microcontrollers in that language, so
why not SBC?

--
Don Pancoe, P.E.
Industrial Designer, Electrical Engineer
DonPancoe.com 


On Mon, Mar 1, 2021 at 4:27 PM set_  wrote:

> Hello,
>
> I literally am havin' the same issue as you right now w/ a GPS module
> working w/ BB-UART2-00A0.dtbo and a grove connector. This is my error:
>
> *py_setup_uart(UART2): set_pin_mode() failed for pin=P9_22Traceback (most
> recent call last):*
> *  File "FirstGPS.py", line 5, in *
> *UART.setup("UART2")*
> *ValueError: Set pin mode failed for uart channel.*
>
> I think things are changing at some point in some way at some level.
> Vague...yes. I can set up my source w/out the .dtbo and use config-pin to
> set my uart2 pins to have my source 'work.'
>
> Anyway, I will be following along to see how far you get b/c right now, I
> am a  little stumped as to why what has worked no longer is viable.
>
> Seth
>
> On Monday, March 1, 2021 at 12:27:01 PM UTC-6 donp...@gmail.com wrote:
>
>> Hello all,
>>
>> I have a BBB Python application (PCBA test fixture) where I am using
>> libpruio, specifically for access to the eCAP pins. Libpruio requires that
>> the universal cape be disabled, but when I needed a UART and I2C, I was
>> able to add those back in using the existing dtbo files from /lib/firmware
>> (shown below) in my uEnv.txt.
>>
>> uboot_overlay_addr0=/lib/firmware/BB-I2C1-00A0.dtbo
>> uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
>> uboot_overlay_addr2=/lib/firmware/DP-GPIO-PCBATest-00A0.dtbo (I talk
>> about this below)
>>
>>
>> Now I want to add an "abort" button to the test fixture since the
>> technicians have reported it takes a lot of time to reset if the board
>> under test locks up. I expect that wiring a pushbutton to a GPIO with an
>> interrupt is the way to handle this, and I've been thinking that there are
>> two ways to get there.
>>
>>1. Include another dtbo file to add a single GPIO that I can then
>>access with Adafruit_BBIO (this is where my efforts have focused so far), 
>> or
>>2. Figure out how to work with the hardware-based IRQ of the PRU
>>with libpruio (which I've been avoiding because it looks even more scary)
>>
>> I've tried to make a custom dtbo by following an example from Derek
>> Molloy (github.com/derekmolloy/boneDeviceTree) and while it compiled and
>> booted OK, I still get the following error when I run a simple test
>> program. The same error as when I tried running the program before I
>> created the dtbo.
>>
>> kapsul@beaglebone:~/pyDev$ sudo python3 abortTest.py
>> Traceback (most recent call last):
>>   File "abortTest.py", line 6, in 
>> GPIO.setup("P9_12", GPIO.IN)
>> ValueError: Set gpio mode failed, missing file or invalid permissions.
>>
>>
>> Further, when I do the following (with or without the dtbo), I get the
>> following...
>>
>> kapsul@beaglebone:~/pyDev$ config-pin -q p9.12
>> P9_12 pinmux file not found!
>> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P9_12_pinmux/state
>>
>>
>> Any input would be appreciated, whether it is correcting me on path 1 or
>> steering me towards path 2. I will happily provide any additional info, but
>> I didn't want to start uploading stuff until I know what, exactly, will be
>> helpful.
>>
>> Thanks,
>> --
>> Don Pancoe, P.E.
>> Industrial Designer, Electrical Engineer
>> DonPancoe.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/58e45b18-f019-49e7-92ce-95015cbc0e63n%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 

[beagleboard] Re: GPIO, libpruio & dtbo Question

[set_]

Hello,

I literally am havin' the same issue as you right now w/ a GPS module 
working w/ BB-UART2-00A0.dtbo and a grove connector. This is my error:

*py_setup_uart(UART2): set_pin_mode() failed for pin=P9_22Traceback (most 
recent call last):*
*  File "FirstGPS.py", line 5, in *
*UART.setup("UART2")*
*ValueError: Set pin mode failed for uart channel.*

I think things are changing at some point in some way at some level. 
Vague...yes. I can set up my source w/out the .dtbo and use config-pin to 
set my uart2 pins to have my source 'work.'

Anyway, I will be following along to see how far you get b/c right now, I 
am a  little stumped as to why what has worked no longer is viable.

Seth

On Monday, March 1, 2021 at 12:27:01 PM UTC-6 donp...@gmail.com wrote:

> Hello all,
>
> I have a BBB Python application (PCBA test fixture) where I am using 
> libpruio, specifically for access to the eCAP pins. Libpruio requires that 
> the universal cape be disabled, but when I needed a UART and I2C, I was 
> able to add those back in using the existing dtbo files from /lib/firmware 
> (shown below) in my uEnv.txt.
>
> uboot_overlay_addr0=/lib/firmware/BB-I2C1-00A0.dtbo
> uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
> uboot_overlay_addr2=/lib/firmware/DP-GPIO-PCBATest-00A0.dtbo (I talk 
> about this below)
>
>
> Now I want to add an "abort" button to the test fixture since the 
> technicians have reported it takes a lot of time to reset if the board 
> under test locks up. I expect that wiring a pushbutton to a GPIO with an 
> interrupt is the way to handle this, and I've been thinking that there are 
> two ways to get there.
>
>1. Include another dtbo file to add a single GPIO that I can then 
>access with Adafruit_BBIO (this is where my efforts have focused so far), 
> or
>2. Figure out how to work with the hardware-based IRQ of the PRU  with 
>libpruio (which I've been avoiding because it looks even more scary)
>
> I've tried to make a custom dtbo by following an example from Derek Molloy 
> (github.com/derekmolloy/boneDeviceTree) and while it compiled and booted 
> OK, I still get the following error when I run a simple test program. The 
> same error as when I tried running the program before I created the dtbo.
>
> kapsul@beaglebone:~/pyDev$ sudo python3 abortTest.py
> Traceback (most recent call last):
>   File "abortTest.py", line 6, in 
> GPIO.setup("P9_12", GPIO.IN)
> ValueError: Set gpio mode failed, missing file or invalid permissions.
>
>
> Further, when I do the following (with or without the dtbo), I get the 
> following...
>
> kapsul@beaglebone:~/pyDev$ config-pin -q p9.12
> P9_12 pinmux file not found!
> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P9_12_pinmux/state
>
>
> Any input would be appreciated, whether it is correcting me on path 1 or 
> steering me towards path 2. I will happily provide any additional info, but 
> I didn't want to start uploading stuff until I know what, exactly, will be 
> helpful.
>
> Thanks,
> --
> Don Pancoe, P.E.
> Industrial Designer, Electrical Engineer
> DonPancoe.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/58e45b18-f019-49e7-92ce-95015cbc0e63n%40googlegroups.com.

[beagleboard] Re: latest machinekit image isn't loading uio dtb

[set_]

Hello,

I am working, well trying still, to get that image to boot w/ Machinekit 
and EmcApplication. Have you looked in the logs /var/log/ and type dmesg or 
journalctl -xe ?

...

I am having some complication so far as I have not tried to compile the 
EmcApplication w/ QEMU yet. But...I got the MachineKit-hal to work just 
fine w/ halrun and halcmd.

Um...upgrading to a newer kernel may prove useful too. I am currently 
trying plain, ole LinuxCNC for now. 

Seth

P.S. W/ LCD Cape, I got it to work but in a server online, the LinuxCNC 
does not want to show up due to errors. Even if this does not help, please 
try to reply. I may think of other items of interest soon b/c of further 
testing.



On Friday, February 26, 2021 at 5:09:58 PM UTC-6 doog wrote:

> Using image:
>
> bone-debian-9.12-machinekit-armhf-2020-05-
> 02-4gb.img.xz
>
> while starting machinekit it just hangs in a wait loop for /sys/class/uio 
> and listing it there is nothing created.
>
> I checked uEnv.txt and it shows uncommented:
> uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
>
> Xylotex board config Xylotex4Axis.ini has this and the pru_generic..bin 
> was confirmed:
> [PRUCONF] 
> DRIVER=hal_pru_generic 
> #PRUCODE=/usr/lib/linuxcnc/rt-preempt/pru_generic.bin pru=1 
> pru_period=25000 halname=hpg num_stepgens=4 num
> _pwmgens=1 
> #PRUBIN=xenomai/pru_generic.bin 
> PRUBIN=/usr/lib/linuxcnc/rt-preempt/pru_generic.bin 
> CONFIG=pru=1 halname=hpg num_stepgens=4 num_pwmgens=1
>
>

-- 
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/766a55ce-cd4c-4723-9c25-5ba43982e335n%40googlegroups.com.

[beagleboard] Re: Compatibility of Debian and Matlab

[Dennis Lee Bieber]

On Sun, 28 Feb 2021 22:01:53 -0800 (PST), in
gmane.comp.hardware.beagleboard.user Cheng Chen
 wrote:

>Yes. Matlab is using SSH for connection. I think the problem I met is 
>exactly what you described: unable to respond to the prompt for root user 
>password. Could you elaborate on "configure the sudoers file to not require 
>a user password for sudo" a little more please? Thanks. 
>

Middle section on adding user to sudoers file -- has an example for a
use with a NOPASSWD option
https://devconnected.com/how-to-add-a-user-to-sudoers-on-debian-10-buster/

If you can configure Matlab as to the user account to use in SSH, you
may be able to create an account specific for it on the Beagle.


-- 
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/fucq3g5fn7av0vpu4hegulebp04h6cpr2b%404ax.com.

[beagleboard] GPIO, libpruio & dtbo Question

[Don Pancoe]

Hello all,

I have a BBB Python application (PCBA test fixture) where I am using
libpruio, specifically for access to the eCAP pins. Libpruio requires that
the universal cape be disabled, but when I needed a UART and I2C, I was
able to add those back in using the existing dtbo files from /lib/firmware
(shown below) in my uEnv.txt.

uboot_overlay_addr0=/lib/firmware/BB-I2C1-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
uboot_overlay_addr2=/lib/firmware/DP-GPIO-PCBATest-00A0.dtbo (I talk about
this below)


Now I want to add an "abort" button to the test fixture since the
technicians have reported it takes a lot of time to reset if the board
under test locks up. I expect that wiring a pushbutton to a GPIO with an
interrupt is the way to handle this, and I've been thinking that there are
two ways to get there.

   1. Include another dtbo file to add a single GPIO that I can then access
   with Adafruit_BBIO (this is where my efforts have focused so far), or
   2. Figure out how to work with the hardware-based IRQ of the PRU  with
   libpruio (which I've been avoiding because it looks even more scary)

I've tried to make a custom dtbo by following an example from Derek Molloy (
github.com/derekmolloy/boneDeviceTree) and while it compiled and booted OK,
I still get the following error when I run a simple test program. The same
error as when I tried running the program before I created the dtbo.

kapsul@beaglebone:~/pyDev$ sudo python3 abortTest.py
Traceback (most recent call last):
  File "abortTest.py", line 6, in 
GPIO.setup("P9_12", GPIO.IN)
ValueError: Set gpio mode failed, missing file or invalid permissions.


Further, when I do the following (with or without the dtbo), I get the
following...

kapsul@beaglebone:~/pyDev$ config-pin -q p9.12
P9_12 pinmux file not found!
Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P9_12_pinmux/state


Any input would be appreciated, whether it is correcting me on path 1 or
steering me towards path 2. I will happily provide any additional info, but
I didn't want to start uploading stuff until I know what, exactly, will be
helpful.

Thanks,
--
Don Pancoe, P.E.
Industrial Designer, Electrical Engineer
DonPancoe.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/CAP3tSUMe396gTjaGsjq9Ucy1w_3zephaq%2BCaprGYdydx-tO0AQ%40mail.gmail.com.

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[robert.sty...@gmail.com]

I assumed you did rebuild all 


On Monday, 1 March 2021 at 17:02:25 UTC lazarman wrote:

> I remember sd  card setup was important on Beagle board. your probably 
> following old or incorrect instructions. What was on this board could be 
> important. What instructions as well.
> They used to have a forum before Blackberry bought them.
>
>
> Sent from Yahoo Mail on Android 
> 
>
> On Mon, Mar 1, 2021 at 10:52 AM, robert.sty...@gmail.com
>  wrote:
>
> I vaguely remember the SP install being two manual steps, one being 
> copying files from one place to another
>
> On Monday, 1 March 2021 at 16:02:15 UTC lucas...@gmail.com wrote:
>
> Hello,
>
> I would like to use QNX on my BeagleBone Black. I have downloaded the QNX 
> Neutrino 6.5.0 SP1 BSP here:
>
>
> https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone
>
> When I load the prebuilt image, it starts perfectly but when I try to 
> build the BSP by myself, I have this : 
>
> *Jumping to QNX*
>
> *System page at phys:80011000 user:fc404000 kern:fc404000*
> *Starting next program at vfe046604*
> *cpu_startnext: cpu0 -> fe046604*
> *VFPv3: fpsid=410330c3*
> *coproc_attach(10): replacing fe07601c with fe0758bc*
> *coproc_attach(11): replacing fe07601c with fe0758bc*
> *Welcome to QNX Neutrino 6.5.0 SP1 on the Texas Instruments BeagleBone 
> (ARMv7 Cortex-A8 core) - Board*
>
> *Shutdown[0,0] S/C/F=11/1/11 C/D=fe01c68c/fe099ff4 state(c0)= now lock*
> *QNX Version 6.5.0 Release 2010/07/09-14:26:46EDT*
> *[0]PID-TID=1-6? P/T FL=00019001/0502 "proc/boot/procnto-instr"*
> *[0]ASPACE PID=2 PF=8012*
> *armle context[effe8f4c]:*
> *: 8ffb2000 8ffb2000 8ffb2c01 0181 effccbf8 0100  
> fc004000*
> *0020: fc004000 effdf47c 01072fff 0008  effe8f90 fe046878 
> fe040e0c*
> *0040: 6013*
> *instruction[fe040e0c]:*
> *06 30 98 e7 1c 20 94 e5 11 00 12 e3 00 70 94 15 18 20 9d 15 07 70 82 11 
> 0c 00*
> *stack[effe8f90]:*
> *: effe8fbc e18a1000  efffb348 effca00c 003f 0a6e 
> e1988160*
> *0020: 8ffb2000 f000  0007 0040 effccbf8 fe099ff0 
> 0100*
> *0040: 00ff efff0090 0073 008d effca6e8 fe044744 effccbf8 
> fe044ad0*
> *0060: efffb348 fe069bac efffb348 fe071e30 effe9018   
> ÿ*
>
>
> As we can see, I have this message : *QNX Version 6.5.0 Release 
> 2010/07/09-14:26:46EDT*
> This means that I try to compile with QNX 6.5.0 and not QNX 6.5.0 SP1. I 
> don't understand why i have this message because I have well installed QNX 
> 6.5.0 SP1 :
> [image: 1.png]
>
> [image: 2.jpg]
> Do I miss something ? Do I have to activate someting somewhere ?
>
> Thank you for your help.
>
> -- 
> 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...@googlegroups.com.
> To view this discussion on the web visit 
>
> https://groups.google.com/d/msgid/beagleboard/84dc332e-7fc5-4b20-bf82-05224d394938n%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/b7cbc2f5-2616-4ae5-937f-d27e32f34b2en%40googlegroups.com.

Re: [beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

['Mark Lazarewicz' via BeagleBoard]

I remember sd  card setup was important on Beagle board. your probably 
following old or incorrect instructions. What was on this board could be 
important. What instructions as well.They used to have a forum before 
Blackberry bought them.


Sent from Yahoo Mail on Android 
 
  On Mon, Mar 1, 2021 at 10:52 AM, 
robert.sty...@gmail.com wrote:   I vaguely 
remember the SP install being two manual steps, one being copying files from 
one place to another

On Monday, 1 March 2021 at 16:02:15 UTC lucas...@gmail.com wrote:

Hello,
I would like to use QNX on my BeagleBone Black. I have downloaded the QNX 
Neutrino 6.5.0 SP1 BSP here:
https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone
When I load the prebuilt image, it starts perfectly but when I try to build the 
BSP by myself, I have this : 
Jumping to QNX
System page at phys:80011000 user:fc404000 kern:fc404000Starting next program 
at vfe046604cpu_startnext: cpu0 -> fe046604VFPv3: 
fpsid=410330c3coproc_attach(10): replacing fe07601c with 
fe0758bccoproc_attach(11): replacing fe07601c with fe0758bcWelcome to QNX 
Neutrino 6.5.0 SP1 on the Texas Instruments BeagleBone (ARMv7 Cortex-A8 core) - 
Board
Shutdown[0,0] S/C/F=11/1/11 C/D=fe01c68c/fe099ff4 state(c0)= now lockQNX 
Version 6.5.0 Release 2010/07/09-14:26:46EDT[0]PID-TID=1-6? P/T 
FL=00019001/0502 "proc/boot/procnto-instr"[0]ASPACE PID=2 PF=8012armle 
context[effe8f4c]:: 8ffb2000 8ffb2000 8ffb2c01 0181 effccbf8 0100 
 fc004020: fc004000 effdf47c 01072fff 0008  effe8f90 
fe046878 fe040e0c0040: 6013instruction[fe040e0c]:06 30 98 e7 1c 20 94 e5 11 
00 12 e3 00 70 94 15 18 20 9d 15 07 70 82 11 0c 00stack[effe8f90]:: 
effe8fbc e18a1000  efffb348 effca00c 003f 0a6e e19881600020: 
8ffb2000 f000  0007 0040 effccbf8 fe099ff0 0140: 
00ff efff0090 0073 008d effca6e8 fe044744 effccbf8 fe044ad00060: 
efffb348 fe069bac efffb348 fe071e30 effe9018   ÿ

As we can see, I have this message : QNX Version 6.5.0 Release 
2010/07/09-14:26:46EDTThis means that I try to compile with QNX 6.5.0 and not 
QNX 6.5.0 SP1. I don't understand why i have this message because I have well 
installed QNX 6.5.0 SP1 :


Do I miss something ? Do I have to activate someting somewhere ?
Thank you for your help.


-- 
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/84dc332e-7fc5-4b20-bf82-05224d394938n%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/325596030.536839.1614618117863%40mail.yahoo.com.

[beagleboard] Re: BeagleBone Black QNX 6.5.0 SP1

[robert.sty...@gmail.com]

I vaguely remember the SP install being two manual steps, one being copying 
files from one place to another

On Monday, 1 March 2021 at 16:02:15 UTC lucas...@gmail.com wrote:

> Hello,
>
> I would like to use QNX on my BeagleBone Black. I have downloaded the QNX 
> Neutrino 6.5.0 SP1 BSP here:
>
>
> https://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone
>
> When I load the prebuilt image, it starts perfectly but when I try to 
> build the BSP by myself, I have this : 
>
> *Jumping to QNX*
>
> *System page at phys:80011000 user:fc404000 kern:fc404000*
> *Starting next program at vfe046604*
> *cpu_startnext: cpu0 -> fe046604*
> *VFPv3: fpsid=410330c3*
> *coproc_attach(10): replacing fe07601c with fe0758bc*
> *coproc_attach(11): replacing fe07601c with fe0758bc*
> *Welcome to QNX Neutrino 6.5.0 SP1 on the Texas Instruments BeagleBone 
> (ARMv7 Cortex-A8 core) - Board*
>
> *Shutdown[0,0] S/C/F=11/1/11 C/D=fe01c68c/fe099ff4 state(c0)= now lock*
> *QNX Version 6.5.0 Release 2010/07/09-14:26:46EDT*
> *[0]PID-TID=1-6? P/T FL=00019001/0502 "proc/boot/procnto-instr"*
> *[0]ASPACE PID=2 PF=8012*
> *armle context[effe8f4c]:*
> *: 8ffb2000 8ffb2000 8ffb2c01 0181 effccbf8 0100  
> fc004000*
> *0020: fc004000 effdf47c 01072fff 0008  effe8f90 fe046878 
> fe040e0c*
> *0040: 6013*
> *instruction[fe040e0c]:*
> *06 30 98 e7 1c 20 94 e5 11 00 12 e3 00 70 94 15 18 20 9d 15 07 70 82 11 
> 0c 00*
> *stack[effe8f90]:*
> *: effe8fbc e18a1000  efffb348 effca00c 003f 0a6e 
> e1988160*
> *0020: 8ffb2000 f000  0007 0040 effccbf8 fe099ff0 
> 0100*
> *0040: 00ff efff0090 0073 008d effca6e8 fe044744 effccbf8 
> fe044ad0*
> *0060: efffb348 fe069bac efffb348 fe071e30 effe9018   
> ÿ*
>
>
> As we can see, I have this message : *QNX Version 6.5.0 Release 
> 2010/07/09-14:26:46EDT*
> This means that I try to compile with QNX 6.5.0 and not QNX 6.5.0 SP1. I 
> don't understand why i have this message because I have well installed QNX 
> 6.5.0 SP1 :
> [image: 1.png]
>
> [image: 2.jpg]
> Do I miss something ? Do I have to activate someting somewhere ?
>
> Thank you for your help.
>

-- 
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/84dc332e-7fc5-4b20-bf82-05224d394938n%40googlegroups.com.

[beagleboard] Re: "Could not initialize egl display" when starting a Qt application

[eb]

This was posted 24 hours ago but it only was approved right now. Since then 
I have solved the issue on the Stretch Imagination Technologies image.

- I updated the kernel using these options: ./update_kernel.sh --ti-channel 
--lts-4_14 --sgx
- I had to install an additional package: apt install libdrm-dev
- I had to do a custom GBM library install, outlined here 
.
 
Seems not everything was set up correctly as part of the image.

After that it started working. Hope this helps someone

Does anyone know if there is any work being done for a similar image for 
Debian Buster and kernel 4.19?
On Monday, March 1, 2021 at 11:02:55 AM UTC-5 eb wrote:

> Hi all! I've spent a few days trying to get an LCD screen working with 
> hardware acceleration, eglfs, on my Beaglebone Black Wireless. My end goal 
> is running a PyQT5 application. After reading some discussions here, I 
> found that the Stretch ImgTec Beaglebone image already has opengl and sgx 
> dependencies installed. After installing that image on my SD and trying to 
> start the test dashboard application as explained here 
> ,
>  
> it just says:
>
> Could not initialize egl display
> Aborted
>
> I know that my display is working as it displays a login screen in the 
> terminal with tty1, AND it shows a basic pyqt5 application using linuxfb
> on the screen with the command `python3 test.py -platform linuxfb`.
>
> If I use qt debug variables, it still doesn't show any errors
>
> cd /usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard
> export QT_LOGGING_RULES=*=true
> export QSG_INFO=1
> export QT_QPA_EGLFS_DEBUG=1
> export QT_DEBUG_PLUGINS=1
> export QT_QPA_PLATFORM=eglfs 
> export QT_QPA_EGLFS_INTEGRATION=none
> ./dashboard
>
> Extracted output (to keep it short):
>
> Got keys from plugin meta data ("eglfs")
> Got keys from plugin meta data ("linuxfb")
> Got keys from plugin meta data ("minimal")
> Got keys from plugin meta data ("minimalegl")
> Got keys from plugin meta data ("offscreen")
> Got keys from plugin meta data ("xcb")
> loaded library 
> "/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqeglfs.so"
> Got keys from plugin meta data ("eglfs_kms_egldevice")
> Got keys from plugin meta data ("eglfs_kms")
> Got keys from plugin meta data ("eglfs_x11")
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard/egldeviceintegrations"
>  
> ...
> qt.qpa.egldeviceintegration: EGL device integration plugin keys: 
> ("eglfs_kms_egldevice", "eglfs_kms", "eglfs_x11")
> qt.qpa.egldeviceintegration: Using base device integration
> Could not initialize egl display
> Aborted
>
> I don't think an X server is running (searched via `ps aux | grep -i x`).
>
> I also tried using Buster image without graphics and followed the 
> instruction in the wiki page listed above, but still no dice. Does anyone 
> have any pointers on how to continue with this?
>

-- 
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/c52a2a50-d041-42dc-9426-eeaa838ace3cn%40googlegroups.com.

Re: [beagleboard] "Could not initialize egl display" when starting a Qt application

[Robert Nelson]

On Mon, Mar 1, 2021 at 10:02 AM eb  wrote:
>
> Hi all! I've spent a few days trying to get an LCD screen working with 
> hardware acceleration, eglfs, on my Beaglebone Black Wireless. My end goal is 
> running a PyQT5 application. After reading some discussions here, I found 
> that the Stretch ImgTec Beaglebone image already has opengl and sgx 
> dependencies installed. After installing that image on my SD and trying to 
> start the test dashboard application as explained here, it just says:
>
> Could not initialize egl display
> Aborted
>
> I know that my display is working as it displays a login screen in the 
> terminal with tty1, AND it shows a basic pyqt5 application using linuxfb
> on the screen with the command `python3 test.py -platform linuxfb`.
>
> If I use qt debug variables, it still doesn't show any errors
>
> cd /usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard
> export QT_LOGGING_RULES=*=true
> export QSG_INFO=1
> export QT_QPA_EGLFS_DEBUG=1
> export QT_DEBUG_PLUGINS=1
> export QT_QPA_PLATFORM=eglfs
> export QT_QPA_EGLFS_INTEGRATION=none
> ./dashboard
>
> Extracted output (to keep it short):
>
> Got keys from plugin meta data ("eglfs")
> Got keys from plugin meta data ("linuxfb")
> Got keys from plugin meta data ("minimal")
> Got keys from plugin meta data ("minimalegl")
> Got keys from plugin meta data ("offscreen")
> Got keys from plugin meta data ("xcb")
> loaded library 
> "/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqeglfs.so"
> Got keys from plugin meta data ("eglfs_kms_egldevice")
> Got keys from plugin meta data ("eglfs_kms")
> Got keys from plugin meta data ("eglfs_x11")
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard/egldeviceintegrations"
>  ...
> qt.qpa.egldeviceintegration: EGL device integration plugin keys: 
> ("eglfs_kms_egldevice", "eglfs_kms", "eglfs_x11")
> qt.qpa.egldeviceintegration: Using base device integration
> Could not initialize egl display
> Aborted
>
> I don't think an X server is running (searched via `ps aux | grep -i x`).

Correct no x server..

>
> I also tried using Buster image without graphics and followed the instruction 
> in the wiki page listed above, but still no dice. Does anyone have any 
> pointers on how to continue with this?

Imagination wrote a fun with beagle, which helps explain the stretch
imgtec image and egl, etc..

https://university.imgtec.com/fun-with-beagle-gpu/

That ^ might help debug what's wrong..

Regards,

-- 
Robert Nelson
https://rcn-ee.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/CAOCHtYhHL%2BbrLn4kF8-pjq%2BuPA7XjW3MgnV07A-CKWaXpVh0uw%40mail.gmail.com.

[beagleboard] "Could not initialize egl display" when starting a Qt application

[eb]

Hi all! I've spent a few days trying to get an LCD screen working with 
hardware acceleration, eglfs, on my Beaglebone Black Wireless. My end goal 
is running a PyQT5 application. After reading some discussions here, I 
found that the Stretch ImgTec Beaglebone image already has opengl and sgx 
dependencies installed. After installing that image on my SD and trying to 
start the test dashboard application as explained here 
,
 
it just says:

Could not initialize egl display
Aborted

I know that my display is working as it displays a login screen in the 
terminal with tty1, AND it shows a basic pyqt5 application using linuxfb
on the screen with the command `python3 test.py -platform linuxfb`.

If I use qt debug variables, it still doesn't show any errors

cd /usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard
export QT_LOGGING_RULES=*=true
export QSG_INFO=1
export QT_QPA_EGLFS_DEBUG=1
export QT_DEBUG_PLUGINS=1
export QT_QPA_PLATFORM=eglfs 
export QT_QPA_EGLFS_INTEGRATION=none
./dashboard

Extracted output (to keep it short):

Got keys from plugin meta data ("eglfs")
Got keys from plugin meta data ("linuxfb")
Got keys from plugin meta data ("minimal")
Got keys from plugin meta data ("minimalegl")
Got keys from plugin meta data ("offscreen")
Got keys from plugin meta data ("xcb")
loaded library 
"/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqeglfs.so"
Got keys from plugin meta data ("eglfs_kms_egldevice")
Got keys from plugin meta data ("eglfs_kms")
Got keys from plugin meta data ("eglfs_x11")
QFactoryLoader::QFactoryLoader() checking directory path 
"/usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard/egldeviceintegrations"
 
...
qt.qpa.egldeviceintegration: EGL device integration plugin keys: 
("eglfs_kms_egldevice", "eglfs_kms", "eglfs_x11")
qt.qpa.egldeviceintegration: Using base device integration
Could not initialize egl display
Aborted

I don't think an X server is running (searched via `ps aux | grep -i x`).

I also tried using Buster image without graphics and followed the 
instruction in the wiki page listed above, but still no dice. Does anyone 
have any pointers on how to continue with this?

-- 
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/d7f68907-1195-445a-8aa5-b064ccc37cben%40googlegroups.com.

[beagleboard] Re: Compatibility of Debian and Matlab

[Cheng Chen]

Hi Dennis, 

Thanks for the reply. 
Yes. Matlab is using SSH for connection. I think the problem I met is 
exactly what you described: unable to respond to the prompt for root user 
password. Could you elaborate on "configure the sudoers file to not require 
a user password for sudo" a little more please? Thanks. 

Regards,
Cheng

在2021年2月27日星期六 UTC-5 上午8:39:43 写道：

> On Fri, 26 Feb 2021 11:51:39 -0800 (PST), in 
> gmane.comp.hardware.beagleboard.user Cheng Chen 
>  wrote: 
>
> >Hi, 
> > 
> >I have a question about connection between Beaglebone Black and Matlab. 
> >I was trying to control BBB with Matlab. But when I ran the command on 
> >Matlab, there is always some errors suggested access denied. Then I found 
> >that is because I do not have access to superuser. While I checked Debian 
> I 
>
> For quite some years now login as root has been disabled in many Linux 
> distributions; logging as a regular user configured for sudoer privilege 
> has been standard. 
>
> What "command"? How does Matlab make its connection -- using SSH? You 
> may have to see how to configure Matlab to use a different account for 
> logging into the BBB, and then modify these commands to use "sudo" (though 
> you still have the problem then of how do you respond to the prompt for 
> user password -- you might be able to configure the sudoers file to not 
> require a user password for sudo; Raspberry-Pi is configured that way for 
> the standard account). 
>
>
>
> -- 
> 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/e39cbdee-46a5-4e1d-9a57-8acce16270bdn%40googlegroups.com.

Re: [beagleboard] Re: Beaglebone Seeed green (custom LCD read post) GUI

[Don Kiser]

LXDE makes more sense, thank you.
While the newer version of Debian will run the LCD doesn't work even if I
copy the .dtbs from the original and update the uEnv.txt file to load them.
This has been my reason for not updating it, yet. I will have to pull the
unit apart and see if I can what chips are on the LCD to figure out how to
drive it.
It appears to be using the LCD pins on the GPIO.


Don Kiser - AC2EV
585-613-1035


On Sun, Feb 28, 2021 at 11:32 PM Dennis Lee Bieber <
dennis.l.bie...@gmail.com> wrote:

> On Sun, 28 Feb 2021 12:03:40 -0800 (PST), in
> gmane.comp.hardware.beagleboard.user Don Kiser
>  wrote:
>
>
> >*UNIT 2:*
> >Device has a modified Debian Jessie OS. By design it starts Qtopia?. The
> >board is a Beagleboard Green from Seeed Studio so no HDMI. I tried
> >installing lxqt but apt doesn't know where to find it.
> >
> Jessie is old enough that the graphical desktop was probably LXDE,
> not
> LXQT.
>
> >My concern is that overwriting it the OS with a new one
> >(bone-debian-9.9-lxqt-armhf-2019-08-03-4gb.img.gz)  will lose what makes
> >the LCD work. I tried this didn't work well, had to dd a different unit
> to
> >get this one working again.
> >
>
> Stretch is pretty old too. Current OS is based on Buster (Debian
> 10.x).
>
> So DON'T overwrite (flash) the eMMC -- run an SD card image
> directly
> until you verify that it does what you want. THEN convert the card to a
> flasher to update the eMMC.
>
> Note: depending upon just how old that Jessie image is, you may
> have to
> use the boot-select button when applying power to the board. I believe it
> was sometime late in the Jessie period that u-Boot was modified to
> automatically switch to the SD card. Also take note of the fact that Jessie
> is still in the "Linux kernel loads device tree overlays" -- for some time
> now, it is u-boot that loads the overlays, so updating the eMMC by some
> means that doesn't update the u-boot will cause problems.
>
>
>
> --
> Dennis L Bieber
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NR4J-ijMXZM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/psqo3g1jdil5f525m4e48ggl0r6hr6anl6%404ax.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/CAC6886MYSkQkybL_T8qy%2BuECef7k2cEsV5rdZFWv1sqHNZMuNQ%40mail.gmail.com.

[beagleboard] USB doesn't come back (usb 1-1: device descriptor read/64, error -110) !

[Philippe Frossard]

Hi,
I'm using Beaglebone black with 3.7v LiPo battery,
When I remove the power 5v supply some seconds and put it back on,
the USB port doesn't work again !

The errors :

usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: device not accepting address 2, error -110
INFO: task scsi_eh_0:81 blocked for more than 60 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Kernel panic - not syncing: hung_task: blocked tasks
[] (unwind_backtrace+0x1/0x9c) from [] 
(panic+0x59/0x15c)

[] (panic+0x59/0x15c) from [] (watchdog+0x19d/0x1c0)
[] (watchdog+0x19d/0x1c0) from [] (kthread+0x6b/0x78)
[] (kthread+0x6b/0x78) from [] (ret_from_fork+0x11/0x34)


I have the same problem with USB mass storage or with a wifi key ...
Any ideas ?
Thanks.

--
-
Philippe Frossard
Portable : +33 617 43 27 75

FROSSARD CSI
Conseil en Systèmes Informatiques
Rézier, 26 Rue des granges Cordies
74890 FESSY (France)
Tél. : +00 33 (0)4 50 36 02 54
Email : i...@frossard-csi.fr ou philippe.fross...@free.fr
Site Internet : http://www.frossard-csi.fr

--
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/47e83bb4-22d2-42a1-4d5c-98b61433eed0%40free.fr.