Re: [beagleboard] Ubuntu 14.04 hangs on the BBB
On 09/03/2015 12:12 PM, gianluca.sa...@gmail.com wrote: > I need it to be as reliable as its big brothers Ubuntu servers... As Dieter asked, what power supply are you using ? I have a few BBB 24/24h with no issue, but I use a good 5V 2A power supply. What are the USB sensor power requirements ? You can start to understand what's going on by connecting to the board console serial port (3.3V!) from another system and logging it to a file and see if there's any kernel error messages. Nuno -- -- 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] Maker Faire Grand Rapids
Heading out there today. Anyone else going? -- 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: Wl12xx
I've the same problem The reason seems to be located here http://lxr.free-electrons.com/source/drivers/regulator/fixed.c#L81 This happens when using the gpio-option on the fixed regulator I still don't get it to work after removing that, the regulator stops giving error, still when loading the wlcore_sdio & wl18xx it doesn't use the regulator as the num_users is still 0 which makes it disabled Den onsdag 19 augusti 2015 kl. 08:05:44 UTC+2 skrev Dileep D R: > > > Hi, > > Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable > to bring up wlan0 interface, please guide me for proper device tree > configuration. > > After booting excecuted > modprobe wlcore_sdio > modprobe wl12xx > > > Below are my configurations. > > Kernel : 4.1 > Rootfs : Debian > > Device Tree: > > / { > vwlan_en_reg: regulator-vwlan-en { > compatible = "regulator-fixed"; > regulator-name = "vwlan_en"; > regulator-min-microvolt = <180>; > regulator-max-microvolt = <180>; > gpio = < 27 0>; > enable-active-high; > startup-delay-us = <7>; > pinctrl-names = "default"; > pinctrl-0 = <_enable_pins>; > }; > }; > > _pinmux { > > wlan_pins: pinmux_wlan_pins { > pinctrl-single,pins = < > 0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */ > >; > }; > > wlan_enable_pins: pinmux_wlan_enable_pins { > pinctrl-single,pins = < > 0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */ > >; > }; > > mmc2_pins: pinmux_mmc2_pins { > pinctrl-single,pins = < > 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */ > 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */ > 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */ > 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */ > 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */ > 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */ > >; > }; > }; > > { > pinctrl-names = "default"; > pinctrl-0 = <_pins>; > > status = "okay"; > clock-frequency = <10>; > > /* ODIN-W160 EEPROM */ > eeprom@5D { > compatible = "at,24c64"; > reg = <0x5D>; > pagesize = <32>; > }; > }; > > { > non-removable; /* TI specific feature */ > bus-width = <4>; > cap-power-off-card; /* TI specific feature */ > vmmc-supply = <_en_reg>; > pinctrl-names = "default"; > pinctrl-0 = <_pins _pins>; > status = "okay"; > > #address-cells = <1>; > #size-cells = <0>; > wlcore: wlcore@0 { > compatible = "ti,wl1273"; > reg = <2>; > interrupt-parent = <>; > interrupts = <26 0x4>; > ref-clock-frequency = <3840>; > }; > }; > > dmesg log: > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Initializing cgroup subsys cpuacct > [0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3 > (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST 2015 > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=10c5387d > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > [0.00] Machine model: TI AM335x BeagleBone Black > [0.00] cma: Reserved 24 MiB at 0x9e00 > [0.00] Memory policy: Data cache writeback > [0.00] On node 0 totalpages: 130560 > [0.00] free_area_init_node: node 0, pgdat c0f4c700, node_mem_map > df96d000 > [0.00] Normal zone: 1152 pages used for memmap > [0.00] Normal zone: 0 pages reserved > [0.00] Normal zone: 130560 pages, LIFO batch:31 > [0.00] CPU: All CPU(s) started in SVC mode. > [0.00] AM335X ES2.1 (sgx neon ) > [0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192 d22720 > u53248 > [0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096 > [0.00] pcpu-alloc: [0] 0 > [0.00] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 129408 > [0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs > rw nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian > ip=192.168.0.105:eth0 > [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) > [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 > bytes) > [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 > bytes) > [0.00] Memory: 475580K/522240K available (10502K kernel code, 881K > rwdata, 3680K rodata, 672K init, 901K bss, 22084K reserved, 24576K > cma-reserved, 0K highmem) > [0.00] Virtual kernel memory layout: > vector : 0x - 0x1000 ( 4 kB) > fixmap : 0xffc0 - 0xfff0 (3072 kB) > vmalloc :
[beagleboard] No usb on 3.14
Hi everyone, I moved from 3.12 to 31.4, usb doesn't seem to work. It fails at the boot. [2.576280] musb-hdrc musb-hdrc.0.auto: Failed to request rx1. [2.582243] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 [2.656156] musb-hdrc musb-hdrc.1.auto: Failed to request rx1. [2.662110] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 It was working fine with 3.12. Any ideas why it is failing? Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Wl12xx
I've the same problem The reason seems to be located here http://lxr.free-electrons.com/source/drivers/regulator/fixed.c#L81 This happens when using the gpio-option on the fixed regulator I still don't get it to work after removing that, the regulator stops giving error, still when loading the wlcore_sdio & wl18xx it doesn't use the regulator as the num_users is still 0 which makes it disabled Den onsdag 19 augusti 2015 kl. 08:05:44 UTC+2 skrev Dileep D R: > > > Hi, > > Interfacing wifi module (wl12xx ti chipset) with beaglebone black. Unable > to bring up wlan0 interface, please guide me for proper device tree > configuration. > > After booting excecuted > modprobe wlcore_sdio > modprobe wl12xx > > > Below are my configurations. > > Kernel : 4.1 > Rootfs : Debian > > Device Tree: > > / { > vwlan_en_reg: regulator-vwlan-en { > compatible = "regulator-fixed"; > regulator-name = "vwlan_en"; > regulator-min-microvolt = <180>; > regulator-max-microvolt = <180>; > gpio = < 27 0>; > enable-active-high; > startup-delay-us = <7>; > pinctrl-names = "default"; > pinctrl-0 = <_enable_pins>; > }; > }; > > _pinmux { > > wlan_pins: pinmux_wlan_pins { > pinctrl-single,pins = < > 0x28 (PIN_INPUT_PULLUP | MUX_MODE7)/* gpio0_26 WL_IRQ */ > >; > }; > > wlan_enable_pins: pinmux_wlan_enable_pins { > pinctrl-single,pins = < > 0x2c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpio0_27 WL_EN */ > >; > }; > > mmc2_pins: pinmux_mmc2_pins { > pinctrl-single,pins = < > 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */ > 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */ > 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */ > 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */ > 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */ > 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */ > >; > }; > }; > > { > pinctrl-names = "default"; > pinctrl-0 = <_pins>; > > status = "okay"; > clock-frequency = <10>; > > /* ODIN-W160 EEPROM */ > eeprom@5D { > compatible = "at,24c64"; > reg = <0x5D>; > pagesize = <32>; > }; > }; > > { > non-removable; /* TI specific feature */ > bus-width = <4>; > cap-power-off-card; /* TI specific feature */ > vmmc-supply = <_en_reg>; > pinctrl-names = "default"; > pinctrl-0 = <_pins _pins>; > status = "okay"; > > #address-cells = <1>; > #size-cells = <0>; > wlcore: wlcore@0 { > compatible = "ti,wl1273"; > reg = <2>; > interrupt-parent = <>; > interrupts = <26 0x4>; > ref-clock-frequency = <3840>; > }; > }; > > dmesg log: > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Initializing cgroup subsys cpuacct > [0.00] Linux version 4.1.3+ (dileep@ubuntu) (gcc version 4.6.3 > (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #2 SMP PREEMPT Tue Aug 18 16:54:12 IST 2015 > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=10c5387d > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > [0.00] Machine model: TI AM335x BeagleBone Black > [0.00] cma: Reserved 24 MiB at 0x9e00 > [0.00] Memory policy: Data cache writeback > [0.00] On node 0 totalpages: 130560 > [0.00] free_area_init_node: node 0, pgdat c0f4c700, node_mem_map > df96d000 > [0.00] Normal zone: 1152 pages used for memmap > [0.00] Normal zone: 0 pages reserved > [0.00] Normal zone: 130560 pages, LIFO batch:31 > [0.00] CPU: All CPU(s) started in SVC mode. > [0.00] AM335X ES2.1 (sgx neon ) > [0.00] PERCPU: Embedded 13 pages/cpu @df925000 s22336 r8192 d22720 > u53248 > [0.00] pcpu-alloc: s22336 r8192 d22720 u53248 alloc=13*4096 > [0.00] pcpu-alloc: [0] 0 > [0.00] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 129408 > [0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs > rw nfsroot=192.168.0.101:/home/dileep/BeagleBone/rootfs_debian > ip=192.168.0.105:eth0 > [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) > [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 > bytes) > [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 > bytes) > [0.00] Memory: 475580K/522240K available (10502K kernel code, 881K > rwdata, 3680K rodata, 672K init, 901K bss, 22084K reserved, 24576K > cma-reserved, 0K highmem) > [0.00] Virtual kernel memory layout: > vector : 0x - 0x1000 ( 4 kB) > fixmap : 0xffc0 - 0xfff0 (3072 kB) > vmalloc :
[beagleboard] USB doesn't work in 3.14 kernel
Hi everyone, I am curious to know if anyone made usb to work in 3.14 kernel from https://github.com/beagleboard/linux.git. It was working fine with 3.12 kernel. Any help would be appreciated. Manish -- 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] Bonescript theory question
Say I create a node.js script in my browser and send the compiled script over usb to the BBB. >From a high-level programming side, how is the data stream from usb processed on the board? What applications/files are utilized to get the data to perform a task (like turn on a gpio)? How does the input interact with the linux os? Does this require webserver httprequests on the BBB side or is it processed another way such as non-http shell scripts or maybe without the linux system at all? (I assume not) The goal of my question is to understand the difference between the mechanics of using bonescript with BBB as opposed to SSHing files into the file system. THANKS! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] USB doesn't work in 3.14 kernel
On Sep 4, 2015 11:51 AM, "Manish Shakya"wrote: > > Hi everyone, > > I am curious to know if anyone made usb to work in 3.14 kernel from https://github.com/beagleboard/linux.git. It was working fine with 3.12 kernel. > > Any help would be appreciated. Did you use the default bb.org_defconfig? Regards, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] USB doesn't work in 3.14 kernel
Disabling DMA mode fixed it. # CONFIG_USB_TI_CPPI41_DMA is not set CONFIG_MUSB_PIO_ONLY=y On Fri, Sep 4, 2015 at 1:40 PM, Robert Nelsonwrote: > > On Sep 4, 2015 11:51 AM, "Manish Shakya" > wrote: > > > > Hi everyone, > > > > I am curious to know if anyone made usb to work in 3.14 kernel from > https://github.com/beagleboard/linux.git. It was working fine with 3.12 > kernel. > > > > Any help would be appreciated. > > Did you use the default bb.org_defconfig? > > Regards, > -- Manish Shakya http://www.manishshakya.com.np -- 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] Audio cape for Beaglebone Black: hard to find
I am looking into BeagleRT. I have a Beaglebone Black already. I need to get the Audio Cape for the BBB. I'm finding that the audio cape seems to be hard to find. Most places say that they are out of stock and don't know when they'll get them. There are some places that have it, but the prices seem to be exorbitant. Does anyone have a lead on where to get one reasonably soon, and by only giving up an arm or a leg, but not both? -- 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] Minicom showing unreadable characters when connected and booting with BBB using FTDI usb-serail
I'm using minicom in ubuntu host to see the logs in boot time of BBB. Minicom is set with following configuration, Serial dev : ttyUSB0 Lock file : /var/lock Bps/par/bits : 115200 8N1 H/W flow cntrl : no S/W flow cntrl : no Minicom opens up and when BBB boots it shows unreadable characters! Did I miss any other config to be made ? pls help! Thanks, Akhil -- 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] Minicom showing unreadable characters when connected and booting with BBB using FTDI usb-serail
On Fri, Sep 4, 2015 at 4:06 PM, akhil mkwrote: > I'm using minicom in ubuntu host to see the logs in boot time of BBB. > Minicom is set with following configuration, > > Serial dev : ttyUSB0 > Lock file : /var/lock > Bps/par/bits : 115200 8N1 > H/W flow cntrl : no > S/W flow cntrl : no > > Minicom opens up and when BBB boots it shows unreadable characters! > Did I miss any other config to be made ? pls help! Double check with gtkterm, if it's still corrupted, invest in a usb-serial adapter that isn't less then $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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Wireless thermometer
Want to add an outdoor wireless thermometer to my beaglebone black application. (Must be able to work / survive in -30 degrees F locale.) Are there any recommendations from successful implementations? Is there an interface that permits receiving data from an Oregon Scientific sensor? -- Bill Barnett -- 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] Minicom showing unreadable characters when connected and booting with BBB using FTDI usb-serail
I Tried with gtkterm in ubuntu & putty in windows. Got same result. May be I should buy a new usb-serial. Thanks. On Sat, Sep 5, 2015 at 2:38 AM, Robert Nelsonwrote: > On Fri, Sep 4, 2015 at 4:06 PM, akhil mk wrote: > > I'm using minicom in ubuntu host to see the logs in boot time of BBB. > > Minicom is set with following configuration, > > > > Serial dev : ttyUSB0 > > Lock file : /var/lock > > Bps/par/bits : 115200 8N1 > > H/W flow cntrl : no > > S/W flow cntrl : no > > > > Minicom opens up and when BBB boots it shows unreadable characters! > > Did I miss any other config to be made ? pls help! > > Double check with gtkterm, if it's still corrupted, invest in a > usb-serial adapter that isn't less then $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 a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/cxoI_vtFqV0/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. > -- 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] What's the plan for a Debian distro with a recent version of node.js?
Anyone know the plans for moving to a more recent release of node.js with the next Debian release? Or where to find that information? -- 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] Error while installing drivers on BBB related to architecture
Hi everyone, I'm trying to install USB N10 driver on BBB. But while installing it is showing following error: make[1]: Entering directory `/usr/src/linux-3.8.13-bone70' Makefile:580: /usr/src/linux-3.8.13-bone70/arch/armv7l/Makefile: No such file or directory make[1]: *** No rule to make target `/usr/src/linux-3.8.13-bone70/arch/armv7l/Makefile'. Stop. make[1]: Leaving directory `/usr/src/linux-3.8.13-bone70' make: *** [modules] Error 2 Shouldn't there be a dir named armv7l in arch dir? We have arm64,arm,avr32 dir there but not armv7l, when I checked my kernel version using uname -a it was showing : Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux so armv7l should be there i think? Where it is exactly located? If someone already encountered same problem (beacuse many people used Asus usb N10 for wifi)then please help with this. If this topic is covered somewhere please let me know. Thanks. Regards, Aashish Khairnar -- 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] BBB P8/P9 GPIO pin availability
Just want to verify something... I an *not* using HDMI, McASP, gpmc, UARTs, the ADC or I2Cs. I am using the EMMC. Just SPI0 and a bunch of GPIOs. Can I assume that any P8/P9 pins labeled as GPIO in some mode, and *not* labeled "allocated for EMMC2"* on Derek Molloy's helpful P8/9 charts is available for GPIO purposes? Are there any other preallocated P8/9 GPIO-potential pins I need to watch out for? Just checking before I commit the cape from Hell to fab. Thanks, Mike * = gpmc_be1n, gpmc_clk, gpmc_dat0-7, or P8 pins 3-6 and 20-25. -- 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] triggering video playback from external source
I’m not sure if this is what you mean, but there is mjpeg streamer, which streams mjpeg compressed video over a wired or wireless network. From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of Ray Sent: Friday, September 04, 2015 8:54 PM To: BeagleBoard Subject: [beagleboard] triggering video playback from external source Hello, I'm looking to learn how to control video playback, perhaps via serial, from an external controller. The thought is for the beaglebone to output a video file, receiving start/stop commands from a serial source. Possible? I would appreciate a push towards any tutorials. Many thanks, Ray -- 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 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] triggering video playback from external source
Hello, I'm looking to learn how to control video playback, perhaps via serial, from an external controller. The thought is for the beaglebone to output a video file, receiving start/stop commands from a serial source. Possible? I would appreciate a push towards any tutorials. Many thanks, Ray -- 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] Bonescript theory question
What you're asking is more of a cloud9 question than bonescript. But if you're seeking more information on bonescript too . . . https://github.com/jadonk/bonescript read the readme.md , as for the rest you'd have to ask someone who is knowledgeable with cloud9. For what it's worth, I've kind of wondered about much of what you're asking too. But I've otherwise spent my time doing other things that are more important to me. Such as using C to do similar things. My reasoning was simple. C( native executables ) are faster, and takes up a hell of a lot less space than Node.js . . . So if I had to learn something, I may as well learn the "better" way. Node.js + express + npm takes up ~60M of disk space. My C application which essentially does the same thing - Well more exactly *exactly* what I need to do. Does not take up 1M . . . steeper learning curve though. On Fri, Sep 4, 2015 at 10:50 AM,wrote: > Say I create a node.js script in my browser and send the compiled script > over usb to the BBB. > > From a high-level programming side, how is the data stream from usb > processed on the board? What applications/files are utilized to get the > data to perform a task (like turn on a gpio)? How does the input interact > with the linux os? Does this require webserver httprequests on the BBB side > or is it processed another way such as non-http shell scripts or maybe > without the linux system at all? (I assume not) > > The goal of my question is to understand the difference between the > mechanics of using bonescript with BBB as opposed to SSHing files into the > file system. > > THANKS! > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > 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] Minicom showing unreadable characters when connected and booting with BBB using FTDI usb-serail
On Fri, Sep 4, 2015 at 4:37 PM, akhil mkwrote: > I Tried with gtkterm in ubuntu & putty in windows. Got same result. May be I > should buy a new usb-serial. Also test the usb cable/hub/connector.. 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Minicom showing unreadable characters when connected and booting with BBB using FTDI usb-serail
The prolific pl2303hx cables work good too. If you're in the market for a new one. Just saw one on newegg for $1.57 . . . but does not say what TTL voltage is. Not sure if all 2303HX cables are 3v3 logic or not. But the ones we got off ebay several month ago were 3v3, and were less than $3 each. They're still working great. On Fri, Sep 4, 2015 at 2:42 PM, Robert Nelsonwrote: > On Fri, Sep 4, 2015 at 4:37 PM, akhil mk wrote: > > I Tried with gtkterm in ubuntu & putty in windows. Got same result. May > be I > > should buy a new usb-serial. > > Also test the usb cable/hub/connector.. > > 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. > 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] Does the Adafruit GPIO python library set GPIO lines low when it loads?
Hello all, I'm using the Adafruit_BBIO python libraries (which I think are great! BTW) in a project with the BeagleBone Black. (OS = Debian, BBB = RevC) I have some GPIO lines that I'm using to interface to a cape we've developed.When I run my python program, I set some lines to outputs and bring them high or low as needed. When I exit the python program back to the command line, I do not change the lines, so I would expect them to be in the last state I wrote them to. This is the case as far as I can tell. What appears to be happening is that any output lines that were set high are forced low when I run the python program again (which loads the library). Is it normal for the Adafruit library to set GPIO outputs to the low state when it gets loaded? Thanks, Dave -- 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] Does the Adafruit GPIO python library set GPIO lines low when it loads?
Hi Dave, This is really a question to ask of the maintainer for the project. Who seems to be Tony DiCola from Adafruit industries. On Fri, Sep 4, 2015 at 2:44 PM,wrote: > Hello all, > > I'm using the Adafruit_BBIO python libraries (which I think are great! > BTW) in a project with the BeagleBone Black. (OS = Debian, BBB = RevC) > > I have some GPIO lines that I'm using to interface to a cape we've > developed.When I run my python program, I set some lines to outputs and > bring them high or low as needed. When I exit the python program back to > the command line, I do not change the lines, so I would expect them to be > in the last state I wrote them to. This is the case as far as I can tell. > > What appears to be happening is that any output lines that were set high > are forced low when I run the python program again (which loads the > library). > > Is it normal for the Adafruit library to set GPIO outputs to the low state > when it gets loaded? > > Thanks, > Dave > > -- > 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 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] USB audio issue with kernel 3.14
I skipped ahead to 4.1.5-ti-r10 but I can verify that it definitely fixed my problem, same as OP's. This problem was driving me nuts for a few days until I finally found this post. Thanks RCN On Tuesday, June 2, 2015 at 11:45:34 AM UTC-4, RobertCNelson wrote: > > On Tue, Jun 2, 2015 at 10:19 AM,> wrote: > > Hello. > > > > I'm trying to get BBB Rev C working with USB sound card. Everything > works > > fine under kernel 3.8. But under 3.14 sound either completely stuck > right > > after the boot (this happens most of the time) or it works for some time > and > > then stuck. I don't know how to debug this issue. Here are usbmon traces > > taken when I issue "paplay /usr/share/sounds/alsa/Front_Center.wav" > command: > > If usb worked with 3.8 but fails with 3.14, it's probally: > > CONFIG_USB_TI_CPPI41_DMA=y > > So rebuild, with: > > # CONFIG_USB_TI_CPPI41_DMA is not set > CONFIG_MUSB_PIO_ONLY=y > > ps, you can also give 4.1.0-rc6 a try: > > sudo apt-get update > sudo apt-get install linux-image-4.1.0-rc6-bone6 > sudo 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Auto Login with Debian ?
Hello all; I am trying to get my BBB to automatically login as root after it boots. This is the image I am running: "Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux" After some Google, I found several methods that appear to be out of date. They all suggest modifying the "/etc/inittab" file as below: First install rungetty using the following command #apt-get install rungetty you need to edit the /etc/inittab file #nano /etc/inittab look for the following line comment out #1:2345:respawn:/sbin/getty 38400 tty1 and add 1:2345:respawn:/sbin/rungetty tty1 --autologin YOUR_USER_NAME or 1:2345:respawn:/bin/login -f root tty1 /dev/tty1 2>&1 none of the above work :-( I'm sure this is do able, I just don't know how to with this image. Thanks; Bill -- 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.