Re: [beagleboard] Driving servos with face position detected from OpenCV?
How about using node.js OpenCV bindings such as; https://github.com/peterbraden/node-opencv Though I'm not sure on the OpenCV functionalities implemented in this package. On Thu, Mar 27, 2014 at 2:55 PM, Shanshan Zhou shshan...@gmail.com wrote: Hey guys! I'm just getting started with my BBB, and the possibility to integrate camera vision in robotic project is what I'm most looking forward to get from BBB. Appologise first, I'm not very experienced with Linux and c++ at all -- and I guess this is why I found it so hard to get started with OpenCV for BBB, even though there are a lot of examples online already. Ok, let me try my best to explain the issue. According to beaglebone.org, we can use BoneScript to control PWM pins allowing us to drive servos. On the other hand, we can use OpenCV c++ to detect face positions. The question is, what should I do if I want to drive the servos based on the face detected with OpenCV? Does that mean I have to write the entire application in c++? Or is there a way to just pass data from the c++ program with OpenCV (only the face position) into a servo driving application written in BoneScript? I guess my options are: 1. c++ face detect position with OpenCV + BoneScript application driving servo. 2. Python: OpenCV in python + Python IO BBIO + driving servo with py application 3. c++: c++ OpenCV, c++ drive servo I have NO experience with c++, little bit experience with python, ok with Javascript and java? What do you guys think? Which options are more feasible? Any better suggestions? Sorry I'm not a computer scientist so I apologies if anything I'm saying sounds silly or doesn't make sense. Thank you guys in advance! Shanshan -- 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] Mono on last debian
Hi, any hint how to install mono in the last debian image? (I need this because a little touchscreen, very jittery in angstrom) I get: root@beaglebone:/# apt-get install mono-runtime Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mono-runtime:armel : Depends: mono-gac:armel (= 2.10.8.1-8) but it is not installable Recommends: binfmt-support:armel (= 1.1.2) E: Unable to correct problems, you have held broken packages. And something similar for mono-complete. Thanks! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Driving servos with face position detected from OpenCV?
Hi Sunjin Thank you! This looks really promising, I will give it a go and let you guys know how it goes. On Thursday, 27 March 2014 19:38:19 UTC+13, Sungjin Chun wrote: How about using node.js OpenCV bindings such as; https://github.com/peterbraden/node-opencv Though I'm not sure on the OpenCV functionalities implemented in this package. On Thu, Mar 27, 2014 at 2:55 PM, Shanshan Zhou shsh...@gmail.comjavascript: wrote: Hey guys! I'm just getting started with my BBB, and the possibility to integrate camera vision in robotic project is what I'm most looking forward to get from BBB. Appologise first, I'm not very experienced with Linux and c++ at all -- and I guess this is why I found it so hard to get started with OpenCV for BBB, even though there are a lot of examples online already. Ok, let me try my best to explain the issue. According to beaglebone.org, we can use BoneScript to control PWM pins allowing us to drive servos. On the other hand, we can use OpenCV c++ to detect face positions. The question is, what should I do if I want to drive the servos based on the face detected with OpenCV? Does that mean I have to write the entire application in c++? Or is there a way to just pass data from the c++ program with OpenCV (only the face position) into a servo driving application written in BoneScript? I guess my options are: 1. c++ face detect position with OpenCV + BoneScript application driving servo. 2. Python: OpenCV in python + Python IO BBIO + driving servo with py application 3. c++: c++ OpenCV, c++ drive servo I have NO experience with c++, little bit experience with python, ok with Javascript and java? What do you guys think? Which options are more feasible? Any better suggestions? Sorry I'm not a computer scientist so I apologies if anything I'm saying sounds silly or doesn't make sense. Thank you guys in advance! Shanshan -- 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: Controlling power to USB connections
https://groups.google.com/forum/#!searchin/beagleboard/USB1_OC https://groups.google.com/forum/#!searchin/beagleboard/USB1_OC https://groups.google.com/forum/#!searchin/beagleboard/turn$20off$20USB$20power https://groups.google.com/forum/#!searchin/beagleboard/USB$20power$20control On Wednesday, March 26, 2014 2:15:27 AM UTC-10, rchrd...@gmail.com wrote: Pity you didn't search this group to see if someone has already done it before. Author: AndrewTaneGlen Date: Jan 17 Subject: Disabling/Enabling USB Host Power And thanks to Andrew for his helpful contribution. Regards ... On Wednesday, March 26, 2014 8:36:02 PM UTC+11, Patrick Walters wrote: Do you happen to know if this accessible from the CLI? I tried looking at :/sys/bus/usb/devices/1-0:1.0/port1/power and thought maybe I could edit the control file, but that didn't seem to work. 6.11 USB Host The board is equipped with a single USB host interface accessible from a single USB Type A female connector. Figure 48 is the design of the USB Host circuitry. 6.11.1 Power Switch U8 is a switch that allows the power to the connector to be turned on or off by the processor. It also has an over current detection that can alert the processor if the current gets too high via the USB1_OC signal. The power is controlled by the USB1_DRVBUS signal from the processor On Monday, March 24, 2014 3:19:41 AM UTC-10, mickeyf wrote: I may have spoken hastily. See section 6.11.1 in the SRM. On Sunday, March 23, 2014 12:37:12 AM UTC-7, Patrick Walters wrote: uname -a Linux beaglebone 3.8.13 #1 SMP Thu Sep 12 10:27:06 CEST 2013 armv7l GNU/Linux Is it possible to control the power to the USB port on the board or a HUB from the CLI? My scenario is that I'd like to be able to turn something on\off that is powered from the USB connection. Thanks, -p -- 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] First one, then two, then three....
I bought a BBB about 3 weeks ago. Was impressed enough that I bought two more. I have a few Rpis is use around the house as well so I have a little experience with SBCs Anyway. all three BBB has been flawless. No problems at all. I did discover one thing. Of all the Linux distros out there, I like Ubuntu the best. I found that Ubuntu does not suffer as badly from creeping featurism or from a lack of essential packages. I tried Angstrom first. It got flushed. Then I tried Arch and Debian. Didn't like Arch at all. Debian was tolerable. Lastly I tried Ubuntu. Ubuntu seems to be the easiest to get configured and running. I was porting code in under an hour. I don't use a GUI so Ubuntu might not be for everyone. The really nice part about the BBB is the fact that it boots without a SD card. That leaves the SD card slot available for extra file storage. SInce I do some software development as well as create various appliance-like things, the added hot-plugable storage is wonderful. The only thing I wish for is the ability to change I2C bus speeds on the fly. All in all, I am very happy with the BBB. Well done! Richard . -- 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] gpio trouble
Well for one, some of the other gpio pins such as pin 13 on P8 won't operate properly. When I try to work with it over cloud9, it doesn't respond to any changes. For instance in the a simple blink sketch, if the setInterval is (blink, 1000) and I change it to (blink, 100), it continues blinking at once per second. On Wednesday, March 26, 2014 10:25:26 PM UTC-4, Gerald wrote: The drive current on the GPIO pins is 6 mA. What other things are not quite right? Gerald On Wed, Mar 26, 2014 at 9:10 PM, Jaden Gani jaden...@gmail.comjavascript: wrote: Hello everyone! I recently received my beaglebone black in the mail. Prior to ordering it, I had done days of research and decided that it was time that I bought one. When I got it in the mail, I eagerly opened it and got started. I used it as a standalone pc, ssh-ed into it, and worked with it in cloud9. However I couldn't seem to get pins 1-4 or 5 working smoothly. When I had an LED hooked up to one of them, it seemed to be blinking with one of the user LED's (this changed sometimes. One time it was blinking with user3 and another time with user0 etc.). Mostly when I connect an LED to one of those pins it just lights dimly and ignores anything that I say to it on the command line (e.g. echo 1 /sys/class/gpio/gpio38/value). There are a few other things that i noticed that weren't quite right. I am wondering if I have a defective board or if I am doing something wrong. Any help would be great. 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] eMMC data corruption due to power removal?
On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. How do routers handle this issue? they save the settings on different devices? Routers save a very small amount of setup data, and either have a very small window when they are writing updates to the filesystem, or in some cases can store the configuration in EEPROM. I have a SQLite db around 1-2M and data will be written to them. Would like to have some easy and quick solution to make it absolutely stable. I don't think easy and quick go together with absolutely stable in this context. You're looking at solutions like adding a backup battery, migrating your SQLite db to a different storage device, or other solutions that do not fit the easy and quick description. I think about the simplest thing you can do is add a uSD card and separate the OS from the data storage. This gets you around the problem of corrupting the OS when writing to the data, but you can still run into problems because the uSD card need to have specific boot files present or the BBB won't boot. That problem can be fixed by updating the u-boot configuration on the eMMC so it ignores the uSD card and always boots from eMMC. You'll still need to be able to deal with data corruption in your db files, but that's a solvable software problem if the system reliably boots. -- Charles Steinkuehler char...@steinkuehler.net -- 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 trouble
What Gerald is saying is that in general you should not expect to drive an LED directly - you will want to drive a transistor which can then supply perhaps 20 ma or more to your LED and at the correct voltage. Perhaps you are already doing this, but you didn't say. I don't know anything about the Cloud 9 interface, but if is blinking by just using the shell ( echo 1 pin whatever) with sleep, sleep may not recognize any increment of less than integral seconds. I'd look into that. Maybe see if it works for longer intervals like 3 or 5 seconds... Speaking strictly for me, when something doesn't work, 99.9% of the time it's something I did wrong, not the hardware etc. -- 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] eMMC data corruption due to power removal?
Thanks for your reply. On Thu, Mar 27, 2014 at 8:41 PM, Charles Steinkuehler char...@steinkuehler.net wrote: On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. What I mean is you can take out battery at back very easily as well. How do routers handle this issue? they save the settings on different devices? Routers save a very small amount of setup data, and either have a very small window when they are writing updates to the filesystem, or in some cases can store the configuration in EEPROM. I have a SQLite db around 1-2M and data will be written to them. Would like to have some easy and quick solution to make it absolutely stable. I don't think easy and quick go together with absolutely stable in this context. You're looking at solutions like adding a backup battery, migrating your SQLite db to a different storage device, or other solutions that do not fit the easy and quick description. I think about the simplest thing you can do is add a uSD card and separate the OS from the data storage. This gets you around the problem of corrupting the OS when writing to the data, but you can still run into problems because the uSD card need to have specific boot files present or the BBB won't boot. That problem can be fixed by updating the u-boot configuration on the eMMC so it ignores the uSD card and always boots from eMMC. You'll still need to be able to deal with data corruption in your db files, but that's a solvable software problem if the system reliably boots. I have already minimized data writes. I hope by next version I will write stuff to eeprom. -- Charles Steinkuehler char...@steinkuehler.net -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] eMMC data corruption due to power removal?
When there are very small time window to update the content in flash. do you choose to: 1. initially mount as ro, remount as rw, write your changes and remount back to ro? OR 2. just mount as rw to boot up? On Thu, Mar 27, 2014 at 8:47 PM, Yiling Cao yiling@gmail.com wrote: Thanks for your reply. On Thu, Mar 27, 2014 at 8:41 PM, Charles Steinkuehler char...@steinkuehler.net wrote: On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. What I mean is you can take out battery at back very easily as well. How do routers handle this issue? they save the settings on different devices? Routers save a very small amount of setup data, and either have a very small window when they are writing updates to the filesystem, or in some cases can store the configuration in EEPROM. I have a SQLite db around 1-2M and data will be written to them. Would like to have some easy and quick solution to make it absolutely stable. I don't think easy and quick go together with absolutely stable in this context. You're looking at solutions like adding a backup battery, migrating your SQLite db to a different storage device, or other solutions that do not fit the easy and quick description. I think about the simplest thing you can do is add a uSD card and separate the OS from the data storage. This gets you around the problem of corrupting the OS when writing to the data, but you can still run into problems because the uSD card need to have specific boot files present or the BBB won't boot. That problem can be fixed by updating the u-boot configuration on the eMMC so it ignores the uSD card and always boots from eMMC. You'll still need to be able to deal with data corruption in your db files, but that's a solvable software problem if the system reliably boots. I have already minimized data writes. I hope by next version I will write stuff to eeprom. -- Charles Steinkuehler char...@steinkuehler.net -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: microSD card reader snapped off one side, bad solder joints?
I ran into the same problem with a BBB I recently purchased. Apparently the force from the sd contacts can lift the leads off the board after sitting for a few months. I re-soldered the socket leads on the side along with the grounds but still had a reliability problem with the card detect line. The demo software would boot from the sd but later not recognize the card. After several days of debugging the software, I finally traced it down to the sd socket lead on the end of the connector also disconnected. The card detect lead location isn't as obvious as the 4 side leads, it doesn't stick out so it can be challenging to re-solder. I thought I would pass this along if others are struggling with similar SD card detect issues. On Tuesday, February 11, 2014 4:24:55 PM UTC-5, Gerald wrote: Yes, the issue is not that USB connector. Hot plug has been talked about for a very long time. If adding an extra drop solder would fix that, I would certainly make that happen. Gerald On Tue, Feb 11, 2014 at 3:23 PM, Tony DiCola to...@tonydicola.comjavascript: wrote: Looks like the USB issue is just this software problem: https://groups.google.com/forum/#!topic/beagleboard/uWMNdBv_aPg Booting up with the device in the USB host port seemed to work. Yikes, that's really a nasty bug that hotplug doesn't work. On Tuesday, February 11, 2014 12:59:52 PM UTC-8, Tony DiCola wrote: The card was just being inserted like normal--no excessive force. Like I said even before it broke the SD reader wasn't working. When I held the boot button down and applied power the Beaglebone never flashed any lights to show it go through booting (even after waiting 10+ seconds with the button held down). After fixing the solder joints on the SD reader the exact same SD card booted up just fine on the first try. Clearly there was something wrong with the joint before it broke. Also for what it's worth I'm noticing wonkiness with the USB connector which is near the SD card reader. When I plug devices like mice, etc. in and run lsusb I don't see any new USB devices. Going to try testing the USB connections with a multimeter to see if they're all connected. On Tuesday, February 11, 2014 12:39:00 PM UTC-8, rh_ wrote: On Tue, 11 Feb 2014 08:17:07 -0600 Gerald Coley ger...@beagleboard.org wrote: Takes a lot of force to rip a connector out of a solder pool that deep. Yeah, was thinking that myself, that looks like someone doesn't know how to use SD card slots. If you're applying that much force to rip that out and continue to apply the force then you need to understand that forcing anything mechanical almost always leads to breakage. -- 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/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/d/optout.
Re: [beagleboard] Re: gpio trouble
You might try the new Bonescript stuff in the latest image based on Debian.It my work better, but I can't say for sure. http://beagleboard.org/latest-images Gerald On Thu, Mar 27, 2014 at 7:46 AM, mickeyf mic...@thesweetoasis.com wrote: What Gerald is saying is that in general you should not expect to drive an LED directly - you will want to drive a transistor which can then supply perhaps 20 ma or more to your LED and at the correct voltage. Perhaps you are already doing this, but you didn't say. I don't know anything about the Cloud 9 interface, but if is blinking by just using the shell ( echo 1 pin whatever) with sleep, sleep may not recognize any increment of less than integral seconds. I'd look into that. Maybe see if it works for longer intervals like 3 or 5 seconds... Speaking strictly for me, when something doesn't work, 99.9% of the time it's something I did wrong, not the hardware etc. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] i2c via bonescript under Debian
On Wed, Mar 26, 2014 at 5:42 PM, Mark A. Yoder mark.a.yo...@gmail.com wrote:
I see the bonescript has some i2c methods. Are there any examples out there
that work under Debian on the Black Bone?
Here's one that works on BoneScript 0.2.4 on Debian, but happens to be
calling the I2C methods from a web page:
http://jsfiddle.net/jkridner/PGL92/ [1]
I had something similar for drawing a Flot graph using the
accelerometer, but not sure where I posted it.
Some more running-from-webpage examples:
http://jsfiddle.net/user/jkridner/fiddles/
[1] source
var canvas = document.getElementById(mysketch);
var p = new Processing(canvas, sketchProc);
function sketchProc(pjs) {
// Sketch global variables
var radius = 50.0;
var X, Y;
var nX, nY;
var delay = 16;
var brightness = 0;
var buttonStatus = 0;
var sliderStatus = 0;
var lastSliderValue = 0;
var BUTTON = 'P8_19';
var SLIDER = 'P9_36';
var port = '/dev/i2c-2'
var address = 0x1c;
// Get the BoneScript library and begin updating the canvas
setTargetAddress('192.168.7.2', {
initialized: run
});
function run() {
var b = require('bonescript');
b.pinMode(BUTTON, b.INPUT);
b.i2cOpen(port, address, {}, onI2C);
// Setup the Processing Canvas
pjs.setup = function () {
pjs.size(256, 256);
pjs.strokeWeight(10);
pjs.frameRate(15);
X = pjs.width / 2;
Y = pjs.height / 2;
nX = X;
nY = Y;
}
// Main draw loop
pjs.draw = function () {
// Calculate some fading values based on the frame count
radius = 50.0 + (15 - sliderStatus) * pjs.sin(pjs.frameCount / 4);
brightness = (radius - 40.0) / 20.0;
// Track circle to new destination
X += (nX - X) / delay;
Y += (nY - Y) / delay;
// Fill canvas grey
pjs.background(100);
// Set fill-color to blue or red, based on button status
if (buttonStatus) pjs.fill(200, 30, 20)
else pjs.fill(0, 121, 184);
// Set stroke-color white
pjs.stroke(255);
// Draw circle
pjs.ellipse(X, Y, radius, radius);
// Update physical values
readSlider();
}
function readSlider() {
b.analogRead(SLIDER, onAnalogRead);
}
// Handle data back from potentiometer
function onAnalogRead(x) {
if (!x.err (x.value = 0) (x.value = 1)) {
if (Math.abs(x.value - lastSliderValue) 0.05) {
lastSliderValue = x.value;
sliderStatus = parseInt(x.value * 10, 10);
}
}
// Fetch button status
b.digitalRead(BUTTON, onDigitalRead);
}
// Handle data back from button
function onDigitalRead(x) {
buttonStatus = (x.value == b.LOW) ? 1 : 0;
// Fetch accelerometer status
readAccel();
}
function onI2C(x) {
if (x.event == 'return') {
b.i2cWriteBytes(port, 0x2a, [0x00], onI2C_A);
}
}
function onI2C_A() {
b.i2cWriteBytes(port, 0x0e, [0x00], onI2C_B);
}
function onI2C_B() {
b.i2cWriteBytes(port, 0x2a, [0x01], pjs.setup);
}
// Fetch accelerometer status
function readAccel() {
b.i2cReadBytes(port, 1, 6, onReadBytes);
}
function onReadBytes(x) {
console.log(JSON.stringify(x));
if (x.event == 'callback') {
var gX = convertToG(x.res[0]);
var gY = convertToG(x.res[2]);
var gZ = convertToG(x.res[4]);
$('#X').html(gX);
$('#Y').html(gY);
$('#Z').html(gZ);
// Update heading of ball
nX = 128 - (gX / 2) * 256;
nY = (gY / 2) * 256 + 128;
//pjs.draw();
}
}
function convertToG(x) {
if (x = 128) x = -((x ^ 0xFF) + 1); // Get two's complement
x = x / 64; // Scale to G
x = x.toFixed(2); // Limit decimal places
return (x);
}
}
}
--Mark
--
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] Anyone successfully used squashfs as rootfs? or other ro fs?
Due to potential write caused SD/eMMC corruption issue we are facing, has anyone successfully used read-only fs? I have used AUFS under x86 with ubuntu, proven to be rock solid. But had no luck with ARM due to some OS+package issue. -- 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] Hard freeze (ethernet related?)
Hello, sorry if it already has been asked but I couldn't find anything like this so I'm gonna post my issue. I'm running ubuntu 13.04 with kernel 3.8.13-bone41 from emmc (powered by a 5V 2A power supply) and I am experiencing this: unplugging (and/or plugging in back) the ethernet cable can result in the board freezing and the USR2 led stuck on. I tried reading output from UART0 but there's nothing useful. How can I further debug this? Is it a known issue? Thanks, Riccardo -- 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: Here is the BeagleBone Debian (beta) image you want to test
I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz On Tuesday, March 25, 2014 1:21:04 AM UTC-4, mbba...@gmail.com wrote: I really like the 2014-03-19 image. It solves most of the problems I was having with Ubuntu and Angstrom. I am now able to connect wirelessly to WPA secured networks using Adafruit's dongle while tethered via a USB cable! This will make developing and debugging an autonomous robot that uses computer vision infinitely easier. I do have a few ideas for making the image slightly better. First, any chance you can install xrdp? This would allow my students to remote into the BeagleBone without having to access the Internet? Second, if I remember correctly it looks like the version designed to run from the SD card lists wlan0 within Wicd, but the eMMC version does not. IAny chance you can list wlan0 within Wicd for both versions? Third, I had to input the passphrase into Wicd, generate the PSK using wpa_passphrase, and then add the PSK into Wicd. Not sure why. Maybe I'm doing something wrong, but I suspect it's some sort of glitch with Wicd. -- 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] Hard freeze (ethernet related?)
Can you try it using the latest Debian image? http://beagleboard.org/latest-images Gerald On Thu, Mar 27, 2014 at 9:18 AM, Riccardo Bortolato rikyz...@gmail.comwrote: Hello, sorry if it already has been asked but I couldn't find anything like this so I'm gonna post my issue. I'm running ubuntu 13.04 with kernel 3.8.13-bone41 from emmc (powered by a 5V 2A power supply) and I am experiencing this: unplugging (and/or plugging in back) the ethernet cable can result in the board freezing and the USR2 led stuck on. I tried reading output from UART0 but there's nothing useful. How can I further debug this? Is it a known issue? Thanks, Riccardo -- 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 CascadeClassifier
I ran trainCascade on my Linux virtual machine and got an xml file, but when I try to run it on the Beaglebone I get the following error. Parsing Error : valid xml should start with ?xml? -- 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: Mono on last debian
Try: https://github.com/alexrp/mono/tree/armhf With build instructions here: https://github.com/alexrp/mono/tree/armhf We are using this with RCN's Ubuntu. Last built it many months ago though and are considering that version stable for our purposes, so can't speak to any recent changes or updates. On Wednesday, March 26, 2014 11:46:45 PM UTC-7, Erwin Ried wrote: Hi, any hint how to install mono in the last debian image? (I need this because a little touchscreen, very jittery in angstrom) I get: root@beaglebone:/# apt-get install mono-runtime Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mono-runtime:armel : Depends: mono-gac:armel (= 2.10.8.1-8) but it is not installable Recommends: binfmt-support:armel (= 1.1.2) E: Unable to correct problems, you have held broken packages. And something similar for mono-complete. Thanks! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test
On Thu, Mar 27, 2014 at 9:25 AM, Mark A. Yoder mark.a.yo...@gmail.com wrote: I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. Humm, that means uenvcmd wasn't defined in uEnv.txt.. I wonder how that happened (1). Does it help if you hold down the boot button? What do you have flashed to the eMMC? (i have it setup to be compatible with atleast Angstrom's 2013.06.20 u-boot) 1: https://github.com/beagleboard/image-builder/blob/master/target/boot/beagleboard.org.txt#L45 I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz Testing now too.. 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: Here is the BeagleBone Debian (beta) image you want to test
On Thu, Mar 27, 2014 at 10:56 AM, Robert Nelson robertcnel...@gmail.com wrote: On Thu, Mar 27, 2014 at 9:25 AM, Mark A. Yoder mark.a.yo...@gmail.com wrote: I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. Humm, that means uenvcmd wasn't defined in uEnv.txt.. I wonder how that happened (1). Does it help if you hold down the boot button? What do you have flashed to the eMMC? (i have it setup to be compatible with atleast Angstrom's 2013.06.20 u-boot) 1: https://github.com/beagleboard/image-builder/blob/master/target/boot/beagleboard.org.txt#L45 I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz Okay tested, and i see the issue.. To save bandwidth i mirror the kernel *.deb locally, which runs/updates at midnight, so the kernel never got installed. So i just need to add that error condition and just rerun the script again.. Thanks for testing, sorry for the error! * U-Boot SPL 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment Net: ethaddr not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1390 bytes read in 5 ms (271.5 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage ** Unable to read file zImage ** reading initrd.img ** Unable to read file initrd.img ** reading /dtbs/am335x-boneblack.dtb ** Unable to read file /dtbs/am335x-boneblack.dtb ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 ** No partition table - mmc 1 ** Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... Booting from nand ... no devices available no devices available Bad Linux ARM zImage magic! U-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] Re: Here is the BeagleBone Debian (beta) image you want to test
Thanks Robert. I'll watch for the update. --Mark On Thursday, March 27, 2014 12:22:12 PM UTC-4, RobertCNelson wrote: On Thu, Mar 27, 2014 at 10:56 AM, Robert Nelson robert...@gmail.comjavascript: wrote: On Thu, Mar 27, 2014 at 9:25 AM, Mark A. Yoder mark.a...@gmail.comjavascript: wrote: I see a 2014-03-26 image has appeared. Unfortunately when I flash [1] and boot from it, it appears to never leave u-boot. Just 3 LEDs light and it just hangs. Humm, that means uenvcmd wasn't defined in uEnv.txt.. I wonder how that happened (1). Does it help if you hold down the boot button? What do you have flashed to the eMMC? (i have it setup to be compatible with atleast Angstrom's 2013.06.20 u-boot) 1: https://github.com/beagleboard/image-builder/blob/master/target/boot/beagleboard.org.txt#L45 I try this on two SD cards and both had the same behavior. --Mark [1] http://rcn-ee.net/deb/testing/2014-03-26/bone-debian-7.4-2014-03-26-2gb.img.xz Okay tested, and i see the issue.. To save bandwidth i mirror the kernel *.deb locally, which runs/updates at midnight, so the kernel never got installed. So i just need to add that error condition and just rerun the script again.. Thanks for testing, sorry for the error! * U-Boot SPL 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment Net: ethaddr not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1390 bytes read in 5 ms (271.5 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage ** Unable to read file zImage ** reading initrd.img ** Unable to read file initrd.img ** reading /dtbs/am335x-boneblack.dtb ** Unable to read file /dtbs/am335x-boneblack.dtb ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 ** No partition table - mmc 1 ** Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** ** No partition table - mmc 1 ** Bad Linux ARM zImage magic! uenvcmd was not defined in uEnv.txt ... Booting from nand ... no devices available no devices available Bad Linux ARM zImage magic! U-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.
[beagleboard] How to get the Boot device in U-Boot
is there anyway to get the effective boot device/media in u-boot ? (MMC oe eMMC) Reading the SYSBOOT Pin is not going to help since if the first media fails BOOT ROM Code will try the next one. Cheers -- 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: eMMC data corruption due to power removal?
On 3/27/2014 12:26 PM, rh_ wrote: On Thu, 27 Mar 2014 07:41:11 -0500 Charles Steinkuehler char...@steinkuehler.net wrote: On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. I pull the battery on my android frequently doing devel. Never had any problems. I pull the plug on my BBB all the time too, at least once/day. No problems. Yes, but are you writing to the flash when you pull the power? There is a huge difference between it works for me and *RELIABLY* avoiding data corruption when power is unexpectedly removed with significant write activity in-progress. -- Charles Steinkuehler char...@steinkuehler.net -- 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] Hard freeze (ethernet related?)
Hello Gerald, I downloaded debian, ran it from the uSD and I was installing a bunch of stuff..after a while here's what I got: [ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds. [ 360.546242] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks [ 360.561039] [c0010443] (unwind_backtrace+0x1/0x8a) from [c0455ced] (panic+0x51/0x148) [ 360.569697] [c0455ced] (panic+0x51/0x148) from [c006770b] (watchdog+0x14f/0x194) [ 360.577909] [c006770b] (watchdog+0x14f/0x194) from [c003fb8f] (kthread+0x67/0x74) [ 360.586206] [c003fb8f] (kthread+0x67/0x74) from [c000c0dd] (ret_from_fork+0x11/0x34) [ 360.594750] drm_kms_helper: panic occurred, switching back to text console USR2 led stuck on Ideas? Thanks 2014-03-27 15:33 GMT+01:00 Gerald Coley ger...@beagleboard.org: Can you try it using the latest Debian image? http://beagleboard.org/latest-images Gerald On Thu, Mar 27, 2014 at 9:18 AM, Riccardo Bortolato rikyz...@gmail.com wrote: Hello, sorry if it already has been asked but I couldn't find anything like this so I'm gonna post my issue. I'm running ubuntu 13.04 with kernel 3.8.13-bone41 from emmc (powered by a 5V 2A power supply) and I am experiencing this: unplugging (and/or plugging in back) the ethernet cable can result in the board freezing and the USR2 led stuck on. I tried reading output from UART0 but there's nothing useful. How can I further debug this? Is it a known issue? Thanks, Riccardo -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/5vaehZewk2U/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.
Re: [beagleboard] Hard freeze (ethernet related?)
Sounds like some sort of SW issue. Gerald On Thu, Mar 27, 2014 at 1:54 PM, Riccardo Bortolato rikyz...@gmail.comwrote: Hello Gerald, I downloaded debian, ran it from the uSD and I was installing a bunch of stuff..after a while here's what I got: [ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds. [ 360.546242] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks [ 360.561039] [c0010443] (unwind_backtrace+0x1/0x8a) from [c0455ced] (panic+0x51/0x148) [ 360.569697] [c0455ced] (panic+0x51/0x148) from [c006770b] (watchdog+0x14f/0x194) [ 360.577909] [c006770b] (watchdog+0x14f/0x194) from [c003fb8f] (kthread+0x67/0x74) [ 360.586206] [c003fb8f] (kthread+0x67/0x74) from [c000c0dd] (ret_from_fork+0x11/0x34) [ 360.594750] drm_kms_helper: panic occurred, switching back to text console USR2 led stuck on Ideas? Thanks 2014-03-27 15:33 GMT+01:00 Gerald Coley ger...@beagleboard.org: Can you try it using the latest Debian image? http://beagleboard.org/latest-images Gerald On Thu, Mar 27, 2014 at 9:18 AM, Riccardo Bortolato rikyz...@gmail.com wrote: Hello, sorry if it already has been asked but I couldn't find anything like this so I'm gonna post my issue. I'm running ubuntu 13.04 with kernel 3.8.13-bone41 from emmc (powered by a 5V 2A power supply) and I am experiencing this: unplugging (and/or plugging in back) the ethernet cable can result in the board freezing and the USR2 led stuck on. I tried reading output from UART0 but there's nothing useful. How can I further debug this? Is it a known issue? Thanks, Riccardo -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/5vaehZewk2U/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. -- 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] Hard freeze (ethernet related?)
On Thu, Mar 27, 2014 at 1:54 PM, Riccardo Bortolato rikyz...@gmail.com wrote: Hello Gerald, I downloaded debian, ran it from the uSD and I was installing a bunch of stuff..after a while here's what I got: [ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds. [ 360.546242] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks [ 360.561039] [c0010443] (unwind_backtrace+0x1/0x8a) from [c0455ced] (panic+0x51/0x148) That's the 3.8 mmc driver.. We've back-ported a few fixes from v3.12/v3.13 to fix that issue, but for some devices it's still a problem. If you aren't using any capes (or just a simple usart/spi ones, we have another option for you, essentially running v3.13.x) 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] Hard freeze (ethernet related?)
Hello Robert, well I just need usart1, usb and ethernet so the 3.13 option is fine for me. Meanwhile I was just searching for similar issues and found this: http://blog.machinekit.io/2013/10/hung-task-bug-in-xenomai-kernel.html which points to http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7472bab236bdee1173412585591329e718f4d324 I am posting this since you replied so fast I didn't even took a look at the patches you added to your kernels! Do you think this is the same issue I posted in the original post? Anyway, now I'll build a 3.13 deb. P.S. thanks for your tools/scripts, the whole process works like a charm :) Thanks 2014-03-27 19:56 GMT+01:00 Robert Nelson robertcnel...@gmail.com: On Thu, Mar 27, 2014 at 1:54 PM, Riccardo Bortolato rikyz...@gmail.com wrote: Hello Gerald, I downloaded debian, ran it from the uSD and I was installing a bunch of stuff..after a while here's what I got: [ 360.539306] INFO: task apt-get:1251 blocked for more than 60 seconds. [ 360.546242] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 360.554638] Kernel panic - not syncing: hung_task: blocked tasks [ 360.561039] [c0010443] (unwind_backtrace+0x1/0x8a) from [c0455ced] (panic+0x51/0x148) That's the 3.8 mmc driver.. We've back-ported a few fixes from v3.12/v3.13 to fix that issue, but for some devices it's still a problem. If you aren't using any capes (or just a simple usart/spi ones, we have another option for you, essentially running v3.13.x) Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/5vaehZewk2U/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.
Re: [beagleboard] Hard freeze (ethernet related?)
On Thu, Mar 27, 2014 at 2:05 PM, Riccardo Bortolato rikyz...@gmail.com wrote: Hello Robert, well I just need usart1, usb and ethernet so the 3.13 option is fine for me. Meanwhile I was just searching for similar issues and found this: http://blog.machinekit.io/2013/10/hung-task-bug-in-xenomai-kernel.html which points to http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7472bab236bdee1173412585591329e718f4d324 I am posting this since you replied so fast I didn't even took a look at the patches you added to your kernels! Yeap, that's the patch we backported.. https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L848 It helped, in some situations but something else between v3.8-v3.13 is also needed.. Do you think this is the same issue I posted in the original post? Anyway, now I'll build a 3.13 deb. P.S. thanks for your tools/scripts, the whole process works like a charm :) So before you build, you can actually test.. cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --beta-kernel For capes, if you need ttyO1 this the way v3.13.x is setup: with: 2014-03-04 cd /boot/uboot/dtbs/ cp am335x-boneblack.dtb am335x-boneblack-bak.dtb cp am335x-boneblack-ttyO1.dtb am335x-boneblack.dtb with: 2014-03-19 Edit: /boot/uboot/uEnv.txt set: CAPE=ttyO1 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: eMMC data corruption due to power removal?
That's because your phone uses a sane filesystems that takes into account this use case and isn't writing constantly (write one byte, the disk writes a whole erase block). This doesn't protect you from eventual disk corruption. The wear leveling bad-block type tables will eventually corrupt/run out of memory lng before your disk space is eaten by bad blocks. http://arstechnica.com/information-technology/2010/12/ext4-filesystem-hits-android-no-need-to-fear-data-loss/ Most Android devices currently use YAFFS, a lightweight filesystem that is optimized for flash storage and is commonly used in mobile and embedded devices. My production Beaglebone image does not support this. Developers who are accessing the filesystem directly will have to be mindful about Ext4's buffering behavior and make sure that the data is actually reaching persistent storage in a timely manner so that it won't be lost in the event of a system failure. It is now an issue with Android! T'so says that there isn't much need for concern. Google and the handset makers will catch platform-level filesystem reliability issues, ensuring that the high-level storage APIs are safe. Is the API you use for disk writes safe? Nope. -Brandon On Thu, Mar 27, 2014 at 10:26 AM, rh_ richard_hubb...@lavabit.com wrote: On Thu, 27 Mar 2014 07:41:11 -0500 Charles Steinkuehler char...@steinkuehler.net wrote: On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. I pull the battery on my android frequently doing devel. Never had any problems. I pull the plug on my BBB all the time too, at least once/day. No problems. For people having issues I would suspect a problem elsewhere. -- 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/dV0ctlQykYI/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: Mono on last debian
Thanks, I will try in Ubuntu too (because the touchscreen maybe it works in there) On Thursday, March 27, 2014 12:41:52 PM UTC-3, mickeyf wrote: Try: https://github.com/alexrp/mono/tree/armhf With build instructions here: https://github.com/alexrp/mono/tree/armhf We are using this with RCN's Ubuntu. Last built it many months ago though and are considering that version stable for our purposes, so can't speak to any recent changes or updates. On Wednesday, March 26, 2014 11:46:45 PM UTC-7, Erwin Ried wrote: Hi, any hint how to install mono in the last debian image? (I need this because a little touchscreen, very jittery in angstrom) I get: root@beaglebone:/# apt-get install mono-runtime Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mono-runtime:armel : Depends: mono-gac:armel (= 2.10.8.1-8) but it is not installable Recommends: binfmt-support:armel (= 1.1.2) E: Unable to correct problems, you have held broken packages. And something similar for mono-complete. Thanks! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Here is the BeagleBone Debian (beta) image you want to test
On Thu, Mar 27, 2014 at 11:24 AM, Mark A. Yoder mark.a.yo...@gmail.com wrote: Thanks Robert. I'll watch for the update. Just pushed out tested locally: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 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] i2c via bonescript under Debian
Hmm... I'm not getting anywhere with this. I have a TMP101 i2c device
wired to P9_19 and P9_20. From the command line this works:
# *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: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: 70 -- -- -- -- -- -- --
# *i2cget -y 1 0x49*
0x17
# *i2cget -y 1 0x49*
0x1b
I stuck my figure on the device and warmed it up for the second i2cget.
Now with bonescript:
var b = require('bonescript');
var port = '/dev/i2c-0'
var TMP102 = 0x48;
b.i2cOpen(port, TMP102, {}, onI2C);
function onI2C(x) {
// console.log(x);
if (x.event == 'return') {
b.i2cScan(port, onScan);
b.i2cReadBytes(port, 0, 1, onReadByte);
}
}
function onScan(x) {
console.log('scan data: ' + x.data);
}
function onReadByte(x) {
console.log('onReadByte: ' + JSON.stringify(x));
console.log('res: ' + JSON.stringify(x.res));
}
When I run with /dev/i2c-*1* I get:
scan data:
scan data: undefined
onReadByte: {err:{},res:[240],event:callback}
res: [240]
onReadByte: {event:return,return:[240]}
res: undefined
That is, scan doesn't find anything. If I run with /dev/i2c-*0*
scan data: 52,80
scan data: undefined
onReadByte: {err:{},res:[240],event:callback}
res: [240]
onReadByte: {event:return,return:[240]}
res: undefined
Scan finds two devices, but I don't see how they relate to whats on the bus.
Any ideas?
--Mark
On Thursday, March 27, 2014 9:40:09 AM UTC-4, Jason Kridner wrote:
On Wed, Mar 26, 2014 at 5:42 PM, Mark A. Yoder
mark.a...@gmail.comjavascript:
wrote:
I see the bonescript has some i2c methods. Are there any examples out
there
that work under Debian on the Black Bone?
Here's one that works on BoneScript 0.2.4 on Debian, but happens to be
calling the I2C methods from a web page:
http://jsfiddle.net/jkridner/PGL92/ [1]
I had something similar for drawing a Flot graph using the
accelerometer, but not sure where I posted it.
Some more running-from-webpage examples:
http://jsfiddle.net/user/jkridner/fiddles/
[1] source
var canvas = document.getElementById(mysketch);
var p = new Processing(canvas, sketchProc);
function sketchProc(pjs) {
// Sketch global variables
var radius = 50.0;
var X, Y;
var nX, nY;
var delay = 16;
var brightness = 0;
var buttonStatus = 0;
var sliderStatus = 0;
var lastSliderValue = 0;
var BUTTON = 'P8_19';
var SLIDER = 'P9_36';
var port = '/dev/i2c-2'
var address = 0x1c;
// Get the BoneScript library and begin updating the canvas
setTargetAddress('192.168.7.2', {
initialized: run
});
function run() {
var b = require('bonescript');
b.pinMode(BUTTON, b.INPUT);
b.i2cOpen(port, address, {}, onI2C);
// Setup the Processing Canvas
pjs.setup = function () {
pjs.size(256, 256);
pjs.strokeWeight(10);
pjs.frameRate(15);
X = pjs.width / 2;
Y = pjs.height / 2;
nX = X;
nY = Y;
}
// Main draw loop
pjs.draw = function () {
// Calculate some fading values based on the frame count
radius = 50.0 + (15 - sliderStatus) * pjs.sin(pjs.frameCount /
4);
brightness = (radius - 40.0) / 20.0;
// Track circle to new destination
X += (nX - X) / delay;
Y += (nY - Y) / delay;
// Fill canvas grey
pjs.background(100);
// Set fill-color to blue or red, based on button status
if (buttonStatus) pjs.fill(200, 30, 20)
else pjs.fill(0, 121, 184);
// Set stroke-color white
pjs.stroke(255);
// Draw circle
pjs.ellipse(X, Y, radius, radius);
// Update physical values
readSlider();
}
function readSlider() {
b.analogRead(SLIDER, onAnalogRead);
}
// Handle data back from potentiometer
function onAnalogRead(x) {
if (!x.err (x.value = 0) (x.value = 1)) {
if (Math.abs(x.value - lastSliderValue) 0.05) {
lastSliderValue = x.value;
sliderStatus = parseInt(x.value * 10, 10);
}
}
// Fetch button status
b.digitalRead(BUTTON, onDigitalRead);
}
// Handle data back from button
function onDigitalRead(x) {
[beagleboard] Here is the BeagleBone Debian (beta + fixes) image you want to test (2014-03-27)
Thanks to everyone for testing the beta images! In this last last week window I've rolled in many of your changes. So please continue to use the bug tracker: http://bugs.elinux.org/projects/debian-image-releases Big Changes: Added support for Hieu Duong's cape-bone-weather-00B0 Added support for Charles Steinkuehlers universal cape https://github.com/cdsteinkuehler/beaglebone-universal-io Small Changes: Packages added: xrdp, wicd-curses, wicd-cli The gadget serial port (ttyGS0) is now enabled, so you can connect serially over the usb connector. So the images are linked to from here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 and the full changelog/tweaklog: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27_Changes 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] Re: First one, then two, then three....
The only thing I wish for is the ability to change I2C bus speeds on the fly. You can do anything with a kernel module and some memory pokes. ;) On Thursday, March 27, 2014 2:47:10 AM UTC-7, Richard-tx wrote: I bought a BBB about 3 weeks ago. Was impressed enough that I bought two more. I have a few Rpis is use around the house as well so I have a little experience with SBCs Anyway. all three BBB has been flawless. No problems at all. I did discover one thing. Of all the Linux distros out there, I like Ubuntu the best. I found that Ubuntu does not suffer as badly from creeping featurism or from a lack of essential packages. I tried Angstrom first. It got flushed. Then I tried Arch and Debian. Didn't like Arch at all. Debian was tolerable. Lastly I tried Ubuntu. Ubuntu seems to be the easiest to get configured and running. I was porting code in under an hour. I don't use a GUI so Ubuntu might not be for everyone. The really nice part about the BBB is the fact that it boots without a SD card. That leaves the SD card slot available for extra file storage. SInce I do some software development as well as create various appliance-like things, the added hot-plugable storage is wonderful. The only thing I wish for is the ability to change I2C bus speeds on the fly. All in all, I am very happy with the BBB. Well done! Richard . -- 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: Here is the BeagleBone Debian (beta) image you want to test
It's working. Thanks! --Mark On Thursday, March 27, 2014 4:18:20 PM UTC-4, RobertCNelson wrote: On Thu, Mar 27, 2014 at 11:24 AM, Mark A. Yoder mark.a...@gmail.comjavascript: wrote: Thanks Robert. I'll watch for the update. Just pushed out tested locally: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-03-27 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] Re: How to use UART Serial Port Using BoneScript Library
Nick:
I have some bonescript code that works with the UART, but I'm not using
the built-in bonescript calls. It works fine with a GPS, though I don't use
it to transmit.
I took would like to see an example that uses the bonescript calls. Before
ruing the code you need to:
beagle# *npm install -g serialport*
beagle# *echo BB-UART4 /sys/devices/bone_capemgr.*/slots*
--Mark
#!/usr/bin/env node
// From: https://github.com/voodootikigod/node-serialport
// From: https://github.com/jamesp/node-nmea
var b = require('bonescript');
var nmea = require('nmea');
//console.log(b.serialOpen);
//var sp = b.serialOpen('/dev/ttyO4', {baudrate: 9600} );
// parser: b.serialParsers.readline(\n)});
var serialport = require(serialport);
var SerialPort = serialport.SerialPort; // localize object constructor
var sp = new SerialPort(/dev/ttyO4, {
parser: serialport.parsers.readline(\n)
});
sp.on(data, function (data) {
console.log(here: +data);
console.log(nmea.parse(data));
});
On Thursday, December 19, 2013 1:49:30 AM UTC-5, Nick Farrell wrote:
I am a newbie to BeagleBone Black(BBB) but have good knowledge about
Arduino. I would like to know how to open a serial port in BBB using the 4
UARTs available in BBB using BoneScript library and use cloud9 ide to see
the serial data on the console. Can anyone help me on this issue.
--
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] eMMC data corruption due to power removal?
From: Brandon I brandon.ir...@gmail.com Reply-To: beagleboard@googlegroups.com Date: Wednesday, March 26, 2014 at 6:46 PM To: beagleboard@googlegroups.com Subject: Re: [beagleboard] eMMC data corruption due to power removal? Here's a good read: http://www.embeddedarm.com/about/resource.php?item=459 I had a lng discussion about this with a colleague of mine after we started seeing boards die. Basically you're eventually doomed unless you mount the whole disk as read only since the wear leveling algorithms in the flash have no knowledge of what a partition is and will eventually end up with suppesed-to-be-read-only data mixed in with the writable partition erase blocks. If you're writing to flash, it will eventually fail by unfortunate design. It tooks his previous company 6 months of fighting to come to terms with this in their last product. They had to write data, so eventually used usb flash that the customer could easily replace when things eventually died. They tried every flash card they could get their hands on, read only partitions, etc and eventually had to give up. Use the SD card you say! Any micro SD card you can put in the slot is absolutely not meant for continuous writing. The SD card spec has a very specific use case in mind (video and images), and logging or using it as a sparse write file system goes completely against the intended SD card design specs. Industrial grade write-tolerant flash will cost you hundreds of dollars more than something on Amazon. With our current product, I told my boss that I was worried about corruption and that we would eventually go to read only once we debugged the boards. Within two weeks of only log messages, all of our boards started dyeing. The next day, all disks were mounted as read only and issues are debugged with the in-memory log files. We haven't seen any failures in 6 months now. The easy solution is trying to force the answer of why are you writing anything to persistent storage? to be there's no good reason since it eventually bricks our product. If you want something that will last forever, you will not write to standard flash media. If you can't, then maybe use a usb flash drive (MUCH better life than a micro sd card) and count the days until it corrupts or someone pulls the power at an inopportune time. You could always use a battery backup to get rid of the power off issue. :-\ This is all doom and gloom, but it's a consequence of inconsistent power, buffers, and the destruction nature of quantum tunneling. What you say is mostly correct. However, you can use supercaps based power supply which will enable you to store data stored in RAM to Non-Volatile storage such as SDCard or eMMC when a power fail is detected. Also, when Linux goes through an orderly shutdown, no corruption occurs. This way, you only write to flash during a power failure so you won¹t see any flash failures. The supercaps don¹t have a limited number of charge cycles which is common in Lithium Iron batteries so these systems should be good for 10 years or more. Plan for about 90 Seconds to write data to flash and Linux shutdown. Regards, John -Brandon On Wednesday, March 26, 2014 2:45:57 PM UTC-7, Sungjin Chun wrote: How about making system partition be mounted as read-only and data partition be mounted after booting and checking? In this case, only data partition has possibility of corruption. Sent from my iPad On Mar 26, 2014, at 9:53 PM, Yiling Cao yilin...@gmail.com javascript: wrote: Hi I have some my products deployed with am335x with Micron eMMC 2GB, but my products allow users to unplug power as they wish. My linux app very rarely writes to the eMMC. and my /etc/fstab specifies /var/log and /tmp to tempfs; fstab mount all partitions with noatime properties. But around 2 months of deployment, I found that around 1-2% am335x machines, have some sort of data corruption, resulting fail to boot up. Can anyone share some thoughts/ experience about how to resolve this issue? In real life product, whats the best practice? -- 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. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To
Re: [beagleboard] eMMC data corruption due to power removal?
I have had a long and painful history using flash in general, and have come to the conclusion that asynchronous removal of power is a very bad thing. The following link shows one low level phenomenon called unstable bits. This seems to be getting worse the more bits that are stuffed into a cell (pretty obvious) :-[ http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits Some other studies suggest that very high density chips may exhibit similar problems even when *_reading_* during a power fail! My conclusions lean to removing power only when ALL accesses to flash have completed. HTH, Dave. On 03/27/2014 04:10 PM, John Syn wrote: From: Brandon I brandon.ir...@gmail.com mailto:brandon.ir...@gmail.com Reply-To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Date: Wednesday, March 26, 2014 at 6:46 PM To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Subject: Re: [beagleboard] eMMC data corruption due to power removal? Here's a good read: http://www.embeddedarm.com/about/resource.php?item=459 I had a lng discussion about this with a colleague of mine after we started seeing boards die. Basically you're eventually doomed unless you mount the whole disk as read only since the wear leveling algorithms in the flash have no knowledge of what a partition is and will eventually end up with suppesed-to-be-read-only data mixed in with the writable partition erase blocks. If you're writing to flash, it will eventually fail by unfortunate design. It tooks his previous company 6 months of fighting to come to terms with this in their last product. They had to write data, so eventually used usb flash that the customer could easily replace when things eventually died. They tried every flash card they could get their hands on, read only partitions, etc and eventually had to give up. Use the SD card you say! Any micro SD card you can put in the slot is absolutely not meant for continuous writing. The SD card spec has a very specific use case in mind (video and images), and logging or using it as a sparse write file system goes completely against the intended SD card design specs. Industrial grade write-tolerant flash will cost you hundreds of dollars more than something on Amazon. With our current product, I told my boss that I was worried about corruption and that we would eventually go to read only once we debugged the boards. Within two weeks of only log messages, all of our boards started dyeing. The next day, all disks were mounted as read only and issues are debugged with the in-memory log files. We haven't seen any failures in 6 months now. The easy solution is trying to force the answer of why are you writing anything to persistent storage? to be there's no good reason since it eventually bricks our product. If you want something that will last forever, you will not write to standard flash media. If you can't, then maybe use a usb flash drive (MUCH better life than a micro sd card) and count the days until it corrupts or someone pulls the power at an inopportune time. You could always use a battery backup to get rid of the power off issue. :-\ This is all doom and gloom, but it's a consequence of inconsistent power, buffers, and the destruction nature of quantum tunneling. What you say is mostly correct. However, you can use supercaps based power supply which will enable you to store data stored in RAM to Non-Volatile storage such as SDCard or eMMC when a power fail is detected. Also, when Linux goes through an orderly shutdown, no corruption occurs. This way, you only write to flash during a power failure so you won't see any flash failures. The supercaps don't have a limited number of charge cycles which is common in Lithium Iron batteries so these systems should be good for 10 years or more. Plan for about 90 Seconds to write data to flash and Linux shutdown. Regards, John -Brandon On Wednesday, March 26, 2014 2:45:57 PM UTC-7, Sungjin Chun wrote: How about making system partition be mounted as read-only and data partition be mounted after booting and checking? In this case, only data partition has possibility of corruption. Sent from my iPad On Mar 26, 2014, at 9:53 PM, Yiling Cao yilin...@gmail.com javascript: wrote: Hi I have some my products deployed with am335x with Micron eMMC 2GB, but my products allow users to unplug power as they wish. My linux app very rarely writes to the eMMC. and my /etc/fstab specifies /var/log and /tmp to tempfs; fstab mount all partitions with noatime properties. But around 2 months of deployment, I found that around 1-2% am335x machines, have some sort of data corruption, resulting fail to boot
[beagleboard] Re: i2c2 file not present in the system
This is one of those things that should be documented a little better. Assuming you are using ubuntu or debian, here is the command. echo BB-I2C1 /sys/devices/bone_capemgr.*/slots That should do it. On Friday, January 10, 2014 5:45:17 AM UTC-6, Jyotirmaya Joon wrote: i2c2 file is not present in the sys/bus/ and i need to use i2c2 how to bring it to the system . -- 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] i2c via bonescript under Debian
On Thu, Mar 27, 2014 at 4:17 PM, Mark A. Yoder mark.a.yo...@gmail.com wrote:
Hmm... I'm not getting anywhere with this. I have a TMP101 i2c device wired
to P9_19 and P9_20. From the command line this works:
# 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: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: 70 -- -- -- -- -- -- --
# i2cget -y 1 0x49
0x17
# i2cget -y 1 0x49
0x1b
I stuck my figure on the device and warmed it up for the second i2cget.
Now with bonescript:
var b = require('bonescript');
var port = '/dev/i2c-0'
var TMP102 = 0x48;
b.i2cOpen(port, TMP102, {}, onI2C);
function onI2C(x) {
// console.log(x);
if (x.event == 'return') {
b.i2cScan(port, onScan);
b.i2cReadBytes(port, 0, 1, onReadByte);
}
}
function onScan(x) {
console.log('scan data: ' + x.data);
}
function onReadByte(x) {
console.log('onReadByte: ' + JSON.stringify(x));
console.log('res: ' + JSON.stringify(x.res));
}
When I run with /dev/i2c-1 I get:
scan data:
scan data: undefined
onReadByte: {err:{},res:[240],event:callback}
res: [240]
onReadByte: {event:return,return:[240]}
res: undefined
That is, scan doesn't find anything. If I run with /dev/i2c-0
scan data: 52,80
scan data: undefined
onReadByte: {err:{},res:[240],event:callback}
res: [240]
onReadByte: {event:return,return:[240]}
res: undefined
Scan finds two devices, but I don't see how they relate to whats on the bus.
Any ideas?
You'll want to use '/dev/i2c-2'.
Check out https://github.com/jadonk/bonescript/blob/master/src/bone.js#L1550
for the mapping.
The reason I chose to use i2c-2 because the adapters are enumerated
out of order. Otherwise, it won't match the hardware documentation.
(http://beagleboard.org/support/bone101/#headers-i2c)
There has been some discussion to fix this in mainline, but I'm not
sure of the current state.
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/116775.html
--Mark
On Thursday, March 27, 2014 9:40:09 AM UTC-4, Jason Kridner wrote:
On Wed, Mar 26, 2014 at 5:42 PM, Mark A. Yoder mark.a...@gmail.com
wrote:
I see the bonescript has some i2c methods. Are there any examples out
there
that work under Debian on the Black Bone?
Here's one that works on BoneScript 0.2.4 on Debian, but happens to be
calling the I2C methods from a web page:
http://jsfiddle.net/jkridner/PGL92/ [1]
I had something similar for drawing a Flot graph using the
accelerometer, but not sure where I posted it.
Some more running-from-webpage examples:
http://jsfiddle.net/user/jkridner/fiddles/
[1] source
var canvas = document.getElementById(mysketch);
var p = new Processing(canvas, sketchProc);
function sketchProc(pjs) {
// Sketch global variables
var radius = 50.0;
var X, Y;
var nX, nY;
var delay = 16;
var brightness = 0;
var buttonStatus = 0;
var sliderStatus = 0;
var lastSliderValue = 0;
var BUTTON = 'P8_19';
var SLIDER = 'P9_36';
var port = '/dev/i2c-2'
var address = 0x1c;
// Get the BoneScript library and begin updating the canvas
setTargetAddress('192.168.7.2', {
initialized: run
});
function run() {
var b = require('bonescript');
b.pinMode(BUTTON, b.INPUT);
b.i2cOpen(port, address, {}, onI2C);
// Setup the Processing Canvas
pjs.setup = function () {
pjs.size(256, 256);
pjs.strokeWeight(10);
pjs.frameRate(15);
X = pjs.width / 2;
Y = pjs.height / 2;
nX = X;
nY = Y;
}
// Main draw loop
pjs.draw = function () {
// Calculate some fading values based on the frame count
radius = 50.0 + (15 - sliderStatus) * pjs.sin(pjs.frameCount /
4);
brightness = (radius - 40.0) / 20.0;
// Track circle to new destination
X += (nX - X) / delay;
Y += (nY - Y) / delay;
// Fill canvas grey
pjs.background(100);
// Set fill-color to blue or red, based on button status
if (buttonStatus) pjs.fill(200, 30, 20)
else pjs.fill(0, 121, 184);
// Set stroke-color white
pjs.stroke(255);
// Draw circle
pjs.ellipse(X, Y, radius, radius);
// Update physical values
readSlider();
}
function readSlider() {
b.analogRead(SLIDER, onAnalogRead);
}
// Handle data back from potentiometer
function
[beagleboard] Re: MMC1: strange voltage values in MMC1 module pins DAT[3-0], WP and CMD
Ok, thanks for your help, I finally got it. My SYS_BOOT configuration was wrong: I inserted also the do not insert resistors. After removing them the card module worked and I was able to boot. The 0.5V is the voltage that you can measure in a pin that has an active pull-down: after fixing the SYS_BOOT the OMAP tried to boot from mmc and it disabled the pull-downs in the mmc pins before attempting to boot from card. El martes, 25 de marzo de 2014 23:01:33 UTC+1, 4ndr...@gmail.com escribió: Hello, I built a board really similar to beagleboard rev4 from scratch. I just added some USB ports and other few changes.(buy the components, manufacture it, design the layers..etc) After some problems I finally got a “40W” in the terminal connected to UART3. I could not boot from SDCard because, despite the voltage in VMMC1 is 3V, my WP, DAT[3-0] and CMD pins have a strange voltage value. The voltage values measured in the SDCard reader are shown in this table: MY BEAGLE ORIGINAL BEAGLE 0.5 V 1.8 V WP Conected to OMAP 1.8 V 1.8 V CD Conected to TPS65950 0.51 V 3 V DAT1 Conected to OMAP 0.507 V 3 V DAT0 Conected to OMAP 0 V 0.078 V DAT7 Conected to OMAP Powered by VSIM 0 V 0 V GND0 V 0.072 V DAT6 Conected to OMAP Powered by VSIM CLK Conected to OMAP 3 V 3 V VDD0 V 0 V GND0 V 0.072 V DAT5 Conected to OMAP Powered by VSIM 0.5 V 3 V CMD Conected to OMAP 0 V 0.073 V DAT4 Conected to OMAP Powered by VSIM 0.513 V 3 V DAT3 Conected to OMAP 0.507 V 3 V DAT2 Conected to OMAP After check the voltages in a real beagleboard I found that DAT[0-3] and CMD are 3V. I have been searching a lot but I could not find why my voltage values are wrong. The hardware configuration is the same as the original beagleboard: to power OMAP3530 I am using TPS65950. The only difference is that due to a design fail I needed to cut the connection of VMMC1 with the TPS65950 and I am powering VMMC1 with an external source (3V). I took care of give power to VDD in the card reader and to VDDS_MMC1 in the OMAP3530. VSIM is 0V after reset despite VAUX12S is powered at 3.6V. I could not load any loader into the board yet. If I can not fix MMC problems I will try to boot from UART, because of the 40W it seems that the OMAP processor is alive. Really thanks. PD: 1) Because all the wrong voltages in my board are almost the same value (0.5 V) I thought that maybe the original beagleboards comes with a different preconfigured pins state-after-reset (pull-down or something) than the OMAP3530 bought directly??? 2) Can I say that VMMC1 is reaching correctly the VDDS_MMC1 pin in the OMAP3530 because of the 0.5V in the pins? or the connection between VMMC1 and VDDS_MMC1 could be cut despite the 0.5V? -- 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: eMMC data corruption due to power removal?
Rh, my earlier reply was to you, and that link shows that it is now a problem with androids use of ext4. On Thu, Mar 27, 2014 at 4:55 PM, rh_ richard_hubb...@lavabit.com wrote: On Thu, 27 Mar 2014 13:41:24 -0500 Charles Steinkuehler char...@steinkuehler.net wrote: On 3/27/2014 12:26 PM, rh_ wrote: On Thu, 27 Mar 2014 07:41:11 -0500 Charles Steinkuehler char...@steinkuehler.net wrote: On 3/26/2014 10:22 PM, Yiling Cao wrote: Thanks Brandon for your experience. I do agree with that better to put whole disk read only. But how do iPhone and Android survive? Esp for those Android phones? They are very prone to sudden power removal as well. What? These devices are battery powered, and other than opening the case and physically removing the battery they are guaranteed enough power to do a proper and orderly shutdown. I pull the battery on my android frequently doing devel. Never had any problems. I pull the plug on my BBB all the time too, at least once/day. No problems. Yes, but are you writing to the flash when you pull the power? Don't know. But it's possible. How would I know? If it doesn't boot? For android there's JAFFS (or is it YAFFS) so it's more robust than ext4 I guess. There is a huge difference between it works for me and *RELIABLY* avoiding data corruption when power is unexpectedly removed with significant write activity in-progress. Ok, but I haven't encountered a problem yet, and I'm never that lucky. With the millions and millions (billions?) of handsets I would think data corruption would be a much more visible problem. I haven't seen it happen yet over many phones and many years. -- 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/dV0ctlQykYI/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] Upgrade kernel from 2.6.32 to 3.0.7
I currently run Angstrom Linux 2.6.32 on BeagleBoard-xM. Image was built on Narcissus with Bootloader Files *(x-load/u-boot/scripts)*. Recently, I downloaded kernel sources 2.6.32.61 from kernel.org and copied them to /usr/src on BB-xM. After making the configuration (make menuconfig), I build (make) and installed (make install) kernel directly to BB-xM *(native toolchain)*. Now, I want to upgrade kernel to 3.0.7. As far I know, the 3.x kernel should be backward compatible with a 2.6 oriented userland, so there should not be any problems following the same procedure as with kernel 2.6.32. However, is there anything else required? Do I have to configure U-Boot? -- 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] Tesseract-ocr installation on beaglebone
Hi everyone, Right now I am working on an embedded system using my BeagleboneA6 (white) and I'm trying to install tesseract-ocr. Unfortunately, I am not very familiar with Linux so I was trying to follow these steps http://miphol.com/muse/2013/05/install-tesseract-ocr-on-ubunt.html I know that the instructions above are for Ubuntu and not Angstrom, but I gave it a try and failed. Can anyone help me out? Thanks in advance, Robert -- 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: eMMC data corruption due to power removal?
On 03/27/2014 07:04 PM, rh_ wrote: On Thu, 27 Mar 2014 16:25:29 -0500 David Lambert d...@lambsys.com wrote: I have had a long and painful history using flash in general, and have come to the conclusion that asynchronous removal of power is a asynchronous? Like pulling the plug and not pushing it? Yes. very bad thing. The following link shows one low level phenomenon called unstable bits. This seems to be getting worse the more bits that are stuffed into a cell (pretty obvious) :-[ low-level phenomenon? You mean a manufacturer defect? An inherent defect in the flash design? Implementation defect? All flash is inherently error prone. That's why long ECC codes are employed as recommended by the flash chip manufacturers Some other studies suggest that very high density chips may exhibit similar problems even when *_reading_* during a power fail! Ouch. My conclusions lean to removing power only when ALL accesses to flash have completed. What technologies were used to reach your conclusion? Filesystems, flash device, etc. From the mid 1990s. Everything from raw NAND, NOR flash chips with ASIC or software ECC controllers/wear leveling. USB/SD/CompactFlash. File systems UBIFS, XFS, Ext2/3/4, FAT, and some proprietary sequential only file systems with embedded EDC/ECC. Why is this technology wide spread if it's got an inherent flaw? Cheap, and with the right controllers, reliable. Wikipedia has a good basic introduction to the technology with some more authoritative citations. For greater depth some of the manufacturers' data sheets may be helpful. http://en.wikipedia.org/wiki/Flash_memory http://www.micron.com/products/nand-flash -- 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] i2c via bonescript under Debian
I get that same result using '/dev/i2c-2' as '/dev/i2c-0. Ant other suggestions? --Mark -- 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] i2c via bonescript under Debian
Oops, I mean the same as '/dev/i2c-1 --Mark -- 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] Tesseract-ocr installation on beaglebone
Why don’t you just install Ubuntu on the white? I have it working perfectly. You will need an 8GB uSD card. Just Google “Beaglebone Ubuntu” http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of robert.g.gr...@gmail.com Sent: Thursday, March 27, 2014 8:13 PM To: beagleboard@googlegroups.com Subject: [beagleboard] Tesseract-ocr installation on beaglebone Hi everyone, Right now I am working on an embedded system using my BeagleboneA6 (white) and I'm trying to install tesseract-ocr. Unfortunately, I am not very familiar with Linux so I was trying to follow these steps http://miphol.com/muse/2013/05/install-tesseract-ocr-on-ubunt.html I know that the instructions above are for Ubuntu and not Angstrom, but I gave it a try and failed. Can anyone help me out? Thanks in advance, Robert -- 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: 2014.0.4354 / Virus Database: 3722/7258 - Release Date: 03/27/14 -- 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] Beagle Black Questions
I just ordered my first Black today. I have been using RPi's for awhile but due to the lousy USB interface I wanted to try the Black. Anyhow I have a few questions. I plan to run Debian and I see I have the option of running it in microSD or the internal EMMC. I am not clear on the advantage/disadvantage of one vs. the other. I know I want to be able to boot at power up without pushing buttons so I suspect the EMMC image is the best choice. When an OS is flashed to EMMC the data (writable) area is Where? In RAM or MicroSD? I want to customize the OS and add my own code is this done on the microSD image and then flashed? I am not clear on how this works. Of course on the RPi the SD card is the OS and and changes you make are stored there. Maybe there is a document that explains 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.
