Re: [beagleboard] BBB desktop manager output resolution when disabled?

[Michael Ascenzi]

so looking at the BBB documentation

[image: hdmi.jpg]
so these are just the supported resolutions for the BBB correct?

In my case, the EVM would have its default resolution associated with it, 
which is what the BBB would be set to. Correct? 

Would changing the resolution via Xrandr have any affect on the image 
transfer rate from the BBB to the EVM? I don't have access to the BBB & EVM 
at the moment. At the office. or else I would try it. I'll try to head  
into the office tomorrow. 

Speaking with the guys over at TI, the EVM is set to a default rate of 60hz 
based on the data being piped over the parallel video input. They say that 
the EVM will update at 60hz, but the week link is the speed at which the 
BBB can load and push the image files over the parrallel video input. 

right now we have an oscilloscope connected to the vsync pin of the gpio on 
the BBB. Which is part of the parrellel video input.  We assumed that the 
BBB was working at 24hz cause of what we were seeing on the scope. This is 
our suspicion because when we measured VSYNC directly on the beagle using 
the P8 expansion header (pin 27 lcd_vsync) and an oscilloscope we measured 
23.6 Hz (basically round up and its 24 Hz). 

Any thoughts?

Michael


On Tuesday, March 24, 2020 at 10:40:18 PM UTC-4, RobertCNelson wrote:
>
>
>
> On Tue, Mar 24, 2020, 9:32 PM Michael Ascenzi  > wrote:
>
>> Robert, 
>>
>> So I'm not actually connecting an HDMI to the BBB. The EVM is a projector 
>> cape that we have sitting ontop of the BBB. 
>>
>> So if nothings plugged in, as you said, it would use a small old 
>> framebruffer. So the question is does that old framebruffer have a default 
>> resolution with a transfer speed? or can it be adjusted?
>>
>
>
> I thought that was the case, but was confused when you stated.
>
> 1920x1080 @24hz
>
> Which isn't the true case, it's running the resolution of the projector..
>
> Regards,
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b865cbbf-7acf-4a1e-b94d-e52aab6c4980%40googlegroups.com.

Re: [beagleboard] BBB desktop manager output resolution when disabled?

[Robert Nelson]

On Tue, Mar 24, 2020, 9:32 PM Michael Ascenzi  wrote:

> Robert,
>
> So I'm not actually connecting an HDMI to the BBB. The EVM is a projector
> cape that we have sitting ontop of the BBB.
>
> So if nothings plugged in, as you said, it would use a small old
> framebruffer. So the question is does that old framebruffer have a default
> resolution with a transfer speed? or can it be adjusted?
>


I thought that was the case, but was confused when you stated.

1920x1080 @24hz

Which isn't the true case, it's running the resolution of the projector..

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjT%3DkUi3N8CwBWNVMB7ZrhtxE7BNMDWBcJyDHYBJ61%3D5w%40mail.gmail.com.

Re: [beagleboard] BBB desktop manager output resolution when disabled?

[Michael Ascenzi]

Robert, 

So I'm not actually connecting an HDMI to the BBB. The EVM is a projector 
cape that we have sitting ontop of the BBB. 

So if nothings plugged in, as you said, it would use a small old 
framebruffer. So the question is does that old framebruffer have a default 
resolution with a transfer speed? or can it be adjusted?

Michael

On Tuesday, March 24, 2020 at 10:04:42 PM UTC-4, RobertCNelson wrote:
>
> On Tue, Mar 24, 2020 at 8:57 PM Michael Ascenzi  > wrote: 
> > 
> > I'm working with the BBB with the utilization of the DLP2000 EVM cape 
> from TI. I'm having difficulties with the speed at which I can transfer 
> 640x320 images across across to the EVM. 
> > 
> > One thing that has been asked has to do with the desktop manager and the 
> image that rendered from the manager. The default resolution of the BBB is 
> 1920x1080 @24hz. Now obviously we can modify the resolution by using xrandr 
> to switch up the resolution to 640x480 so that it would run at 60hz. 
> > 
> > Part of the software that takes the images and transfer them over the 
> framebuffer to the EVM is a command to shutdown the desktop manager. If I 
> don't shutdown the manager, when I send over a frame, there's a chance that 
> the desktop can insert its own image between the images I'm sending. This 
> is an issue, as I need the images I'm sending and only those images. 
> > 
> > So my question is whats the resolution of the BBB if I disable the 
> desktop manager? is it still 1920x1080? or is that no longer a factor? 
> > 
> > I might be completely off base in my understanding this, I'm guessing 
> that I am. If i disable the desktop manager, do I still have control over 
> the screen resolution with xrandr? 
>
> The desktop manager get's the default list of resolutions from the 
> monitor plugged into the HDMI port. 
>
> You can either, not have anything plugged in, and it'll use a small 
> old framebufffer default, or override the edid values thru a kernel 
> boot arg listed in /boot/uEnv.txt... 
>
> 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/829a76e3-93b2-4f05-bb4b-f012ba4731e9%40googlegroups.com.

Re: [beagleboard] UART to USB adapter causes USB port to fail

[Zeph]

Thank you for this! I was able to get it working by externally powering the 
lidar before starting the BeagleBone.

