Re: [beagleboard] Re: 192.168.7.2 is NOT opening or reachable
It is possible that you either have a bad USB cable or your PC can not provide enough power to properly power up the BBB. The preference would be to upgrade you eMMC, however, this message does appear in your files though: [ 8428.112630] sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 8428.408057] usb 2-1: new high-speed USB device number 8 using xhci_hcd [ 8428.536147] usb 2-1: Device not responding to setup address. [ 8428.744111] usb 2-1: Device not responding to setup address. [ 8428.952095] usb 2-1: device not accepting address 8, error -71 [ 8429.924105] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 8429.924193] usb usb2-port1: attempt power cycle [ 8431.272034] usb 2-1: new high-speed USB device number 10 using xhci_hcd [ 8431.293196] usb 2-1: New USB device found, idVendor=1d6b, idProduct=0104, bcdDevice= 4.01 [ 8431.293200] usb 2-1: New USB device strings: Mfr=3, Product=4, SerialNumber=5 [ 8431.293202] usb 2-1: Product: BeagleBoneBlack [ 8431.293205] usb 2-1: Manufacturer: Circuitco [ 8431.293206] usb 2-1: SerialNumber: C0-5018BBBK0C2 Jon On Wednesday, July 15, 2020 at 9:57:56 AM UTC-7, Pankaj Rai wrote: > > PFA for screenshots of the output message on running the command dmesg > with plugged in BBB. > > thanks. > > On Wed, Jul 15, 2020 at 10:15 PM Pankaj Rai > wrote: > >> Hi, >> I could see couple of errors listed out with and without BBB connected to >> my laptop using mini USB cable(given in box). But i couldn't figure out >> totally, the difference between plugged and unplugged BBB. >> >> I'm attaching the output file hereby for your reference. thanks for your >> help. >> >> pankaj >> >> On Wed, Jul 15, 2020 at 9:35 PM jonnymo > >> wrote: >> >>> Unplug and plug the BBB back in and then check the output of running the >>> command : dmesg >>> >>> Jon >>> >>> On Wed, Jul 15, 2020 at 8:25 AM Pankaj Rai >> > wrote: >>> Hi, It seems I'm not getting the 192.168.6.1 or 192.168.7.1 on command ifconfig -a Thanks On Wed, Jul 15, 2020, 20:19 amf > wrote: > Only way to update the emmc os without a ethernet connection is by > using a USB-to-SERIAL adapter, make sure to get the 3.3 volt version. > Not sure if you answered the prior question. does your laptop show > 192.168.6.1 and/or 192.168.7.1 when doing 'ifconfig -a' from a terminal > window? > If it does, I don't see any reason why you cannot at least ping the > BBB at 6.2 or 7.2. > > On Tuesday, July 14, 2020 at 10:19:21 AM UTC-5, Pankaj Rai wrote: >> >> Hi, >> Currently I'm working with my personal laptop only. And also i've >> ordered a 16 gb sd card for sure. But meanwhile i was trying to make it >> work with with preinstalled os in eMMC only. >> >> Is there any way we can update the eMMC OS? So that it may able to >> connect to 192.168.7.2 or 192.168.6.2 ( this is because somewhere i've >> seen >> that Linux system uses this ip to connect with BBB). >> >> Thanks >> Pankaj >> >> On Tue, Jul 14, 2020, 20:25 amf wrote: >> >>> connecting the ethernet to the computer will not provide you with an >>> IP address on the BBB. BBB wants to use dhcp to get an IP, which what >>> happens when connected to the router. >>> You should be able to ping 192.168.7.2 from the laptop, if you see >>> 192.168.7.1 on the laptop. >>> Is this your personal laptop or a company laptop? companies tend to >>> secure laptops such that ping and ssh aren't allowed (My personal >>> experience) >>> Would recommend getting an sdcard, again if this is a company >>> laptop, it may not help. >>> >>> >>> >>> On Monday, July 13, 2020 at 9:58:28 PM UTC-5, Pankaj Rai wrote: Hi, Can we connect the BBB using ethernet cable to the computers ethernet port? ( It's because I'm living in hostel and here we have the hostel wifi available) And can we power the BBB using 5 V charger? If not, then will it work out on using the flashed sd card as boot? (I'm thinking to buy one(16gb) for this if doesn't work) Thanks Pankaj On Tue, Jul 14, 2020, 00:19 Dennis Lee Bieber wrote: > On Mon, 13 Jul 2020 23:24:06 +0530, in > gmane.comp.hardware.beagleboard.user > Pankaj Rai <> wrote: > > >Hi, > >I've enabled the port 22 on my pc and I'm not using sd card for > flashing so > >I don't think i need to press the s2 button. > >And also i don't have any debugger and i tried pinging the BBB on > that > >address but it shows all the sent packets are lost so i think I'm > unable to > >ping. > > > >Is there
[beagleboard] Re: accessing P9.13 on Beaglebone AI
According to the spreadsheet that Jason sent some time back, P9.13 does not
have the gpio value highlighted in blue but I am not sure what that really
means. However, it seems the pins with a gpio value in blue seem to work
fine, such as P9.12 (gpio5_0).
https://docs.google.com/spreadsheets/d/1fE-AsDZvJ-bBwzNBj1_sPDrutvEvsmARqFwvbw_HkrE/edit?usp=sharing
You could check the output of showpins to see what P9.13x is set to:
sudo /opt/scripts/device/bone/show-pins.pl |grep "P9.13"
P9.13b 160 AB10 e fast rx gpio6_12
P9.13a 204 C17 e fastdown
With P9.12 set, it looks as such:
sudo /opt/scripts/device/bone/show-pins.pl |grep "P9.12"
P9.12171 B14 e fast rx gpio5_0
Also, I do add this in the .dts file:
cape_pins: cape_pins {
compatible = "gpio-leds";
pinctrl-names = "default";
gpios = < 12 GPIO_ACTIVE_HIGH>,
< 0 GPIO_ACTIVE_HIGH>;
pinctrl-0 = <_pins_default>;
};
Perhaps there is another trick to get P9.13b to work as a GPIO pin.
Cheers,
Jon
On Monday, May 11, 2020 at 3:25:59 PM UTC-7, John Allwine wrote:
>
> When I manually wire a pull up resistor, I still am not able to detect a
> high signal using the methods I listed, though I can verify with a
> multimeter that P9.13 is high.
>
> On Monday, May 11, 2020 at 3:17:36 PM UTC-6, John Allwine wrote:
>>
>> I'm trying to configure P9.13 on the Beaglebone AI as an input pull up,
>> but am not having any success. In the System Manual
>>
>>
>> it lists P9.13a as not being bound to a GPIO port, but P9.13b is bound to
>> GPIO6_12. This is the device tree overlay I'm using
>>
>> with
>> line 56 showing how I'm attempting to configure P9.13b (and P9.13a the line
>> above it). Am I doing something wrong in my device tree overlay? I've had
>> success configuring many other pins, but P9.13 is giving me trouble for
>> some reason.
>>
>> I'm testing it a couple ways:
>> 1) with sysfs
>> echo 172 > /sys/class/gpio/export
>> cat /sys/class/gpio/gpio172/value
>>
>> 2) with libgpio
>> gpioget gpiochip5 12
>>
>> Both return a value of 0, when I'd expect it to be 1 (I don't have
>> anything wired to it). Any idea what I'm doing wrong?
>>
>
--
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/d808c9de-7abd-42bd-ab24-a697fb5f1913%40googlegroups.com.
Re: [beagleboard] Re: Enable Bluetooth?
Yeah, an external BT device might be the solution but if the BT/BLE feature is not support on the BBAI, then it should be stated as such and listed as WiFi only. I've tried a few more things but still I can't get it to work or even show an address. $ sudo modprobe hci_uart debian@beaglebone:~$ sudo lsmod |grep hci hci_uart 69632 0 btqca 16384 1 hci_uart bluetooth 548864 11 btsdio,hci_uart,btqca,bnep systemctl enable bluetooth.service systemctl start bluetooth.service I am not sure why 'hciuart.service' is missing: $debian@beaglebone:~$ sudo systemctl status hciuart.service Unit hciuart.service could not be found $ sudo ls /lib/systemd/system/hciuart.service ls: cannot access '/lib/systemd/system/hciuart.service': No such file or directory debian@beaglebone:~$ sudo lsmod |grep -i sdio btsdio 16384 0 bluetooth 548864 9 btsdio,bnep This is what I see from 'dmesg' debian@beaglebone:~$ dmesg |grep -Ei 'blue|firm' [ 23.488304] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 [ 25.046041] vpe 489d.vpe: loading firmware vpdma-1b8.bin [ 25.736322] Bluetooth: Core ver 2.22 [ 25.736564] Bluetooth: HCI device and connection manager initialized [ 25.736605] Bluetooth: HCI socket layer initialized [ 25.736636] Bluetooth: L2CAP socket layer initialized [ 25.736745] Bluetooth: SCO socket layer initialized [ 25.790364] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 30.510745] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 30.510768] Bluetooth: BNEP filters: protocol multicast [ 30.510807] Bluetooth: BNEP socket layer initialized [ 1535.224971] Bluetooth: HCI UART driver ver 2.3 [ 1535.224998] Bluetooth: HCI UART protocol H4 registered [ 1535.230749] Bluetooth: HCI UART protocol LL registered [ 1535.230779] Bluetooth: HCI UART protocol ATH3K registered [ 1535.230803] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1535.230821] Bluetooth: HCI UART protocol QCA registered Still, not working: $ sudo hciconfig -a hci0: Type: Primary Bus: SDIO BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: SLAVE ACCEPT debian@beaglebone:~$ sudo bluetoothd -d -n bluetoothd[1997]: Bluetooth daemon 5.50 bluetoothd[1997]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ DiscoverableTimeout” in group “General” bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ PairableTimeout” in group “General” bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ Privacy” in group “General” bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “Name ” in group “General” bluetoothd[1997]: src/main.c:parse_config() class=0x020100 bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ DeviceID” in group “General” bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ ReverseServiceDiscovery” in group “General” bluetoothd[1997]: src/main.c:parse_config() Key file does not have key “ MinEncKeySize” in group “GATT” D-Bus setup failed: Name already in use bluetoothd[1997]: Unable to get on D-Bus debian@beaglebone:~$ sudo hciconfig hci0 up Can't init device hci0: Input/output error (5) debian@beaglebone:~$ sudo bluetoothctl Agent registered [bluetooth]# list [bluetooth]# show No default controller available [bluetooth]# power on No default controller available >From what I can gather, this is the BT device on the BBAI but I am not sure where to get a driver for it. https://deviwiki.com/wiki/AzureWave_AW-CM256SM I'm not sure what else to try. Cheers, Jon -- 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/08f3efe5-82b7-421a-87cc-a29bad3f676e%40googlegroups.com.
Re: [beagleboard] Re: Enable Bluetooth?
Sorry to dig this up again, but has this been fixed? I am seeing the same issue with the latest image , "am57xx-debian-10.3-iot-tidl-armhf-2020-04-06-6gb.img.xz" where the bluetooth device does not appear to be working. The WiFi is working but not the bluetooth device. debian$ hciconfig hci0: Type: Primary Bus: SDIO BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 $ sudo hcitool dev Devices: $ sudo hcitool lescan Could not open device: No such device $ dmesg |grep -i brcm [ 22.472541] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455 -sdio.bin for chip 0x004345(17221) rev 0x06 [ 22.474228] usbcore: registered new interface driver brcmfmac [ 22.816956] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4 $ dmesg |grep -i blue [ 24.843545] Bluetooth: Core ver 2.22 [ 24.843753] Bluetooth: HCI device and connection manager initialized [ 24.849439] Bluetooth: HCI socket layer initialized [ 24.849474] Bluetooth: L2CAP socket layer initialized [ 24.849594] Bluetooth: SCO socket layer initialized [ 24.923314] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 30.630971] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 30.630993] Bluetooth: BNEP filters: protocol multicast [ 30.631034] Bluetooth: BNEP socket layer initialized Side Note: At BeagleBoard.og, the 10.3 IoT TiDL image is listed as an 8Gb image but the file shows 6gb https://beagleboard.org/latest-images "AM5729 Debian 10.3 2020-04-06 8GB SD IoT TIDL" Cheers, Jon On Thursday, January 9, 2020 at 9:51:16 AM UTC-8, RobertCNelson wrote: > > On Thu, Jan 9, 2020 at 11:39 AM Bryan > > wrote: > > > > Should the bb-bbai-firmware package work to enable Bluetooth on the BBAI > (not the BBB)? > > > > See my previous posts in this thread for details but I can't get it to > function. For now I'm using a USB bluetooth dongle as an alternative. > > bb-bbai-firmware just installs the firmware for the bbai, i thought it > worked thru bluetoothctl, it's been a few months since i looked at it. > > 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/1f4a2c16-f077-4c3f-bb1d-38772b42bfe9%40googlegroups.com.
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. Cheers, Jon On Friday, March 27, 2020 at 4:07:58 AM UTC-7, 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: >> >> >> >> Setting '-d /dev/video1' in the common Makefile seemed to do the trick. I >> now have video from the camera in the TIDL example. >> >> This is what I changed at line 170 in the Makefile at: >> /var/lib/cloud9/common$ >> >> else ifeq ($(PROC),tidl) >> ti-mct-heap-check -c >> sudo mjpg_streamer -i "input_opencv.so -d /dev/video1 -r 640x480 >> --filter ./$(TARGET)$(EXE)" -o "output_http.so -p 8080 -w >> /usr/share/mjpg-streamer/www" >> else >> >> >> >> On Thu, Mar 26, 2020 at 9:20 AM Robert Nelson > > wrote: >> >>> On Thu, Mar 26, 2020 at 10:27 AM > >>> wrote: >>> > >>> > Hi, >>> > I just came across this post that is relevant to the same problem. I >>> just started working on this Beaglebone AI two days ago. I got the latest >>> os image and updates and upgrades everything. I tried >>> classification.tidl.cpp and I got the same last message that Jon Morss >>> got. And your latest message was about /dev/video0. On my board I got >>> /dev/video0, /dev/video1 and it does recognize the camera. Do you mean that >>> I can fix it with the change to the default dev for the camera ? And where >>> can I change that? I worked with OpenCV and this VideoCapture::open() >>> failed message seems to indicate a wrong /dev/video index? >>> >>> Please submit a bug to: >>> >>> https://github.com/beagleboard/cloud9-examples >>> >>> the classification demo should allow you to specify a video offset.. >>> >>> 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 beagl...@googlegroups.com . >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjyA8yTBWKs-%3DFUoE4kh20XgiQNpheJLfnzHG7_ouqVNA%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 beagl...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CAG99bko9Nkz-Jb%2BnBYd-RvhBzGhNHJMkv1%2B7bVcn6hLdaqDcTA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/beagleboard/CAG99bko9Nkz-Jb%2BnBYd-RvhBzGhNHJMkv1%2B7bVcn6hLdaqDcTA%40mail.gmail.com?utm_medium=email_source=footer> >> . >> > -- > https://beagleboard.org/about - a 501c3 non-profit educating around open > hardware computing > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/285fd1d7-e1bc-4a68-855c-a649ca5a4ac2%40googlegroups.com.
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:18 AM UTC-7, maste...@gmail.com wrote: > > 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 Silicon Motion SM731 webcam works > 5. OLD EyeToy webcam - occasional image tears > > check out https://elinux.org/RPi_USB_Webcams for some camera info. > > I modified the common Makefile and it works. Just for curiosity I modified > the local Makefile as well and > I's weird that the LOCAL Makefile is corrupted when I rebooted the board. > It came up with a dialog box asking if you want to reload file from disk > (that Makefile was modified in previous session and saved "-r /dev/video1" > similar to the common Makefile) . If I clicked "Y" it showed the correct > mod -d/dev/video1, and if I clicked "no", it showed -d /dev/ > > > On Thursday, March 26, 2020 at 10:23:17 PM UTC-4, 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 >> now have video from the camera in the TIDL example. >> >> This is what I changed at line 170 in the Makefile at: >> /var/lib/cloud9/common$ >> >> else ifeq ($(PROC),tidl) >> ti-mct-heap-check -c >> sudo mjpg_streamer -i "input_opencv.so -d /dev/video1 -r 640x480 >> --filter ./$(TARGET)$(EXE)" -o "output_http.so -p 8080 -w >> /usr/share/mjpg-streamer/www" >> else >> >> >> >> On Thu, Mar 26, 2020 at 9:20 AM Robert Nelson >> wrote: >> >>> On Thu, Mar 26, 2020 at 10:27 AM wrote: >>> > >>> > Hi, >>> > I just came across this post that is relevant to the same problem. I >>> just started working on this Beaglebone AI two days ago. I got the latest >>> os image and updates and upgrades everything. I tried >>> classification.tidl.cpp and I got the same last message that Jon Morss >>> got. And your latest message was about /dev/video0. On my board I got >>> /dev/video0, /dev/video1 and it does recognize the camera. Do you mean that >>> I can fix it with the change to the default dev for the camera ? And where >>> can I change that? I worked with OpenCV and this VideoCapture::open() >>> failed message seems to indicate a wrong /dev/video index? >>> >>> Please submit a bug to: >>> >>> https://github.com/beagleboard/cloud9-examples >>> >>> the classification demo should allow you to specify a video offset.. >>> >>> 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 beagl...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjyA8yTBWKs-%3DFUoE4kh20XgiQNpheJLfnzHG7_ouqVNA%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/2e52e2e3-639e-48d1-b3b9-8886457b988e%40googlegroups.com.
Re: [beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade
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.
[beagleboard] CLoud9 TIDL example sees CMEM Error after recent upgrade
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] TIDL kernel 4.19 support
I noticed some work has been on going with the BeagleBoard 4.19 branch on GitHub and I was wondering if TIDL will be supported with 4.19 (or later) anytime soon? Cheers, Jon -- 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/c607bce6-d399-4dc3-bac2-f52df7705cf7%40googlegroups.com.
Re: [beagleboard] Re: TIDL Classification example not properly identify objects
. For this classifier network, it is said to >>>>> be fastest to run the first 11 stages on EVEs as fixed-point processes >>>>> and then run the last 3 layers as floating-point >>>>> processes on the C66 DSPs. And, because we'd only be running 3 layers >>>>> on the DSPs, we only need a single DSP. >>>>> >>>>> Anyway, I didn't assign the layers properly and I still need to look >>>>> at the code a bit more to set them properly. >>>>> >>>>> For now, I've just switched back to running on all 14 layers on 4 >>>>> EVEs. The 30fps data from the camera seems to >>>>> be reasonably processed with this configuration. >>>>> >>>>> I picked up a Logitech C922 that is capable of doing 60fps and I'll be >>>>> looking to update the demo to run that way soon >>>>> and finishing up the segmentation demo. >>>>> >>>>> Checking the commit-log is a nice way to check-up on me, even if my >>>>> comments aren't the best. >>>>> >>>>> The errors are mostly due to the fact that I'm learning as well. I'm >>>>> trying to get the TI developers to use my methodology >>>>> of single-file mjpg-streamer filters rather then OpenCV desktop apps >>>>> as I feel those the desktop apps are overly complex >>>>> and don't represent an embedded developer's use-case. They are pretty >>>>> reasonably documented, >>>>> but, as you can see, it is taking me some time to understand them. >>>>> Some additional debug visibility needs to be added >>>>> to my approach and I'll be chatting to the TI developers about that >>>>> some in my call later today about this stuff. >>>>> >>>>> Development work is on-going for Tensorflow Lite support. All should >>>>> be much easier once that lands. >>>>> >>>>> And, yes, I keep talking about TI as if I don't work there, and I do >>>>> work there, but my working with open source >>>>> developers all day keeps me from adopting certain development >>>>> processes other TI developers take as granted. >>>>> I don't install Code Composer Studio. I don't setup an Open Embedded >>>>> build environment. I don't cross-compile. >>>>> I don't setup JTAG. I hope you get the idea. >>>>> >>>>> >>>>> On Wednesday, October 23, 2019 at 12:46:26 AM UTC-4, Jon Morss wrote: >>>>>> >>>>>> >>>>>> Yeah, I always find it suspect when am example is posted and demo'd >>>>>> but does not seem to work for others. >>>>>> >>>>>> Headbanging continues. >>>>>> >>>>>> Jon >>>>>> >>>>>> On Tuesday, October 22, 2019 at 4:03:38 PM UTC-7, Dobrin Alexiev >>>>>> wrote: >>>>>>> >>>>>>> In my case I also see often ping-pong_ball, or more often >>>>>>> "segmentation fault". >>>>>>> I wonder how can I debug this? >>>>>>> >>>>>>> >>>>>>> On Sunday, October 20, 2019 at 2:11:54 AM UTC-4, Jon Morss wrote: >>>>>>>> >>>>>>>> I am attempting to run the TIDL example with a Beaglebone AI and >>>>>>>> the only thing it seems to report identifying is a ping-pong, although >>>>>>>> I am >>>>>>>> not presenting a ping pong to the camera. I am using a Logitech C920 >>>>>>>> camera and have performed all of the updates to the system, so am not >>>>>>>> sure >>>>>>>> what I am missing. >>>>>>>> >>>>>>>> This is what I see when running the classification.tidl.cpp example: >>>>>>>> >>>>>>>> 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 >>>>>>
[beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio
Hi,
I've been trying to configure a header gpio pin such as P9_15 as an output
port on the BBAI but I am having no luck. This pin is used with the Cloud9
Python and JS examples but it is not working so I have tried to enable it
manually.
I've added the following in the am5729-beagleboneai.dts file and run make
and make install and a reboot:
cape_pins: cape_pins {
compatible = "gpio-leds";
pinctrl-names = "default";
gpios = < 12 GPIO_ACTIVE_HIGH>;
pinctrl-0 = <_pins_default>;
};
DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15:
vin1a_d8.gpio3_12 - MDIR2A */
The config-pins tools shows
debian@beaglebone:~$ sudo config-pin -q p9.15
[sudo] password for debian:
P9_15 pinmux file not found!
Pin has no cape: P9_15
The show-pins tools shows:
debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
Can't locate Inline/Files.pm in @INC (you may need to install the
Inline::Files module) (@INC contains: /etc/perl
/usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1
/usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5
/usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at
/opt/scripts/device/bone/show-pins.pl line 11.
BEGIN failed--compilation aborted at /opt/scripts/device/bone/show-pins.pl
line 11.
This is the output of version.sh:
debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[b4e40ed94bc1e15bb291d10af48e0e9893864197]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[BeagleBoard.org Debian Image 2019-08-03]
UBOOT: Booted Device-Tree:[am5729-beagleboneai.dts]
kernel:[4.19.73-ti-r29]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.4.20191017.0-0rcnee0~stretch+20191017]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal 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
[1.209487] remoteproc remoteproc0: 4b234000.pru is available
[1.209792] remoteproc remoteproc1: 4b238000.pru is available
[1.210130] remoteproc remoteproc2: 4b2b4000.pru is available
[1.210420] remoteproc remoteproc3: 4b2b8000.pru is available
[1.580068] remoteproc remoteproc4: 5882.ipu is available
[1.580495] remoteproc remoteproc5: 5502.ipu is available
[1.580963] remoteproc remoteproc6: 4080.dsp is available
[1.581450] remoteproc remoteproc7: 4100.dsp is available
[1.582238] remoteproc remoteproc4: Direct firmware load for dra7-ipu1-fw
.xem4 failed with error -2
[1.582247] remoteproc remoteproc4: powering up 5882.ipu
[1.582322] remoteproc remoteproc4: Direct firmware load for dra7-ipu1-fw
.xem4 failed with error -2
[1.582330] remoteproc remoteproc4: request_firmware failed: -2
[1.588375] remoteproc remoteproc5: Direct firmware load for dra7-ipu2-fw
.xem4 failed with error -2
[1.588383] remoteproc remoteproc5: powering up 5502.ipu
[1.588455] remoteproc remoteproc5: Direct firmware load for dra7-ipu2-fw
.xem4 failed with error -2
[1.588463] remoteproc remoteproc5: request_firmware failed: -2
[1.594532] remoteproc remoteproc6: Direct firmware load for dra7-dsp1-fw
.xe66 failed with error -2
[1.594542] remoteproc remoteproc6: powering up 4080.dsp
[1.594630] remoteproc remoteproc6: Direct firmware load for dra7-dsp1-fw
.xe66 failed with error -2
[1.594639] remoteproc remoteproc6: request_firmware failed: -2
[1.600688] remoteproc remoteproc7: Direct firmware load for dra7-dsp2-fw
.xe66 failed with error -2
[1.600697] remoteproc remoteproc7: powering up 4100.dsp
[1.600770] remoteproc remoteproc7: Direct firmware load for dra7-dsp2-fw
.xe66 failed with error -2
[1.600777] remoteproc remoteproc7: request_firmware failed: -2
dmesg | grep pru
[1.209487] remoteproc remoteproc0: 4b234000.pru is available
[1.209560] pru-rproc 4b234000.pru: PRU rproc node pru@4b234000 probed
successfully
[1.209792] remoteproc remoteproc1: 4b238000.pru is available
[1.209874] pru-rproc 4b238000.pru: PRU rproc node pru@4b238000 probed
successfully
[1.210130] remoteproc remoteproc2: 4b2b4000.pru is available
[1.210200] pru-rproc 4b2b4000.pru: PRU rproc node pru@4b2b4000 probed
successfully
[1.210420] remoteproc remoteproc3: 4b2b8000.pru is
[beagleboard] Re: TIDL Classification example not properly identify objects
Yeah, I always find it suspect when am example is posted and demo'd but does not seem to work for others. Headbanging continues. Jon On Tuesday, October 22, 2019 at 4:03:38 PM UTC-7, Dobrin Alexiev wrote: > > In my case I also see often ping-pong_ball, or more often "segmentation > fault". > I wonder how can I debug this? > > > On Sunday, October 20, 2019 at 2:11:54 AM UTC-4, Jon Morss wrote: >> >> I am attempting to run the TIDL example with a Beaglebone AI and the only >> thing it seems to report identifying is a ping-pong, although I am not >> presenting a ping pong to the camera. I am using a Logitech C920 camera >> and have performed all of the updates to the system, so am not sure what I >> am missing. >> >> This is what I see when running the classification.tidl.cpp example: >> >> 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) >> allocating executors >> allocating individual EOPs >> allocating I/O memory for each EOP >> Allocating input and output buffers >> Allocating input and output buffers >> Allocating input and output buffers >> Allocating input and output buffers >> num_eops=4 >> About to start ProcessFrame loop!! >> http://localhost:8080/?action=stream >> o: www-folder-path..: /usr/share/mjpg-streamer/www/ >> o: HTTP TCP port: 8080 >> o: HTTP Listen Address..: (null) >> o: username:password: disabled >> o: commands.: enabled >> (722)=ping-pong_ball >> (722)=ping-pong_ball >> (722)=ping-pong_ball >> (722)=ping-pong_ball >> (722)=ping-pong_ball >> (722)=ping-pong_ball >> >> >> This is what I see from dmesg: >> >> [20753.769040] usb 1-1: New USB device found, idVendor=046d, idProduct= >> 082d >> [20753.769075] usb 1-1: New USB device strings: Mfr=0, Product=2, >> SerialNumber=1 >> [20753.769097] usb 1-1: Product: HD Pro Webcam C920 >> [20753.769118] usb 1-1: SerialNumber: C0DB0F6F >> [20754.099831] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d: >> 082d) >> [20754.120146] uvcvideo 1-1:1.0: Entity type for entity Processing 3 was >> not initialized! >> [20754.120179] uvcvideo 1-1:1.0: Entity type for entity Extension 6 was >> not initialized! >> >> [20754.120323] uvcvideo 1-1:1.0: Entity type for entity Extension 11 was >> not initialized! >> [20754.125089] input: HD Pro Webcam C920 as /devices/platform/ >> 4400.ocp/488c.omap_dwc3_2/488d.usb/xhci-hcd.1.auto/usb1/1-1/1 >> -1:1.0/input/input3 >> [20754.135851] usbcore: registered new interface driver uvcvideo >> [20754.135871] USB Video Class driver (1.1.1) >> [20754.437849] usbcore: registered new interface driver snd-usb-audio >> [20867.134498] usb 1-1: reset high-speed USB device number 3 using xhci- >> hcd >> [20867.558788] omap-iommu 58882000.mmu: 58882000.mmu: version 2.1 >> [20867.605127] omap_hwmod: mmu0_dsp2: _wait_target_disable failed >> [20867.605206] omap-iommu 41501000.mmu: 41501000.mmu: version 3.0 >> [20867.605483] omap-iommu 41502000.mmu: 41502000.mmu: version 3.0 >> [20867.619103] omap_hwmod: mmu0_dsp1: _wait_target_disable failed >> >> >> Am I missing a step? >> >> Cheers, >> >> Jon >> > -- 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/e28fe150-3638-4a56-8b34-95034d60bf0e%40googlegroups.com.
[beagleboard] TIDL Classification example not properly identify objects
I am attempting to run the TIDL example with a Beaglebone AI and the only thing it seems to report identifying is a ping-pong, although I am not presenting a ping pong to the camera. I am using a Logitech C920 camera and have performed all of the updates to the system, so am not sure what I am missing. This is what I see when running the classification.tidl.cpp example: 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) allocating executors allocating individual EOPs allocating I/O memory for each EOP Allocating input and output buffers Allocating input and output buffers Allocating input and output buffers Allocating input and output buffers num_eops=4 About to start ProcessFrame loop!! http://localhost:8080/?action=stream o: www-folder-path..: /usr/share/mjpg-streamer/www/ o: HTTP TCP port: 8080 o: HTTP Listen Address..: (null) o: username:password: disabled o: commands.: enabled (722)=ping-pong_ball (722)=ping-pong_ball (722)=ping-pong_ball (722)=ping-pong_ball (722)=ping-pong_ball (722)=ping-pong_ball This is what I see from dmesg: [20753.769040] usb 1-1: New USB device found, idVendor=046d, idProduct=082d [20753.769075] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [20753.769097] usb 1-1: Product: HD Pro Webcam C920 [20753.769118] usb 1-1: SerialNumber: C0DB0F6F [20754.099831] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d ) [20754.120146] uvcvideo 1-1:1.0: Entity type for entity Processing 3 was not initialized! [20754.120179] uvcvideo 1-1:1.0: Entity type for entity Extension 6 was not initialized! [20754.120323] uvcvideo 1-1:1.0: Entity type for entity Extension 11 was not initialized! [20754.125089] input: HD Pro Webcam C920 as /devices/platform/4400.ocp/ 488c.omap_dwc3_2/488d.usb/xhci-hcd.1.auto/usb1/1-1/1-1:1.0/input/ input3 [20754.135851] usbcore: registered new interface driver uvcvideo [20754.135871] USB Video Class driver (1.1.1) [20754.437849] usbcore: registered new interface driver snd-usb-audio [20867.134498] usb 1-1: reset high-speed USB device number 3 using xhci-hcd [20867.558788] omap-iommu 58882000.mmu: 58882000.mmu: version 2.1 [20867.605127] omap_hwmod: mmu0_dsp2: _wait_target_disable failed [20867.605206] omap-iommu 41501000.mmu: 41501000.mmu: version 3.0 [20867.605483] omap-iommu 41502000.mmu: 41502000.mmu: version 3.0 [20867.619103] omap_hwmod: mmu0_dsp1: _wait_target_disable failed Am I missing a step? Cheers, Jon -- 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/379db11f-882e-4981-9466-3e9fa9248f84%40googlegroups.com.
[beagleboard] Re: BBBLues
I have a BBBlue that experienced the same fate as your #1 except I get R11 that is dimly lit and no blinky LEDs after a bit. Trying to reflash the eMMC or other image install has resolved the issue. If you find a cure for the Zombie BBBlue, I would be interested in it. Cheers, Jon On Wednesday, September 4, 2019 at 11:02:33 PM UTC, todd.c...@gmail.com wrote: > > So I have had nothing but trouble with my two BBBls. I attempted every > walk through I could find on both of them, every time I would get stuck at > a different point before I could ever get to installing ardupilot software. > I finally got fed up with them, bought a Pixhack, combined it with a I.MX6 > scavenged from a 3DR Solo, and went on about my business. Due to a recent > operator > error induced gravitational field incident, the pixhack seems to have > developed dementia as it no longer oriented as to place time or self. > Therefore, I have recently found it necessary to bring the BBBls out of > storage and give them a second chance. > > > *Here is the problem*: both of these little beauties seem to have called > it quits. When I connect them to a computer, any computer (I've tried Win7, > Win10, and Ubuntu 18.something) with any usb cable sometimes the computer > will acknowledge that a device was connected, sometimes it won't. On > windows, when it realizes that a device is there, it tells me that I need > to format the SD card, as if that was the only thing I connected, Linux > machines will let me view the files but that's it. I no longer have the > "Out the box" files that came on the BBBls that used to be there, the ones > with the little picture of the dog and the "getting started" stuff. Where'd > they go? *Can I re-download the factory software somewhere? or is there a > Factory reset option?* > > > The pictures below are included to show the lights that stay on on each > one. > > #1 G,R,75, and the one by the 12v input light up immediately when power is > applied, with or without an SD card, and 0-3 light up sequentially after > about 5 seconds without a card, a little slower with one. > > #2 goes through the same process, but eventually all lights cut off except > the one by the 12v plug and led zero goes into a double blink, pause > pattern; with or without a card. > > [image: BBBLues1.jpg] > > > [image: BBBLues2.jpg] > > When I say "card", I mean one flashed with > "bone-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz" > > I have installed BONE_64 on my PCs > -- 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/b5bf90e3-01d5-4ebb-928a-e506996f97f4%40googlegroups.com.
[beagleboard] BeagelBone AI release revision
Hi, I was quite excited to have received the BeagelBone AI I purchased, however looking at the System Reference Manual, it lists revision A1a as the the initial production rev yet the one I have received shows it is a A1. Is the one I have the wrong revision for production and should I return it? Ref: https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#board-changes 2.2.2 Rev A1 Second round prototype 2.2.3 Rev A1a Alpha pilot-run units and initial production. Cheers, Jon -- 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/77f13324-781b-4686-8158-620d0afefba0%40googlegroups.com.
[beagleboard] BeagleBoard.org - Bad Gateway
When attempting to access anything at BeagleBoard.org I am getting a "502 Bad Gateway nginx/1.12.2" error. Is this site down? Cheers, Jon -- 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/86f498a1-c394-4ce5-9e03-9814f43bceab%40googlegroups.com.
[beagleboard] Beagebone AI release revision
Hi, I was quite excited to have received the BeagleBone AI I purchased, however looking at the System Reference Manual it lists revision A1a as the the initial production rev yet the one I have received shows it is a A1. Is the one I have the wrong revision for production and should I return it? Ref: https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#board-changes 2.2.3 Rev A1a Alpha pilot-run units and initial production. Cheers, Jon -- 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/73beb98c-6cff-473e-ad90-c6aa13fe1022%40googlegroups.com.
