Re: [beagleboard] Using BB to measure power
Really ouch. I you do it like this and connect your BB(B) to the lan, then all computers in your school are under tension (Brrr)! Therefore: NEVER USE A VOLTAGE DIVIDER WITH NET CURRENT, unless you really now what you do! You need to have a galvanic separation like a transformer or a diode. Have a look at this: http://www.instructables.com/id/Real-time-Web-Based-Household-Power-Usage-Monitor/?ALLSTEPS On Wed, Oct 30, 2013 at 10:31 PM, Przemek Klosowski przemek.klosow...@gmail.com wrote: Ouch, and another ouch since you seem to live in a 220VAC country. You can't just connect 220V to a voltage regulator---it has maximum allowed input voltage around 35V---you'd exceed that by a factor of almost 10. You probably should either do some reading about line voltage electronics and 220V power supplies (hint---what you propose could work if you used a transformer to get 220V down to 12V or so). My suggestion to you would be to consider a low-cost commercial power meter like Kill-A-Watt ($20 or so) then point a BBB with a webcam at its display, and do a little image processing to read out the power. People also cracked them open and interfaced directly to their internal circuitry. On Wed, Oct 30, 2013 at 2:57 PM, jredr...@gmail.com wrote: I'd like to use my BeagleBone Black to build a small power efficiency station for my school. For that I plan to measure power consumption using a current transformer and a voltage transformer, feed the data into a small fast database and show it through a web interface to the school staff. I see that 50 Hz are not a problem for BB ADCs, but I'm not sure at all using them is a good idea. Intially I planned to use the same voltage I must measure to power the BB. I'm starting from a circuit like the attached one (replacing the UA78M33 by a UA7805CKCT which provides up to 1.5 A output) Changing the R1/R2 divisor I can make the 220V signal lower , but I'd always get a signal with a negative side (-0.9V - +0.9V) in the best case. Same for the current transformer, after applying its output to a 100 ohms resistor. So, first, is it an awful idea to use BB for this purpose? If not, how can I avoid the negative part of the signal before feeding the BB ADCs? Thanks in advance -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: modprobe rtc-ds3231 returns module not found?
On Thursday, October 31, 2013 7:49:27 AM UTC-4, Will Kostelecky wrote: It's on i2c-1. The frustrating thing is that the HW works with another image that I built a while ago. I am now trying to build a clean new image (post all my development messing around) and it is not working with the new build. I am pretty sure I did not have to do anything other than what I am doing now but obviously I have missed something in the new build. Newer builds require the use of a device tree overlay to ensure the hardware you need is available, in older builds, you had to rebuild the kernel if what you wanted wasn't available. Although recent builds have had the dto support, I have found various issues here and there. So i2c-1 is the enumeration linux gave one of the i2c buses and does not necessarily correspond to the i2c pins you are using. The BBB has two usable i2c devices [1], as follows: - i2c0: Not exposed in the expansion headers - i2c1: pins P9 17,18 (and 24,26) - i2c2: pins P9 19,20 (and 21,22) The i2c devices appear in the AM335x memory map [2] at the following locations: - i2c0: 0x44E0_B000 - i2c1: 0x4802_A000 - i2c2: 0x4819_C000 Linux creates mappings in the /sys/bus/i2c/devices pseudo-filesystem that indicates the mappings from the i2c-* devices to the underlying hardware: root@beaglebone:~# ls -l /sys/bus/i2c/devices/i2c-* lrwxrwxrwx1 root root 0 Jan 1 2000 /sys/bus/i2c/devices/i2c-0 - ../../../devices/ocp.2/*44e0b000*.i2c/i2c-0 lrwxrwxrwx1 root root 0 Jan 1 2000 /sys/bus/i2c/devices/i2c-1 - ../../../devices/ocp.2/*4819c000*.i2c/i2c-1 So you can see here, that on my BBB, i2c0 is mapped to /dev/i2c-0 and i2c2 is mapped to /dev/i2c-1. You can check your system, but I suspect that i2c-1 is actually i2c2 on pins P9_19,20. -W. [1] BBB I2C Ports. See http://circuitco.com/support/index.php?title=Cape_Expansion_Headers#2_I2C_Ports [2] TI Sitara AM335x SRM, page 211, 212. See http://elinux.org/images/6/65/Spruh73c.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/groups/opt_out.
Re: [beagleboard] Re: modprobe rtc-ds3231 returns module not found?
It is now working. I have no idea what I have done to make it work. I even created a new image and tried to get it to not work again and could not. I guess this is good news? On Thursday, 31 October 2013 11:49:27 UTC, Will Kostelecky wrote: It's on i2c-1. The frustrating thing is that the HW works with another image that I built a while ago. I am now trying to build a clean new image (post all my development messing around) and it is not working with the new build. I am pretty sure I did not have to do anything other than what I am doing now but obviously I have missed something in the new build. Will -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Using BB to measure power
El miércoles, 30 de octubre de 2013 22:31:43 UTC+1, Przemek Klosowski escribió: Ouch, and another ouch since you seem to live in a 220VAC country. You can't just connect 220V to a voltage regulator---it has maximum allowed input voltage around 35V---you'd exceed that by a factor of almost 10. You probably should either do some reading about line voltage electronics and 220V power supplies (hint---what you propose could work if you used a transformer to get 220V down to 12V or so). Maybe I didn't explain it correctly: I'm connecting a current transformer and a current voltage transformer (220/9) to the circuit in the scheme. So the voltage regulator is receiving 9v (about 12.7 V , but with about 0.6v less because of the diode rectifier) My suggestion to you would be to consider a low-cost commercial power meter like Kill-A-Watt ($20 or so) then point a BBB with a webcam at its display, and do a little image processing to read out the power. I don't like this solution, too many things to add... People also cracked them open and interfaced directly to their internal circuitry. mmm, do you know if there are any publications of the results of these cracks? They might provide me some ideas. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: BeagleBone Black (BBB) 7 LCD LVDS bundle (Cape + 7 Display) form Chalkboard
Hi Berthold, I bought this cape too, but without the LCD, which I have many over my table, and have cable and monitor, to test. Could I know if you make this cape works already ? if not, and I make some success :) I will share here. Best Regards, On Monday, July 15, 2013 5:36:26 AM UTC-3, Berthold Braun wrote: I have put the bbb on ice for now, because it is quite new and i think that the bbw capes are not always compatible to it. For now I am useing an beagleboard xM for my project with an LC display from chalkboard. It works out of the box, only the resulution has to be altered. so the bbb will slumber till chalkboard or anybody else will build an 7Display kit for the BBB. KR Berthold Am Donnerstag, 6. Juni 2013 22:52:37 UTC+2 schrieb Berthold Braun: Hello Guys, Today I received my BeagleBone Black and the 7 LCD LVDS bundle (Cape + 7 Display) form Chalkboard ( http://www.chalk-elec.com/?page_id=1280#!/~/product/category=3094859id=13727570 ). On thier page i couldn´t find any manual how to setup the bungle or software guides for the BBB just one small software guide for the BBW . I have updated to the current Angstrom version and would like to use the BBB with the LCD cape. First of all I am not really sure how to connect the hardware to the board. Of cause the cape is just plugged on top and also the connection to the display is self explaining, but there is another little PCB which can be plugin in two ways and has an mini USB port. https://lh5.googleusercontent.com/--7kbeN9WrGw/UbDwPxeRS9I/AfA/CoMwDMotD5o/s1600/IMAG0627_1.jpg and this little board: which in my understanding can be plugged in here, but there is no failsave so i could also turn it around ...: https://lh6.googleusercontent.com/-I3EpsOzYM_I/UbDy5m-vTgI/Afk/ak0ypfd-pRg/s1600/IMAG0637_1.jpg But the backlight of the LCD is running without this litte pcb when I plug the board to power. It stays black! Is that becasue the BBB isn´t configured for this display or becasue the little PCB needs to be connected. My Problem is I don´t have an micro HDMI cable here right now to see if the Cape is recognized by the board or not. I was under the impression that I wouldn´t need it, because it was plug and play :( Has anybody an BBB running with this cape and display and can give me some tips on how to configure it. Kindest Regards and many Thanks in advance. Berthold -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Confusion over the use of the compatible property in device tree overlays
I've read in the wiki's that the compatible property will hold a list in the format: manufacturer, model to indicate board compatibility. Then there is also where the compatible property will hold a list in the format manufacturer, model for hardware on the board so the os will assign the driver best suited for the device - if known by the os. But the use of the compatible property that seems a little confusing is where the compatible property will hold for example: compatible = spidev or compatible = bone-pincntrl-helper. My question is are these drivers or functions that are used by the OCP to configure or communicate with the peripheral and if they are is there a listing of these driver and or functions that I can access and study? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: No access to 192.168.7.2 BeagleBone A6a
Hi, Had the same problem. But ping 192.168.7.2 worked. It appeared that the proxy setting in the browser was causing the problem. Op vrijdag 25 oktober 2013 09:07:44 UTC+2 schreef steftn: Hi, My operating system is Win 7 64 bit with US-language packet. My internet browser is Mozilla Firefox. I have a BeagleBoard A6a which I want to access on my computer. I used the 'getting startet' tutorial to access on my BeagleBoard but the connection to 192.168.7.2 via USB doesn't work. Does anyone know why? Here the link to the 'getting started' tutorial: http://beagleboard.org/Getting%20Started My procedure: 1. Connect the BeagleBone via USB cable to my computer 2. Install and execute this driver: beagleboard.org/static/Drivers/Windows/BONE_D64.exe 3. Typed 192.169.7.2 to launch BeagleBone --- and this didn't work!!! But the access to the microSD card works perfectly! Does anyone know what I make wrong? Thanks for help, bye! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Does Angstrom use hard float ?
Of course it works. There is even the same from the OE environment -and I mean : from the official repo - , here is set for my angstrom-SDK : export CC=arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 --sysroot=/usr/local/oecore-i686/sysroots/cortexa8hf-vfp-neon-angstrom-linux-gnueabi Here are the options that pointed out from the Arm Cortex Documentation. Which works nicely on my board. David 2013/10/31 Markus Reichl rei...@t-online.de After trying to cross-compile with the hard float library without success, I finally use the soft float library and it work. Hi tee, on the BBB in /lib I just did: ln -s ld-linux.so.3 ld-linux-armhf.so.3 Now my cross compiled binaries work on BBB. I used crosstool-ng 1.19 for generating the cross-toolchain on my PC (opensuse 12.2). I attach the .config for crosstool-ng. -- Markus -- 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/hZ39EQr_tyk/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: I2C on ubuntu linux 3.8, BBB pin confusion?
On Thursday, October 31, 2013 1:45:16 PM UTC-4, Dacobi wrote: But how do I translate this to pin numbers on P8 and P9? Take a look at this thread/post, it should help: https://groups.google.com/d/msg/beagleboard/v9r8UkN7klk/h3rFKFJDLnUJ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: I2C on ubuntu linux 3.8, BBB pin confusion?
Ok, I did a cycle of the reset pin on the sensor board, and now it responds to i2cdetect -r 1 at address 0x60 :) this is using pins 19 for CLK and 20 for DATA. with VDD at pin 5 (5V) thanks for the link. /Jacob 2013/10/31 Jacob Ole Juul Kolding dac...@gmail.com I'm not sure if either my sensor isn't working or if it is something else. I've tried all combinations of 17,18 / 19,20 / 21,22 / 24,26 and i2cdetect -r 0 i2cdetect -r 1 i2cdetect -r 2 but nothing shows up at 0x60, the address of my sensor (MPL115A2) http://www.adafruit.com/products/992#Tutorials /Jacob 2013/10/31 smith.winston@gmail.com On Thursday, October 31, 2013 1:45:16 PM UTC-4, Dacobi wrote: But how do I translate this to pin numbers on P8 and P9? Take a look at this thread/post, it should help: https://groups.google.com/d/msg/beagleboard/v9r8UkN7klk/h3rFKFJDLnUJ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- If you're not a socialist when you're young, it's because you have no heart. If you stop being a socialist when you get older, it's because you lack intellect and imagination. -- If you're not a socialist when you're young, it's because you have no heart. If you stop being a socialist when you get older, it's because you lack intellect and imagination. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Using BB to measure power
Thanks for your answer Andrew, I'm going to checkt the ADE7763. In fact I was studying now the MCP3909 or MCP3901. These products look similar to the ADE7763. Any advice to choose the best one to interface with BB is very welcome. Regards. José L. El jueves, 31 de octubre de 2013 19:35:50 UTC+1, AndrewTaneGlen escribió: Hey Jose, You could implement a very basic rectifier http://en.wikipedia.org/wiki/Rectifier#Single-phase_rectifiers to get an always-positive voltage Alternatively, you could use something like the ADE7763 ( http://www.analog.com/en/analog-to-digital-converters/energy-measurement/ade7763/products/product.html), in combination with your step-down transformers to get all of the volts/amps/power/phase infor you're after. I would recommend this option. Regards, Andrew. On Friday, 1 November 2013 05:40:47 UTC+13, José Luis Redrejo wrote: El jueves, 31 de octubre de 2013 13:28:12 UTC+1, Dieter Wirz escribió: Really ouch. I you do it like this and connect your BB(B) to the lan, then all computers in your school are under tension (Brrr)! Therefore: NEVER USE A VOLTAGE DIVIDER WITH NET CURRENT, unless you really now what you do! You need to have a galvanic separation like a transformer or a diode. I do, I do, maybe I didn't explain it . In my first message, the CONN_2 connector is connected to a 220/9 AC Transformer, so, I'm using 9 V AC to feed that circuit. Have a look at this: http://www.instructables.com/id/Real-time-Web-Based-Household-Power-Usage-Monitor/?ALLSTEPS Great, it's very similar to what I want to do. But, re-reading the article I see he's using a power factor of 0.75 and a voltage value of 110 V, to calculate Active Power. I want to measure these parameters to get the real active /reactive power values, that's why I have the ADC_VAC line in my circuit. That's exactly the line I don't know how to pass from negative/positive values to only positive values lower than 1.8 v to feed the BB ADC. On Wed, Oct 30, 2013 at 10:31 PM, Przemek Klosowski przemek@gmail.com wrote: Ouch, and another ouch since you seem to live in a 220VAC country. You can't just connect 220V to a voltage regulator---it has maximum allowed input voltage around 35V---you'd exceed that by a factor of almost 10. You probably should either do some reading about line voltage electronics and 220V power supplies (hint---what you propose could work if you used a transformer to get 220V down to 12V or so). My suggestion to you would be to consider a low-cost commercial power meter like Kill-A-Watt ($20 or so) then point a BBB with a webcam at its display, and do a little image processing to read out the power. People also cracked them open and interfaced directly to their internal circuitry. On Wed, Oct 30, 2013 at 2:57 PM, jred...@gmail.com wrote: I'd like to use my BeagleBone Black to build a small power efficiency station for my school. For that I plan to measure power consumption using a current transformer and a voltage transformer, feed the data into a small fast database and show it through a web interface to the school staff. I see that 50 Hz are not a problem for BB ADCs, but I'm not sure at all using them is a good idea. Intially I planned to use the same voltage I must measure to power the BB. I'm starting from a circuit like the attached one (replacing the UA78M33 by a UA7805CKCT which provides up to 1.5 A output) Changing the R1/R2 divisor I can make the 220V signal lower , but I'd always get a signal with a negative side (-0.9V - +0.9V) in the best case. Same for the current transformer, after applying its output to a 100 ohms resistor. So, first, is it an awful idea to use BB for this purpose? If not, how can I avoid the negative part of the signal before feeding the BB ADCs? Thanks in advance -- 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/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to
[beagleboard] Re: Does PINCTRL work on BB xM, kernel v. 3.11?
Well, so I think I understand a bit more about the DTS support for GPIO. I
configured the pinctrl for GPIO5 channel, and it seems to have some effect
on the GPIO pins. After the kernel starts up the LEDs are being turned off.
omap3_pmx_core {
vvv_gpio_pins: pinmux_gpio_pins {
pinctrl-single,pins =
0x136 (PIN_OUTPUT | MUX_MODE4) /* gpio_137
*/
0x138 (PIN_OUTPUT | MUX_MODE4) /* gpio_138
*/
0x13a (PIN_OUTPUT | MUX_MODE4) /* gpio_139
*/
;
};
};
gpio5 {
pinctrl-names = default;
pinctrl-0 = vvv_gpio_pins;
};
However the GPIO export mechanism from userspace is still not working.
Basically, no matter what value you try to set gpio137-139, they stay low
(although the value in the /sys/class/gpio/gpioXXX/value file is being
changed appropriately. It's as if gpiochip128 is not really associated
with gpio5.
I am also worried about not being able to dump *
/sys/kernel/debug/pinctrl/48002030.pinmux/pins* . The kernel hiccup occurs
on the base 3.11 DTB file, so it's not my change that's causing it.
On Friday, October 25, 2013 3:13:46 PM UTC-4, porkupan wrote:
Trying to dump the pinmux states
(/sys/kernel/debug/pinctrl/48002030.pinmux/pins) in 3.11 seems to cause a
kernel crash:
http://paste.ubuntu.com/6302171/
GPIO access via /sys/class/gpio appears to be nonoperational in 3.11. It
looks like a reasonable assumption that GPIOs may not be muxed into the
GPIO pins.
I tried to add a devicetree entry to to force-mux GPIOs:
omap3_pmx_core {
vvv_gpio_pins: pinmux_gpio_pins {
pinctrl-single,pins =
0x134 (PIN_OUTPUT | MUX_MODE4) /*
gpio_137 */
0x135 (PIN_OUTPUT | MUX_MODE4) /*
gpio_138 */
0x136 (PIN_OUTPUT | MUX_MODE4) /*
gpio_139 */
;
};
};
ocp {
gpio_helper: helper {
compatible = ti,omap3-gpio;
pinctrl-names = default;
pinctrl-0 = vvv_gpio_pins;
status = okay;
};
};
Doesn't seem to do anything. The only indication that the kernel is
actually trying to parse the fake helper device is these lines in the
message log:
[0.369201] omap_gpio helper.26: could not find pctldev for node
/ocp/pinmux@48002030/pinmux_gpio_pins, deferring probe
[0.369232] platform helper.26: Driver omap_gpio requests probe deferral
...
[3.354125] omap_gpio helper.26: Invalid IRQ resource
Obviously, I have no idea what compatible driver should I chose,
omap3_gpio just sounded like something that could fit. For BBB they
reference bone-pinmux-helper, which I assume is BBB-specific?
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/groups/opt_out.
[beagleboard] Beagle Black sturt-up
Hi all, I would buy this card but i need some informations: which version of ubuntu I can mount on the board? I need only linux without graphics so how to customize kernel? there is a LTIB here or menuconfig? 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/groups/opt_out.
Re: [beagleboard] EMC measurement
All of that information is posted on the support Wiki. http://circuitco.com/support/index.php?title=BeagleBoneBlack#Regulatory_Compliance_Documents Gerald On Thu, Oct 31, 2013 at 10:57 AM, pasha...@gmail.com wrote: Hi Gerald, I want to use the beagleboard black in a medical product which should pass the EMC tests for the standards. Do you have any suggestions for that?and can I have the FCC part 15 report ? On Monday, February 21, 2011 10:53:49 PM UTC+3:30, Gerald wrote: The -xM has passed FCC part 15. I can get you the report if you contact me direct. Gerald On Mon, Feb 21, 2011 at 7:08 AM, Thomas Weber thomas.we...@** googlemail.com wrote: Has someone made emc measurement with the beagleboard. And how are the results? Regards, Thomas -- You received this message because you are subscribed to the Google Groups Beagle Board group. To post to this group, send email to beagl...@googlegroups.com. To unsubscribe from this group, send email to beagleboard...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/beagleboard?hl=enhttp://groups.google.com/group/beagleboard?hl=en . -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Variable processor speeds?
From a HW perspective this is controlled by changing the clock speed of the processor inside the processor and lowering the voltage on the power rails using the power management IC. It is supported in the kernel. You can find more information in the processor Technical Reference Manual found at http://www.ti.com/product/am3359. For the PMIC, you find this at http://www.ti.com/product/tps65217C Gerald On Thu, Oct 31, 2013 at 2:02 PM, pyroartist...@gmail.com wrote: In one of the posts here someone mentioned 200, 400, 800 and 1Ghz speeds for the processor. I see nothing about this in the BBB manual PDF. How is this controlled? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver
On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner jkrid...@beagleboard.org wrote: On Thu, Oct 17, 2013 at 6:12 PM, clarkbriggs...@gmail.com wrote: AIW: I went back thru the adafruit library and didn't find anything specific on I2C, although it is listed as a topic. I have been looking at their github adafruit-beaglebone-io-python library. I also found and looked thru PyBBIO. Even tho I'm not using Python, I can see the access mechanisms that they use. I can use the MPU6050 device ok enough just reading via /dev/i2c/i2c-x, but that is too slow. I'm trying to figure out how to invoke and use the inv-mpu6050 driver and adafruit doesn't use that. Thx -- Clark On Thursday, October 17, 2013 9:47:44 AM UTC-7, AIW wrote: Some good info on I2C tools at http://www.acmesystems.it/i2c. Python and the adafruit BBIO I2C library makes it very easy to use I2C on Beaglebone Black as well. Python import smbus is fairly easy to use too. Some examples of use is available in the code I provide for my radio project herewww.aiwindustries.com. Not trying to sell the product, but I know that the I2C function was giving me some issues so I'm just trying to help the community. Python code is available to download and look at usage so feel free. On Tuesday, October 15, 2013 5:02:59 PM UTC-5, clarkbr...@gmail.com wrote: We are using the Invensense MPU6050 IMU on I2C with Beaglebone Black (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c but the read speed is disappointingly slow. We only read the 3x gyros and 3x accels (each one byte at a time plus the 2 byte temperature reading) and it takes ~2msecs. My estimate of the I2C bus cycles for a block read suggests this should take ~160 bus cycles or .38msec on a 400MHz I2C bus. You are running at 400kHz, not 400MHz, right? I2C doesn't do 400MHz. The distribution includes the Invensense driver inv-mpu6050.ko but there is no indication that reading through /dev/i2c invokes it. This is a very popular IMU and Invensense widely distributes the driver over many Linux platforms. The driver source includes “successful installation will create two directories under /sys/bus/iio/devices” and lists the files there (aka functions). I can never get these to show up. I can “insmod /lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050/inv-mpu6050.ko” and “echo inv-mpu6050 0x68 /sys/class/i2c-adapter/i2c-1/new_device”. This causes a new directory named 1-0068 to show in /sys/class/i2c-adapter/i2c-1with entries like name and modalias but no functions. It never shows in /sys/bus/iio/devices. I don't have an MPU6050, but I just ordered a couple on express overnight from Sparkfun. I bought https://www.sparkfun.com/products/11028 and played with it briefly before being distracted and again today, but I don't understand why I'm not able to get it to reply to me. I have the following connections: VCC: P9_4 (VDD_3V3) GNC: P9_1 (GND) INT: P9_11 (GPIO) FSYNC: - SCL: P9_19 (I2C2_SCL) SDA: P9_20 (I2C2_SDA) VIO: P9_3 (VDD_3V3) CLK: - ASCL: - ASDA: - I then perform: root@beaglebone:~# i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Very confused why it doesn't show up. Since you have it responding to you, how do you have it wired? Here's the behavior I'm seeing without the board connected: root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# ls inv-mpu6050.ko root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# dmesg | tail -1 [ 2992.799594] i2c i2c-1: new_device: Instantiated device inv-mpu6050 at 0x68 root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# lsmod Module Size Used by ip_tables 8294 0 x_tables 15072 1 ip_tables g_multi55905 2 libcomposite 15228 1 g_multi rfcomm 25106 0 ircomm_tty 14503 0 ircomm 8846 1 ircomm_tty irda 89974 2 ircomm_tty,ircomm ipv6 229989 14 hidp 10112 0 bluetooth 146100 4 hidp,rfcomm rfkill 16510 2 bluetooth autofs417432 2 I looked for the installed device: root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# cat /sys/bus/iio/devices/iio*/name tiadc root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# ls /sys/bus/iio/devices/iio* -d /sys/bus/iio/devices/iio:device0 It is clearly missing
[beagleboard] Re: Variable processor speeds?
Thanks, Gerald. So what is the normal default speed that the processor runs at in the BBB? Or does it vary depending on what? I only need high speed for short bursts of one second intervals. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Variable processor speeds?
Under Angstrom we generally we have the automatic mode on. It can vary between 300MHz 600MHz 800MHz and then 1GHz bases on the settings you pick. It has four modes, Conservative, ondemand, performance, and power save. You can add a control for it by adding it to the top tool bar. To do that: 1) hover the mouse over the top too bar 2) Right click the mouse 3) Click on Add Panel 4) Then select CPU Frequency Scaling Monitor 5) Select the Add button Once installed hover the mouse over it an click the left button. You will then see what I described above. It also shows you the current processor frequency. Gerald On Thu, Oct 31, 2013 at 3:36 PM, pyroartist...@gmail.com wrote: Thanks, Gerald. So what is the normal default speed that the processor runs at in the BBB? Or does it vary depending on what? I only need high speed for short bursts of one second intervals. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] linux kernel 3.12.0-rc7 usb webcam 0bda:5801 uvcvideo hangs on beaglebone black
Greetings, First, thank you Robert Nelson for the fine work, moving the beaglebone black forward to the latest kernels! I've got a usb webcam, 0bda:5801 , that works with the TI PSP 3.2.x kernel, but not with the 3.8.x or 3.12.0-rc7 kernels. I am using the Wheezy distro. It hangs -- not only with my small python extension grabber, but also with standard programs like Camorama and luvcview. The outputs from uvcdynctrl -l, and v4l2-ctl -V, seem reasonable, yet the programs hang, right away, on the first frame. I think the problem is related to DMA, so I am hoping there is some kernel parameter that I can tweak to get it working. It is a special camera, so I can't just toss it and choose another one. Thanks in advance for any suggestions! William -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Extracting eMMC contents using FAT formatted card
On Thu, Oct 31, 2013 at 1:34 PM, vincent.cource...@gmail.com wrote: Hi Jason, I really like the method you propose. Except the fact I tried it and I can't get it to work, or at least not following your directions. - I’ve flashed my BBB to Debian (http://elinux.org/BeagleBoardDebian) worked like a charm – now booting to the SD by default - I followed your instructions (8GB µSD, FAT32 formatted) o If I press no button, the BBB boots on the eMMC This tells me that the bootloader you flashed onto the eMMC doesn't properly work with the uEnv.txt put onto the uSD card as part of following my instructions. o If I press the “boot” button while plugging the power, the BBB just doesn’t boot (stays in a “powered off” state, with only the LED near the power plug on) This means that the uSD card FAT partition isn't marked as bootable. You can do that with 'fdisk' from your BeagleBone running Debian in all likelihood. root@beaglebone:~# fdisk /dev/mmcblk1 Welcome to fdisk (util-linux 2.23.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): a Partition number (1,2, default 2): 1 Command (m for help): p Disk /dev/mmcblk1: 3904 MB, 3904897024 bytes, 7626752 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x Device Boot Start End Blocks Id System /dev/mmcblk1p1 *2048 133119 65536e W95 FAT16 (LBA) /dev/mmcblk1p2 133120 7626751 3746816 83 Linux The BBB is brand new, so maybe they changed something. Who's they? It is possible CircuitCo switched the bootloader image on the eMMC, but it sounds more like you did that above. Thanks for your help. On Thursday, September 26, 2013 10:16:54 AM UTC-7, Jason Kridner wrote: There are lots of ways to extract the contents of the eMMC to save off and reuse. I'm proposing a method using Buildroot and an initramfs such that you can simply drop a few files from a .zip onto a normal, FAT-formatted SD card to perform the extraction. There are several things really handy here, such as the ability to edit autorun.sh to be whatever script you want to run on your board at boot. In the archive, I only have the necessary autorun.sh for *saving* your eMMC content. The flip-side is provided here in the text such that you need to go through a couple of steps before you trash your eMMC. The steps for saving off your eMMC contents to a file: * Get a 4GB or larger uSD card that is FAT formatted. * Download https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zip and extract the contents onto your uSD card. * Eject uSD card from your computer, insert into powered-off BeagleBone Black and apply power to your board. * You'll notice USR0 (the LED closest to the S1 button in the corner) will (after about 20 seconds) start to blink steadily, rather than the double-pulse heartbeat pattern that is typical when your BeagleBone Black is running the typical Linux kernel configuration. * It'll run for a bit under 10 minutes and then USR0 will stay ON steady. That's your cue to remove power, remove the uSD card and put it back into your computer. * You should see a file called BeagleBoneBlack-eMMC-image-X.img, where X is a set of random numbers. Save off this file to use for restoring your image later. Because the date won't be set on your board, you might want to adjust the date on the file to remember when you made it. Delete the file if you want to make room for a new backup image. For storage on your computer, these images will typically compress very well, so use your favorite compression tool. To restore the file, make sure there is a valid BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit autorun.sh with your favorite text editor to contain the following: #!/bin/sh echo timer /sys/class/leds/beaglebone\:green\:usr0/trigger dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M sync echo default-on /sys/class/leds/beaglebone\:green\:usr0/trigger *NOTE*: Be certain to replace the 'X' above with the proper name of your image file. This image was built using Buildroot. The sources are at https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. Download via https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or clone the git repo. It is a small fork from git://git.buildroot.net/buildroot tag e9f6011617528646768e69203e85fe64364b7efd. To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'. Output files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in the output/images subdirectory. The following files were created manually. uEnv.txt: bootpart=0:1 bootdir= fdtaddr=0x81FF optargs=quiet
Re: [beagleboard] Using BB to measure power
mmm, do you know if there are any publications of the results of these cracks? They might provide me some ideas. For instance, http://lowpowerlab.com/blog/2012/12/28/wattmote-moteino-based-wireless-killawatt/killawatt-moteino-internal-connections/ and there are others, just google internal connections to kill-a-watt -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Variable processor speeds?
On 13-10-31 02:02 PM, pyroartist...@gmail.com wrote: In one of the posts here someone mentioned 200, 400, 800 and 1Ghz speeds for the processor. I see nothing about this in the BBB manual PDF. How is this controlled? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. ~# cpufreq-set At least one parameter out of -f/--freq, -d/--min, -u/--max, and -g/--governor must be passed ~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: generic_cpu0 CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 300 us. hardware limits: 300 MHz - 1000 MHz available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 300 MHz and 1000 MHz. The governor performance may decide which speed to use within this range. current CPU frequency is 1000 MHz (asserted by call to hardware). cpufreq stats: 300 MHz:nan%, 600 MHz:nan%, 800 MHz:nan%, 1000 MHz:nan% -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] BeagleBonewhite Power via Expansion header
I was trying to power the beaglebone white with the expansion header - connecting 12 in P9 to GND and 5 and 6 in P9 to 5V. All was fine till I connected the USB cable to the Beaglebone and it will no longer work. It died instantly and without any smoke/pop sound. What could be the reason. Is it a bad idea to power it via expansion header? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] NAND flash with BeagleBone variant
On 10/29/2013 09:50 AM, Ezequiel García wrote: Oh, sorry then. I thought you were related in some way to Circuitco. Anyway, looking at the NAND cape wiki page, there's a sign saying there's no software support for the cape. Odd as it sound, maybe the cape is really not usable :-( It seems that the issue is like this: 1) Current U-Boot from git supports (8Bit-)NAND. It can be used by U-Boot (!) by means of the nand ... commands. You can write images to NAND and read them back. 2) (8Bit-)NAND also works with the beaglebone kernel (3.8.13) when the device tree contains a correct gpmc node with ti,nand-ecc-opt = bch8; or ti,nand-ecc-opt = sw; Both seem to work. SO you can use UBI on your NAND. 3) But the NAND implementation - probably the ECC schemes - from recent U-Boot and the beagleboard repository are incompatible. This is the same even with the mentioned U-Boot NAND patch by Pekon Gupta applied. But I cannot tell which side (u-Boot or Linux) is right. Perhaps its a kernel 3.8 issue. I will try a more recent kernel, but perhaps anybody know where it comes from. Matthias In case anybody has this same issue, there are some patches floating around from Pekon Gupta to support x16 NAND in U-Boot, but they are still work-in-progress and could need some tweaking: http://lists.denx.de/pipermail/u-boot/2013-September/162294.html Thanks! Ezequiel On 28 October 2013 21:36, Gerald Coley ger...@beagleboard.org wrote: Ahh, well. We don't sell capes. That is done by third parties. BB.org has no capes. They are made by various manufacturers. I suggest you contact the manufacturer of that board direct. There may also be others that have used that cape that can also help you out. The TI forum won't help on the capes. again. I suggest you contact the manufacturer of that board direct. Gerald On Mon, Oct 28, 2013 at 4:58 PM, Ezequiel García ezequ...@vanguardiasur.com.ar wrote: Ah, OK. I thought you provided some minimal software to use the capes you sold. Was I wrong? In that case, sorry for bothering. I'll ask in the TI forum, although they don't seem the most knowledgeable engineers out there. Let's cross fingers and hope that I get lucky. Right now, I have this cape connected, but it's completely unusable to me, without the capability of booting to it :-( Thanks for the prompt answer! On 28 October 2013 14:14, Gerald Coley ger...@beagleboard.org wrote: Nope. That is a SW question. You might try the TI e2e forum, I know that support for it is inside TI. http://e2e.ti.com/support/arm/default.aspx Gerald On Mon, Oct 28, 2013 at 12:07 PM, ezequ...@vanguardiasur.com.ar wrote: Hi Gerald, I have the 16-bit NAND cape connected to me Beaglebone Black board in my desk. Using mainline U-Boot and kernel the NAND is detected (had to modify the muxing for 16-bit) but the nand write/read doesn't work. I get ECC uncorrectable on every nand read. Can you point me to some custom U-Boot tree where this is supported? I need to boot from NAND, so I need to put both SPL and U-Boot in the flash, but for now, I would like to at least flash the kernel to NAND and boot it from SD. Sorry to ask you directly, but I've been googling all past week for this issue, and I found nothing but to hack U-Boot myself! Regards and thanks in advance! Ezequiel El martes, 28 de agosto de 2012 21:13:07 UTC-3, Gerald escribió: No idea at all. We should have support for NAND in the BeagleBone release in about 4-6 weeks. In the mena time you best bet may be to get help on the TI forums to get access to the unofficial things that is currently going on. I do know that you will need changes to UBoot for NAND to work in linux in general. Gerald On Tue, Aug 28, 2012 at 7:08 PM, Stan Hu sta...@gmail.com wrote: Gerald, I got the onboard NAND flash working on U-Boot by disabling the MMC1 pin mux (the BeagleBone daughter card settings was reconfiguring the pad for GPMC_CSN0), but now Linux still doesn't seem to recognize the NAND chip. The manufacturer and chip ID return 0 right now. I checked that the pin mux settings are right in Linux. Looking at the scope, I think the chip select line is being toggled way too fast--it doesn't remain active low for long enough. Do you have any idea why this might be happening? On Tue, Aug 28, 2012 at 12:18 PM, Gerald Coley ger...@beagleboard.org wrote: We have a memory cape in house where we have 16b NAND working. I don't believe anything has been done with 8b. Gerald On Tue, Aug 28, 2012 at 2:13 PM, Stan Hu sta...@gmail.com wrote: I've got an 8-bit Micron MT29 NAND flash hooked up to the GPMC lines on a custom board derived from the BeagleBone and AM335x EVM. The NAND flash is hooked up to the GPMC lines identically to the AM335X EVM. U-Boot does not see the NAND flash for some reason. When I probe the WE and RE GPMC lines, I can see that the processor is
Re: [beagleboard] Re: Help with I2C on BBB in Debian
Thanks Maycon, That did the trick. Josh On Sun, Oct 27, 2013 at 8:53 AM, may...@magsoft.com.br wrote: Sory, please read... echo BB-I2C1 /sys/devices/bone_capemgr.??**??/slots Maycon On Sunday, October 27, 2013 12:50:32 PM UTC-2, may...@magsoft.com.brwrote: The Debian maps the i2c-0 to i2c0, and i2c-1 to i2c2, if you use echo BB-I2C2 /sys/devices/bone_capemgr.??**??/slots this enables i2c-2 maped to i2c1 on BBB in all cases the bus is configured with pull-ups, be careful with capacitance in line, long wires can add... i2c0 - internal i2c1 - pins 17-18 i2c2 - pins 19-20 Maycon On Saturday, October 26, 2013 4:38:27 PM UTC-2, Joshua Datko wrote: In the default Debian imagine, can any I2C bus be used from the P9 expansion header, without rebuilding the kernel? If so, which pins? (19 20, or 17 18?) When I run i2cdetect, I have two I2C buses, but I'm not sure which buses they map to on the BBB: i2c-0 i2c OMAP I2C adapter I2C adapter i2c-1 i2c OMAP I2C adapter I2C adapter Assuming I have a working I2C slave device, if I wire SDA to P9_20, SCL to P9_19, 3.3V power to P9_3, GND to P9_1, would one expect the device to show up on the i2c bus (the breakout board already has a pull-up resistor)? Josh -- 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/7reYt7Tmdjs/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Extracting eMMC contents using FAT formatted card
On Thursday, October 31, 2013 2:10:24 PM UTC-7, Jason Kridner wrote: - I followed your instructions (8GB µSD, FAT32 formatted) o If I press no button, the BBB boots on the eMMC This tells me that the bootloader you flashed onto the eMMC doesn't properly work with the uEnv.txt put onto the uSD card as part of following my instructions. I've no idea what bootloader the Debian image flashed to my eMMC (as a lot of people, I know nothing about Angström, and the first thing I did was to put Debian into my device, a much more common distrib, because I just want a cheap linux server to do some stuff at home). I'm kind of a noob using the BBB, sorry about that (I'm using a RPi for quite a while now, but I'm not considering myself as a power user -- despite managing some linux servers and having a master in embedded systems, I'm a web developer and I love high level programming). What I mean but all that is: something that could look obvious to you isn't for 95% of the people reading your guides, the 95% that aren't doing BBB related stuff for a living. But well, if I could boot onto the µSD using the boot button that would be ever more fine to me (I could leave the µSD into the BBB and boot on it when I want to backup my distrib). o If I press the “boot” button while plugging the power, the BBB just doesn’t boot (stays in a “powered off” state, with only the LED near the power plug on) This means that the uSD card FAT partition isn't marked as bootable. You can do that with 'fdisk' from your BeagleBone running Debian in all likelihood. Huge thanks for the step by step :) I think it would be way easier for everybody (including you ^^) if you made a .img image of the card (maybe in different sizes?) -- this would eliminate any possible mistake in the process. As most people, I'm using Windows and formatting a card doesn't mark the partition as bootable, so following your base instructions just doesn't work. I've found that my µSD is in /dev/mmcblk0 (I tried /dev/mmcblk1 at first and it bricked my BBB, I had to flash it again -- not a big deal) root@arm:~# cat /proc/partitions major minor #blocks name 17907822336 mmcblk0 17917818240 mmcblk0p1 17981875968 mmcblk1 1799 72261 mmcblk1p1 179 101799280 mmcblk1p2 179 24 1024 mmcblk1boot1 179 16 1024 mmcblk1boot0 The card is now bootable: root@arm:~# fdisk /dev/mmcblk0 Command (m for help): p Disk /dev/mmcblk0: 8010 MB, 8010072064 bytes 214 heads, 8 sectors/track, 9138 cylinders, total 15644672 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/mmcblk0p1 *819215644671 7818240b W95 FAT32 It was still booting to the eMMC by default, so I powered it on while having the boot button but -- no matter if I pressed the button for 4 seconds or until LEDs are on - it somewhat booted, but the USR0 was directly steady on. So I tried to reboot it (using the reset button) and it's now correctly writing the image to the SD. I don't really know how the boot button works, but considering this behaviour I would say it disables the eMMC while pressed, isn't? So my create image process is: power the BBB on with the boot button pressed for like 5s, and once the USR0 is steady on, press the reset button and then wait 10min for USR0 to be steady on again. Again, thank you a lot for your help. I really like the BBB, the only think I don't like is how difficult it is to make an image of the eMMC and your method is a huge step into making it simple. root@beaglebone:~# fdisk /dev/mmcblk1 Welcome to fdisk (util-linux 2.23.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): a Partition number (1,2, default 2): 1 Command (m for help): p Disk /dev/mmcblk1: 3904 MB, 3904897024 bytes, 7626752 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x Device Boot Start End Blocks Id System /dev/mmcblk1p1 *2048 133119 65536e W95 FAT16 (LBA) /dev/mmcblk1p2 133120 7626751 3746816 83 Linux The BBB is brand new, so maybe they changed something. Who's they? It is possible CircuitCo switched the bootloader image on the eMMC, but it sounds more like you did that above. Yeah, I thought maybe CircuitCo changed something in the bootloading or something, but it definitively doesn't seems to be the issue here. -- For more options, visit http://beagleboard.org/discuss
Re: [beagleboard] BeagleBonewhite Power via Expansion header
That should have worked. The only thing I can think of is that there may be a grounding issue where the ground for the PC is different than the ground of the power supply you are using for the 5V input on pins 5 and 6. Make sure they are the same. Without looking at your schematic of how it is hooked up, it is really hard to say what happened. Gerald On Thu, Oct 31, 2013 at 4:50 PM, Aravind V aravind.v...@gmail.com wrote: I was trying to power the beaglebone white with the expansion header - connecting 12 in P9 to GND and 5 and 6 in P9 to 5V. All was fine till I connected the USB cable to the Beaglebone and it will no longer work. It died instantly and without any smoke/pop sound. What could be the reason. Is it a bad idea to power it via expansion header? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] announce new documentation resource
Hi all I've fought B3/Angstrom into submission over the past few weeks, and have been writing down everything I did. Perhaps parts of it will be of some use to some of you: www.cowsheep.net/articles?series=B3W I've got several embedded interfaces up and running too (UART, I2C, GPIO, AIN) and am currently pulling my notes together into articles for these too. I'll post them when they're ready. Best o' luck! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: 3.12-rc4: kernel testing time...
I use kernel source from https://github.com/RobertCNelson/linux-dev followed default build steps ./build_kernel.sh ./tools/install_kernel.sh but my beaglebone network and usb not working, i use ubuntu 'raring', and bone hardware version A6a. On Friday, October 11, 2013 8:09:24 AM UTC+8, RobertCNelson wrote: So here is the deal; 3.8 is old, and 3.12-rc4 is newer/better/etc... Functionally, it seems ready in my small 5 board sample size. 3 of which have been running 24/7 @ 100% since rc3.. Anywho, we need community testing. (Here's looking at you!) Kernel Branch: https://github.com/beagleboard/linux/tree/3.12 Kernel src Script: https://github.com/beagleboard/kernel/tree/3.12 Regression/testing: Are we missing any kernel config settings from 3.8 that you used? Does your Cape still work? Other thoughts... Some users will build/install these from src, however anyone interested in a quick test-me.sh* script which will install the new kernel on a daily/weekly basis? * script currently doesn't exist, but after a few beers it might... 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/groups/opt_out.
[beagleboard] Re: 3.12-rc4: kernel testing time...
sorry, when i checkout 3.12-rc7-bone8 branch rebuild,it works well. On Friday, November 1, 2013 10:14:54 AM UTC+8, Chong Yang wrote: I use kernel source from https://github.com/RobertCNelson/linux-dev followed default build steps ./build_kernel.sh ./tools/install_kernel.sh but my beaglebone network and usb not working, i use ubuntu 'raring', and bone hardware version A6a. On Friday, October 11, 2013 8:09:24 AM UTC+8, RobertCNelson wrote: So here is the deal; 3.8 is old, and 3.12-rc4 is newer/better/etc... Functionally, it seems ready in my small 5 board sample size. 3 of which have been running 24/7 @ 100% since rc3.. Anywho, we need community testing. (Here's looking at you!) Kernel Branch: https://github.com/beagleboard/linux/tree/3.12 Kernel src Script: https://github.com/beagleboard/kernel/tree/3.12 Regression/testing: Are we missing any kernel config settings from 3.8 that you used? Does your Cape still work? Other thoughts... Some users will build/install these from src, however anyone interested in a quick test-me.sh* script which will install the new kernel on a daily/weekly basis? * script currently doesn't exist, but after a few beers it might... 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/groups/opt_out.
Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver
So I've been struggling with I2C. Somebody on this list gave me the tip to do: echo BB-I2C1 /sys/devices/bone_capemgr.??**??/slots which enables the third I2C bus and my device then was visible via i2cdetect -y -r 1 on pins P9_19 and P9_20. Although, after doing that, you'll have an i2c1 and a i2c2 bus, so might want to check both. But, I'm not quite sure why this works :) In my case, I don't think there is device tree entry for the device I'm using, so I was planning on interacting with it over raw I2C. Hope this helps, Josh On Thursday, October 31, 2013 2:32:46 PM UTC-6, Jason Kridner wrote: On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner jkri...@beagleboard.orgjavascript: wrote: On Thu, Oct 17, 2013 at 6:12 PM, clarkbr...@gmail.com javascript: wrote: AIW: I went back thru the adafruit library and didn't find anything specific on I2C, although it is listed as a topic. I have been looking at their github adafruit-beaglebone-io-python library. I also found and looked thru PyBBIO. Even tho I'm not using Python, I can see the access mechanisms that they use. I can use the MPU6050 device ok enough just reading via /dev/i2c/i2c-x, but that is too slow. I'm trying to figure out how to invoke and use the inv-mpu6050 driver and adafruit doesn't use that. Thx -- Clark On Thursday, October 17, 2013 9:47:44 AM UTC-7, AIW wrote: Some good info on I2C tools at http://www.acmesystems.it/i2c. Python and the adafruit BBIO I2C library makes it very easy to use I2C on Beaglebone Black as well. Python import smbus is fairly easy to use too. Some examples of use is available in the code I provide for my radio project herewww.aiwindustries.com. Not trying to sell the product, but I know that the I2C function was giving me some issues so I'm just trying to help the community. Python code is available to download and look at usage so feel free. On Tuesday, October 15, 2013 5:02:59 PM UTC-5, clarkbr...@gmail.comwrote: We are using the Invensense MPU6050 IMU on I2C with Beaglebone Black (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c but the read speed is disappointingly slow. We only read the 3x gyros and 3x accels (each one byte at a time plus the 2 byte temperature reading) and it takes ~2msecs. My estimate of the I2C bus cycles for a block read suggests this should take ~160 bus cycles or .38msec on a 400MHz I2C bus. You are running at 400kHz, not 400MHz, right? I2C doesn't do 400MHz. The distribution includes the Invensense driver inv-mpu6050.ko but there is no indication that reading through /dev/i2c invokes it. This is a very popular IMU and Invensense widely distributes the driver over many Linux platforms. The driver source includes “successful installation will create two directories under /sys/bus/iio/devices” and lists the files there (aka functions). I can never get these to show up. I can “insmod /lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050/inv-mpu6050.ko” and “echo inv-mpu6050 0x68 /sys/class/i2c-adapter/i2c-1/new_device”. This causes a new directory named 1-0068 to show in /sys/class/i2c-adapter/i2c-1with entries like name and modalias but no functions. It never shows in /sys/bus/iio/devices. I don't have an MPU6050, but I just ordered a couple on express overnight from Sparkfun. I bought https://www.sparkfun.com/products/11028 and played with it briefly before being distracted and again today, but I don't understand why I'm not able to get it to reply to me. I have the following connections: VCC: P9_4 (VDD_3V3) GNC: P9_1 (GND) INT: P9_11 (GPIO) FSYNC: - SCL: P9_19 (I2C2_SCL) SDA: P9_20 (I2C2_SDA) VIO: P9_3 (VDD_3V3) CLK: - ASCL: - ASDA: - I then perform: root@beaglebone:~# i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Very confused why it doesn't show up. Since you have it responding to you, how do you have it wired? Here's the behavior I'm seeing without the board connected: root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# ls inv-mpu6050.ko root@beaglebone:/lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050# dmesg | tail -1 [ 2992.799594] i2c i2c-1: new_device: Instantiated device inv-mpu6050 at 0x68
Re: [beagleboard] Re: I2C and Invensense MPU6050 Driver
Nevemind, that may be unrelated. I just rebooted and my device enumerated fine. I think what's confusing (me) is the I2C2 by the SRM (P9_19/20) shoes up as I2C1... some output: ebian@arm:~$ ls -l /sys/bus/i2c/devices/i2c-* lrwxrwxrwx 1 root root 0 Nov 1 04:02 /sys/bus/i2c/devices/i2c-0 - ../../../devices/ocp.2/44e0b000.i2c/i2c-0 lrwxrwxrwx 1 root root 0 Nov 1 04:02 /sys/bus/i2c/devices/i2c-1 - ../../../devices/ocp.2/4819c000.i2c/i2c-1 debian@arm:~$ su Password: root@arm:/home/debian# i2cdetect -r 1 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-1 using read byte commands. I will probe address range 0x03-0x77. Continue? [Y/n] Y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- -- 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- On Thursday, October 31, 2013 9:57:08 PM UTC-6, Joshua Datko wrote: So I've been struggling with I2C. Somebody on this list gave me the tip to do: echo BB-I2C1 /sys/devices/bone_capemgr.??**??/slots which enables the third I2C bus and my device then was visible via i2cdetect -y -r 1 on pins P9_19 and P9_20. Although, after doing that, you'll have an i2c1 and a i2c2 bus, so might want to check both. But, I'm not quite sure why this works :) In my case, I don't think there is device tree entry for the device I'm using, so I was planning on interacting with it over raw I2C. Hope this helps, Josh On Thursday, October 31, 2013 2:32:46 PM UTC-6, Jason Kridner wrote: On Tue, Oct 29, 2013 at 2:19 PM, Jason Kridner jkri...@beagleboard.org wrote: On Thu, Oct 17, 2013 at 6:12 PM, clarkbr...@gmail.com wrote: AIW: I went back thru the adafruit library and didn't find anything specific on I2C, although it is listed as a topic. I have been looking at their github adafruit-beaglebone-io-python library. I also found and looked thru PyBBIO. Even tho I'm not using Python, I can see the access mechanisms that they use. I can use the MPU6050 device ok enough just reading via /dev/i2c/i2c-x, but that is too slow. I'm trying to figure out how to invoke and use the inv-mpu6050 driver and adafruit doesn't use that. Thx -- Clark On Thursday, October 17, 2013 9:47:44 AM UTC-7, AIW wrote: Some good info on I2C tools at http://www.acmesystems.it/i2c. Python and the adafruit BBIO I2C library makes it very easy to use I2C on Beaglebone Black as well. Python import smbus is fairly easy to use too. Some examples of use is available in the code I provide for my radio project herewww.aiwindustries.com. Not trying to sell the product, but I know that the I2C function was giving me some issues so I'm just trying to help the community. Python code is available to download and look at usage so feel free. On Tuesday, October 15, 2013 5:02:59 PM UTC-5, clarkbr...@gmail.comwrote: We are using the Invensense MPU6050 IMU on I2C with Beaglebone Black (Angstrom 3.8.13). We can use I2C-tools and file I/O thru /dev/i2c but the read speed is disappointingly slow. We only read the 3x gyros and 3x accels (each one byte at a time plus the 2 byte temperature reading) and it takes ~2msecs. My estimate of the I2C bus cycles for a block read suggests this should take ~160 bus cycles or .38msec on a 400MHz I2C bus. You are running at 400kHz, not 400MHz, right? I2C doesn't do 400MHz. The distribution includes the Invensense driver inv-mpu6050.ko but there is no indication that reading through /dev/i2c invokes it. This is a very popular IMU and Invensense widely distributes the driver over many Linux platforms. The driver source includes “successful installation will create two directories under /sys/bus/iio/devices” and lists the files there (aka functions). I can never get these to show up. I can “insmod /lib/modules/3.8.13/kernel/drivers/iio/imu/inv_mpu6050/inv-mpu6050.ko” and “echo inv-mpu6050 0x68 /sys/class/i2c-adapter/i2c-1/new_device”. This causes a new directory named 1-0068 to show in /sys/class/i2c-adapter/i2c-1with entries like name and modalias but no functions. It never shows in /sys/bus/iio/devices. I don't have an MPU6050, but I just ordered a couple on express overnight from Sparkfun. I bought https://www.sparkfun.com/products/11028 and played with it briefly before being distracted and again today, but I don't understand why I'm not able to get it to reply to me. I have the following connections: VCC: P9_4