On Tuesday, March 24, 2020 at 5:39:29 PM UTC-7, Jim F wrote:
>
> Looks like you're using too much power from the USB. Maybe you can run 
> your device from its own power instead of off the bus.
>
> On Tue, Mar 24, 2020 at 8:11 PM Zeph > 
> wrote:
>
>> I am using a BeagleBone Black with Ubuntu 18.04 and I am attempting to 
>> use an SLAMTEC RPLidar A3M1 which uses a UART to USB adapter to connect to 
>> a computer. I was able to get this to work with my laptop running Ubuntu 
>> 18.04. When I plug in the adapter, I can see the device appears in the /dev 
>> folder as ttyUSB0.
>>
>> When I plug the adapter into the BeagleBone there is no /dev/ttyUSB0 and 
>> nothing shows up in lsusb. 
>>
>> dmesg shows the following after plugging in:
>> [  272.262281] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, <
>> AValid), retry #1, port1 0104
>> [  272.319876] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <
>> AValid), retry #2, port1 0104
>> [  272.377607] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <
>> AValid), retry #3, port1 0104
>> [  272.435203] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, <
>> AValid), retry #3, port1 0008010c
>>
>>
>> Once the adapter is plugged in, no other USB devices are recognized by 
>> the BeagleBone anymore.
>>
>> Is it possible to get this device to work with the BeagleBone or should I 
>> give up on using this device?
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/57393ee1-51d0-447f-ab74-c6660fa8e989%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/2bd0c20d-c8a7-4604-ada8-e19f7ec1132d%40googlegroups.com.

Re: [beagleboard] BBB desktop manager output resolution when disabled?

[Robert Nelson]

On Tue, Mar 24, 2020 at 8:57 PM Michael Ascenzi  wrote:
>
> I'm working with the BBB with the utilization of the DLP2000 EVM cape from 
> TI. I'm having difficulties with the speed at which I can transfer 640x320 
> images across across to the EVM.
>
> One thing that has been asked has to do with the desktop manager and the 
> image that rendered from the manager. The default resolution of the BBB is 
> 1920x1080 @24hz. Now obviously we can modify the resolution by using xrandr 
> to switch up the resolution to 640x480 so that it would run at 60hz.
>
> Part of the software that takes the images and transfer them over the 
> framebuffer to the EVM is a command to shutdown the desktop manager. If I 
> don't shutdown the manager, when I send over a frame, there's a chance that 
> the desktop can insert its own image between the images I'm sending. This is 
> an issue, as I need the images I'm sending and only those images.
>
> So my question is whats the resolution of the BBB if I disable the desktop 
> manager? is it still 1920x1080? or is that no longer a factor?
>
> I might be completely off base in my understanding this, I'm guessing that I 
> am. If i disable the desktop manager, do I still have control over the screen 
> resolution with xrandr?

The desktop manager get's the default list of resolutions from the
monitor plugged into the HDMI port.

You can either, not have anything plugged in, and it'll use a small
old framebufffer default, or override the edid values thru a kernel
boot arg listed in /boot/uEnv.txt...

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/CAOCHtYgC8BYtApnS%2BUL%3DzF6m8h7i_Gj4ZzAov_ycVFQ9JDXdjA%40mail.gmail.com.

Re: [beagleboard] I can't install beaglebone specific nodes

[Robert Nelson]

On Tue, Mar 24, 2020 at 7:41 PM Son Le  wrote:
>
> I can't install beaglebone specific nodes when update latest image,
> Help me resolve it, thanks.

Please be more specific, of exactly what you are trying to install,
then maybe we can assist you..

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

[beagleboard] Beagle Board communication with PC

[praveentpf]

Hi There

I need some help with the communication between a Beagle Board and a PC , 

- I am using a Acer SP513-52N with Windows 10.  

- I have installed the Bone_D64.ex

I have not been able to connect to the BB as the Linux USB Ethernet /RNDIS 
Gadget does not appear in the Ports (COM & LPT) in Manage Devices

192.168.7.2 does not respond! 

Can some one help

Thanks

Ferdie


-- 
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/e56f56b7-d3c2-4b29-88f8-aac4f82ab246%40googlegroups.com.

[beagleboard] BBB desktop manager output resolution when disabled?

[Michael Ascenzi]

I'm working with the BBB with the utilization of the DLP2000 EVM cape from 
TI. I'm having difficulties with the speed at which I can transfer 640x320 
images across across to the EVM. 

One thing that has been asked has to do with the desktop manager and the 
image that rendered from the manager. The default resolution of the BBB is 
1920x1080 @24hz. Now obviously we can modify the resolution by using xrandr 
to switch up the resolution to 640x480 so that it would run at 60hz. 

Part of the software that takes the images and transfer them over the 
framebuffer to the EVM is a command to shutdown the desktop manager. If I 
don't shutdown the manager, when I send over a frame, there's a chance that 
the desktop can insert its own image between the images I'm sending. This 
is an issue, as I need the images I'm sending and only those images. 

So my question is whats the resolution of the BBB if I disable the desktop 
manager? is it still 1920x1080? or is that no longer a factor?

I might be completely off base in my understanding this, I'm guessing that 
I am. If i disable the desktop manager, do I still have control over the 
screen resolution with xrandr?


-- 
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/a9ed8453-b322-4c5b-a222-b992f2823fb2%40googlegroups.com.

Re: [beagleboard] "Address already in use" errors in TIDL examples

[Bernard Fischer]

I played around with the camera some more and figured out that it actually 
is working.  I could see output from guvcview.  Unfortunately, now I can't 
get the little popup window with MJPGstreamer.  I can open the window from 
the url that's output by the script and see the classification. I don't 
know why it worked the one time, but not now.  It's a puzzle.

