[beagleboard] Re: How fast/reliable is ADC sampling from the PRU
Am Freitag, 6. März 2015 12:47:00 UTC+1 schrieb Paco Gil: maybe libpruio can sample as fast as 1.4-1.6 MHz?? It can. Just configure the ADC steps accordingly. Lenny code is not interesting for a multi purpose library like libpruio. BR -- 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: libpruio (fast and easy D/A - I/O)
Thanks for feedback! BR -- 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] Booting from microSD
You are using the wrong image L That one “bbxm ….” Is for the “Beagle Board XM’ You want one that says ‘bone70’ or what ever number they are up to …. No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke (1729 - 1797) http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of Ray Madigan Sent: Friday, March 06, 2015 12:57 AM To: beagleboard@googlegroups.com Subject: [beagleboard] Booting from microSD I have two beaglebone blacks rev B and I am trying to boot either of them from a microSD card and I can't make either one of them work. I must be doing something wrong and I need some help. I have a 32GB microSD card Pro from Samsung.I wrote the image: bbxm-ubuntu-14.04.2-console-armhf-2015-02-19-2gb.img to the microsd card. I have the bone connected to a monitor, keyboard and mouse. It boots normally. I insert the microSD card press the user boot button and power it up, no light comes on at all for as long as I hold the button. If I try without the button press three lights light up immediately and stay there for ever. Am I doing something wrong? I tired connected to a network and not with the same result. Any guidance would be appreciated? -- 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. _ No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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 won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Nothing to assume :-) , there is NO ground connection between the BB and the bread board from what the picture shows, just 3 wires (Red, Green, Blue) not 4. How that could have damaged the BBB is what we don't understand. The wires to the BBB were connected to the MOSFET gates. -- 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] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
First of all, the output level from the GPIO is about 3.3V and MOSFETs are voltage controlled devices. So you will need a transistor to boost the voltage to 12 volts. Second: Do you have an actual schematic? Third: Are you using P or N Channel MOSFET’s ? Because high current versions like the ones you are using have a built in body diode … Get back to us with more info, Ok No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke (1729 - 1797) http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of g...@sensa.io Sent: Friday, March 06, 2015 1:41 AM To: beagleboard@googlegroups.com Subject: [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8 http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 The Adafruit support said that setup should not have hurt the board. I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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. _ No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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: GPIO and permissions
All of these suggestions are terrible. The right question to ask is How do I give a non-root user permission to set GPIOs? If this can't be done, then this distribution of Linux is broken. I can add my user to the kmem group, then change the group ownership of /sys/class/gpio/export to kmem, the chmod g+w, and then my user can export the GPIOs. But when they appear, direction is still owned root:root perms 644, so I can't do anything with the GPIO I just created, even though, as a member of kmem, I could do the equivalent memory-mapped IO. It is not acceptable to require a program to run as root. I not quite Linux-savvy enough to fix 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.
Re: [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Sure, thanks a lot for the continued help. Here are the FETs that I used, which are N-Channel and can switch 30V/60A: https://www.adafruit.com/products/355 Here is the wiring I followed (diagram about half way down; first one that doesn't have the 100-220ohm resistors): https://learn.adafruit.com/rgb-led-strips/usage Except I connected the voltage wire on the LED strip to a separate 12V supply, and did not ground the circuit to the Beaglebone GND as you can see in the picture I posted on the Adafruit forum. They say at the bottom there in regards to connecting to separate 12V supply, Make sure to connect the ground of that supply to the ground of the Arduino/MOSFETs!, but in the forum post, they implied it wouldn't burn out the board if I didn't do this. Here is the schematic of the LED strip: https://learn.adafruit.com/rgb-led-strips/schematic On Friday, March 6, 2015 at 5:10:59 PM UTC-8, William Pretty Security wrote: First of all, the output level from the GPIO is about 3.3V and MOSFETs are voltage controlled devices. So you will need a transistor to boost the voltage to 12 volts. Second: Do you have an actual schematic? Third: Are you using P or N Channel MOSFET’s ? Because high current versions like the ones you are using have a built in body diode … Get back to us with more info, Ok No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke *(1729 - 1797)* http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 *From:* beagl...@googlegroups.com javascript: [mailto: beagl...@googlegroups.com javascript:] *On Behalf Of *gr...@sensa.io javascript: *Sent:* Friday, March 06, 2015 1:41 AM *To:* beagl...@googlegroups.com javascript: *Subject:* [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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. -- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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 won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
1st of all IF you used the FETs shown on Adafruit they are logic level FETs, so you can drive them directly from the BB. Resistors are only required if you had used the transistors instead of the FETs. As discussed you missed the GND wire (Black) as shown on Adafruit. Where did you measure the 200mV? From the BB GND to the outputs or elsewhere? As you don't have a common GND readings are pretty much meaningless. FETs have a large capacitance on the Gate, without a common ground you could have several hundred (or thousands) volts of static charge for a very short period, but it could be large enough to kill the processor. Very likely if you have carpets around. If you unplug everything you added to the BB will it boot up again? If not the above may be possible. You seem to be using P9_12, P9_16 and P9_21 they should be safe to use as I'm using them on a couple of projects without problems, you MUST add the GND wire from any pin 1 or 2 of either P8 or P9 to the GND track of your breadboard. I may think of something else later on... meanwhile, as I said above, unplug everything from the BB and see if it powers up, if not it's shopping time again. -- 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] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
what you have done is fry the boards by not connecting the ground. On 3/6/2015 6:24 PM, g...@sensa.io wrote: Sure, thanks a lot for the continued help. Here are the FETs that I used, which are N-Channel and can switch 30V/60A: https://www.adafruit.com/products/355 Here is the wiring I followed (diagram about half way down; first one that doesn't have the 100-220ohm resistors): https://learn.adafruit.com/rgb-led-strips/usage Except I connected the voltage wire on the LED strip to a separate 12V supply, and did not ground the circuit to the Beaglebone GND as you can see in the picture I posted on the Adafruit forum. They say at the bottom there in regards to connecting to separate 12V supply, Make sure to connect the ground of that supply to the ground of the Arduino/MOSFETs!, but in the forum post, they implied it wouldn't burn out the board if I didn't do this. Here is the schematic of the LED strip: https://learn.adafruit.com/rgb-led-strips/schematic On Friday, March 6, 2015 at 5:10:59 PM UTC-8, William Pretty Security wrote: First of all, the output level from the GPIO is about 3.3V and MOSFETs are voltage controlled devices. So you will need a transistor to boost the voltage to 12 volts. Second: Do you have an actual schematic? Third: Are you using P or N Channel MOSFET’s ? Because high current versions like the ones you are using have a built in body diode … Get back to us with more info, Ok No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke /(1729 - 1797)/ http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 *From:*beagl...@googlegroups.com javascript: [mailto:beagl...@googlegroups.com javascript:] *On Behalf Of *gr...@sensa.io javascript: *Sent:* Friday, March 06, 2015 1:41 AM *To:* beagl...@googlegroups.com javascript: *Subject:* [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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 https://groups.google.com/d/optout. No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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 mailto: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
Re: [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Can you explain how that happened? When I measured the gate pin on the FETs, it was only 200mV. How would this fry the board, and what exactly would it fry on the Bone? On Friday, March 6, 2015 at 5:48:00 PM UTC-8, Wulf Man wrote: what you have done is fry the boards by not connecting the ground. On 3/6/2015 6:24 PM, gr...@sensa.io javascript: wrote: Sure, thanks a lot for the continued help. Here are the FETs that I used, which are N-Channel and can switch 30V/60A: https://www.adafruit.com/products/355 Here is the wiring I followed (diagram about half way down; first one that doesn't have the 100-220ohm resistors): https://learn.adafruit.com/rgb-led-strips/usage Except I connected the voltage wire on the LED strip to a separate 12V supply, and did not ground the circuit to the Beaglebone GND as you can see in the picture I posted on the Adafruit forum. They say at the bottom there in regards to connecting to separate 12V supply, Make sure to connect the ground of that supply to the ground of the Arduino/MOSFETs!, but in the forum post, they implied it wouldn't burn out the board if I didn't do this. Here is the schematic of the LED strip: https://learn.adafruit.com/rgb-led-strips/schematic On Friday, March 6, 2015 at 5:10:59 PM UTC-8, William Pretty Security wrote: First of all, the output level from the GPIO is about 3.3V and MOSFETs are voltage controlled devices. So you will need a transistor to boost the voltage to 12 volts. Second: Do you have an actual schematic? Third: Are you using P or N Channel MOSFET’s ? Because high current versions like the ones you are using have a built in body diode … Get back to us with more info, Ok No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke *(1729 - 1797)* http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 *From:* beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] *On Behalf Of *gr...@sensa.io *Sent:* Friday, March 06, 2015 1:41 AM *To:* beagl...@googlegroups.com *Subject:* [beagleboard] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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. -- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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: BBB: Serial Wiring For External Device Over UART1
Hi All. Thanks for the replies. I managed to get it working with your help: 1. Make sure RX on serial device points to UARTX TX and TX on serial device points to UARTX RX. 2. nano /boot/uboot/uEnv.txt add optargs=capemgr.enable_partno=BB-UART1 or alternatively add a systemd service (I'm running Debian) to execute the command echo BB-UART1 /sys/devices/bone_capemgr*/slots 3. to make sure this succeeded: run : ls /dev/ttyO* - you should see ttyO1 run cat /sys/devices/bone_capemgr*/slots - you should see BB-UART1 added to the output. This pretty much enabled UART over serial for me. Pieter On Wednesday, November 26, 2014 at 12:21:06 AM UTC+2, John Mladenik wrote: I would make sure that the Analog device IC has the output TX connected to the TX on the Ext. Board and the input RX to RX. I wish I had a nickel for every time I saw the DTE (Data Terminal Equipment) and DCE (Data Communications Equipment) swapped. It would be helpfull to probe the RX and TX line to see if there is activity on it using a logic analyzer or o-scope. This will let you verify the TX/RX and baud rates of the two devices. I did not have to change any configuration or enable anything to get the UARTS working using Bonescript commands on my two Rev C BBB's. I have a simple HTML/Java app that you can point to from Chrome to send out data bytes on the UART if you want that let me know, I havn't gotten to the receive part of my app yet. I am probably less experienced than you with software so this is the only way I got the UARTs working. -- 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: Linphone for Angstrom distribution on Beagleboard
hello..I AM GURPARTAP SINGH FROM NOIDA Please help me how to cross compile linphone for beagleboard .I am new to this field.My project is to build Intercom based on SIP protocol. -- 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: BBB SPI device tree overlay, device number confusion
I see the same problems. Guys, will it work though using the pins described for spi0? 2015. február 22., vasárnap 5:18:34 UTC+1 időpontban Steve French a következőt írta: Matt, I agree!!! It is very confusing, especially when you are trying to figure out which pin to probe!! -frenchy On Thursday, January 23, 2014 at 12:18:57 PM UTC-5, Matt Graham wrote: I think I posted to the wrong section of the group. Apologies for this repost. Running the latest angstrom image, with update, upgrade. Installing BB-SPIDEV0 seems to produce /dev/spidev1 which doesn't seem right. I was expecting /dev/spidev0 based on this http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0 Any ideas on this problem? root@beaglebone:~# find /dev -iname *spi* root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI root@beaglebone:~# echo BB-SPIDEV0 /sys/devices/bone_capemgr.*/slots root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPIDEV0 root@beaglebone:~# find /dev -iname *spi* /dev/spidev1.0 /dev/spidev1.1 root@beaglebone:~# -- 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] BBB power led blinking, revived after several power button presses
I already burned down three of BBB, and now I totally give it up! On Feb 27, 2015, at 12:26 AM, David Crawford crawford.dav...@gmail.com wrote: The power supply I bought is from AdaFruit, which I expected to be well suited to my BBB. I haven't yet tried booting from an SD card, so I'll do that this evening. On Thursday, February 26, 2015, Gerald Coley ger...@beagleboard.org wrote: I suggest you switch to a \different power supply. A good one. http://www.elinux.org/Beagleboard:BeagleBoneBlack#Improper_Power_DownAll_Revisions Gerald On Wed, Feb 25, 2015 at 7:38 PM, crawford...@gmail.com wrote: My Rev C BBB purchased from Adafruit just died on my in the exact same way. I can't get it to boot at all whether connected to USB or 5V power supply. On Wednesday, February 25, 2015 at 2:02:07 PM UTC-5, Mike Traynor wrote: Thx. Will try another PS if I can find one. Otherwise will have to stick with USB for now. M. On Wed, Feb 25, 2015 at 9:07 AM, Gerald Coley ger...@beagleboard.org wrote: I have seen this before. The USB path and 5VDC paths are different through the PMIC. It is possible that the PMIC has sustained some damage or it could be the 5VDC power supply is not powering up properly, where it has a voltage spike, causing the PMIC to shutdown. Past performance of power supplies is no guarantee of future performance. It could be right on the edge. Gerald On Wed, Feb 25, 2015 at 10:27 AM, mdtsa...@gmail.com wrote: Identical problem this morning: BBB boots fine when powered by USB, but not when powered by a 2.0 mA rated 5.0 V DC power supply (nicked from some other device). BBB power LED blinks continuously. This power supply has worked with this BBB in the past. Mike. On Friday, January 23, 2015 at 8:44:59 PM UTC-8, 1127...@gmail.com wrote: I had a similar problem- my power LED would just continue blinking when connected to a 5V power source. This meant there was something wrong. First, I checked if my BBB was still alive. To find that, I connected my board to a computer via USB. Surprisingly, this time power LED turned on normally. Then to make sure that everything was properly, I ran some program as given in the BB website http://beagleboard.org/getting-started. I was happy to see, the programs on the website worked just fine on my board. Thus, I was able to conclude that strangely, my BBB board didn't like 5V external power source! On Friday, November 22, 2013 at 6:41:41 AM UTC-8, Bert Lindner wrote: Just had a 5V powered Beaglebone Black seemingly die on me. First the power led kept blinking, then after removing the (BB Toys CAN) cape the power led would flash just once after applying power. Looking back in previous threads this seemed to mean I killed the board somehow; there was also a GPS module attached to one of the UARTs and a probably power hungry USB wlan stick that I'm trying to get to work, so a power hungry setup. I was ready to declare it dead, it remained just flashing once after repeatedly unplugging and reattaching the power supply. However I noticed the single power led flash would also happen if I pressed the power button (leaving the 5V plug in). Doing that repeatedly seems to have revived the board, will see if new problems occur. For now it behaves normally. Is this expected behaviour? Best, -Bert -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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/jBFshjlPeHI/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. -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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
[beagleboard] Re: How fast/reliable is ADC sampling from the PRU
Hi TJF, Did you find Lenny code interesting?? maybe libpruio can sample as fast as 1.4-1.6 MHz?? 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] Booting from microSD
On Thu, Mar 5, 2015 at 11:56 PM, Ray Madigan raymond.madi...@gmail.com wrote: I have two beaglebone blacks rev B and I am trying to boot either of them from a microSD card and I can't make either one of them work. I must be doing something wrong and I need some help. I have a 32GB microSD card Pro from Samsung.I wrote the image: bbxm-ubuntu-14.04.2-console-armhf-2015-02-19-2gb.img to the microsd card. bbxm = BeagleBoard xM... You have a bone... So either: http://elinux.org/BeagleBoardUbuntu#BeagleBone.2FBeagleBone_Black or: http://elinux.org/BeagleBoardUbuntu#eMMC:_BeagleBone_Black 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 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: libpruio (fast and easy D/A - I/O)
[SOLVED] Hello TJF, I will answer in English to give other users the possibility to use this information as well. Thank you for your answer. With this information I was able to compile the supplied libpruio FreeBASIC examples. Steps to take (on the BeagleBone, as root, otherwise use 'sudo'): 1.) wget http://www.freebasic-portal.de/dlfiles/625/freebasic_1.01.0debian7_armhf.deb 2.) dpkg --install freebasic_1.01.0debian7_armhf.deb (Note: On http://www.freebasic-portal.de/downloads/fb-on-arm/debian-package-fbc-1-01-357.html you type: freebasic_1.01.0~debian7_armhf.deb which make copy and paste from the website resulting in an error) 3.) apt-get -f install 4.) rm /usr/local/bin/fbc 5.) reboot 6.) cp -R /usr/local/include/freebasic/BBB /usr/include/freebasic/ After this, compiling fbc -w all analyse.bas works. Thank you. -- 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] Installing ubuntu + preempt rt on BBB
Hi all I am trying to run Ubuntu with preempt rt on my beaglebone black. I've been trying this for days without much success... I can boot my BBB into ubuntu by using BBB-eMMC-flasher-ubuntu-13.04-2013-06-14.img and other similar files. However, I fail to update its kernel. 1. I figured that there is kernel 3.8-rt in github. I followed the instruction in http://dev.ardupilot.com/wiki/building-the-code/building-for-beaglebone-black-on-linux/ However, my BBB won't boot. I know that the instruction is meant for debian. So, it it not applicable to Ubuntu? I've tried other beagle bone kernels in github, but I get errors while applying preempt-rt patch. 2. How do I install a new kernel? what I'm doing right now is: a) build kernel with make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- beaglebone_defconfig -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage dtbs LOADADDR=0x80008000 -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- am335x-boneblack.dtb -j4 mkdir -p ../export/rootfs make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- INSTALL_MOD_PATH=../export/rootfs/ modules_install b) copy kernel to BBB lib/modules/my_new_kernel_modules - rootfs/lib/modules kernel/arch/arm/boot/zImage - rootfs/boot/uboot kernel/arch/arm/boot/dts/am335x-boneblack.dtb - /boot/uboot Sometimes, after installing a kernel, BBB manages to boot and I see multiple kernels when I do ls /lib/modules. However, uname -r tells me that I am still booting from the old kernel. Is there anyway to choose the kernel to boot? I really need some help, and any help would be greatly appreciated Regards, Steve -- 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] Debian 3.14 Kernel Complication Walkthrough
Hi Robert. Thanks for the guid. I have everything working up to the point where we compile the deb. sudo make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-ti-r53 CROSS_COMPILE=arm-linux-gnueabihf- KDEB_PKGVERSION=1cross deb-pkg *make: *** No rule to make target `deb-pkg'. Stop.* Any advice on whats missing in my configuration? Pieter On Thursday, March 5, 2015 at 11:22:21 PM UTC+2, RobertCNelson wrote: On Thu, Mar 5, 2015 at 1:49 PM, pietersyd...@gmail.com javascript: wrote: Hi Guys, I need to recompile the debian 3.14 kernel but all the step by step guides I get all refer to 3.8. Does anyone know of a proper guide to get the latests beaglebone supported kernel running on my beaglebone black? git clone https://github.com/beagleboard/linux cd linux Look at the tag's: https://github.com/beagleboard/linux/tags git checkout 3.14.34-ti-r53 -b tmp make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bb.org_defconfig make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig (to make changes) make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-ti-r53 CROSS_COMPILE=arm-linux-gnueabihf- KDEB_PKGVERSION=1cross deb-pkg Copy *.deb to bbb, run: sudo dpkg -i linux-image* ; sudo reboot 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 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] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
On Thu, 5 Mar 2015 22:41:16 -0800 (PST), you wrote: I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. some mosfets have protective diodes on the gate inputs. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. If I assume that the ground on the circuit didn't have a connection to the BBB ground, and that the 12 volt supply was connected to the circuit +12 and gnd, then you put floating lines on the BBB outputs, and any leakage in the power supply to ground (or the BBB ground) could put any voltage on the output pins of the BBB. The gates were floating, which is why the circuit was unstable. BTW: these had to be enhancement mode FETs for this to work. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * If connected properly. I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Voltage is not measured in ma, do you mean 200 mv? The meter you used loaded the circuit, and would not show the true voltage. It's not a matter of current into the chip, it's a matter of voltage (period). The voltage can cause nasty things in the chip transistors driving the pin, and the power supply of the chip itself then does the damage. Does anyone have any ideas on this? How could this have fried 2 boards? A suggestion for you. Next time, do not make single connections to pins on the BBB (or anything else unless you're quite certain of what you're doing). Best to take a ribbon connector that makes connections to everything at once, run it to a breakout board, and then hard wire your connections to that. A frequent problem in breadboards is wires coming loose. This way the ground is automatically made to the chips on the breadboard. Another option would be to use a darlington transistor array, such as the ULN2803 or the ULN2003 instead of the FETS. Again, the same warning about grounding is in effect. Since you have two non-functional BBB's I'd suggest taking a meter and checking the voltages at the various regulators on the board. You have a schematic, and it may be possible that you have a bad regulator somehow. That's better than a fried CPU. Harvey Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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] Prevent data drop via uart
I am using to read data through UART port. I found that the uart port occasionally drop some byte of data. Does any one have idea to prevent data drop through uart port? I have tried the baud rate from 9600 to 115200. All baud rate have lost some byte. -- 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] Installing ubuntu + preempt rt on BBB
On Thu, Mar 5, 2015 at 10:23 PM, sdfzz...@gmail.com wrote: Hi all I am trying to run Ubuntu with preempt rt on my beaglebone black. I've been trying this for days without much success... I can boot my BBB into ubuntu by using BBB-eMMC-flasher-ubuntu-13.04-2013-06-14.img and other similar files. However, I fail to update its kernel. 1. I figured that there is kernel 3.8-rt in github. I followed the instruction in http://dev.ardupilot.com/wiki/building-the-code/building-for-beaglebone-black-on-linux/ However, my BBB won't boot. I know that the instruction is meant for debian. So, it it not applicable to Ubuntu? I've tried other beagle bone kernels in github, but I get errors while applying preempt-rt patch. 2. How do I install a new kernel? what I'm doing right now is: a) build kernel with make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- beaglebone_defconfig -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage dtbs LOADADDR=0x80008000 -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules -j4 make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- am335x-boneblack.dtb -j4 mkdir -p ../export/rootfs make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- INSTALL_MOD_PATH=../export/rootfs/ modules_install b) copy kernel to BBB lib/modules/my_new_kernel_modules - rootfs/lib/modules kernel/arch/arm/boot/zImage - rootfs/boot/uboot kernel/arch/arm/boot/dts/am335x-boneblack.dtb - /boot/uboot Sometimes, after installing a kernel, BBB manages to boot and I see multiple kernels when I do ls /lib/modules. However, uname -r tells me that I am still booting from the old kernel. Is there anyway to choose the kernel to boot? I really need some help, and any help would be greatly appreciated Start with: http://elinux.org/BeagleBoardUbuntu#BeagleBone.2FBeagleBone_Black then: sudo apt-get update ; sudo apt-get install linux-image-3.14.34-ti-rt-r53 ; sudo reboot Which has CONFIG_PREEMPT_RTB=y enabled... CONFIG_PREEMPT_RT_FULL is still disabled as that doesn't boot.. 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 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] Debian 3.14 Kernel Complication Walkthrough
On Fri, Mar 6, 2015 at 1:30 AM, pietersydneythe...@gmail.com wrote: Hi Robert. Thanks for the guid. I have everything working up to the point where we compile the deb. sudo make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-ti-r53 CROSS_COMPILE=arm-linux-gnueabihf- KDEB_PKGVERSION=1cross deb-pkg don't use sudo.. use fakeroot if you must.. make: *** No rule to make target `deb-pkg'. Stop. Any advice on whats missing in my configuration? Your probably in the wrong directory... Reread my previous email.. If you've done every as specified, pastebin.com your terminal log. 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 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] Dell monitor touchscreen and QT tslib
Hello there, I have a E2014T dell touch monitor and I am trying to use it in pair with BeagleBone Black. The touch module is connected using usb cable. I have read in this tutorial: http://embedded.von-kannen.net/2014/05/21/qt-4-8-6-on-beaglebone-black/#comment-4288 How to enable the tslib and touchscreen. But I think, that this reffers to a touchscreen not connected to the usb, because it doesnt work. Without adding those variables to enviroment: $ sudo nano /etc/environment - add the following lines QWS_MOUSE_PROTO=tslib:/dev/input/event0 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/etc/ts.conf TSLIB_PLUGINDIR=/usr/lib/ts - Save (Ctrl + O) and exit (Ctrl + X) $ sudo reboot Touchscreen works out of the box, but it is not even close to being calibrated. The offset is really big and it changes when my finger is in different part of the display. After enabling the: QWS_MOUSE_PROTO=tslib:/dev/input/event0 Touchscreen stops working. I feel like its not event0 at all. When I run ts_calibrate and try to press the crosshair, it doesnt work. It feels like touchscreen is off for the ts_calibrate program. Does anyone has any expirience in such usb touchscreens and BeagleBone Black? I Would really aprichiate some 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] Slow 720p playback
Hi all, Was trying to get some 720P video playback on my BBB on a neat touchscreen monitor I got from here http://www.ebay.com/itm/New-10-1-Open-Frame-LCD-Display-with-Capacitive-Multi-Touch-Screen-HDMI-VGA-RCA-/181669154495?ssPageName=ADME:X:RTQ:US:1123. Surprisingly the screen works pretty well after just plugging it in. However, when trying to playback 720p video through VLC (no audio), I've got some major latency, youtube suffers the same way.This is a generic out-of-the-box BBB from Adafruit (element14) on 3.8.13-bone47, Debian 7. After doing some searching, I found: http://beagleboard.narkive.com/Ebgduatx/debian-sgx-v3-14-x which I thought would solve my issue (granted, this seems to be for 3D acceleration, I'm not sure how it would actually help me with playback, I'm just grasping at straws here). Unluckily though, it doesn't seem to be a simple as sudo apt-get update ; sudo apt-get install linux-image-3.14.15-bone6, My apt-cache search linux-image returns this http://pastebin.com/raw.php?i=Lx8Z9xJt (as you can see, no 3.14. My sources list: deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free #deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free #deb-src http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free #deb-src http://security.debian.org/ wheezy/updates main contrib non-free #deb http://ftp.debian.org/debian wheezy-backports main contrib non-free ##deb-src http://ftp.debian.org/debian wheezy-backports main contrib non-free #deb [arch=armhf] http://debian.beagleboard.org/packages wheezy-bbb main #deb-src [arch=armhf] http://debian.beagleboard.org/packages wheezy-bbb main deb [arch=armhf] http://repos.rcn-ee.net/debian wheezy main #deb-src [arch=armhf] http://repos.rcn-ee.net/debian wheezy main I'm not particularly trying to create a 1080p media center or anything super graphically fancy with this, in fact I'd like to use the BBB because I've got uses for all the IO it has access to, but if I could play 720p video at 60 FPS (with or without audio is fine), then that would be ideal. I wouldn't mind downgrading to a different kernel version/switching distros either as long as I could take advantage of the IO still. Does anyone have any advice for the next steps I should take here? Maybe a different video player? Some logs I could look at? 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: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Thanks very much for your response Harvey. Right sorry on the mA, I meant mV. Also I sent a picture of the circuit to the Adafruit customer support, it's in that forum thread that I linked to. And they said from looking at it, it shouldn't have been capable of frying the Bone. I'm surprised I can't find anything similar to this issue. I will check out the regulators. On Thursday, March 5, 2015 at 10:41:17 PM UTC-8, gr...@sensa.io wrote: I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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] Dell monitor touchscreen and QT tslib
Which version of Qt are you using? Debian or Angstrom On the Bone? Is there any other event in /dev/input? -- 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: BBBAndroid with USB Bluetooth Adapter Support
Hi Micheal,
In the backports folder can you do a ls -al and send me the output.
Also Andrew has yet to review or try my patches.
Keith
On Fri, Mar 6, 2015 at 1:41 AM, mgobb...@orcasolutions.be wrote:
Hey Andrew,
I received the patch files and the backports from Keith by mail. So I can
progress. However, I seem to have a problem when building the backports
tree. I included them in the root of the bbbandroid repo and when the kernel
is being built in the make process I'm getting the following output/error:
Building modules, stage 2.
MODPOST 1257 modules
make[1]: Leaving directory `/home/michael/kernel'
make -C backports-3.18.1-1 ARCH=arm
CROSS_COMPILE=/home/michael/prebuilts/gcc/linux-x86/arm/arm-gnueabihf-4.7/bin/arm-linux-gnueabihf-
KLIB_BUILD=../kernel
make[1]: Entering directory `/home/michael/backports-3.18.1-1'
/--
| You shouldn't run make in the backports tree, but only in
| the generated output. This here is only the skeleton code
| copied into the output directory. To use the backport system
| from scratch, go into the top-level directory and run
| ./gentree.py /path/to/linux-next/ /tmp/output
| and then make menuconfig/... in the output directory. See
| ./gentree.py --help
| for more options.
\--
make[2]: *** [modules] Error 1
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/michael/backports-3.18.1-1'
make: *** [kernel_build] Error 2
Maybe you could shed some light on this?
Thanks,
Michael
Op donderdag 5 maart 2015 22:22:11 UTC+1 schreef Andrew Henderson:
I have the integration of Bluetooth into BBBAndroid in my work queue, and
I'm getting to it, but it will still be a few days (at least).
On Wednesday, March 4, 2015 at 10:45:05 AM UTC-5, Michael Gobbers wrote:
That would be great! I'm in kind of a hurry. At the moment I completer
step 2 of the steps you mentioned.
Cheers,
Michael
On Mar 4, 2015 4:42 PM, Keith Conger keith@gmail.com wrote:
Hi Michael,
I've sent them to Andrew to review and hopefully include in bbbandroid.
If you're in a hurry I could email them to you.
Keith
On Wednesday, March 4, 2015 at 8:26:23 AM UTC-7,
mgob...@orcasolutions.be wrote:
Hi All,
Hi All I'm trying to do the exact same thing here with bbbandroid. I
have an asus 4.0 dongle with the BCM20702A0 chipset. I'm not really
experienced when it comes to making my own kernels.
I do understand what you are doing with these high level steps you
laid out here. However, I could use some help to actually execute
them... I
see you are going to include them as patches? Is the patch already
available? Where can I find it? Thanks!
Michael
Op vrijdag 20 februari 2015 00:13:13 UTC+1 schreef Keith Conger:
On Thursday, February 19, 2015 at 12:27:37 PM UTC-7, Andrew Henderson
wrote:
On Thursday, February 19, 2015 at 1:50:43 PM UTC-5, Keith Conger
wrote:
I've got bluetooth finally working. Andrew, what would be the best
way to pass you the changes needed?
Patches generated by git are fine. If you know the major parts that
you patched, you can also cd into the appropriate directory and do a
git
status to show you which files have changed and just mail me those
files
(hendersa (at) icculus.org). For subdirectories that are completely
new
(like the Bluez added into external/), you can just tar up the
directory and
send it to me. My understanding is that you added in Bluez, modified
the
build scripts to pull that external project in, patched bionic, and
changed
the kernel config to build in Bluetooth. Does that sound about right?
Ok I'll start work on getting it over to you. Basically you are
correct. Here are the steps at a high level:
* Add bluez repo to the manifest and told it to not pull bluedroid.
* Patched bionic, although I see bluez has a patched bionic in a repo
for 4.4, maybe I can just change the manifest.
* Built bluetooth kernel modules from backports, 3.8 is too old
* Added insmod commands to init.{ro.hardware}.rc on boot and added
import init.bluetooth.rc
* Commented out qemu=1 check for bluetooth.
* Had to manually move some libraries to /system/lib/hw/ from
/system/lib/
Keith
--
Keith Conger
keith DOT conger AT gmail DOT com
http://thecongers.org
--
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] Slow 720p playback
On Fri, Mar 6, 2015 at 12:06 PM, smallsponged...@gmail.com wrote: Hi all, Was trying to get some 720P video playback on my BBB on a neat touchscreen monitor I got from here. Surprisingly the screen works pretty well after just plugging it in. However, when trying to playback 720p video through VLC (no audio), I've got some major latency, youtube suffers the same way.This is a generic out-of-the-box BBB from Adafruit (element14) on 3.8.13-bone47, Debian 7. sgx doesn't do video acceleration... Only 3d After doing some searching, I found: http://beagleboard.narkive.com/Ebgduatx/debian-sgx-v3-14-x which I thought would solve my issue (granted, this seems to be for 3D acceleration, I'm not sure how it would actually help me with playback, I'm just grasping at straws here). Unluckily though, it doesn't seem to be a simple as sudo apt-get update ; sudo apt-get install linux-image-3.14.15-bone6, My apt-cache search linux-image returns this (as you can see, no 3.14. Those directions are old: Look at: http://elinux.org/BeagleBoardDebian#SGX_Drivers 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 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: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
On Fri, 6 Mar 2015 10:34:23 -0800 (PST), you wrote: Thanks very much for your response Harvey. Right sorry on the mA, I meant mV. Also I sent a picture of the circuit to the Adafruit customer support, it's in that forum thread that I linked to. And they said from looking at it, it shouldn't have been capable of frying the Bone. Pictures of the setup help little, except to find an uninstalled wire. The picture you put on the forum shows connections to the strip, but none to the drivers, nor from the drivers to the board. A schematic would be good, as well as the part numbers of the FETS. Otherwise, it's difficult to do anything but guess, although in this case, the guesses might be decent enough. I'm surprised I can't find anything similar to this issue. I will check out the regulators. Even in a relatively simple circuit, the number of ways that a circuit can be miswired is about N! where you count the parts and the wires. And that's just with miswiring, not forgetting something or adding bad parts. Hopefully, you damaged an easily replaceable part. The outputs on this chip are relatively fragile. There are other (perhaps older, perhaps a different design of chip) processors that have more robust outputs. Harvey On Thursday, March 5, 2015 at 10:41:17 PM UTC-8, gr...@sensa.io wrote: I wired up a circuit with an LED strip, 3 N-channel MOSFETs, and a separate 12V power supply, with the gate pins on the MOSFETS connected to I/O pins on the Beaglebone. When I didn't connect the circuit to the Bone ground, I apparently fried 2 boards. Neither will boot up. One gives a flicker on the power light and then goes off, and on the other the power light turns on, but the other LEDs don't flash and I can't get into either board. Here is the thread on the Adafruit forum with a photo of the circuit: http://forums.adafruit.com/viewtopic.php?f=8t=69691p=353330sid=eff0f5bd69bba9338e6f0ec2d7fa70c4#p353330 *The Adafruit support said that setup should not have hurt the board. * I checked the voltage on the gate pin on each MOSFET that was connected to the Bone and it was nominal (~200mA). Does anyone have any ideas on this? How could this have fried 2 boards? Thanks for any help. And PS I posted this earlier today but didn't see it show up in the forum. Sorry if it needed to be approved and you are getting a duplicate. -- 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] Dell monitor touchscreen and QT tslib
I am using debian. I cant tell the exact qt version now, as i dont have the hardware on me. I remember that there are inputa from 0 to 3 though. I tried all of them I think. The touch screen only barelly works with none of them selected and they appear only after i connect the monitor through usb... Weird. On March 6, 2015 8:07:55 PM James S s190...@gmail.com wrote: Which version of Qt are you using? Debian or Angstrom On the Bone? Is there any other event in /dev/input? -- 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/t4YGC-Y3a1Q/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] DTO and GPIO output error
I am trying to run the example blinkled project shown at https://github.com/BestFriendofDoug/PRUSS-C/tree/master/am335x_pru_package/pru_sw/app_loader/lib but I am not getting any output to the GPIO pins. I have set up the dto to output P9.12, and the blinkled.c is using StarterWare programs to toggle P9.12, but there is no output to the pins when the program runs. The git repo should have everything you need. I occasionally get the below error: ./blinkled INFO: Starting PRU_memAccess_DDR_PRUsharedRAM example. INFO: Initializing example. ./blinkled: symbol lookup error: ./blinkled: undefined symbol: prussdrv_load_datafile Which was solved for me when re-running the Makefile in /root/PRUSS-C/am335x_pru_package/app_loader/interface Any help on this issue would be appreciated!! -- 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] BBB latest Debian on eMMC Wifi broken after reboot
On Fri, Mar 6, 2015 at 1:30 PM, mike rankin 0mik...@gmail.com wrote: I've decided to put the BBB to use as a home media server instead of leaving my pc on all the time. I put the latest Debian flashable image on a microSD, held down the button, installed the image on the flash, removed the microSD, plugged in the wifi usb module. Got it working, updated the OS but the wifi stops on a reboot. I have to manually bring it up by: ifup wlan0 Adafruit has a tutorial at: https://learn.adafruit.com/setting-up-wifi-with-beaglebone-black/overview but it's a no go because uEnv.txt is not there anymore. /boot/uEnv.txt 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 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] Latest image in-built Python
On Fri, Mar 6, 2015 at 2:20 PM, Enoch i...@hotmail.com wrote: Good day to all, The latest BBB image is still using Python 2.7.3: debian@beaglebone:~$ python --version Python 2.7.3 debian@beaglebone:~$ uname -a Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux This means reworking certain SSL stuff which was introduced in Python 2.7.9. What would you recommend? Correct, wheezy is still 2.7.3: https://packages.debian.org/wheezy/python You could use the jessie image, but even that is only 2.7.8.. This is the way debian works, what ever version of a package in the repo around freeze time, is the version you'll get. Bugs/Security patches can be added, but they don't upgrade for the sake of upgrading.. 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 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: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Hi Harvey, I believe this is the main regulator pictured: TL5209, an LDO. https://lh5.googleusercontent.com/-ux4mly1xzM4/VPoRbI1S7SI/BYA/7QDwaWrj8Lg/s1600/BBB%2Bmain%2Bregulator.jpg On our BBB I read 5V going into the board, but only 1V on the regulator input, and 0V coming out... What could that mean? On Sam's BBB I read 5V into and 3.3V out of the regulator. This board's power light comes on and stays on, so that regulator seems fine. I'll keep looking into this one. BBB schematic: https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SCH.pdf Regulator manual: http://www.ti.com/lit/ds/symlink/tl5209.pdf -- 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] DTO and GPIO Output Test File Error
I am trying to run an example program shown at https://github.com/BestFriendofDoug/PRUSS-C but I can't get an output on my GPIO pin P9.12. All instructions should be available and possible errors/solutions. I have been having trouble with the following error at times: ./blinkled INFO: Starting PRU_memAccess_DDR_PRUsharedRAM example. INFO: Initializing example. ./blinkled: symbol lookup error: ./blinkled: undefined symbol: prussdrv_load_datafile but re-running the Makefile in /root/PRUSS-C/am335x_pru_package/app_loader/interface/ should rebuild the libprussdrv.so file and solve that issue. Any help on getting this example to run would be appreciated!! -- 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] best gui industrial automation development software
I found crank and Qt but not much else. Any other suggestions would be really helpful. Crank is quite expensive and Qt doesn't fit my needs. -- 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: BBB SPI device tree overlay, device number confusion
Don't know, I don't have the hardware to connect to yet On Fri, Mar 6, 2015, 16:00 Matt Graham matti...@gmail.com wrote: It's been a while since I was tinkering with this, but as I recall, the pin designations were as expected. Is your SPI not working? On Fri, Mar 6, 2015 at 4:55 AM, axo...@gmail.com wrote: I see the same problems. Guys, will it work though using the pins described for spi0? 2015. február 22., vasárnap 5:18:34 UTC+1 időpontban Steve French a következőt írta: Matt, I agree!!! It is very confusing, especially when you are trying to figure out which pin to probe!! -frenchy On Thursday, January 23, 2014 at 12:18:57 PM UTC-5, Matt Graham wrote: I think I posted to the wrong section of the group. Apologies for this repost. Running the latest angstrom image, with update, upgrade. Installing BB-SPIDEV0 seems to produce /dev/spidev1 which doesn't seem right. I was expecting /dev/spidev0 based on this http://elinux.org/ BeagleBone_Black_Enable_SPIDEV#SPI0 Any ideas on this problem? root@beaglebone:~# find /dev -iname *spi* root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI root@beaglebone:~# echo BB-SPIDEV0 /sys/devices/bone_capemgr.*/slots root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPIDEV0 root@beaglebone:~# find /dev -iname *spi* /dev/spidev1.0 /dev/spidev1.1 root@beaglebone:~# -- 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/4IeImY8I4-g/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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/4IeImY8I4-g/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] Re: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
If I assume that the ground on the circuit didn't have a connection to the BBB ground Nothing to assume :-) , there is NO ground connection between the BB and the bread board from what the picture shows, just 3 wires (Red, Green, Blue) not 4. If Adafruit said they could not see anything wrong with the wiring I would be very worried about their technical support -- 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] DTO and GPIO output error
That URL doesn't point to the source code. Can you simplify the step-by-step a bit further. I'm curious if http://sourceforge.net/projects/prudebug/ would help know that your code is properly loaded and running. On Fri, Mar 6, 2015 at 3:14 PM, Karl Anderson andersonkar...@gmail.com wrote: I am trying to run the example blinkled project shown at https://github.com/BestFriendofDoug/PRUSS-C/tree/master/am335x_pru_package/pru_sw/app_loader/lib but I am not getting any output to the GPIO pins. I have set up the dto to output P9.12, and the blinkled.c is using StarterWare programs to toggle P9.12, but there is no output to the pins when the program runs. The git repo should have everything you need. I occasionally get the below error: ./blinkled INFO: Starting PRU_memAccess_DDR_PRUsharedRAM example. INFO: Initializing example. ./blinkled: symbol lookup error: ./blinkled: undefined symbol: prussdrv_load_datafile Which was solved for me when re-running the Makefile in /root/PRUSS-C/am335x_pru_package/app_loader/interface Any help on this issue would be appreciated!! -- 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] OpenCV dependency problem
In order to trim down the default Debian distribution to reclaim some disk space, I had no problem deleting a few things I wouldn't need like Apache and libsane (not running a server and certainly don't plan to add a scanner). But trying to remove OpenCV--which is huge--Debian gets confused and tells me that most of X11 / Gtk / FreeDesktop is now unnecessary and can be autoremoved. Of course I don't want to do this--I need the desktop. I can't imagine why the desktop thinks it isn't needed anymore, as if it were a mere dependency of OpenCV (which it is), but not of anything else. -- 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: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Also, I believe the RasPi uses 5V logic while the BBB uses 3.3V logic /IO No one could make a greater mistake than he who did nothing because he could do only a little. All that is necessary for the triumph of evil is that good men do nothing Edmond Burke (1729 - 1797) http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of JS-BBB Sent: Friday, March 06, 2015 11:01 PM To: beagleboard@googlegroups.com Subject: [beagleboard] Re: BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply 1st of all IF you used the FETs shown on Adafruit they are logic level FETs, so you can drive them directly from the BB. Resistors are only required if you had used the transistors instead of the FETs. As discussed you missed the GND wire (Black) as shown on Adafruit. Where did you measure the 200mV? From the BB GND to the outputs or elsewhere? As you don't have a common GND readings are pretty much meaningless. FETs have a large capacitance on the Gate, without a common ground you could have several hundred (or thousands) volts of static charge for a very short period, but it could be large enough to kill the processor. Very likely if you have carpets around. If you unplug everything you added to the BB will it boot up again? If not the above may be possible. You seem to be using P9_12, P9_16 and P9_21 they should be safe to use as I'm using them on a couple of projects without problems, you MUST add the GND wire from any pin 1 or 2 of either P8 or P9 to the GND track of your breadboard. I may think of something else later on... meanwhile, as I said above, unplug everything from the BB and see if it powers up, if not it's shopping time again. -- 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. _ No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5646 / Virus Database: 4299/9212 - Release Date: 03/02/15 -- 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] Linux-firmware for Realtek rtl8192cu wifi dongle
Dear I'm using buildroot to build a custom root file system for BeagleBone. My application uses a wifi dongle (Realtek 8192 chipset). I rebuilt kernel image (ver 3.2.0) and the image and wifi dongle work well with Debian root file system. My problem is : the built buildroot root file system get firmware error when modprobe rtl8192cu: # modprobe rtl8192cu [ 194.077442] cfg80211: Calling CRDA to update world regulatory domain Feb 15 08:01:23 beaglebone kern.info kernel: [ 194.077442] cfg80211: Calling CRDA to update world regulatory domain [ 194.171603] rtl8192cu: MAC address: 00:0f:13:59:0f:e1 [ 194.176981] rtl8192cu: Board Type 0 Feb 15 08:01:23 beaglebone kern.info kernel: [ 194.171603] rtl8192cu: MAC address: 00:0f:13:59:0f:e1 Feb 15 08:01:23 beaglebone kern.info kernel: [ 194.176981] rtl8192cu: Board Type 0 [ 255.203972] usbcore: registered new interface driver rtl8192cu # Feb 15 08:02:24 beaglebone kern.debug kernel: [ 255.203643] rtl8192cu:rtl92cu_init_sw_vars():0-0 Failed to request firmware! Feb 15 08:02:24 beaglebone kern.debug kernel: [ 255.203668] rtlwifi:rtl_usb_probe():0-0 Can't init_sw_vars. Feb 15 08:02:24 beaglebone kern.info kernel: [ 255.203972] usbcore: registered new interface driver rtl8192cu I also chose the option: Target packages - Hardware handling - Frimware - wifi firmware: [ ] Marvell Wifi-Ex SD 8787 [ ] Ralink rt2501/rt61 [ ] Ralink rt73 [ ] Ralink rt27xx/rt28xx/rt30xx [*] Realtek 81xx [*] Realtek 87xx [*] Realtek 88xx [*] TI wl127x [*] TI wl128x [ ] TI wl18xx But it can not change the error Please help me Thank you -- 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: BBBAndroid with USB Bluetooth Adapter Support
Hey Andrew,
I received the patch files and the backports from Keith by mail. So I can
progress. However, I seem to have a problem when building the backports
tree. I included them in the root of the bbbandroid repo and when the
kernel is being built in the make process I'm getting the following
output/error:
Building modules, stage 2.
MODPOST 1257 modules
make[1]: Leaving directory `/home/michael/kernel'
make -C backports-3.18.1-1 ARCH=arm
CROSS_COMPILE=/home/michael/prebuilts/gcc/linux-x86/arm/arm-gnueabihf-4.7/bin/arm-linux-gnueabihf-
KLIB_BUILD=../kernel
make[1]: Entering directory `/home/michael/backports-3.18.1-1'
/--
| You shouldn't run make in the backports tree, but only in
| the generated output. This here is only the skeleton code
| copied into the output directory. To use the backport system
| from scratch, go into the top-level directory and run
| ./gentree.py /path/to/linux-next/ /tmp/output
| and then make menuconfig/... in the output directory. See
| ./gentree.py --help
| for more options.
\--
make[2]: *** [modules] Error 1
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/michael/backports-3.18.1-1'
make: *** [kernel_build] Error 2
Maybe you could shed some light on this?
Thanks,
Michael
Op donderdag 5 maart 2015 22:22:11 UTC+1 schreef Andrew Henderson:
I have the integration of Bluetooth into BBBAndroid in my work queue, and
I'm getting to it, but it will still be a few days (at least).
On Wednesday, March 4, 2015 at 10:45:05 AM UTC-5, Michael Gobbers wrote:
That would be great! I'm in kind of a hurry. At the moment I completer
step 2 of the steps you mentioned.
Cheers,
Michael
On Mar 4, 2015 4:42 PM, Keith Conger keith@gmail.com wrote:
Hi Michael,
I've sent them to Andrew to review and hopefully include in
bbbandroid. If you're in a hurry I could email them to you.
Keith
On Wednesday, March 4, 2015 at 8:26:23 AM UTC-7,
mgob...@orcasolutions.be wrote:
Hi All,
Hi All I'm trying to do the exact same thing here with bbbandroid. I
have an asus 4.0 dongle with the BCM20702A0 chipset. I'm not really
experienced when it comes to making my own kernels.
I do understand what you are doing with these high level steps you
laid out here. However, I could use some help to actually execute them... I
see you are going to include them as patches? Is the patch already
available? Where can I find it? Thanks!
Michael
Op vrijdag 20 februari 2015 00:13:13 UTC+1 schreef Keith Conger:
On Thursday, February 19, 2015 at 12:27:37 PM UTC-7, Andrew Henderson
wrote:
On Thursday, February 19, 2015 at 1:50:43 PM UTC-5, Keith Conger
wrote:
I've got bluetooth finally working. Andrew, what would be the best
way to pass you the changes needed?
Patches generated by git are fine. If you know the major parts that
you patched, you can also cd into the appropriate directory and do a git
status to show you which files have changed and just mail me those files
(hendersa (at) icculus.org). For subdirectories that are completely new
(like the Bluez added into external/), you can just tar up the directory
and send it to me. My understanding is that you added in Bluez, modified
the build scripts to pull that external project in, patched bionic, and
changed the kernel config to build in Bluetooth. Does that sound about
right?
Ok I'll start work on getting it over to you. Basically you are
correct. Here are the steps at a high level:
* Add bluez repo to the manifest and told it to not pull bluedroid.
* Patched bionic, although I see bluez has a patched bionic in a repo
for 4.4, maybe I can just change the manifest.
* Built bluetooth kernel modules from backports, 3.8 is too old
* Added insmod commands to init.{ro.hardware}.rc on boot and added
import init.bluetooth.rc
* Commented out qemu=1 check for bluetooth.
* Had to manually move some libraries to /system/lib/hw/ from
/system/lib/
Keith
--
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] BeagleBone Black won't boot after wiring up LED strip w MOSFETs and separate 12V power supply
Right, Adafruit was aware there was no ground connection. They just said this should not have caused the BBB to fry from voltage running through the FET gate pins which were connected to the board. On Friday, March 6, 2015, JS-BBB jsamperi2...@gmail.com wrote: If I assume that the ground on the circuit didn't have a connection to the BBB ground Nothing to assume :-) , there is NO ground connection between the BB and the bread board from what the picture shows, just 3 wires (Red, Green, Blue) not 4. If Adafruit said they could not see anything wrong with the wiring I would be very worried about their technical support -- 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/-_CH3VS1uz4/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com javascript:_e(%7B%7D,'cvml','beagleboard%2bunsubscr...@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.
