Re: [beagleboard] Disabling HDMI kills WiFi
Thanks! That worked. On Thursday, June 22, 2017 at 11:13:59 PM UTC-4, RobertCNelson wrote: > > On Thu, Jun 22, 2017 at 8:50 PM, Brent H Horine <bho...@gmail.com > > wrote: > > Eventually I want to use PRU and want to disable HDMI to have more > inputs > > available. I setup WiFi and verify it works. In /boot/uEnv.txt, I > uncomment > > > > ##BeagleBone Black: HDMI (Audio/Video) disabled: > > dtb=am335x-boneblack-emmc-overlay.dtb > > > > and reboot. > > > > Once back in I try to ping my server and get the response: "connect: > Network > > is unreachable". Trying to use "sudo connmanctl" gives all sorts of > > complaints such as 'Method "Scan" with signature "" on interface > > "net.connman.technology" doesn't exist'. Re-commenting the dtb line and > > rebooting allows WiFi operation again (without even need to go through > > connmanctl again). > > > > Is there a way to disable the HDMI while retaining WiFi? > > > > Output of uname -a > > Linux beaglebone 4.4.54-ti-r93 #1 SMP Fri Mar 17 13:08:22 UTC 2017 > armv7l > > GNU/Linux > > This has to be done with u-boot overlays: > > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > enable_uboot_overlays=1 > disable_uboot_overlay_video=1 > > 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/859be6ae-f4a5-478d-91aa-9d8a4ddb4381%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Disabling HDMI kills WiFi
Eventually I want to use PRU and want to disable HDMI to have more inputs available. I setup WiFi and verify it works. In /boot/uEnv.txt, I uncomment ##BeagleBone Black: HDMI (Audio/Video) disabled: dtb=am335x-boneblack-emmc-overlay.dtb and reboot. Once back in I try to ping my server and get the response: "connect: Network is unreachable". Trying to use "sudo connmanctl" gives all sorts of complaints such as 'Method "Scan" with signature "" on interface "net.connman.technology" doesn't exist'. Re-commenting the dtb line and rebooting allows WiFi operation again (without even need to go through connmanctl again). Is there a way to disable the HDMI while retaining WiFi? Output of uname -a Linux beaglebone 4.4.54-ti-r93 #1 SMP Fri Mar 17 13:08:22 UTC 2017 armv7l GNU/Linux -- 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/bf4e9695-d198-4ece-b770-ffdf563db56c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Module is loaded, but no wlan0 interface
Thanks for the help - I figured it out... it was operator error. The evaluation board that I was using with the Marvell chip apparently just needed another connector plugged in for power. Once I plugged that in, the interface was available for me to bring up. On Saturday, September 27, 2014 10:44:16 PM UTC-4, liyaoshi wrote: I am not sure about if 3.8.x kernel support marvel 8797 . In my previous experience , when ifconfig -a show nothing about your adapter , try another newer version driver http://wireless.kernel.org/en/users/Download/stable/ maybe you can try compat-wireless hope its be useful 2014-09-27 10:35 GMT+08:00 Brent bren...@hotmail.com javascript:: Anyone have any ideas what else I could try? I'll try to contact the manufacturer, but have a feeling that won't go very far... On Monday, September 22, 2014 10:13:13 PM UTC-4, Brent wrote: Here is what I get when I run 'ip addr': [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff I'm not sure if the driver needs ndiswrapper or not... how do I tell? I did find the following website, but looks like it's for Ubuntu. http://askubuntu.com/questions/257600/marvells- wireless-driver-not-recognized On Mon, Sep 22, 2014 at 9:31 PM, Don deJuan donju...@gmail.com javascript: wrote: On 09/22/2014 06:15 PM, Brent wrote: Also, other USB to WiFi adapters work just fine. For example, I have one that uses the rtl8192cu driver, and this one creates a wlan0 interface automatically. Any ideas what would be causing this? On Monday, September 22, 2014 7:49:37 PM UTC-4, Brent wrote: I have not done anything with udev yet... I read through the Wireless netwrok configuration wiki, but didn't see anywhere on how to create the interface. https://wiki.archlinux.org/index.php/Wireless_network_ configuration#Interface_activation I'm starting to read the wiki on udev, but is that too general, or do you know of something else I should be looking at? https://wiki.archlinux.org/index.php/udev ip addr only lists eth0 and lo. [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff Thanks, On Mon, Sep 22, 2014 at 6:54 PM, Don deJuan wrote: On 09/22/2014 02:25 PM, Brent wrote: I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet
Re: [beagleboard] Module is loaded, but no wlan0 interface
Anyone have any ideas what else I could try? I'll try to contact the manufacturer, but have a feeling that won't go very far... On Monday, September 22, 2014 10:13:13 PM UTC-4, Brent wrote: Here is what I get when I run 'ip addr': [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff I'm not sure if the driver needs ndiswrapper or not... how do I tell? I did find the following website, but looks like it's for Ubuntu. http://askubuntu.com/questions/257600/marvells-wireless-driver-not-recognized On Mon, Sep 22, 2014 at 9:31 PM, Don deJuan donjuans...@gmail.com wrote: On 09/22/2014 06:15 PM, Brent wrote: Also, other USB to WiFi adapters work just fine. For example, I have one that uses the rtl8192cu driver, and this one creates a wlan0 interface automatically. Any ideas what would be causing this? On Monday, September 22, 2014 7:49:37 PM UTC-4, Brent wrote: I have not done anything with udev yet... I read through the Wireless netwrok configuration wiki, but didn't see anywhere on how to create the interface. https://wiki.archlinux.org/index.php/Wireless_network_ configuration#Interface_activation I'm starting to read the wiki on udev, but is that too general, or do you know of something else I should be looking at? https://wiki.archlinux.org/index.php/udev ip addr only lists eth0 and lo. [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff Thanks, On Mon, Sep 22, 2014 at 6:54 PM, Don deJuan wrote: On 09/22/2014 02:25 PM, Brent wrote: I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.54.183.74 netmask 255.255.255.0 broadcast 10.54.183.255 inet6 fe80::caa0:30ff:feac:e319 prefixlen 64 scopeid 0x20link ether c8:a0:30:ac:e3:19 txqueuelen 1000 (Ethernet) RX packets 11697 bytes 1387285 (1.3 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 1117 bytes 148026 (144.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 40 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 186 bytes 14214 (13.8 KiB) RX errors 0 dropped
[beagleboard] Module is loaded, but no wlan0 interface
I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.54.183.74 netmask 255.255.255.0 broadcast 10.54.183.255 inet6 fe80::caa0:30ff:feac:e319 prefixlen 64 scopeid 0x20link ether c8:a0:30:ac:e3:19 txqueuelen 1000 (Ethernet) RX packets 11697 bytes 1387285 (1.3 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 1117 bytes 148026 (144.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 40 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 186 bytes 14214 (13.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186 bytes 14214 (13.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@alarm ~]# lsmod Module Size Used by mwifiex_usb 8870 0 mwifiex 123902 1 mwifiex_usb cfg80211 421700 1 mwifiex rfkill 18407 1 cfg80211 omap_rng4599 0 autofs421976 2 [root@alarm ~]# modinfo mwifiex_usb filename: /lib/modules/3.8.13-34-ARCH/kernel/drivers/net/wireless/mwifiex/mwifiex_usb.ko.gz firmware: mrvl/usb8797_uapsta.bin license:GPL v2 version:1.0 description:Marvell WiFi-Ex USB Driver version1.0 author: Marvell International Ltd. srcversion: 430F2EB6A43396FC9E1AE01 alias: usb:v1286p2044d*dc*dsc*dp*icFFiscFFipFFin* alias: usb:v1286p2043d*dc*dsc*dp*ic*isc*ip*in* depends:mwifiex intree: Y vermagic: 3.8.13-34-ARCH SMP mod_unload modversions ARMv7 p2v8 [root@alarm ~]# -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Module is loaded, but no wlan0 interface
I have not done anything with udev yet... I read through the Wireless netwrok configuration wiki, but didn't see anywhere on how to create the interface. https://wiki.archlinux.org/index.php/Wireless_network_configuration#Interface_activation I'm starting to read the wiki on udev, but is that too general, or do you know of something else I should be looking at? https://wiki.archlinux.org/index.php/udev ip addr only lists eth0 and lo. [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff Thanks, On Mon, Sep 22, 2014 at 6:54 PM, Don deJuan donjuans...@gmail.com wrote: On 09/22/2014 02:25 PM, Brent wrote: I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.54.183.74 netmask 255.255.255.0 broadcast 10.54.183.255 inet6 fe80::caa0:30ff:feac:e319 prefixlen 64 scopeid 0x20link ether c8:a0:30:ac:e3:19 txqueuelen 1000 (Ethernet) RX packets 11697 bytes 1387285 (1.3 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 1117 bytes 148026 (144.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 40 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 186 bytes 14214 (13.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186 bytes 14214 (13.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@alarm ~]# lsmod Module Size Used by mwifiex_usb 8870 0 mwifiex 123902 1 mwifiex_usb cfg80211 421700 1 mwifiex rfkill 18407 1 cfg80211 omap_rng4599 0 autofs421976 2 [root@alarm ~]# modinfo mwifiex_usb filename: /lib/modules/3.8.13-34-ARCH/kernel/drivers/net/wireless/mwifiex/mwifiex_usb.ko.gz firmware: mrvl/usb8797_uapsta.bin license:GPL v2 version:1.0 description:Marvell WiFi-Ex USB Driver version1.0 author: Marvell International Ltd. srcversion: 430F2EB6A43396FC9E1AE01 alias: usb:v1286p2044d*dc*dsc*dp*icFFiscFFipFFin* alias: usb:v1286p2043d*dc*dsc*dp*ic*isc*ip*in* depends:mwifiex intree: Y vermagic: 3.8.13-34-ARCH SMP mod_unload modversions ARMv7 p2v8 [root@alarm ~]# -- 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
Re: [beagleboard] Module is loaded, but no wlan0 interface
Also, other USB to WiFi adapters work just fine. For example, I have one that uses the rtl8192cu driver, and this one creates a wlan0 interface automatically. Any ideas what would be causing this? On Monday, September 22, 2014 7:49:37 PM UTC-4, Brent wrote: I have not done anything with udev yet... I read through the Wireless netwrok configuration wiki, but didn't see anywhere on how to create the interface. https://wiki.archlinux.org/index.php/Wireless_network_configuration#Interface_activation I'm starting to read the wiki on udev, but is that too general, or do you know of something else I should be looking at? https://wiki.archlinux.org/index.php/udev ip addr only lists eth0 and lo. [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff Thanks, On Mon, Sep 22, 2014 at 6:54 PM, Don deJuan wrote: On 09/22/2014 02:25 PM, Brent wrote: I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.54.183.74 netmask 255.255.255.0 broadcast 10.54.183.255 inet6 fe80::caa0:30ff:feac:e319 prefixlen 64 scopeid 0x20link ether c8:a0:30:ac:e3:19 txqueuelen 1000 (Ethernet) RX packets 11697 bytes 1387285 (1.3 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 1117 bytes 148026 (144.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 40 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 186 bytes 14214 (13.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186 bytes 14214 (13.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@alarm ~]# lsmod Module Size Used by mwifiex_usb 8870 0 mwifiex 123902 1 mwifiex_usb cfg80211 421700 1 mwifiex rfkill 18407 1 cfg80211 omap_rng4599 0 autofs421976 2 [root@alarm ~]# modinfo mwifiex_usb filename: /lib/modules/3.8.13-34-ARCH/kernel/drivers/net/wireless/mwifiex/mwifiex_usb.ko.gz firmware: mrvl/usb8797_uapsta.bin license:GPL v2 version:1.0 description:Marvell WiFi-Ex USB Driver version1.0 author: Marvell International Ltd. srcversion: 430F2EB6A43396FC9E1AE01 alias: usb:v1286p2044d*dc*dsc*dp*icFFiscFFipFFin* alias: usb:v1286p2043d*dc*dsc*dp*ic*isc*ip*in* depends:mwifiex intree: Y vermagic: 3.8.13-34-ARCH SMP mod_unload modversions ARMv7 p2v8 [root@alarm
Re: [beagleboard] Module is loaded, but no wlan0 interface
Here is what I get when I run 'ip addr': [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff I'm not sure if the driver needs ndiswrapper or not... how do I tell? I did find the following website, but looks like it's for Ubuntu. http://askubuntu.com/questions/257600/marvells-wireless-driver-not-recognized On Mon, Sep 22, 2014 at 9:31 PM, Don deJuan donjuans...@gmail.com wrote: On 09/22/2014 06:15 PM, Brent wrote: Also, other USB to WiFi adapters work just fine. For example, I have one that uses the rtl8192cu driver, and this one creates a wlan0 interface automatically. Any ideas what would be causing this? On Monday, September 22, 2014 7:49:37 PM UTC-4, Brent wrote: I have not done anything with udev yet... I read through the Wireless netwrok configuration wiki, but didn't see anywhere on how to create the interface. https://wiki.archlinux.org/index.php/Wireless_network_ configuration#Interface_activation I'm starting to read the wiki on udev, but is that too general, or do you know of something else I should be looking at? https://wiki.archlinux.org/index.php/udev ip addr only lists eth0 and lo. [root@alarm ~]# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:a0:30:ac:e3:19 brd ff:ff:ff:ff:ff:ff Thanks, On Mon, Sep 22, 2014 at 6:54 PM, Don deJuan wrote: On 09/22/2014 02:25 PM, Brent wrote: I'm having trouble getting the wlan0 interface to show up for a Marvell 8797 USB to WiFi chip, and it seems like everything should be working. I'm running Arch Linux Arm, 3.8.13 kernel, and have verified that the modules are loaded correctly, and that it recognizes the device, but still no wlan0 interface. I also verified that the firmware is indeed in the /lib/firmware/mrvl/ directory. Am I missing something obvious? Here is my output from dmesg, lsmod, and modinfo. [ 15.321430] usb usb1: usb wakeup-resume [ 15.321482] usb usb1: usb auto-resume [ 15.321503] hub 1-0:1.0: hub_resume [ 15.321551] hub 1-0:1.0: port 1: status 0101 change 0001 [ 15.424482] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 15.424547] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 15.529900] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ 15.650300] usb 1-1: default language 0x0409 [ 15.651367] usb 1-1: udev 2, busnum 1, minor = 1 [ 15.651387] usb 1-1: New USB device found, idVendor=1286, idProduct=2043 [ 15.651399] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 15.651410] usb 1-1: Product: Marvell Wireless Device [ 15.651420] usb 1-1: Manufacturer: Marvell [ 15.651430] usb 1-1: SerialNumber: [ 15.651958] usb 1-1: usb_probe_device [ 15.651978] usb 1-1: configuration #1 chosen from 1 choice [ 15.655328] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 15.656222] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 15.656269] hub 1-0:1.0: port 1 enable change, status 0503 [ 15.787448] cfg80211: Calling CRDA to update world regulatory domain [ 15.811632] usb8797 1-1:1.0: usb_probe_interface [ 15.811661] usb8797 1-1:1.0: usb_probe_interface - got id [ 15.820715] usbcore: registered new interface driver usb8797 [root@alarm ~]# ifconfig -a eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 10.54.183.74 netmask 255.255.255.0 broadcast 10.54.183.255 inet6 fe80::caa0:30ff:feac:e319 prefixlen 64 scopeid 0x20link ether c8:a0:30:ac:e3:19 txqueuelen 1000 (Ethernet) RX packets 11697 bytes 1387285 (1.3 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 1117 bytes 148026 (144.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 40 lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback) RX packets 186 bytes 14214 (13.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186 bytes 14214 (13.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@alarm ~]# lsmod Module Size Used by mwifiex_usb 8870 0 mwifiex
Re: [beagleboard] Re: Cross-Compiling Qt5 on Beaglebone Black with OpenGL
Don, This may sound strange, but would I be able to install qt5 on arch linux, and then copy all of the qt libraries over to my Angstrom OS and have it work? I am currently not able to switch to an new OS in our product at the current time, so I'm looking for ways to make this work. Thanks, On Monday, July 21, 2014 12:35:14 PM UTC-4, don wrote: On 07/21/2014 09:29 AM, Jay wrote: Hey guys, No luck for me in getting this working. Beaglebone seems to have quite a few issues with Qt5 and the build doesn't seem to want to cooperate. For others looking to pursue the same route, I got several suggestions to take the route of Yocto and bitbaking the meta-ti recipe, which seems promising. For me, because my project is flexible, (call me a traitor) I switched to a Raspberry Pi to build Qt5 on to. It was incredibly easy to get the latest Qt5.3.1 build on there and all the driv Or you could just use an OS for BBB that has it built for you since you seem to not be able to build it yourself on that platform. wipe Debian, install archlinux-arm pacman -S qt5 AndWhatEverElseYouWantQT5Related Again you can even install qt4 and at5 side by side profit. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAN bus recovery
Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai devan@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAN bus recovery
Well, I'm not reading a guide, but I'll share a few links that helped me get started. I have a Qt application and I use the SocketCAN to read/write CAN messages. This will work with J1939 as well. https://www.kernel.org/doc/Documentation/networking/can.txt http://en.wikipedia.org/wiki/SocketCAN http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent...@gmail.com javascript: wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai deva...@gmail.com javascript: wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: CAN bus recovery
Ah, yes. The TT3201 cape has three CAN channels, but two of them are over SPI. This should help you out... https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/TT3201-001-01.dts On Thu, Sep 11, 2014 at 8:00 PM, William Hermans yyrk...@gmail.com wrote: Thank Brent, However I was more curious about the bring up of the hardware on the BBB. IS there cape file I have not noticed yet ? If so I can probably figure it out on my own. On Thu, Sep 11, 2014 at 4:52 PM, Brent brent...@hotmail.com wrote: Well, I'm not reading a guide, but I'll share a few links that helped me get started. I have a Qt application and I use the SocketCAN to read/write CAN messages. This will work with J1939 as well. https://www.kernel.org/doc/Documentation/networking/can.txt http://en.wikipedia.org/wiki/SocketCAN http://www.can-cia.org/fileadmin/cia/files/icc/13/kleine-budde.pdf On Thursday, September 11, 2014 7:44:50 PM UTC-4, William Hermans wrote: Brent, what guide are you reading for CAN ? I've never used CAN personally, and am curious . . . On Thu, Sep 11, 2014 at 2:25 PM, Brent Sink brent...@gmail.com wrote: Adding restart-ms did the trick! Thanks so much, I never knew that was even there. On Wed, Sep 10, 2014 at 8:37 PM, Devan Lai deva...@gmail.com wrote: You can configure the controller to automatically recover from bus-off conditions by setting the restart-ms option. The python-can documentation has some useful notes on socket-can and bus-off conditions: http://python-can.readthedocs.org/en/latest/socketcan.html#can-errors On Wednesday, September 10, 2014 9:39:21 AM UTC-7, Brent wrote: I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/SdvoxYkgagc/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Will the watchdog reset if the kernel panics?
Does anyone know that if the watchdog timer is enabled, will a kernel panic still allow the watchdog to reset? Since it's not an external watchdog, I wasn't sure what would happen. I've seen some cases where the kernel will panic and completely brick my device until it is manually rebooted. I haven't had a chance to debug why the kernel panics at what seems like random times, so I need to do some investigation. However, my band-aid to the problem would be to enable the watchdog timer so that it will automatically reboot. I would just try it, but I'm having a hard time reproducing a kernel panic. Also, on a side note, how do you change the default duration of 60 seconds? It seems like this info would be all over the internet, but I haven't found anywhere that talks about this. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Will the watchdog reset if the kernel panics?
I figured out how to change the watchdog duration. The example program is here: http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/ And a good description of the available commands is here: https://github.com/shengchao/beaglebone-angstrom-xenomai/blob/master/Documentation/watchdog/watchdog-api.txt However, my first question regarding the kernel panic still remains. Also, if I do get a kernel panic, how do I record the error message/code so that I can debug it later? On Thursday, September 11, 2014 9:15:02 PM UTC-4, Brent wrote: Does anyone know that if the watchdog timer is enabled, will a kernel panic still allow the watchdog to reset? Since it's not an external watchdog, I wasn't sure what would happen. I've seen some cases where the kernel will panic and completely brick my device until it is manually rebooted. I haven't had a chance to debug why the kernel panics at what seems like random times, so I need to do some investigation. However, my band-aid to the problem would be to enable the watchdog timer so that it will automatically reboot. I would just try it, but I'm having a hard time reproducing a kernel panic. Also, on a side note, how do you change the default duration of 60 seconds? It seems like this info would be all over the internet, but I haven't found anywhere that talks about this. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] CAN bus recovery
I have noticed that if I short CAN_H and CAN_L together, or if there is noise on the bus, the BeagleBone will stop sending and receiving CAN messages. When this happens, if I execute ifconfig can0 down and ifconfig can0 up, things start working again. Is there a way to detect this automatically and recover? I'm using SocketCAN, but haven't found anything that would tell me when I get a bus off or bus heavy. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to properly update my application
The MD5 sum seems like a good approach. For anyone reading this, I found
this link useful:
http://askubuntu.com/questions/318530/generate-md5-checksum-for-all-files-in-a-directory
find -exec md5sum {} \; checklist.chk
md5sum -c checklist.chk # runs through the list to check them
On Saturday, September 6, 2014 6:33:33 PM UTC-4, William Hermans wrote:
Define something gets messed up. You're going to have to know what this
something *is* before solving the issue. But perhaps you could use an MD5
sum to verify the file ? Then when there is a mismatch you delete the
target file and try again ?
On Sat, Sep 6, 2014 at 3:02 PM, Brent bren...@hotmail.com javascript:
wrote:
I have a Qt application that runs at start up. Currently, I update my
application by allowing the user to press a button inside of my application
which copies the updated application files from the USB drive to the eMMC.
It then sets a flag inside of a text file to 1, and reboots. When my
start up script is ran, it firsts checks the text file to see if there is a
1, and if so it overwrites the old files with the new ones and then
launches the application. This works most of the time, but there are
occasions where something gets messed up and the new application does not
start.
I was wondering if there is a better way of updating my application.
Could I use opkg to do this, and if so, how? Will it allow my application
to be running while it is updating it? What is the proper way to do this?
Thanks in advance for your help!
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout.
--
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.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BeagleBone Black switching to 3.14 kernel
Thanks for the update Jason... I didn't realize the kernel repo had moved - I was wondering why there wasn't much activity recently! I was looking at the 3.8 branch and noticed that Robert had added SGX... it would appear that 3.8 will also now have SGX working, not only 3.14, right? I didn't see any commits regarding DMA for USB though... On Sunday, August 17, 2014 9:26:34 PM UTC-4, Jason Kridner wrote: It is time to make another big software push for BeagleBone Black. We have several recent updates from Robert, including managing the kernel as Debian packages. To try out the new code, use one of the recent images from: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 Then, you'll need to switch to the 3.14 kernel: sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 Report issues to one of these trackers: https://github.com/beagleboard/linux http://bugs.elinux.org/projects/debian-image-releases The device tree overlay support is still under development as is built-in 'config-pin/cape-universal' support, so static configuration of the .dtb is currently required. Your help is requested to make sure the default .dtb file includes as many configurations as possible that can be enabled from userspace. Update summary: * Repo moved to https://github.com/beagleboard/linux * Layout of Debian images now enable 'apt-get' updates to the kernel, but you need to grab a newer starting distro image * The false-start on the cape-firmware repo has been abandoned and device tree overlays are now part of the kernel tree * The kernel currently uses DMA for the USB and includes SGX support I've setup a buildbot hosted at http://builds.beagleboard.org, but I'm still working on getting it to handle pull requests, multiple branches, etc. like the MachineKit folks are doing, as well as pushing out the builds. After a bit more feedback, I'll push out some blog posts, etc. to get more people involved. Thanks for your help! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to properly update my application
I have a Qt application that runs at start up. Currently, I update my application by allowing the user to press a button inside of my application which copies the updated application files from the USB drive to the eMMC. It then sets a flag inside of a text file to 1, and reboots. When my start up script is ran, it firsts checks the text file to see if there is a 1, and if so it overwrites the old files with the new ones and then launches the application. This works most of the time, but there are occasions where something gets messed up and the new application does not start. I was wondering if there is a better way of updating my application. Could I use opkg to do this, and if so, how? Will it allow my application to be running while it is updating it? What is the proper way to do this? Thanks in advance for your help! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to properly update my application
I can't quite define it, but something seems to get corrupted. When the new corrupted application runs, it only shows a white rectangle, rather than the application. I guess I was wondering how others update their own software applications - if they do something similar to what I'm doing or if they are using opkg/apt-get/etc. The MD5 sum may be something I could look into... I'm not familiar on how to implement that, but I'll do some research. Thanks, On Sat, Sep 6, 2014 at 6:33 PM, William Hermans yyrk...@gmail.com wrote: Define something gets messed up. You're going to have to know what this something *is* before solving the issue. But perhaps you could use an MD5 sum to verify the file ? Then when there is a mismatch you delete the target file and try again ? On Sat, Sep 6, 2014 at 3:02 PM, Brent brent...@hotmail.com wrote: I have a Qt application that runs at start up. Currently, I update my application by allowing the user to press a button inside of my application which copies the updated application files from the USB drive to the eMMC. It then sets a flag inside of a text file to 1, and reboots. When my start up script is ran, it firsts checks the text file to see if there is a 1, and if so it overwrites the old files with the new ones and then launches the application. This works most of the time, but there are occasions where something gets messed up and the new application does not start. I was wondering if there is a better way of updating my application. Could I use opkg to do this, and if so, how? Will it allow my application to be running while it is updating it? What is the proper way to do this? Thanks in advance for your help! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/4FY8Owh_i_I/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] NTSC/PAL video input
I ended up buying an encoder from Grandstream that converts analog video to Ethernet. Once the camera is on Ethernet, you can use mplayer or the player of your choice to play the mjpeg/rtsp stream. On Fri, Jul 18, 2014 at 12:21 PM, ctmatthie...@gmail.com wrote: Hey Brent - did you have any luck with analog video capture on the BBB? I need to also capture analog video and am struggling to find a solution that is capable of 30fps NTSC. What did you end up doing to solve your problem??? On Monday, October 14, 2013 7:31:11 PM UTC-7, Brent wrote: I wish the USB based NTSC capture dongle were that simple. I've tried Hauppauge USB Live-2, and Easy-Cap, but neither work with the BeagleBone Black. It seems that the BBB is to slow for that. I've considered the camera capes that are available, but really need a solution that interfaces with an analog camera. On Mon, Oct 14, 2013 at 10:27 PM, Chris Whittenburg whitt...@gmail.com wrote: On Mon, Oct 14, 2013 at 8:37 PM, Brent bren...@hotmail.com wrote: I'm looking for a reference design for a NTSC/PAL video input on the BeagleBone Black. The only thing I found so far is from e-consystems.com, but there is no schematic available. I have an analog camera where I need to capture the input and display it on an LCD, but so far I haven't been able to find any good decoder schematics. Does anyone know of any that may exist? http://www.e-consystems.com/NTSC-PAL-Video-Decoder-Board-Gumstix.asp That board is for the Gumstix Overo, which is an OMAP3730, and more like the Beagleboard XM. It would work for the Beaglebone Black, which doesn't have the same sort of camera interface. You would have to do something more like the Beaglebone Camera Cape, which uses a special purpose chip to interface the camera to the GPMC port of the bone. It would be quite a bit of work. I would suggest some sort of cheap USB based NTSC capture dongle that already has linux support. -chris -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/beagleboard/iMs8S90aXzk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/iMs8S90aXzk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -brent -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Using mplayer framebuffer on top of application
I have a Qt application (QML) that requires me to play videos. I tried the QtMultimediaKit with not much luck so I decided to switch to mplayer and have had great success. In my Qt application, I create a new process to launch mplayer and it plays the video on the framebuffer just fine. However, if I have an element underneath the video that gets updated, the element pokes through the video for as long as the element is updated. It basically looks like Qt and mplayer are fighting to paint the screen. Is there a way to make mplayer take the highest z-order to prevent this from happening? mplayer -slave -really-quiet -vo fbdev2 -fps 15 -zoom -x 800 -y 400 myVideo.mp4 -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Ok, got it. I need to contribute to try it out. Here is my problem, and I would like to hear if this solves it. I have a hub that uses the SMSC 2512 hub chip (USB2512QFN36). Mass storage devices work as long as it's inserted at power up. Any hot plugging after boot will not work. Does your kernel fix this problem? Also, I have some other items in the kernel that I need enabled. If I contribute $50 or $125 I only get whatever you built into your kernel... right? Could I give you my .config and you build it? On Mon, Dec 23, 2013 at 6:33 PM, APRichelieu aprichel...@gmail.com wrote: Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent: Where do I go to get Ulf's kernel? I would like to test but I don't know where to look. Is there a patch somewhere that I missed? Check The http://igg.me link in your post. On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.comwrote: I've also put in $125 and must say that I haven't had any troubles since using Ulf's kernel. Thanks Ulf On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote: I've ponied up for the $125 donation. Gotta have this running right. On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu apric...@gmail.com wrote: Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com: I'm using my Beaglebone Black with a USB temperature sensor. It works very well, however I noticed monitoring stopped last night after roughly 35 days uptime. This morning I looked more closely into the log file and noticed: kernel: [2892926.929555] CAUTION: musb: Babble Interrupt Occurred I wasn't able to successfully reset the USB device and before I was able to restart the BBB stopped responding. I power-cycled it and it was back to normal again. Any ideas what caused this kernel message? I set up a crowd-funding project on http://igg.me/at/eMagii/x/5581172 for people that wants to have USB host hot-plugging on the Beaglebone Black -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Playing .avi, .mpg, or .mp4 files
Scott, I tried building VLC using: bitbake vlc, but it fails, and I have no idea how to fix this. The output from the bitbake recipe is below. Any suggestions? ERROR: Function failed: do_compile (see /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/temp/log.do_compile.18454 for further information) ERROR: Logfile of failure stored in: /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/temp/log.do_compile.18454 Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j2 -e MAKEFLAGS= KERNEL_PATH=/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone/usr/src/kernel KERNEL_SRC=/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone/usr/src/kernel KERNEL_VERSION=3.8.13 CC=arm-angstrom-linux-gnueabi-gcc -mno-thumb-interwork -marm LD=arm-angstrom-linux-gnueabi-ld AR=arm-angstrom-linux-gnueabi-ar BUILD=release TI_PLATFORM=ti335x | make -C /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone/usr/src/kernel M=`pwd` | make[1]: Entering directory `/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone/usr/src/kernel' | CC [M] /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o | /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.c: In function 'bc_cat_init': | /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.c:612:6: error: implicit declaration of function 'cpu_is_omap3530' [-Werror=implicit-function-declaration] | /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.c:612:6: error: implicit declaration of function 'omap_rev' [-Werror=implicit-function-declaration] | /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.c:612:56: error: 'OMAP3430_REV_ES3_0' undeclared (first use in this function) | /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.c:612:56: note: each undeclared identifier is reported only once for each function it appears in | cc1: some warnings being treated as errors | make[3]: *** [/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o] Error 1 | make[2]: *** [/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM/services4/3rdparty/bufferclass_ti] Error 2 | make[1]: *** [_module_/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/Graphics_SDK_4_05_00_03/GFX_Linux_KM] Error 2 | make[1]: Leaving directory `/media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone/usr/src/kernel' | make: *** [all] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (see /media/brent/Disk2/oe/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/beaglebone-angstrom-linux-gnueabi/omap3-sgx-modules-4.05.00.03-r23b/temp/log.do_compile.18454 for further information) ERROR: Task 1523 (/media/brent/Disk2/oe/setup-scripts/sources/meta-ti/recipes-bsp/powervr-drivers/omap3-sgx-modules_4.05.00.03.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2477 tasks of which 2475 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /media/brent/Disk2/oe/setup-scripts/sources/meta-ti/recipes-bsp/powervr-drivers/omap3-sgx-modules_4.05.00.03.bb, do_compile Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. On Saturday, November 23, 2013 11:34:49 PM
[beagleboard] Re: Playing a RTSP video stream on BeagleBone
ffmpeg seems to stream the video just fine, but I cannot seem to get it to display the video on either the framebuffer or on X if I'm running the gdm service. For example: This works by streaming the video and saving it as a .mov file. If I copy this to my development machine the .mov file plays just fine. ffmpeg -i rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov -c:v libx264 -f h264 test.mov This does not work. I get a lot of weird looking pixels on my display. ffmpeg -i rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov -c:v libx264 -f h264 /dev/fb0 Suggestions? On Wednesday, November 20, 2013 4:19:52 PM UTC-5, Brent wrote: I'm trying to stream a video using RTSP to the BeagleBone, but I have not had any luck. Using mplayer, I call the following command: mplayer -vo fbdev2 -demuxer live555 rtsp:// 184.72.239.149/vod/mp4:BigBuckBunny_115k.mov This video works just fine with VLC player in Ubuntu (x86), but when running on the BeagleBone it does not. I have installed the gst-plugins-good-rtsp, and libgstrtsp-0.10-0 packages. Anything else that I could try? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Playing .avi, .mpg, or .mp4 files
for compiling it. On Saturday, 23 November 2013 23:14:24 UTC-5, Brent wrote: Thanks for the response, but I am not using a window manager, so I can't use VLC. I need to be able to display the video on the frame buffer. I've also tried ffmpeg, but no luck there either. On Saturday, November 23, 2013 10:50:43 PM UTC-5, Scott Force wrote: I am in the process of ordering my very first BeagleBone Black so I can't attest to how it plays videos. Maybe try a different video player such as VLC and see if it makes a difference. On Wednesday, 20 November 2013 15:15:06 UTC-5, Brent wrote: This should be straightforward, but I'm having some problems getting this to work. Using mplayer, I use the following command: mplayer -ao alsa -vo fbdev2 -zoom -x 800 -y 480 test.mpg Whenever I run this command, it shows the first frame, and then nothing else. I've tried .avi, .mpg, and .mp4 files, but they all have the same result. Has anyone been able to play videos on the BeagleBone Black? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Playing .avi, .mpg, or .mp4 files
Has anyone had any luck playing videos on the Beaglebone? It it just a setting or codec I'm missing? On Wednesday, November 20, 2013 3:15:06 PM UTC-5, Brent wrote: This should be straightforward, but I'm having some problems getting this to work. Using mplayer, I use the following command: mplayer -ao alsa -vo fbdev2 -zoom -x 800 -y 480 test.mpg Whenever I run this command, it shows the first frame, and then nothing else. I've tried .avi, .mpg, and .mp4 files, but they all have the same result. Has anyone been able to play videos on the BeagleBone Black? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Playing .avi, .mpg, or .mp4 files
This should be straightforward, but I'm having some problems getting this to work. Using mplayer, I use the following command: mplayer -ao alsa -vo fbdev2 -zoom -x 800 -y 480 test.mpg Whenever I run this command, it shows the first frame, and then nothing else. I've tried .avi, .mpg, and .mp4 files, but they all have the same result. Has anyone been able to play videos on the BeagleBone Black? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Set default volume of Alsa
Whenever my BeagleBone starts up, the volume always seems to be somewhere around 40%. I open up alsamixer and increase the volume to 100% and all is good. However, is there a way to make the default volume always be set at 100%? (I know there is, but how?) -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Playing a RTSP video stream on BeagleBone
I'm trying to stream a video using RTSP to the BeagleBone, but I have not had any luck. Using mplayer, I call the following command: mplayer -vo fbdev2 -demuxer live555 rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov This video works just fine with VLC player in Ubuntu (x86), but when running on the BeagleBone it does not. I have installed the gst-plugins-good-rtsp, and libgstrtsp-0.10-0 packages. Anything else that I could try? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: CAUTION: musb: Babble Interrupt Occurred
Not surprised. I've had all sorts of problems with USB when using a hub chip. It all seems to point to a software/driver glitch. I really wish I could help out to fix it, but I'm more of an application developer. On Oct 28, 2013 8:33 PM, p...@ideos.com wrote: I've got the same 'CAUTION: musb: Babble Interrupt Occurred' error in dmesg. Running the latest Angstrom on the Black with a Symbol DS457 attached. On Thursday, October 24, 2013 2:17:01 AM UTC-4, Rune wrote: That's what I'm running, so then maybe that's not the answer :) Any other ideas as to why the USB drops out? Regards, Rune On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote: On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg gre...@gmail.com wrote: Have you confirmed that this patch works? That patch was first enabled with the 3.8.13-bone28 release.. I'm running Debian Wheezy and getting the same issue myself. Wifi dongle drops out and will not come back up unless i power cycle. Would this kernel fix work with Debian? Or just Anstrom? I often get another message as well: [92458.978265] CAUTION: musb: Babble Interrupt Occurred [92459.049531] gadget: high-speed config #1: Multifunction with RNDIS These two almost always travel in pairs. Sometimes multiples of them will appear. Running an rtl819cu wifi chipset. The one adafruit sells. Btw, as long as you are not using any capes, you can also give v3.12-rc6 a try as usb seems to be working a lot better with these wifi devices.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/C6gMT2_FfiM/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] NTSC/PAL video input
As far as you did, it appears. I was not the one who actually worked with the ezcap or the USB-Live 2 devices, but the failure was attributed to the BBB's inability to support isochronous transfers from the device. Devices using the uvcvideo driver seems to work just fine, but others do not. On Sun, Oct 20, 2013 at 12:59 PM, jesco...@googlemail.com wrote: Hi Brent, Just wondering how far you got with the ezcap device? I've also got a requirement to capture some analog video, but have been hitting a brick wall with my ezcap clone (STK1160 driver). Seems it's failing to read a full frame each time, resulting in a corrupt picture. I see the same issue with mplayer, gstreamer, and a stand-alone still capture utility. Tested on 3.8 3.12-rc5. WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Got unexpected frame size of 265434 instead of 829440. Additional debug info: gstv4l2src.c(919): gst_v4l2src_get_mmap (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0 The amount of data retrieved varies a little with each frame, but is always something similar.. Regards, Jon. On Tuesday, 15 October 2013 03:31:11 UTC+1, Brent wrote: I wish the USB based NTSC capture dongle were that simple. I've tried Hauppauge USB Live-2, and Easy-Cap, but neither work with the BeagleBone Black. It seems that the BBB is to slow for that. I've considered the camera capes that are available, but really need a solution that interfaces with an analog camera. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/iMs8S90aXzk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] NTSC/PAL video input
By the way, I think I may have settled on the TVP5150 decoder chip from TI. Using the reference schematic from herehttp://www.sleepyrobot.com/wp-content/uploads/2013/01/tvp5151_sch.pdfI think I may have a chance. However, does anyone have any pointers on which signals I need to connect to the BeagleBone? http://www.sleepyrobot.com/wp-content/uploads/2013/01/tvp5151_sch.pdf On Monday, October 14, 2013 10:27:35 PM UTC-4, chrisw wrote: On Mon, Oct 14, 2013 at 8:37 PM, Brent bren...@hotmail.com javascript:wrote: I'm looking for a reference design for a NTSC/PAL video input on the BeagleBone Black. The only thing I found so far is from e-consystems.com, but there is no schematic available. I have an analog camera where I need to capture the input and display it on an LCD, but so far I haven't been able to find any good decoder schematics. Does anyone know of any that may exist? http://www.e-consystems.com/NTSC-PAL-Video-Decoder-Board-Gumstix.asp That board is for the Gumstix Overo, which is an OMAP3730, and more like the Beagleboard XM. It would work for the Beaglebone Black, which doesn't have the same sort of camera interface. You would have to do something more like the Beaglebone Camera Cape, which uses a special purpose chip to interface the camera to the GPMC port of the bone. It would be quite a bit of work. I would suggest some sort of cheap USB based NTSC capture dongle that already has linux support. -chris -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] NTSC/PAL video input
I wish the USB based NTSC capture dongle were that simple. I've tried Hauppauge USB Live-2, and Easy-Cap, but neither work with the BeagleBone Black. It seems that the BBB is to slow for that. I've considered the camera capes that are available, but really need a solution that interfaces with an analog camera. On Mon, Oct 14, 2013 at 10:27 PM, Chris Whittenburg whittenb...@gmail.comwrote: On Mon, Oct 14, 2013 at 8:37 PM, Brent brent...@hotmail.com wrote: I'm looking for a reference design for a NTSC/PAL video input on the BeagleBone Black. The only thing I found so far is from e-consystems.com, but there is no schematic available. I have an analog camera where I need to capture the input and display it on an LCD, but so far I haven't been able to find any good decoder schematics. Does anyone know of any that may exist? http://www.e-consystems.com/NTSC-PAL-Video-Decoder-Board-Gumstix.asp That board is for the Gumstix Overo, which is an OMAP3730, and more like the Beagleboard XM. It would work for the Beaglebone Black, which doesn't have the same sort of camera interface. You would have to do something more like the Beaglebone Camera Cape, which uses a special purpose chip to interface the camera to the GPMC port of the bone. It would be quite a bit of work. I would suggest some sort of cheap USB based NTSC capture dongle that already has linux support. -chris -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/iMs8S90aXzk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -brent -- 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. For more options, visit https://groups.google.com/groups/opt_out.