On Sunday, March 22, 2020 at 8:42:37 AM UTC-5, Bernard Fischer wrote:
>
> Thanks.  I checked the makefiles.  The Makefile in the TIDL directory has 
> this block
> run:
> ti-mct-heap-check -c
> mjpg_streamer -i "input_opencv.so -r 640x480 --filter ./
> classification.tidl.so" -o "output_http.so -p 8090 -w 
> /usr/share/mjpg-streamer/www" 2> /dev/null
>
> while the Makefile in ../common has
>
> start:
> ifneq ($(PRU_DIR),)
> @echo write_init_pins.sh
> @$(COMMON)/write_init_pins.sh /lib/firmware/$(CHIP)-pru$(PRUN)-fw
> @echo "-Starting PRU $(PRUN)"
> @echo start > $(PRU_DIR)/state
> else ifeq ($(PROC),tidl)
> ti-mct-heap-check -c
> sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter 
> ./$(TARGET)$(EXE)" -o "output_http.so -p 8080 -w 
> /usr/share/mjpg-streamer/www"
> else
> ./$(TARGET)$(EXE)
> endif
>
> Since the error message referenced "start" I changed the port to 8090 to 
> match the tidl Makefile.  I got no errors but I didn't get an image on 
> MJPGStreamer either.   I don't know if it's my camera but it is there in 
> linux
>
> debian@beaglebone:/var/lib/cloud9$ v4l2-ctl --list-devices
> TTQ 8MP Camera: TTQ 8MP Camera (usb-xhci-hcd.1.auto-1):
> /dev/video0
>
> thanks
>
> On Saturday, March 21, 2020 at 8:35:53 PM UTC-5, RobertCNelson wrote:
>>
>> On Sat, Mar 21, 2020 at 8:30 PM Bernard Fischer 
>>  wrote: 
>> > 
>> > When I try to run the "classification" or "dummy" AI examples in 
>> Cloud9, I get the following errors 
>> > 
>> > bind: Address already in use 
>> > 
>> > bind: Address already in use 
>> > 
>> > o: server_thread(): bind(8080) failed 
>> > 
>> > /var/lib/cloud9/common/Makefile:169: recipe for target 'start' failed 
>> > 
>> > I can't tell what is generating this error, or what the address refers 
>> to.  Does it refer to the URL for mjpgstreamer? 
>>
>> 8080 is user port on nginx, to see /var/www/html/ 
>>
>> (Cloud9 is proxy'ed thru nginx).. 
>>
>> @Jason Kridner  is that demo correct with nginx serving traffic on 8080? 
>>
>> 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/48296f7a-07de-44f9-a28c-c394ab293918%40googlegroups.com.

[beagleboard] I can't install beaglebone specific nodes

[Son Le]

I can't install beaglebone specific nodes when update latest image,
Help me resolve it, thanks.

-- 
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/b09c8e21-5e73-4b1f-ad11-66a70e09c914%40googlegroups.com.

Re: [beagleboard] UART to USB adapter causes USB port to fail

[Jim F]

Looks like you're using too much power from the USB. Maybe you can run your
device from its own power instead of off the bus.

On Tue, Mar 24, 2020 at 8:11 PM Zeph  wrote:

> I am using a BeagleBone Black with Ubuntu 18.04 and I am attempting to use
> an SLAMTEC RPLidar A3M1 which uses a UART to USB adapter to connect to a
> computer. I was able to get this to work with my laptop running Ubuntu
> 18.04. When I plug in the adapter, I can see the device appears in the /dev
> folder as ttyUSB0.
>
> When I plug the adapter into the BeagleBone there is no /dev/ttyUSB0 and
> nothing shows up in lsusb.
>
> dmesg shows the following after plugging in:
> [  272.262281] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, <
> AValid), retry #1, port1 0104
> [  272.319876] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <
> AValid), retry #2, port1 0104
> [  272.377607] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <
> AValid), retry #3, port1 0104
> [  272.435203] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, <
> AValid), retry #3, port1 0008010c
>
>
> Once the adapter is plugged in, no other USB devices are recognized by the
> BeagleBone anymore.
>
> Is it possible to get this device to work with the BeagleBone or should I
> give up on using this device?
>
> --
> 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/57393ee1-51d0-447f-ab74-c6660fa8e989%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/CAGS%2B2h_gBAPco_Tny0SymJTfaDti_Jqv%2B6atAUx5tiiK%3DRvxbg%40mail.gmail.com.

[beagleboard] UART to USB adapter causes USB port to fail

[Zeph]

I am using a BeagleBone Black with Ubuntu 18.04 and I am attempting to use 
an SLAMTEC RPLidar A3M1 which uses a UART to USB adapter to connect to a 
computer. I was able to get this to work with my laptop running Ubuntu 
18.04. When I plug in the adapter, I can see the device appears in the /dev 
folder as ttyUSB0.

When I plug the adapter into the BeagleBone there is no /dev/ttyUSB0 and 
nothing shows up in lsusb. 

dmesg shows the following after plugging in:
[  272.262281] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, 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/57393ee1-51d0-447f-ab74-c6660fa8e989%40googlegroups.com.

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

[Robert Nelson]

