Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
You cannot imagine how I feel when see this on my terminal:

 EGL  yes
  OpenVG . no
  OpenGL:
Desktop OpenGL ... no
OpenGL ES 2.0  yes
OpenGL ES 3.0  yes
OpenGL ES 3.1  yes
OpenGL ES 3.2  yes
  Vulkan . yes
  Session Management . yes
Features used by QPA backends:
  evdev .. yes
  libinput ... no
  INTEGRITY HID .. no
  mtdev .. no
  tslib .. no
  xkbcommon .. yes
  X11 specific:
XLib . yes
XCB Xlib . yes
EGL on X11 ... yes
QPA backends:
  DirectFB ... no
  EGLFS .. yes
  EGLFS details:
EGLFS OpenWFD  no
EGLFS i.Mx6 .. no
EGLFS i.Mx6 Wayland .. no
EGLFS RCAR ... no
EGLFS EGLDevice .. no
EGLFS GBM  no
EGLFS VSP2 ... no
EGLFS Mali ... no
EGLFS Raspberry Pi ... no
EGLFS X11  yes

We are almost 95% done.
Thank you very much. 
That not only helps, that works.

I'm starting -make that, i will write here again when it's done.
Thank you again.

Regards, Jeremias.


El lunes, 26 de octubre de 2020 a las 1:35:42 UTC-3, jonn...@gmail.com 
escribi贸:

