Re: [beagleboard] Re: CLoud9 TIDL example sees CMEM Error after recent upgrade

Okay, you need to change the port in the extras/mjpg-stream.html to get it to work with the way Jason has it set: debian@beaglebone:/var/lib/cloud9/common$ cat ../extras/mjpg-stream.html /*global location*/ var element = document.getElementById("mjpg-iframe"); element.src = "

Re: [beagleboard] Display still compatable

On Fri, Mar 27, 2020 at 3:22 PM KenUnix wrote: > > > Can you tell me is the > > GEN4-4DCAPE-43CT-CLB - > > BeagleBone Black Cape, LCD, 4.3", Capacitive Touchscreen with Cover Lens Beze > > > still supported under Debian 9 stretch on the BBB with kernel 4.19 > and can this device be written to, to

Re: [beagleboard] Re: CLoud9 TIDL example sees CMEM Error after recent upgrade

Where does one define this? The error occurs when launching MJPG-Streamer from the Cloud9 interface. Why change the port to 8090? Jon On Fri, Mar 27, 2020 at 12:51 PM Dennis Lee Bieber < dennis.l.bie...@gmail.com> wrote: > On Fri, 27 Mar 2020 11:48:35 -0700, in gmane.comp.hardware.beagleboard

[beagleboard] Display still compatable

Can you tell me is the GEN4-4DCAPE-43CT-CLB - BeagleBone Black Cape, LCD, 4.3", Capacitive Touchscreen with Cover Lens Beze still supported under Debian 9 stretch on the BBB with kernel 4.19 and can this device be written to, to just display information? Thanks -- For more options, visit ht

Re: [beagleboard] libgpiod on Beaglebone AI

On Fri, Mar 27, 2020 at 8:45 PM John Allwine wrote: > > I don't intend to toggle a GPIO as fast as possible (except to test), but > from a performance standpoint that demonstration seemed to indicate that > there are issues with sysfs. Hopefully, libgpiod will prove to be better! Bartosz explai

[beagleboard] Re: CLoud9 TIDL example sees CMEM Error after recent upgrade

On Fri, 27 Mar 2020 11:48:35 -0700, in gmane.comp.hardware.beagleboard.user jonnymo wrote: >Cool, thanks. > >Oh, with Jason's change, I get the following error due to the port being >set to 8090. >Unable to connect > > >*Firefox can’t establish a connection to the server at 192.168.2.210:8080 >

Re: [beagleboard] libgpiod on Beaglebone AI

I don't intend to toggle a GPIO as fast as possible (except to test), but from a performance standpoint that demonstration seemed to indicate that there are issues with sysfs. Hopefully, libgpiod will prove to be better! -- For more options, visit http://beagleboard.org/discuss --- You receive

Re: [beagleboard] libgpiod on Beaglebone AI

On Fri, Mar 27, 2020 at 11:46 AM Drew Fustini wrote: > On Fri, Mar 27, 2020 at 4:48 PM John Allwine > wrote: > > > > That was it! gpioget gpiochip3 10 worked. > > It would be interesting to know if libgpiod proves fast enough for > your application. It has C++ and Python bindings that allow you

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

Cool, thanks. Oh, with Jason's change, I get the following error due to the port being set to 8090. Unable to connect *Firefox can’t establish a connection to the server at 192.168.2.210:8080 .* *If I change it back to 8080, it seems to work.* Cheers, Jon On Fri, M

[beagleboard] Re: how to access GPIO on Beaglebone AI via /dev/mem

Here[1] are some notes I wrote for my students for accessing GPIO via /dev/mem on the BB Black. I'm not sure how much carries over to the AI. --Mark [1] https://elinux.org/EBC_Exercise_11b_gpio_via_mmap On Friday, March 27, 2020 at 1:13:57 PM UTC-4, Dennis Bieber wrote: > > On Fri, 27 Mar 2020

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

On Fri, Mar 27, 2020 at 1:27 PM jonnymo wrote: > Jason, > > Thanks. > > What are you referring to with regards to "making it continue to work with > older kernels"? > > As far as understand it, the kernel on my BBAI is updated to the latest > 4.14 kernel; well at least to 4.14.108-ti-r131 from a

[beagleboard] Re: PRU phandle is changing

Which kernel version are you using? Can you post your DTS changes? Yes, it is expected phandle to have different value for different DTBs. See https://elinux.org/Device_Tree_Mysteries#Phandle Personally I found it much easier to use rpmsg, which sits on top of remoteproc. The mainline example

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

Jason, Thanks. What are you referring to with regards to "making it continue to work with older kernels"? As far as understand it, the kernel on my BBAI is updated to the latest 4.14 kernel; well at least to 4.14.108-ti-r131 from a few days ago.. Is this supported on 4.19 or later now? Cheers,

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

On Fri, Mar 27, 2020 at 7:07 AM Jason Kridner wrote: > Any thoughts on making it more generic? Select the highest index? > > On Thu, Mar 26, 2020 at 10:22 PM jonnymo wrote: > >> In the GitHub issue that was filed, I noted the following which seems to >> get the camera active again: >> >> >> >> S

[beagleboard] Re: how to access GPIO on Beaglebone AI via /dev/mem