On Tue, Mar 24, 2020 at 7:07 PM Robert Nelson  wrote:
>
> On Tue, Mar 24, 2020 at 6:57 PM Jon Morss  wrote:
> >
> > Hey Robert,
> >
> > Cool.  Thanks.
> >
> > However, I now end up with a different error:
> >
> > NOTE: I did an upgrade after the update. Also, the update_kernel bumped my 
> > kernel to r131 from r130.
> > info: you are running: [4.14.108-ti-r130], latest is: [4.14.108-ti-r131] 
> > updating...
> >
> > The result of removing and installing the cmem modules:
> > debian@beaglebone:~$ sudo apt remove ti-cmem-4.15.00.02-modules-`uname -r` 
> > --purge
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Package 'ti-cmem-4.15.00.02-modules-4.14.108-ti-r131' is not installed, so 
> > not removed
> > The following packages were automatically installed and are no longer 
> > required:
> >   bb-beaglebone-io-installer bb-johnny-five-installer
> >   ti-c6000-cgt-v8.2.x-installer
> > Use 'sudo apt autoremove' to remove them.
> > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
> >
> > debian@beaglebone:~$ sudo apt install ti-cmem-4.16.00.00-modules-`uname -r`
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > ti-cmem-4.16.00.00-modules-4.14.108-ti-r131 is already the newest version 
> > (1stretch).
> > The following packages were automatically installed and are no longer 
> > required:
> >   bb-beaglebone-io-installer bb-johnny-five-installer
> >   ti-c6000-cgt-v8.2.x-installer
> > Use 'sudo apt autoremove' to remove them.
> > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
>
>
> The stack switched to ti-c6000-cgt-v8.3
>
> > Error from TIDL classification example:
> >
> > Started /var/lib/cloud9/: classification.tidl.cpp
> > File path: /var/lib/cloud9/BeagleBone/AI/tidl
> > File: /var/lib/cloud9/BeagleBone/AI/tidl/classification.tidl.cpp
> > Arguments:
> > File name: classification.tidl.cpp
> > File extension: cpp
> > File base name: classification.tidl
> > Packages: ~.c9/packages
> > Project path: /var/lib/cloud9/
> > Project name: projectname
> > Hostname: localhost
> > Hostname path: https://undefined/BeagleBone/AI/tidl/classification.tidl.cpp
> > URL: http://localhost
> > Port: 8080
> > IP: 0.0.0.0
> > Command: BeagleBone/AI/tidl/classification.tidl.cpp
> > Python: python3
> > Python path: 
> > /usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
> > /var/lib/cloud9/common/Makefile:28: 
> > MODEL=BeagleBoard.org_BeagleBone_AI,TARGET=classification.tidl,COMMON=/var/lib/cloud9/common
> > /var/lib/cloud9/common/Makefile:147: 
> > GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PROC=tidl,PRUN=,PRU_DIR=,EXE=.so
> > CXX classification.tidl.cpp
> > LD  /tmp/cloud9-examples/classification.tidl.o
> > ti-mct-heap-check -c
> > sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter 
> > ./classification.tidl.so" -o "output_http.so -p 8080 -w 
> > /usr/share/mjpg-streamer/www"
> > [sudo] password for debian:
> > MJPG Streamer Version.: 2.0
> >  i: device... : default
> >  i: Desired Resolution: 640 x 480
> > Unable to stop the stream: Invalid argument
> >  i: VideoCapture::open() failed
> > /var/lib/cloud9/common/Makefile:169: recipe for target 'start' failed
> > make: *** [start] Error 1
> > rm /tmp/cloud9-examples/classification.tidl.o

Oh and with r131, there's a new "/dev/video0" device now available,
the guys at TI have a got a way to utilze that internal processor to
do things even faster..

Thus your old usb webcam is no londer /dev/video0...

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/CAOCHtYgGxaOuwVUq09ZSY564iBOdTFg%2BZ6pUO_7dZychGhvWiQ%40mail.gmail.com.

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

[Robert Nelson]

On Tue, Mar 24, 2020 at 6:57 PM Jon Morss  wrote:
>
> Hey Robert,
>
> Cool.  Thanks.
>
> However, I now end up with a different error:
>
> NOTE: I did an upgrade after the update. Also, the update_kernel bumped my 
> kernel to r131 from r130.
> info: you are running: [4.14.108-ti-r130], latest is: [4.14.108-ti-r131] 
> updating...
>
> The result of removing and installing the cmem modules:
> debian@beaglebone:~$ sudo apt remove ti-cmem-4.15.00.02-modules-`uname -r` 
> --purge
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package 'ti-cmem-4.15.00.02-modules-4.14.108-ti-r131' is not installed, so 
> not removed
> The following packages were automatically installed and are no longer 
> required:
>   bb-beaglebone-io-installer bb-johnny-five-installer
>   ti-c6000-cgt-v8.2.x-installer
> Use 'sudo apt autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
>
> debian@beaglebone:~$ sudo apt install ti-cmem-4.16.00.00-modules-`uname -r`
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> ti-cmem-4.16.00.00-modules-4.14.108-ti-r131 is already the newest version 
> (1stretch).
> The following packages were automatically installed and are no longer 
> required:
>   bb-beaglebone-io-installer bb-johnny-five-installer
>   ti-c6000-cgt-v8.2.x-installer
> Use 'sudo apt autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.


The stack switched to ti-c6000-cgt-v8.3