> Okay, I think I have something that works.  This completes the configure 
> step, completes make, and make install.
> As far as the issue where it is still picking up the previous toolchain in 
> your config, each time after I compile or run into an issue, I remove the 
> build, the qt source, the toolchain folders and anything else that 
> indicates it was touched during the build of qt. I had to remove the 
> sysroot folder and resync the files from the Beaglebone at least once.
>
> With my config, I found I was missing a couple of folders from the BB 
> where there were files linked to other locations.  This is what I have for 
> creating the sysroot for the BB.
>
> *mkdir -p sysroot/{lib,sbin,usr/{include,lib,bin},etc/alternatives}*
>
> *rsync -avz deb...@192.168.7.2:/lib sysroot/*
>
> *rsync -avz deb...@192.168.7.2:/sbin sysroot/*
>
> *rsync -avz deb...@192.168.7.2:/usr/include sysroot/usr*
>
> *rsync -avz deb...@192.168.7.2:/usr/lib sysroot/usr*
>
> *rsync -avz deb...@192.168.7.2:/usr/bin sysroot/usr*
>
> *rsync -avz deb...@192.168.7.2:/etc/alternatives sysroot/etc*
>
>
> Get this tool to fix relative links:
>
> *wget 
> https://raw.githubusercontent.com/riscv/riscv-poky/master/scripts/sysroot-relativelinks.py
>  
> *
> *chmod +x sysroot-relativelinks.py*
> *./sysroot-relativelinks.py sysroot*
>
> This is the qmake.conf that I am using
>
> *#*
> *# qmake configuration for the BeagleBoard and BeagleBoard xM boards*
> *# http://beagleboard.org/ *
>
> *MAKEFILE_GENERATOR  = UNIX*
> *CONFIG += incremental*
> *QMAKE_INCREMENTAL_STYLE = sublib*
>
> *#include(../../common/linux.conf)*
> *#include(../../common/gcc-base-unix.conf)*
> *#include(../../common/g++-unix.conf)*
>
> *include(../common/linux_device_pre.conf)*
>
> *load(device_config)*
>
> *QT_QPA_DEFAULT_PLATFORM = eglfs*
>
> *# modifications to g++.conf*
> *QMAKE_CC= $${CROSS_COMPILE}gcc*
> *QMAKE_CXX   = $${CROSS_COMPILE}g++*
> *QMAKE_LINK  = $${QMAKE_CXX}*
> *QMAKE_LINK_SHLIB= $${QMAKE_CXX}*
>
> *# modifications to linux.conf*
> *QMAKE_AR= $${CROSS_COMPILE}ar cqs*
> *QMAKE_OBJCOPY   = $${CROSS_COMPILE}objcopy*
> *QMAKE_NM= $${CROSS_COMPILE}nm -P*
> *QMAKE_STRIP = $${CROSS_COMPILE}strip*
>
> *COMPILER_FLAGS  = -march=armv7-a -mtune=cortex-a8 -mfpu=neon 
> -mthumb*
>
> *#modifications to gcc-base.conf*
> *QMAKE_CFLAGS   += $${COMPILER_FLAGS}*
> *QMAKE_CXXFLAGS += $${COMPILER_FLAGS}*
> *QMAKE_CXXFLAGS_RELEASE += -O3*
>
> *INCLUDEPATH += 
> /home/bbbuild/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include/c++/7.5.0
>  
> *
>
> *QMAKE_LIBS += -lrt -lpthread -ldl*
>
>
> *# Extra stuff (OpenGL, DirectFB, ...)*
>
> *QMAKE_INCDIR_EGL= 
> /home/bbbuild/develop/bbuild/sysroot/usr/include *
> *QMAKE_LIBDIR_EGL= 
> /home/bbbuild/develop/bbuild/sysroot/usr/lib/arm-linux-gnueabihf *
>
> *QMAKE_INCDIR_OPENGL_ES2 = $${QMAKE_INCDIR_EGL}*
> *QMAKE_LIBDIR_OPENGL_ES

Re: [beagleboard] Problems with SPI on BB Blue

2020-10-26 Thread Michele Xiloyannis 
HI TB, 

thanks a lot for posting your issue and the solution. I am having exactly 
the same problem with a BBBlue, with the 2018-10-07 BeagleBone Blue Flasher 
Image 

 from 
Strawson Design. 
Could you please give me a bit more details on how you disabled the eqep0? 
Where did you add the overly that does so?
Many thanks!

Michele 
On Friday, May 1, 2020 at 7:02:21 AM UTC+2 TB wrote:

> ok, I solved the sending part:
>
> [image: spi_capture_ok.png]
>
> I added an overlay that disables `eqep0`:
>
> /dts-v1/;
> /plugin/;
>
>
> / {
> model = "TI AM335x BeagleBone Blue";
> compatible = "ti,am335x-bone-blue", "ti,am33xx";
>
>
> fragment@0 {
> target = <&eqep0>;
> __overlay__ {
>  status = "disabled";
> };
> };
> };
>
>
> And how the pins are correctly muxed:
>
> P9.42a89 C18 fast 2 spi 1 cs 1   
> ocp/C18_pinmux (pinmux_C18_spi_pin)
> P9.31 / hdmi audio clk   100 A13 fast rx  up  3 spi 1 clk   
>  ocp/P9_31_pinmux (pinmux_P9_31_spi_sclk_pin)
>
> P9.29 / hdmi audio fs101 B13 fast rx down 3 spi 1 data 0 
> ocp/P9_29_pinmux (pinmux_P9_29_spi_pin)
>
> P9.30102 D12 fast rx down 3 spi 1 data 1 
> ocp/P9_30_pinmux (pinmux_P9_30_spi_pin)
>
>
>
>
>
>
>

-- 
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/d54661ea-8181-4f6c-b0fc-3f656a46f64dn%40googlegroups.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
Well, I can't compile it. 馃樁
I got those errors after a while:

In file included from
/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/bits/stl_algo.h:59:0,
 from
/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/algorithm:62,
 from
../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qglobal.h:142,
 from ../../include/QtCore/qglobal.h:1,
 from
../../include/QtGui/../../../../qt5/qtbase/src/gui/kernel/qtguiglobal.h:43,
 from ../../include/QtGui/qtguiglobal.h:1,
 from
/opt/qt5129bbb/qt5/qtbase/src/gui/kernel/qt_gui_pch.h:50:
/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
fatal error: stdlib.h: No such file or directory
 #include_next 
   ^~
compilation terminated.
Makefile:1926: recipe for target '.pch/Qt5Gui.gch/c++' failed
make[3]: *** [.pch/Qt5Gui.gch/c++] Error 1
make[3]: Leaving directory '/opt/qt5129bbb/build/qtbase/src/gui'
Makefile:555: recipe for target 'sub-gui-make_first' failed
make[2]: *** [sub-gui-make_first] Error 2
make[2]: Leaving directory '/opt/qt5129bbb/build/qtbase/src'
Makefile:50: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory '/opt/qt5129bbb/build/qtbase'
Makefile:82: recipe for target 'module-qtbase-make_first' failed
make: *** [module-qtbase-make_first] Error 2

I'm trying to figure out what's wrong with the library.
PS: I tried removing the line you add to the conf file, just in case.

El lun., 26 oct. 2020 a las 9:30, 'Jeremias Ramirez' via BeagleBoard (<
beagleboard@googlegroups.com>) escribi贸:

> You cannot imagine how I feel when see this on my terminal:
>
>  EGL  yes
>   OpenVG . no
>   OpenGL:
> Desktop OpenGL ... no
> OpenGL ES 2.0  yes
> OpenGL ES 3.0  yes
> OpenGL ES 3.1  yes
> OpenGL ES 3.2  yes
>   Vulkan . yes
>   Session Management . yes
> Features used by QPA backends:
>   evdev .. yes
>   libinput ... no
>   INTEGRITY HID .. no
>   mtdev .. no
>   tslib .. no
>   xkbcommon .. yes
>   X11 specific:
> XLib . yes
> XCB Xlib . yes
> EGL on X11 ... yes
> QPA backends:
>   DirectFB ... no
>   EGLFS .. yes
>   EGLFS details:
> EGLFS OpenWFD  no
> EGLFS i.Mx6 .. no
> EGLFS i.Mx6 Wayland .. no
> EGLFS RCAR ... no
> EGLFS EGLDevice .. no
> EGLFS GBM  no
> EGLFS VSP2 ... no
> EGLFS Mali ... no
> EGLFS Raspberry Pi ... no
> EGLFS X11  yes
>
> We are almost 95% done.
> Thank you very much.
> That not only helps, that works.
>
> I'm starting -make that, i will write here again when it's done.
> Thank you again.
>
> Regards, Jeremias.
>
>
> El lunes, 26 de octubre de 2020 a las 1:35:42 UTC-3, jonn...@gmail.com
> escribi贸:
>
>> Okay, I think I have something that works.  This completes the configure
>> step, completes make, and make install.
>> As far as the issue where it is still picking up the previous toolchain
>> in your config, each time after I compile or run into an issue, I remove
>> the build, the qt source, the toolchain folders and anything else that
>> indicates it was touched during the build of qt. I had to remove the
>> sysroot folder and resync the files from the Beaglebone at least once.
>>
>> With my config, I found I was missing a couple of folders from the BB
>> where there were files linked to other locations.  This is what I have for
>> creating the sysroot for the BB.
>>
>> *mkdir -p sysroot/{lib,sbin,usr/{include,lib,bin},etc/alternatives}*
>>
>> *rsync -avz deb...@192.168.7.2:/lib sysroot/*
>>
>> *rsync -avz deb...@192.168.7.2:/sbin sysroot/*
>>
>> *rsync -avz deb...@192.168.7.2:/usr/include sysroot/usr*
>>
>> *rsync -avz deb...@192.168.7.2:/usr/lib sysroot/usr*
>>
>> *rsync -avz deb...@192.168.7.2:/usr/bin sysroot/usr*
>>
>> *rsync -avz deb...@192.168.7.2:/etc/alternatives sysroot/etc*
>>
>>
>> Get this tool to fix relative links:
>>
>> *wget
>> https://raw.githubusercontent.com/riscv/riscv-poky/master/scripts/sysroot-relativeli

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread jonnymo 
I had that issue but it seemed to be resolved by adding the following line
in the qmake.conf file:

*INCLUDEPATH +=
/home/bbbuild/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include/c++/7.5.0*


Ensure you adjust the path, and other paths, to match your configuration.
This is fully qualified based on where the toolchain is installed on my
system.

Cheers,

Jon

On Mon, Oct 26, 2020 at 9:35 AM 'Jeremias Ramirez' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Well, I can't compile it. 馃樁
> I got those errors after a while:
>
> In file included from
> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/bits/stl_algo.h:59:0,
>  from
> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/algorithm:62,
>  from
> ../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qglobal.h:142,
>  from ../../include/QtCore/qglobal.h:1,
>  from
> ../../include/QtGui/../../../../qt5/qtbase/src/gui/kernel/qtguiglobal.h:43,
>  from ../../include/QtGui/qtguiglobal.h:1,
>  from
> /opt/qt5129bbb/qt5/qtbase/src/gui/kernel/qt_gui_pch.h:50:
> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
> fatal error: stdlib.h: No such file or directory
>  #include_next 
>^~
> compilation terminated.
> Makefile:1926: recipe for target '.pch/Qt5Gui.gch/c++' failed
> make[3]: *** [.pch/Qt5Gui.gch/c++] Error 1
> make[3]: Leaving directory '/opt/qt5129bbb/build/qtbase/src/gui'
> Makefile:555: recipe for target 'sub-gui-make_first' failed
> make[2]: *** [sub-gui-make_first] Error 2
> make[2]: Leaving directory '/opt/qt5129bbb/build/qtbase/src'
> Makefile:50: recipe for target 'sub-src-make_first' failed
> make[1]: *** [sub-src-make_first] Error 2
> make[1]: Leaving directory '/opt/qt5129bbb/build/qtbase'
> Makefile:82: recipe for target 'module-qtbase-make_first' failed
> make: *** [module-qtbase-make_first] Error 2
>
> I'm trying to figure out what's wrong with the library.
> PS: I tried removing the line you add to the conf file, just in case.
>
> El lun., 26 oct. 2020 a las 9:30, 'Jeremias Ramirez' via BeagleBoard (<
> beagleboard@googlegroups.com>) escribi贸:
>
>> You cannot imagine how I feel when see this on my terminal:
>>
>>  EGL  yes
>>   OpenVG . no
>>   OpenGL:
>> Desktop OpenGL ... no
>> OpenGL ES 2.0  yes
>> OpenGL ES 3.0  yes
>> OpenGL ES 3.1  yes
>> OpenGL ES 3.2  yes
>>   Vulkan . yes
>>   Session Management . yes
>> Features used by QPA backends:
>>   evdev .. yes
>>   libinput ... no
>>   INTEGRITY HID .. no
>>   mtdev .. no
>>   tslib .. no
>>   xkbcommon .. yes
>>   X11 specific:
>> XLib . yes
>> XCB Xlib . yes
>> EGL on X11 ... yes
>> QPA backends:
>>   DirectFB ... no
>>   EGLFS .. yes
>>   EGLFS details:
>> EGLFS OpenWFD  no
>> EGLFS i.Mx6 .. no
>> EGLFS i.Mx6 Wayland .. no
>> EGLFS RCAR ... no
>> EGLFS EGLDevice .. no
>> EGLFS GBM  no
>> EGLFS VSP2 ... no
>> EGLFS Mali ... no
>> EGLFS Raspberry Pi ... no
>> EGLFS X11  yes
>>
>> We are almost 95% done.
>> Thank you very much.
>> That not only helps, that works.
>>
>> I'm starting -make that, i will write here again when it's done.
>> Thank you again.
>>
>> Regards, Jeremias.
>>
>>
>> El lunes, 26 de octubre de 2020 a las 1:35:42 UTC-3, jonn...@gmail.com
>> escribi贸:
>>
>>> Okay, I think I have something that works.  This completes the configure
>>> step, completes make, and make install.
>>> As far as the issue where it is still picking up the previous toolchain
>>> in your config, each time after I compile or run into an issue, I remove
>>> the build, the qt source, the toolchain folders and anything else that
>>> indicates it was touched during the build of qt. I had to remove the
>>> sysroot folder and resync the files from the Beaglebone at least once.
>>>
>>> With my config, I found I was missing a couple of folders from the BB
>>> where there were files linked to other

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
Ok! Checking the paths again...
The only difference I see against your setup is that I'm using the Arm8
version of the toolchain.

Regards, Jeremias.

El lun., 26 oct. 2020 a las 13:41, jonnymo () escribi贸:

> I had that issue but it seemed to be resolved by adding the following line
> in the qmake.conf file:
>
> *INCLUDEPATH +=
> /home/bbbuild/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include/c++/7.5.0*
>
>
> Ensure you adjust the path, and other paths, to match your configuration.
> This is fully qualified based on where the toolchain is installed on my
> system.
>
> Cheers,
>
> Jon
>
> On Mon, Oct 26, 2020 at 9:35 AM 'Jeremias Ramirez' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
>> Well, I can't compile it. 馃樁
>> I got those errors after a while:
>>
>> In file included from
>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/bits/stl_algo.h:59:0,
>>  from
>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/algorithm:62,
>>  from
>> ../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qglobal.h:142,
>>  from ../../include/QtCore/qglobal.h:1,
>>  from
>> ../../include/QtGui/../../../../qt5/qtbase/src/gui/kernel/qtguiglobal.h:43,
>>  from ../../include/QtGui/qtguiglobal.h:1,
>>  from
>> /opt/qt5129bbb/qt5/qtbase/src/gui/kernel/qt_gui_pch.h:50:
>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
>> fatal error: stdlib.h: No such file or directory
>>  #include_next 
>>^~
>> compilation terminated.
>> Makefile:1926: recipe for target '.pch/Qt5Gui.gch/c++' failed
>> make[3]: *** [.pch/Qt5Gui.gch/c++] Error 1
>> make[3]: Leaving directory '/opt/qt5129bbb/build/qtbase/src/gui'
>> Makefile:555: recipe for target 'sub-gui-make_first' failed
>> make[2]: *** [sub-gui-make_first] Error 2
>> make[2]: Leaving directory '/opt/qt5129bbb/build/qtbase/src'
>> Makefile:50: recipe for target 'sub-src-make_first' failed
>> make[1]: *** [sub-src-make_first] Error 2
>> make[1]: Leaving directory '/opt/qt5129bbb/build/qtbase'
>> Makefile:82: recipe for target 'module-qtbase-make_first' failed
>> make: *** [module-qtbase-make_first] Error 2
>>
>> I'm trying to figure out what's wrong with the library.
>> PS: I tried removing the line you add to the conf file, just in case.
>>
>> El lun., 26 oct. 2020 a las 9:30, 'Jeremias Ramirez' via BeagleBoard (<
>> beagleboard@googlegroups.com>) escribi贸:
>>
>>> You cannot imagine how I feel when see this on my terminal:
>>>
>>>  EGL  yes
>>>   OpenVG . no
>>>   OpenGL:
>>> Desktop OpenGL ... no
>>> OpenGL ES 2.0  yes
>>> OpenGL ES 3.0  yes
>>> OpenGL ES 3.1  yes
>>> OpenGL ES 3.2  yes
>>>   Vulkan . yes
>>>   Session Management . yes
>>> Features used by QPA backends:
>>>   evdev .. yes
>>>   libinput ... no
>>>   INTEGRITY HID .. no
>>>   mtdev .. no
>>>   tslib .. no
>>>   xkbcommon .. yes
>>>   X11 specific:
>>> XLib . yes
>>> XCB Xlib . yes
>>> EGL on X11 ... yes
>>> QPA backends:
>>>   DirectFB ... no
>>>   EGLFS .. yes
>>>   EGLFS details:
>>> EGLFS OpenWFD  no
>>> EGLFS i.Mx6 .. no
>>> EGLFS i.Mx6 Wayland .. no
>>> EGLFS RCAR ... no
>>> EGLFS EGLDevice .. no
>>> EGLFS GBM  no
>>> EGLFS VSP2 ... no
>>> EGLFS Mali ... no
>>> EGLFS Raspberry Pi ... no
>>> EGLFS X11  yes
>>>
>>> We are almost 95% done.
>>> Thank you very much.
>>> That not only helps, that works.
>>>
>>> I'm starting -make that, i will write here again when it's done.
>>> Thank you again.
>>>
>>> Regards, Jeremias.
>>>
>>>
>>> El lunes, 26 de octubre de 2020 a las 1:35:42 UTC-3, jonn...@gmail.com
>>> escribi贸:
>>>
 Okay, I think I have something that works.  This completes the
 configure step, completes make, and make install.
 As far as the issue where it is still picking up the previous toolchain
 in your config, each time after I compile or run into an issue, I remove
 the buil

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
Okay, i owe you another coffee.
I corrected the paths, but forgot just the arm8.
Was:
/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/arm-linux-gnueabihf/include/c++/7.5.0
Must be:
/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/arm
*v8l*-linux-gnueabihf/include/c++/7.5.0

Trying, again.


El lun., 26 oct. 2020 a las 13:44, Jeremias Ramirez (<
iguanadeje...@googlemail.com>) escribi贸:

> Ok! Checking the paths again...
> The only difference I see against your setup is that I'm using the Arm8
> version of the toolchain.
>
> Regards, Jeremias.
>
> El lun., 26 oct. 2020 a las 13:41, jonnymo ()
> escribi贸:
>
>> I had that issue but it seemed to be resolved by adding the
>> following line in the qmake.conf file:
>>
>> *INCLUDEPATH +=
>> /home/bbbuild/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include/c++/7.5.0*
>>
>>
>> Ensure you adjust the path, and other paths, to match your
>> configuration.  This is fully qualified based on where the toolchain is
>> installed on my system.
>>
>> Cheers,
>>
>> Jon
>>
>> On Mon, Oct 26, 2020 at 9:35 AM 'Jeremias Ramirez' via BeagleBoard <
>> beagleboard@googlegroups.com> wrote:
>>
>>> Well, I can't compile it. 馃樁
>>> I got those errors after a while:
>>>
>>> In file included from
>>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/bits/stl_algo.h:59:0,
>>>  from
>>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/algorithm:62,
>>>  from
>>> ../../include/QtCore/../../../../qt5/qtbase/src/corelib/global/qglobal.h:142,
>>>  from ../../include/QtCore/qglobal.h:1,
>>>  from
>>> ../../include/QtGui/../../../../qt5/qtbase/src/gui/kernel/qtguiglobal.h:43,
>>>  from ../../include/QtGui/qtguiglobal.h:1,
>>>  from
>>> /opt/qt5129bbb/qt5/qtbase/src/gui/kernel/qt_gui_pch.h:50:
>>> /opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
>>> fatal error: stdlib.h: No such file or directory
>>>  #include_next 
>>>^~
>>> compilation terminated.
>>> Makefile:1926: recipe for target '.pch/Qt5Gui.gch/c++' failed
>>> make[3]: *** [.pch/Qt5Gui.gch/c++] Error 1
>>> make[3]: Leaving directory '/opt/qt5129bbb/build/qtbase/src/gui'
>>> Makefile:555: recipe for target 'sub-gui-make_first' failed
>>> make[2]: *** [sub-gui-make_first] Error 2
>>> make[2]: Leaving directory '/opt/qt5129bbb/build/qtbase/src'
>>> Makefile:50: recipe for target 'sub-src-make_first' failed
>>> make[1]: *** [sub-src-make_first] Error 2
>>> make[1]: Leaving directory '/opt/qt5129bbb/build/qtbase'
>>> Makefile:82: recipe for target 'module-qtbase-make_first' failed
>>> make: *** [module-qtbase-make_first] Error 2
>>>
>>> I'm trying to figure out what's wrong with the library.
>>> PS: I tried removing the line you add to the conf file, just in case.
>>>
>>> El lun., 26 oct. 2020 a las 9:30, 'Jeremias Ramirez' via BeagleBoard (<
>>> beagleboard@googlegroups.com>) escribi贸:
>>>
 You cannot imagine how I feel when see this on my terminal:

  EGL  yes
   OpenVG . no
   OpenGL:
 Desktop OpenGL ... no
 OpenGL ES 2.0  yes
 OpenGL ES 3.0  yes
 OpenGL ES 3.1  yes
 OpenGL ES 3.2  yes
   Vulkan . yes
   Session Management . yes
 Features used by QPA backends:
   evdev .. yes
   libinput ... no
   INTEGRITY HID .. no
   mtdev .. no
   tslib .. no
   xkbcommon .. yes
   X11 specific:
 XLib . yes
 XCB Xlib . yes
 EGL on X11 ... yes
 QPA backends:
   DirectFB ... no
   EGLFS .. yes
   EGLFS details:
 EGLFS OpenWFD  no
 EGLFS i.Mx6 .. no
 EGLFS i.Mx6 Wayland .. no
 EGLFS RCAR ... no
 EGLFS EGLDevice .. no
 EGLFS GBM  no
 EGLFS VSP2 ... no
 EGLFS Mali ... no
 EGLFS Raspberry Pi ... no
 EGLFS X11  yes

 We are almost 95% done.
 Thank you very much.
 T

[beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread Dennis Lee Bieber 
On Mon, 26 Oct 2020 13:35:09 -0300, in gmane.comp.hardware.beagleboard.user
"'Jeremias Ramirez' via BeagleBoard"
 wrote:


>/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
>fatal error: stdlib.h: No such file or directory
> #include_next 
>   ^~
>compilation terminated.

Per https://gcc.gnu.org/onlinedocs/cpp/Wrapper-Headers.html
"include_next" says to: find the next file in the search path with this
name. That seems to indicate that the include file search path needs to be
correctly ordered -- the implication is that there is a modified stdlib.h
in the source being built, and it then wants to include the normal system
stdlib.h for completeness.


{Is it really necessary to include 8+ levels of quoting that have nothing
relevant to the current incident?}


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

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread jonnymo 
Dennis,

Yeah, that is the intent of  INCLUDEPATH since the location of the includes
in the toolchain are in a different location than where Qt is looking.  I
did see a post where it was suggested to remove the Default path but there
were other comments in the same post where it did not work.  What I posted
seems to work; at least in my config.

I don't understand this comment:
"
{Is it really necessary to include 8+ levels of quoting that have nothing
relevant to the current incident?}"


Jon

On Mon, Oct 26, 2020 at 10:05 AM Dennis Lee Bieber <
dennis.l.bie...@gmail.com> wrote:

> On Mon, 26 Oct 2020 13:35:09 -0300, in gmane.comp.hardware.beagleboard.user
> "'Jeremias Ramirez' via BeagleBoard"
>  wrote:
>
>
>
> >/opt/qt5129bbb/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/armv8l-linux-gnueabihf/include/c++/7.5.0/cstdlib:75:15:
> >fatal error: stdlib.h: No such file or directory
> > #include_next 
> >   ^~
> >compilation terminated.
>
> Per https://gcc.gnu.org/onlinedocs/cpp/Wrapper-Headers.html
> "include_next" says to: find the next file in the search path with this
> name. That seems to indicate that the include file search path needs to be
> correctly ordered -- the implication is that there is a modified stdlib.h
> in the source being built, and it then wants to include the normal system
> stdlib.h for completeness.
>
>
> {Is it really necessary to include 8+ levels of quoting that have nothing
> relevant to the current incident?}
>
>
> --
> 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/ksvdpfpg96clk5v5a5ms4e8e5scm1kj4t6%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/CAG99bko%3D_ppfNXwd%3D1qM0f-xUQ2SJiM%3DZi4mRiXs87hbE1P9kQ%40mail.gmail.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
Dennis, to be honest, the quotes I see are only three little dots at the
end of the mail that I simply ignore. I don't know where are you reading
this, but I didn't realize that quotes may be annoying.
My apologies.

Now running make again. Let's see what happens next.

Thanks again for the support.

Regards, Jeremias.

-- 
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%2B7X7njmoeOb_kaESoAT%2BKAHMe%2BOd%3D7cE3DY_Dnd67%2B15%3DwX6w%40mail.gmail.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread jonnymo 
Jeremias,

Which Beagleboard are you compiling for?

My Beaglebone Black reports as an ARMv7 and not an ARMv8 so are you sure
that is the correct toolchain for a BB Black.

*debian@beaglebone:~$ cat /proc/cpuinfo | grep -i arm*
*model name  : ARMv7 Processor rev 2 (v7l)*


Jon

On Mon, Oct 26, 2020 at 10:25 AM 'Jeremias Ramirez' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Dennis, to be honest, the quotes I see are only three little dots at the
> end of the mail that I simply ignore. I don't know where are you reading
> this, but I didn't realize that quotes may be annoying.
> My apologies.
>
> Now running make again. Let's see what happens next.
>
> Thanks again for the support.
>
> Regards, Jeremias.
>
> --
> 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%2B7X7njmoeOb_kaESoAT%2BKAHMe%2BOd%3D7cE3DY_Dnd67%2B15%3DwX6w%40mail.gmail.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/CAG99bkqw2eZp3wVcMfbjA30%2BH_8o6wT4448e%2BmjDBDGm6nwDRg%40mail.gmail.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread 'Jeremias Ramirez' via BeagleBoard 
I just checked that and you are right, my board is a BeaglBone Black with
ARM v7.
I mixed the term cortex-8 with the Arm version.
So, I don't know why, but I've been working with this well.

I will correct it as soon as possible.

Thanks.

El lun., 26 de oct. de 2020 14:42, jonnymo  escribi贸:

> Jeremias,
>
> Which Beagleboard are you compiling for?
>
> My Beaglebone Black reports as an ARMv7 and not an ARMv8 so are you sure
> that is the correct toolchain for a BB Black.
>
> *debian@beaglebone:~$ cat /proc/cpuinfo | grep -i arm*
> *model name  : ARMv7 Processor rev 2 (v7l)*
>
>
> Jon
>
> On Mon, Oct 26, 2020 at 10:25 AM 'Jeremias Ramirez' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
>> Dennis, to be honest, the quotes I see are only three little dots at the
>> end of the mail that I simply ignore. I don't know where are you reading
>> this, but I didn't realize that quotes may be annoying.
>> My apologies.
>>
>> Now running make again. Let's see what happens next.
>>
>> Thanks again for the support.
>>
>> Regards, Jeremias.
>>
>> --
>> 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%2B7X7njmoeOb_kaESoAT%2BKAHMe%2BOd%3D7cE3DY_Dnd67%2B15%3DwX6w%40mail.gmail.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/CAG99bkqw2eZp3wVcMfbjA30%2BH_8o6wT4448e%2BmjDBDGm6nwDRg%40mail.gmail.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/CA%2B7X7njJiQFgjdqcvQ_yDDpwLWi_S7vJT0OY6UsUP_GT33EvwQ%40mail.gmail.com.

Re: [beagleboard] What is the image for bbgw that includes Node-Red with NODES FOR GROVE?

2020-10-26 Thread Julian Reyes 
Robert, are there a Nodes for Grove group? or or what does your question 
refer to? 

As an additional reference, I read this article 
(https://tech.scargill.net/beaglebone-green-wireless/ )  in which they 
mention that there is NODES FOR GROVE included in an image for BBGW.





El jueves, 22 de octubre de 2020 a la(s) 08:26:11 UTC-5, RobertCNelson 
escribi贸:

> On Thu, Oct 22, 2020 at 7:30 AM  wrote:
> >
> > I have been working with beaglebone green wireles and node red, I need 
> to use the seed grove sensors,
> > but I can't find NODES FOR GROVE that works with BBGW, I know there is 
> an image that already includes it, can you
> > please tell me which image it is and where to find it?
>
> Nodes for Grove, do you have a link to that project?
>
> 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/94208ef9-c601-4929-9c68-c1d787d8e261n%40googlegroups.com.

Re: [beagleboard] Device Tree Overlay for BeagleBone-AI

2020-10-26 Thread Deepak Khatri 
If anybody else stuck with a similar issue please follow the proper 
installation steps provided on the official site for compatibility Layer 
project -> https://deepaklorkhatri.me/GSoC2020_BeagleBoard.org/

Some updates might not be available directly and you have to install them 
with these additional steps,

   1. git clone https://github.com/beagleboard/BeagleBoard-DeviceTrees.git
   2. cd BeagleBoard-DeviceTrees
   3. sudo make install


On Friday, October 9, 2020 at 5:11:05 AM UTC+5:30 douglas...@vention.cc 
wrote:

>
>
> Thanks for the reply Robert! Just a quick update, today I was able to 
> configure some spi2 pins to interface with an ENC28J60-H development board 
> (SPI to Ethernet) with the following dts file:
>
>
> */dts-v1/;/plugin/;*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *#include /** Helper to show 
> loaded overlays under: /proc/device-tree/chosen/overlays/*/&{/chosen} {
> overlays {BONE-SPI2_0 = __TIMESTAMP__;};};/* * Update the 
> default pinmux of the pins. * See these files for the phandles (&P9_* & 
> &P8_*) * 
> BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am335x-bone-common-univ.dtsi
>  * 
> BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am572x-bone-common-univ.dtsi
>  */&ocp 
> {P9_17_pinmux { pinctrl-0 = <&P9_17_spi_cs_pin>; }; /* CS0 */   
>  //P9_23_pinmux { pinctrl-0 = <&P9_23_spi_cs_pin>; }; /* CS1 */
> P9_21_pinmux { pinctrl-0 = <&P9_21_spi_pin>; }; /* MOSI */P9_18_pinmux 
> { pinctrl-0 = <&P9_18_spi_pin>; };/* MISO */P9_22_pinmux { 
> pinctrl-0 = <&P9_22_spi_sclk_pin>; }; /* CLK */P8_07_pinmux {status = 
> "disabled";}; /* gpios reserved for RESET and INTERRUPT pins */
> P8_09_pinmux {status = "disabled";};P8_08_pinmux {status = 
> "disabled";};P8_10_pinmux {status = "disabled";};};/* * See these files 
> for the phandles (&bone_*) and other bone bus nodes * 
> BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi * 
> BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbb-bone-buses.dtsi 
> */&bone_spi_0{   
>  status = "okay";#address-cells = <1>;#size-cells = <0>;   
>  channel@0 {reg = <0>;compatible = 
> "microchip,enc28j60";pinctrl-names = "default";pinctrl-0 = 
> <&P8_09_default_pin>, <&P8_07_gpio_pin> ;//reg = 
> <0x0>;/* Use chip select 0 */
> interrupt-parent = <&gpio6>;/* Interrupt on GPIO6[18] */
> interrupts = <18 IRQ_TYPE_EDGE_FALLING>;symlink = "bone/spi/2.0";   
>  spi-max-frequency = <1600>;//spi-cpha;};};*
>
> I still need to make use of the CS1 pin mode on P9_23. However, I see in 
> *BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am572x-bone-common-univ.dtsi,*
> there is no entry for *P9_23_spi_cs_pin. *I tried adding the following 
> lines to the bone-common-univ.dtsi:
>
>
>
> *P9_23_spi_cs_pin: pinmux_P9_23_spi_cs_pin { pinctrl-single,pins = 
> ; };/* 
> spi2_cs1.spi2_cs1, mcasp1_axr1.off */*
>
> But even after a make clean, make all, the resulting dtbo will brick my 
> device..
>
> I was wondering if you had any pointers/ideas as to how I could make this 
> work? Eventually, I would like to run both channels with different 
> interrupt,chip select and rest pins as defined above.
>
> Thanks again,
>
> Doug
>
>
> On Wednesday, October 7, 2020 at 2:51:22 PM UTC-4 RobertCNelson wrote:
>
>> On Wed, Oct 7, 2020 at 11:40 AM Douglas Conover 
>>  wrote: 
>> > 
>> > Hi! Thanks for this update! I've been playing around in the device 
>> trees for a little while in the AI, basing myself on the 
>> ``am5729-beagleboneai-roboticscape.dts`` and the v4.14 kernel iot image. I 
>> have a hardware application that requires me to use two ENC28J60 ethernet 
>> adapters and the SPI 2 pins (I need two chip selects and due to potential 
>> pin conflicts I need to use SPI2). After struggling with the v4.14 
>> kernel/image, I decided to try upgrading to the 4.19 kernel/image provided 
>> in this discussion. I was wondering if this was possible by modifying some 
>> of the overlay files provided in: 
>> > 
>> > 
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
>>  
>> > 
>> > Inspecting 
>> ``BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi``,
>>  
>> I could only find the bone_spi_0 and bone_spi_1 groups. Does anyone have 
>> any pointers on enabling spi2? 
>>
>> Here is the mapping: 
>>
>>
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi#L413-L420
>>  
>>
>> 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 u

[beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread Dennis Lee Bieber 
On Mon, 26 Oct 2020 14:24:54 -0300, in gmane.comp.hardware.beagleboard.user
"'Jeremias Ramirez' via BeagleBoard"
 wrote:

>Dennis, to be honest, the quotes I see are only three little dots at the
>end of the mail that I simply ignore. I don't know where are you reading
>this, but I didn't realize that quotes may be annoying.
>My apologies.
>
I read via the gmane NNTP server. According to my newsreader, the post
I'd responded to, and trimmed, had 1520 LINES of text in it.

I suspect whatever client you are using is simply masking quoted
material by not displaying it, but it is none-the-less being included in
replies.

And... I wasn't really targetting you with the complaint. It's a
general gripe I find in forums that didn't grow up with Usenet etiquette
(or "pay per minute" connections).

https://www.ietf.org/rfc/rfc1855.txt  
Section 2.1.1 for individual email (ie: one-to-one messages)
"""
- Be brief without being overly terse.  When replying to a message,
  include enough original material to be understood but no more. It
  is extremely bad form to simply reply to a message by including
  all the previous message: edit out all the irrelevant material.
"""
Section 3.1.1 for lists and Usenet (one-to-many messages)
"""
- If you are sending a reply to a message or a posting be sure you
  summarize the original at the top of the message, or include just
  enough text of the original to give a context.  This will make
  sure readers understand when they start to read your response.
  Since NetNews, especially, is proliferated by distributing the
  postings from one host to another, it is possible to see a
  response to a message before seeing the original.  Giving context
  helps everyone.  But do not include the entire original!
"""

Unfortunately... Then came Microsoft Outlook -- which sought to produce
a business ethic in which quoted material is the equivalent of a photocopy
attached to a snail-mail letter as a courtesy for the recipient (who should
already be familiar with the content, the copy just saves them looking up
archived mails for any details they forgot), and the entire reply is
provided "above" the copy.


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

[beagleboard] Bluetooth audio not playing

2020-10-26 Thread Neil Roy 

We connected a bluetooth speaker to the Beaglebone Green Wireless and tried 
to play a sample .wav audio file using aplay and there was no sound. We 
tried using other audio players as well such as mplayer, with the same 
results. Aplay appears to be  trying to play the audio file, but when we 
use mplayer it keeps saying "Audio device got stuck!" Any suggestions?

-- 
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/b37d394c-9af7-45a6-b585-b32fb86d8f5bn%40googlegroups.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-26 Thread jonnymo 
I believe if you respond directly from the Google Groups Beagleboard Forum
it will automatically add the previous conversation content.  If you extend
the '...' then you will see what is being added.  I just respond directly
in GMail and avoid the quotes unless I find them necessary.

Jeremias,

If you want to take the discussion offline I am cool with that.

Jon


On Mon, Oct 26, 2020 at 12:50 PM Dennis Lee Bieber <
dennis.l.bie...@gmail.com> wrote:

> On Mon, 26 Oct 2020 14:24:54 -0300, in gmane.comp.hardware.beagleboard.user
> "'Jeremias Ramirez' via BeagleBoard"
>  wrote:
>
> >Dennis, to be honest, the quotes I see are only three little dots at the
> >end of the mail that I simply ignore. I don't know where are you reading
> >this, but I didn't realize that quotes may be annoying.
> >My apologies.
> >
> I read via the gmane NNTP server. According to my newsreader, the
> post
> I'd responded to, and trimmed, had 1520 LINES of text in it.
>
> I suspect whatever client you are using is simply masking quoted
> material by not displaying it, but it is none-the-less being included in
> replies.
>
> And... I wasn't really targetting you with the complaint. It's a
> general gripe I find in forums that didn't grow up with Usenet etiquette
> (or "pay per minute" connections).
>
> https://www.ietf.org/rfc/rfc1855.txt
> Section 2.1.1 for individual email (ie: one-to-one messages)
> """
> - Be brief without being overly terse.  When replying to a message,
>   include enough original material to be understood but no more. It
>   is extremely bad form to simply reply to a message by including
>   all the previous message: edit out all the irrelevant material.
> """
> Section 3.1.1 for lists and Usenet (one-to-many messages)
> """
> - If you are sending a reply to a message or a posting be sure you
>   summarize the original at the top of the message, or include just
>   enough text of the original to give a context.  This will make
>   sure readers understand when they start to read your response.
>   Since NetNews, especially, is proliferated by distributing the
>   postings from one host to another, it is possible to see a
>   response to a message before seeing the original.  Giving context
>   helps everyone.  But do not include the entire original!
> """
>
> Unfortunately... Then came Microsoft Outlook -- which sought to
> produce
> a business ethic in which quoted material is the equivalent of a photocopy
> attached to a snail-mail letter as a courtesy for the recipient (who should
> already be familiar with the content, the copy just saves them looking up
> archived mails for any details they forgot), and the entire reply is
> provided "above" the copy.
>
>
> --
> 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/h49epf9b24efhlrsimfue7or7pb3u4h8bv%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/CAG99bkoBwZC-_CT%3D4YLAjSE6ZUioOxaB%2BY%2Bbf7j_Y%2BmzZfoB%2BQ%40mail.gmail.com.

Re: [beagleboard] What is the image for bbgw that includes Node-Red with NODES FOR GROVE?

2020-10-26 Thread Julian Reyes 
Thanks a lot Robert, it works!

What about sensors? Do you have an example? I have a Seeed Temperature 
Sensor, using node-red how can I get temperature?

El lunes, 26 de octubre de 2020 a la(s) 13:15:04 UTC-6, RobertCNelson 
escribi贸:

> On Mon, Oct 26, 2020 at 2:05 PM Julian Reyes  
> wrote:
> >
> > Robert, are there a Nodes for Grove group? or or what does your question 
> refer to?
> >
> > As an additional reference, I read this article (
> https://tech.scargill.net/beaglebone-green-wireless/ ) in which they 
> mention that there is NODES FOR GROVE included in an image for BBGW.
>
>
> Oh, that was from 2016, that ended. It was replaced in a generic way..
>
> Here is a quick example..
>
> https://gist.github.com/RobertCNelson/db447839232261a054af8008440d86b4
>
> Just click import, it'll look like attached..
>
> Just make sure you have the latest version of bb-node-red-installer to
> fix a gpio issue..
>
> debian@beaglebone:/var/lib/cloud9$ dpkg --list | grep node-red
> ii bb-node-red-installer
> 1.2.2-0rcnee2~buster+20201021 armhf Node-RED
> installer for beagleboard.org
>
> 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/52071ec4-b98e-436e-84a4-0fff189f2fbfn%40googlegroups.com.

[beagleboard] Re: What is the image for bbgw that includes Node-Red with NODES FOR GROVE?

2020-10-26 Thread Dennis Lee Bieber 


Sliding into this thread...

On Mon, 26 Oct 2020 15:03:52 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Julian Reyes
 wrote:

>What about sensors? Do you have an example? I have a Seeed Temperature 
>Sensor, using node-red how can I get temperature?

Seeed/Grove has many types of temperature (and humidity) sensors.

https://www.seeedstudio.com/Grove-Temperature-Sensor.html
Is a thermistor design. It outputs an analog voltage which you then scale
(using parameters provided in the documentation) to determine the
temperature. PROBLEM: Beaglebone ADC inputs max at 1.8V; if you power this
version with a 3.3V feed, you will need to use a voltage divider to reduce
the 0.0-3.3V output into 0.0-1.8V. You also need to connect it to one of
the pins that is configured as ADC input, NOT GPIO.

https://www.seeedstudio.com/Grove-Temperature-Humidity-Sensor-DHT11.html
uses a DHT-11. The DHT-11 has a very complex protocol in which one has to
measure the length of high/low pulses to determine if a 1 or 0 bit is being
output. Using compiled (C/C++ or assembler) MAY allow a program running in
the Linux realm to successfully read such a unit, but native Python or
Javascript (which, as I understand it, is what gets run through the
Node-Red interface) is not fast enough to reliably read one of these.

https://www.seeedstudio.com/Grove-BME280-Environmental-Sensor-Temperature-Humidity-Barometer.html
uses the BME280 chip. This sensor has both I2C and SPI interface modes.
Reading such requires connecting to pins that are configured for either I2C
or SPI, and issuing commands followed by reading the return data. The good
news, the data IS in binary (it may need some scaling, but has no analog to
timing based problems).

https://www.seeedstudio.com/Grove-I2C-High-Accuracy-Temperature-Sensor-MCP9808.html
is another I2C interface type

https://www.seeedstudio.com/DS18B20-Temperature-Sensor-1-Wire-Digital-Thermometer-p-4281.html
is a Dallas Semiconductor (now Maxim) "1-wire" protocol
https://en.wikipedia.org/wiki/1-Wire


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

Re: [beagleboard] What is the image for bbgw that includes Node-Red with NODES FOR GROVE?

2020-10-26 Thread Robert Nelson 
On Mon, Oct 26, 2020 at 5:04 PM Julian Reyes  wrote:
>
> Thanks a lot Robert, it works!
>
> What about sensors? Do you have an example? I have a Seeed Temperature 
> Sensor, using node-red how can I get temperature?

So the "Beaglebone-io" library that i used in that example can do analog..

Here's the full readme:

https://www.npmjs.com/package/beaglebone-io

Sorry i don't have an example, from Johnny5 grab the gpio-in, then
change it to "analog pin".. (attached..)

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/CAOCHtYgHqhgOC1-YBBtHpU0sz5wMeUJ%3DUX5YpAzY2g2gSDxShg%40mail.gmail.com.

Re: [beagleboard] What is the image for bbgw that includes Node-Red with NODES FOR GROVE?

2020-10-26 Thread Robert Nelson 
On Mon, Oct 26, 2020 at 7:25 PM Robert Nelson  wrote:
>
> On Mon, Oct 26, 2020 at 5:04 PM Julian Reyes  
> wrote:
> >
> > Thanks a lot Robert, it works!
> >
> > What about sensors? Do you have an example? I have a Seeed Temperature 
> > Sensor, using node-red how can I get temperature?
>
> So the "Beaglebone-io" library that i used in that example can do analog..
>
> Here's the full readme:
>
> https://www.npmjs.com/package/beaglebone-io
>
> Sorry i don't have an example, from Johnny5 grab the gpio-in, then
> change it to "analog pin".. (attached..)

That seems to work pretty well..

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/CAOCHtYgxLuGcmB8ETfSxNFmPKSyx3Ti3iHPvYaesJXJnXRQM0Q%40mail.gmail.com.