On Fri, 27 Mar 2020 05:37:02 -0700 (PDT), in gmane.comp.hardware.beagleboard.user John Allwine wrote: >What is or how do I find the control register address for the AM5x? The system >manual > > seems >to l

Re: [beagleboard] libgpiod on Beaglebone AI

On Fri, Mar 27, 2020 at 4:48 PM John Allwine wrote: > > That was it! gpioget gpiochip3 10 worked. It would be interesting to know if libgpiod proves fast enough for your application. It has C++ and Python bindings that allow you to set and get multiple lines on a gpiochip with a single ioctl().

[beagleboard] Latest Image - Spring 2020 Release - Final RC

Our Final RC is now up, sorry it took a little longer this week! For those BeagleBone-AI/X15 users you may have noticed the massively updated OpenCL/TIDL stack.. We are now feature parity with TI's SDK 06.02.00.81! (We even have the same x15 OpenCL + v4.19.x-ti bug) So the Buster TIDL image is n

Re: [beagleboard] libgpiod on Beaglebone AI

That was it! gpioget gpiochip3 10 worked. Thanks Robert! On Friday, March 27, 2020 at 9:42:15 AM UTC-6, RobertCNelson wrote: > > On Fri, Mar 27, 2020 at 10:34 AM John Allwine > wrote: > > > > I'm looking into using libgpiod to control the GPIO on the Beaglebone AI > in user space. I'm startin

Re: [beagleboard] libgpiod on Beaglebone AI

On Fri, Mar 27, 2020 at 10:34 AM John Allwine wrote: > > I'm looking into using libgpiod to control the GPIO on the Beaglebone AI in > user space. I'm starting small and trying to use the included command line > tools gpioget and gpioset, but not having any success. > > The Beaglebone AI System

[beagleboard] libgpiod on Beaglebone AI

I'm looking into using libgpiod to control the GPIO on the Beaglebone AI in user space. I'm starting small and trying to use the included command line tools gpioget and gpioset, but not having any success. The Beaglebone AI System Manual

[beagleboard] emmc or sd write protect

Is it possible to write protect either or both the on-board emmc or SD card memories after flashing? I would like to verify nothing was written, no code change or malicious code present, upon return of the BBB for service. -- For more options, visit http://beagleboard.org/discuss --- You re

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

Thanks! This fixed my problems for me. On Friday, March 27, 2020 at 3:23:17 AM UTC+1, jonnymo wrote: > > In the GitHub issue that was filed, I noted the following which seems to > get the camera active again: > > > > Setting '-d /dev/video1' in the common Makefile seemed to do the trick. I >

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

I am not sure and would have to look at it a bit closer. Perhaps checking whether or not there is something attached to the video device or show a list of possible video devices and prompt the user to select one. I suppose they would need to know which video device is the active one though. C

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

Yeah, I tried the Makefile in the classification example and it did not do anything. I had to hunt around and found the examples originated the build in the common Makefile so I changed it there and it seems to work. I too have a Logitech C920. Cheers, Jon On Friday, March 27, 2020 at 6:25:

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

That works! Thank you I tested out 5 webcams with both dummy.tidl and classificatin.tidl 1. Logitech C920 webcam works 2. VERY Old Creative VF0230 webcam - did not work 3. VERY Old trinket AMD Smarter Choice webcam -images torn up with overread errors-n as n goes randomly from 1 to 8 4. OLD Silico

Re: [beagleboard] how to access GPIO on Beaglebone AI via /dev/mem

> Dynamic pinmux changes on AM5x have issues specific to AM5x. > > For GPIO, accessing via register writes in userspace (/dev/mem) has no > more negative consequences than on AM3x or on any system running Linux for > that matter. Standard caveats apply. > > Ideally, we’d create a kernel modul

Re: [beagleboard] how to access GPIO on Beaglebone AI via /dev/mem

Dynamic pinmux changes on AM5x have issues specific to AM5x. For GPIO, accessing via register writes in userspace (/dev/mem) has no more negative consequences than on AM3x or on any system running Linux for that matter. Standard caveats apply. Ideally, we’d create a kernel module to avoid latency

Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade

Any thoughts on making it more generic? Select the highest index? On Thu, Mar 26, 2020 at 10:22 PM jonnymo wrote: > In the GitHub issue that was filed, I noted the following which seems to > get the camera active again: > > > > Setting '-d /dev/video1' in the common Makefile seemed to do the tri

Re: [beagleboard] how to access GPIO on Beaglebone AI via /dev/mem

You my want to consider using libgpiod with the /dev/gpiochipN character device. You can get and set multiple lines in one syscall. The libgpiod tools are installed on the Debian image. More info: https://www.cnx-software.com/2017/11/03/learn-more-about-linuxs-new-gpio-user-space-subsystem-libgp

Re: [beagleboard] how to access GPIO on Beaglebone AI via /dev/mem

Hello Robert, if I get this correctly, setting the direction of a gpio via the corresponding register (e.g. let's say gpio4 base_addr + 0x134) should be avoided? We use the BBB in combination with a carrier-board to have some industrial in- and outputs. Therefore, some pins enable some flipfl