> Error from TIDL classification example:
>
> Started /var/lib/cloud9/: classification.tidl.cpp
> File path: /var/lib/cloud9/BeagleBone/AI/tidl
> File: /var/lib/cloud9/BeagleBone/AI/tidl/classification.tidl.cpp
> Arguments:
> File name: classification.tidl.cpp
> File extension: cpp
> File base name: classification.tidl
> Packages: ~.c9/packages
> Project path: /var/lib/cloud9/
> Project name: projectname
> Hostname: localhost
> Hostname path: https://undefined/BeagleBone/AI/tidl/classification.tidl.cpp
> URL: http://localhost
> Port: 8080
> IP: 0.0.0.0
> Command: BeagleBone/AI/tidl/classification.tidl.cpp
> Python: python3
> Python path: 
> /usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
> /var/lib/cloud9/common/Makefile:28: 
> MODEL=BeagleBoard.org_BeagleBone_AI,TARGET=classification.tidl,COMMON=/var/lib/cloud9/common
> /var/lib/cloud9/common/Makefile:147: 
> GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PROC=tidl,PRUN=,PRU_DIR=,EXE=.so
> CXX classification.tidl.cpp
> LD  /tmp/cloud9-examples/classification.tidl.o
> ti-mct-heap-check -c
> sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter 
> ./classification.tidl.so" -o "output_http.so -p 8080 -w 
> /usr/share/mjpg-streamer/www"
> [sudo] password for debian:
> MJPG Streamer Version.: 2.0
>  i: device... : default
>  i: Desired Resolution: 640 x 480
> Unable to stop the stream: Invalid argument
>  i: VideoCapture::open() failed
> /var/lib/cloud9/common/Makefile:169: recipe for target 'start' failed
> make: *** [start] Error 1
> rm /tmp/cloud9-examples/classification.tidl.o
>
>
> Process exited with code: 2

Everything before was based on tidl 1.2.x, we now have the tidl 1.4.x stack..

@Jason Kridner in think needs to update the demos..


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/CAOCHtYjFGGvS4SHzeP_S%3DvGwNoUV7VsOTjHPx3cwq1%2Bf9V_6Lg%40mail.gmail.com.

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

[Jon Morss]

Hey Robert,

Cool.  Thanks.

However, I now end up with a different error:

NOTE: I did an upgrade after the update. Also, the update_kernel bumped my 
kernel to r131 from r130.
info: you are running: [4.14.108-ti-r130], latest is: [4.14.108-ti-r131] 
updating...

The result of removing and installing the cmem modules:
debian@beaglebone:~$ sudo apt remove ti-cmem-4.15.00.02-modules-`uname -r` 
--purge
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'ti-cmem-4.15.00.02-modules-4.14.108-ti-r131' is not installed, so 
not removed
The following packages were automatically installed and are no longer 
required:
  bb-beaglebone-io-installer bb-johnny-five-installer
  ti-c6000-cgt-v8.2.x-installer
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.


debian@beaglebone:~$ sudo apt install ti-cmem-4.16.00.00-modules-`uname -r`
Reading package lists... Done
Building dependency tree
Reading state information... Done
ti-cmem-4.16.00.00-modules-4.14.108-ti-r131 is already the newest version 
(1stretch).
The following packages were automatically installed and are no longer 
required:
  bb-beaglebone-io-installer bb-johnny-five-installer
  ti-c6000-cgt-v8.2.x-installer
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.



Error from TIDL classification example:
 
Started /var/lib/cloud9/: classification.tidl.cpp
File path: /var/lib/cloud9/BeagleBone/AI/tidl
File: /var/lib/cloud9/BeagleBone/AI/tidl/classification.tidl.cpp
Arguments: 
File name: classification.tidl.cpp
File extension: cpp
File base name: classification.tidl
Packages: ~.c9/packages
Project path: /var/lib/cloud9/
Project name: projectname
Hostname: localhost
Hostname path: https://undefined/BeagleBone/AI/tidl/classification.tidl.cpp
URL: http://localhost
Port: 8080
IP: 0.0.0.0
Command: BeagleBone/AI/tidl/classification.tidl.cpp
Python: python3
Python path: 
/usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
/var/lib/cloud9/common/Makefile:28: 
MODEL=BeagleBoard.org_BeagleBone_AI,TARGET=classification.tidl,COMMON=/var/lib/cloud9/common
/var/lib/cloud9/common/Makefile:147: 
GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PROC=tidl,PRUN=,PRU_DIR=,EXE=.so
CXX classification.tidl.cpp
LD  /tmp/cloud9-examples/classification.tidl.o
ti-mct-heap-check -c
sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter 
./classification.tidl.so" -o "output_http.so -p 8080 -w 
/usr/share/mjpg-streamer/www"
[sudo] password for debian:
MJPG Streamer Version.: 2.0
 i: device... : default
 i: Desired Resolution: 640 x 480
Unable to stop the stream: Invalid argument
 i: VideoCapture::open() failed
/var/lib/cloud9/common/Makefile:169: recipe for target 'start' failed
make: *** [start] Error 1
rm /tmp/cloud9-examples/classification.tidl.o


Process exited with code: 2



Cheers,

Jon


On Tuesday, March 24, 2020 at 3:40:47 PM UTC-7, RobertCNelson wrote:
>
> On Tue, Mar 24, 2020 at 5:31 PM Jon Morss > 
> wrote: 
> > 
> > After recently upgrading my BBAI via the link below, the Cloud9 TIDL 
> classification example fails for CMEM error. 
> > Link used to upgrade BBAI 
> > https://beagleboard.org/upgrade 
>
> > CMEM Error: init: major version mismatch between interface and driver. 
> > CMEM Error: needs driver version 0x416, got 0x4150002 
> > TIOCL FATAL: The cmemk kernel module is not installed. Consult the 
> OpenCL UserGuide at 
> http://software-dl.ti.com/mctools/esd/docs/opencl/index.html 
>
> Yeap, I've been busy upgrading both Debian Stretch & Buster to TI's 
> sdk  06.02.00.81 
>
> https://github.com/beagleboard/Latest-Images/issues/11 
>
> To fix your problem, two fixes: 
>
> Fix 1: update "./update_kernel.sh" so stretch uses cmem 4.16.00.00 on 
> kernel modules: 
>
> https://github.com/RobertCNelson/boot-scripts/commit/43e2e0e554b10d779fdbc730bb0d5d197e467d02
>  
>
> Run: 
>
> cd /opt/scripts/tools/ 
> git pull 
>
> Fix 2: switch your current version of cmem: (the kernel update script 
> will fix it going forward, but this will fix your version today) 
>
> Run: 
>
> sudo apt update 
> sudo apt remove ti-cmem-4.15.00.02-modules-`uname -r` --purge 
> sudo apt install ti-cmem-4.16.00.00-modules-`uname -r` 
> sudo depmod -a 
> sudo update-initramfs -uk `uname -r` 
>
> and reboot.. 
>
> 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/1ef9bf14-ed1a-49dd-8b0a-3a5525eb7c00%40googlegroups.com.

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

[Robert Nelson]

On Tue, Mar 24, 2020 at 5:31 PM Jon Morss  wrote:
>
> After recently upgrading my BBAI via the link below, the Cloud9 TIDL 
> classification example fails for CMEM error.
> Link used to upgrade BBAI
> https://beagleboard.org/upgrade

> CMEM Error: init: major version mismatch between interface and driver.
> CMEM Error: needs driver version 0x416, got 0x4150002
> TIOCL FATAL: The cmemk kernel module is not installed. Consult the OpenCL 
> UserGuide at http://software-dl.ti.com/mctools/esd/docs/opencl/index.html

Yeap, I've been busy upgrading both Debian Stretch & Buster to TI's
sdk  06.02.00.81

https://github.com/beagleboard/Latest-Images/issues/11

To fix your problem, two fixes:

Fix 1: update "./update_kernel.sh" so stretch uses cmem 4.16.00.00 on
kernel modules:
https://github.com/RobertCNelson/boot-scripts/commit/43e2e0e554b10d779fdbc730bb0d5d197e467d02

Run:

cd /opt/scripts/tools/
git pull

Fix 2: switch your current version of cmem: (the kernel update script
will fix it going forward, but this will fix your version today)

Run:

sudo apt update
sudo apt remove ti-cmem-4.15.00.02-modules-`uname -r` --purge
sudo apt install ti-cmem-4.16.00.00-modules-`uname -r`
sudo depmod -a
sudo update-initramfs -uk `uname -r`

and reboot..

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/CAOCHtYgRKwH0%2BKjX3vP_ywWRVh%3D%2B-4z3naERRD536Z%2BDdrq4xQ%40mail.gmail.com.

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

[Jon Morss]

After recently upgrading my BBAI via the link below, the Cloud9 TIDL 
classification example fails for CMEM error.
Link used to upgrade BBAI
https://beagleboard.org/upgrade

Error seen:

File path: /var/lib/cloud9/BeagleBone/AI/tidl
File: /var/lib/cloud9/BeagleBone/AI/tidl/classification.tidl.cpp
Arguments: 
File name: classification.tidl.cpp
File extension: cpp
File base name: classification.tidl
Packages: ~.c9/packages
Project path: /var/lib/cloud9/
Project name: projectname
Hostname: localhost
Hostname path: https://undefined/BeagleBone/AI/tidl/classification.tidl.cpp
URL: http://localhost
Port: 8080
IP: 0.0.0.0
Command: BeagleBone/AI/tidl/classification.tidl.cpp
Python: python3
Python path: 
/usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
/var/lib/cloud9/common/Makefile:28: 
MODEL=BeagleBoard.org_BeagleBone_AI,TARGET=classification.tidl,COMMON=/var/lib/cloud9/common
/var/lib/cloud9/common/Makefile:147: 
GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PROC=tidl,PRUN=,PRU_DIR=,EXE=.so
ti-mct-heap-check -c
sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter 
./classification.tidl.so" -o "output_http.so -p 8080 -w 
/usr/share/mjpg-streamer/www"
[sudo] password for debian:
MJPG Streamer Version.: 2.0
 i: device... : default
 i: Desired Resolution: 640 x 480
 i: filter... : ./classification.tidl.so
 i: filter args . :
Initializing filter
loading configuration
allocating execution object pipelines (EOP)
CMEM Error: init: major version mismatch between interface and driver.
CMEM Error: needs driver version 0x416, got 0x4150002
TIOCL FATAL: The cmemk kernel module is not installed. Consult the OpenCL 
UserGuide at http://software-dl.ti.com/mctools/esd/docs/opencl/index.html
/var/lib/cloud9/common/Makefile:169: recipe for target 'start' failed
make: *** [start] Error 1


Output from version.sh
debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[43e2e0e554b10d779fdbc730bb0d5d197e467d02]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[BeagleBoard.org Debian Image 2019-08-03]
UBOOT: Booted Device-Tree:[am5729-beagleboneai.dts]
kernel:[4.14.108-ti-r130]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.14.20200312.0-0rcnee0~stretch+20200312]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~stretch+20200322]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy sudo audio dip video 
plugdev users systemd-journal input i2c bluetooth netdev gpio pwm eqep 
remoteproc admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=80 quiet 
video=HDMI-A-1:1920x1080@60e]
dmesg | grep remote
[   39.306068] remoteproc remoteproc0: 5882.ipu is available
[   39.345676] remoteproc remoteproc1: 5502.ipu is available
[   39.395618] remoteproc remoteproc2: 4080.dsp is available
[   39.398003] remoteproc remoteproc3: 4100.dsp is available
[   39.455514] remoteproc remoteproc1: powering up 5502.ipu
[   39.455562] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, 
size 3751356
[   39.465881] remoteproc remoteproc0: powering up 5882.ipu
[   39.465928] remoteproc remoteproc0: Booting fw image dra7-ipu1-fw.xem4, 
size 7051536
[   39.927096] Modules linked in: omap_remoteproc virtio_rpmsg_bus 
rpmsg_core uio_pdrv_genirq uio usb_f_ecm usb_f_mass_storage usb_f_rndis 
u_ether libcomposite cmemk(O)
[   39.928076] Modules linked in: omap_remoteproc virtio_rpmsg_bus 
rpmsg_core uio_pdrv_genirq uio usb_f_ecm usb_f_mass_storage usb_f_rndis 
u_ether libcomposite cmemk(O)
[   39.967301] remoteproc remoteproc3: powering up 4100.dsp
[   39.967350] remoteproc remoteproc3: Booting fw image dra7-dsp2-fw.xe66, 
size 21014532
[   39.977004] remoteproc remoteproc2: powering up 4080.dsp
[   39.977039] remoteproc remoteproc2: Booting fw image dra7-dsp1-fw.xe66, 
size 21014532
[   39.999179] remoteproc remoteproc1: registered virtio1 (type 7)
[   39.999203] remoteproc remoteproc1: remote processor 5502.ipu is now 
up
[   40.001317] remoteproc remoteproc0: registered virtio0 (type 7)
[   40.001339] remoteproc remoteproc0: remote processor 5882.ipu is now 
up
[   40.106153] remoteproc remoteproc2: registered virtio2 (type 7)
[   40.106177] remoteproc remoteproc2: remote processor 4080.dsp is now 
up
[   40.134498] remoteproc remoteproc3: registered virtio3 (type 7)
[   40.134522] remoteproc remoteproc3: remote processor 4100.dsp is now 
up
[   61.744815] remoteproc remoteproc4: 4b234000.pru is available
[   61.768955] remoteproc remoteproc5: 4b238000.pru is available
[   61.780959] remoteproc remoteproc6: 

[beagleboard] Re: After build_kernel.sh

[Paul Beam]

I'm going to answer (mostly) my own question here for posterity.  At 
appears my process was mostly right, but I failed to update the reference 
to AM335X-PRU-RPROC-4-14-TI-00A0 in uEnv.txt, and that apparently does some 
weird things.  

Executing /lib/systemd/systemd-modules-load shows that the module 
pruss_intc is not found, so I need to investigate why this is since I 
selected all the pru options in the kernel config.  Perhaps, this module 
has changed names or combined with another?

-- 
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/665a0d5c-988c-4ec3-a621-9d3ec6fd9bf6%40googlegroups.com.

[beagleboard] After build_kernel.sh

[Paul Beam]

So I am trying to build my own kernel for a Pocketbeagle, and I have 
cross-compiled in a Debian VM, and have the output in the deploy directory 
after executing build_kernel.sh on kernel version 4.19.94-ti-rt-r41.  My 
problem is getting it to boot properly on the target system.  I have moved 
the products to the target and put them, I think, in the proper places 
creating an appropriate /lib/modules/4.19.94-ti-rt-r41 and 
/boot/dtbs/4.19.94-ti-rt-r41 directories, renamed the zImage and updated 
uEnv.txt to version 4.19.94-ti-rt-r41.  Upon reboot, that kernel does come 
up but systemd-modules-load.service fails, so I think I must be missing 
something.  Is there another step?

root@beaglebone:~# systemctl --failed
  UNIT LOAD   ACTIVE SUBDESCRIPTION
● systemd-modules-load.service loaded failed failed Load Kernel Modules

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@beaglebone:~# [   83.036964] wkup_m3_ipc 44e11324.wkup_m3_ipc: could 
not get rproc handle
q
-bash: q: command not found
root@beaglebone:~# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
static; ven
   Active: failed (Result: exit-code) since Tue 2020-03-24 21:30:41 UTC; 
7min ag
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
  Process: 153 ExecStart=/lib/systemd/systemd-modules-load (code=exited, 
status=
 Main PID: 153 (code=exited, status=1/FAILURE)

-- 
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/d8e11e2c-ad66-49a6-889b-837df621f4a2%40googlegroups.com.

[beagleboard] Re: javascript / bonescript structure

[ddchapa09]

this is what i was looking for.  how do i access the timers that the BBB 
has?  that link will lead me to all that?

On Tuesday, March 24, 2020 at 10:51:08 AM UTC-5, TJF wrote:
>
> You don't need interrupts for counting pulses. Instead use the hardware 
> counters inbuild in the AM335x CPU. Those are
>
>- 3xPWMSS.eQEP
>- 3xPWMSS.eCAP
>- 4xTIMERSS
>
> Find details and example code (C, Python, BASIC) in the libpruio 
> documentation 
> .
>
> Regards
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e92b97af-0881-4500-b54e-3538fc83d103%40googlegroups.com.

[beagleboard] Re: javascript / bonescript structure

[TJF]

You don't need interrupts for counting pulses. Instead use the hardware 
counters inbuild in the AM335x CPU. Those are

   - 3xPWMSS.eQEP
   - 3xPWMSS.eCAP
   - 4xTIMERSS

Find details and example code (C, Python, BASIC) in the libpruio 
documentation 
.

Regards

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a32defda-913a-41c1-b38b-4f74ec02479a%40googlegroups.com.

Re: [beagleboard] Re: BBAI and Updating to Stop the Heat Transfer at https://beagleboard.org/upgrade

[Robert Nelson]

On Tue, Mar 24, 2020 at 8:28 AM Jason Kridner 
wrote:

> I'm sure there's probably a better thread, but this one is the first one
> that came up for me.
>
> The Fan Cape is finally in stock at Newark:
> https://www.newark.com/element14/6100310/beaglebone-ai-fan-cape/dp/50AH3704
>
> Not sure when other distributors will have stock.
>

Did embest ever finalize the "eeprom" on these? adding to cart/order to
test one right now..

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/CAOCHtYj02mx3HpRmK%3DsBgESwAOvAd5%2BdZTyepYPo0HavchY%2BQw%40mail.gmail.com.

Re: [beagleboard] Re: BBAI and Updating to Stop the Heat Transfer at https://beagleboard.org/upgrade

[Jason Kridner]

I'm sure there's probably a better thread, but this one is the first one
that came up for me.

The Fan Cape is finally in stock at Newark:
https://www.newark.com/element14/6100310/beaglebone-ai-fan-cape/dp/50AH3704

Not sure when other distributors will have stock.


On Tue, Mar 3, 2020 at 7:42 PM Mala Dies  wrote:

> Hello,
>
> Here it is:
>
>
> 
> |Thermal zone   |temp   |mode   |cdev0_type |cdev1_type
>
> 
> |cpu_thermal|38600  |enabled|thermal-cpufreq-0  |
>  |passive:55000|critical:85000|
> |gpu_thermal|38600  |enabled|   |
>  |critical:85000|
> |core_thermal   |38600  |enabled|   |
>  |critical:85000|
> |dspeve_thermal |37800  |enabled|   |
>  |critical:85000|
> |iva_thermal|39000  |enabled|   |
>  |critical:85000|
>
> 
> |Cooling type   |state  |max_state  |
>
> 
> |thermal-cpufreq-0  |0  |3  |
>
> 
>
> Enjoy,
>
> Seth
>
>
>
> On Monday, January 27, 2020 at 9:07:33 AM UTC-6, Jason Kridner wrote:
>>
>> Perhaps:
>>
>> watch /opt/scripts/device/x15/test_thermal.sh
>>
>> ?
>>
>>
>> The output of 'test_thermal.sh' would really be helpful for those
>> complaining about the heat. The update should stop it from overheating, at
>> least in a room temperature environment. That doesn't mean it won't be hot
>> to the touch... just not so hot that it will need to shutdown.
>>
>> Can I get some more feedback on this?
>>
>> Sorry for the VERY LONG delay on the Fan Cape. Chinese New Year recently
>> entered the reasons for delay, but it is coming. The other big missing
>> thing for BBAI is the Python Tensorflow library, which is also coming. I'll
>> be talking a lot more about BBAI once the two of those are out there.
>>
>> Anyway, just running the update should give you a nice solution for
>> running "regular" code. Please explain to me if that really isn't the case.
>>
>> On Mon, Jan 27, 2020 at 6:42 AM Mala Dies  wrote:
>>
>>> Hello,
>>>
>>> No...this fellow gave me a script to test for temp. continuously.
>>>
>>> Seth
>>>
>>> On Monday, January 20, 2020 at 8:19:00 AM UTC-6, IO wrote:

 You mean, by running cat
 /sys/devices/virtual/thermal/thermal_zone0/temp ?

 On Sunday, January 19, 2020 at 7:54:46 PM UTC+2,
 se...@lafayette-parish.com wrote:
>
> Hello,
>
> Just an update, if you run the temp. sensors onboard the AI and run
> the fan, on my end, you will receive a 38c or below temp. for the board
> chips and surrounding area.
>
> Seth
>
> P.S. Nice! Fans!
>
> On Thursday, January 2, 2020 at 1:18:29 AM UTC-6, Mala Dies wrote:
>>
>> Hello,
>>
>> Thank you for this update. I did update the board already as the link
>> suggested. My fan was a 24v fan. I need to get another fan.
>>
>> Seth
>>
>> P.S. I might get the digikey.com fan you have listed. Anyway, if
>> anyone has any other ideas, shoot!
>>
>> On Sunday, December 29, 2019 at 5:30:02 PM UTC-6, jonnymo wrote:
>>>
>>> Jason recently posted an update regarding the Fan Cape he is working
>>> on.
>>> In the mean time, he recommended the Coolerguys USB fan that is
>>> listed in the BBAI FAQ:
>>>
>>> https://github.com/beagleboard/beaglebone-ai/wiki/Frequently-Asked-Questions#fans
>>>
>>> https://www.coolerguys.com/collections/usb-fans/products/25mm-25x25x10-usb-fan
>>>
>>> Previously, the X15FANKIT was suggested but it requires wiring to 5v
>>> and grnd on the BBAI.  I am using this and it seems to work fine for my
>>> BBAI. This does fit perfectly on the BBAI heat-sink and the provided 
>>> screws
>>> work just fine.
>>>
>>> https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#3-1-2-fans
>>>
>>> https://www.digikey.com/product-detail/en/digi-key-electronics/X15FANKIT/X15FANKIT-ND/5822502
>>>
>>>
>>> Cheers,
>>>
>>> Jon
>>>
>>> On Sun, Dec 29, 2019 at 10:03 PM Mala Dies  wrote:
>>>
 Hello,

 Thank you for the idea. USB powered fans. I guess they make
 everything these days.

 Seth

 P.S. I was just going to power it from the sys_5v pin and GND on
 the BBAI. I guess there are many more ways to go about making things