Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?
Pick a distributor. Place an order. Do not wait until they show stock. We are basically keeping up with the back logs at most of the distributors. As you can see we ship 700 per day and no one shows stock. Ever wonder why that is? We have 140,000 board back log at this time. A lot of those orders have only come in the last couple of months. Lead times on some parts is 26 weeks. capacity is not the issue. Gerald Gerald On Tue, Feb 18, 2014 at 1:46 AM, anil.gupta...@gmail.com wrote: I have been looking for 3+ weeks and unable to find any stock anywhere. Is there a way to see the order backlog with Circuitco and current supply capability? Is the issue getting better or worse? (My anecdotal experience suggests it may be getting worse.) The current situation is frustrating. If the news is bad, let us know it early and deal with it. Right now, there is no data at all. Gerald: thanks for your timely and open updates. On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote: We are focused on the community. Feel free to build it yourself however. All the materials to build it are provided for free and you don't have to pay any development costs. Gerald -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?
On Tue, 18 Feb 2014, Gerald Coley wrote: Pick a distributor. Place an order. Do not wait until they show stock. We are basically keeping up with the back logs at most of the distributors. As you can see we ship 700 per day and no one shows stock. Ever wonder why that is? We have 140,000 board back log at this time. A lot of those orders have only come in the last couple of months. Lead times on some parts is 26 weeks. wow ... i'm glad i have a drawerful at home. :-) rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Is there a 'latest stable build' of Angstrom available, and changed regularly?
John Syn john3...@gmail.com wrote: Then download the Angstrom repo and build what you want. If this is too complicated for you, then stay with Robert¹s Debian builds. Robert does an amazing job of keeping everything current and he is the best at responding to issues. I'm quite happy to build stuff myself. That's not the issue. The problem is the lack of clarity about Angstrom releases, their stability. etc. Angstrom is stable, but it isn't going anywhere. Given that the Beagle group are migrating to Debian, I like many others have made that migration also. Robert's Debian image can do everything Angstrom can do and more. OK, sounds good to me, I'd be very happy with Debian. It would be nice to see this stuff (proposed migration to Debian etc.) more upfront though. -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] When to allow inputs - after SYS_RESET or VDD_3V3B?
The BBB manual says both these things about applying inputs to the I/O pins:- NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES HIGH. Do not drive any external signals into the I/O pins until after the VDD_3V3B rail is up. So, do these actually mean basically the same thing, or if not, which one is actually correct? Using the VDD_3V3B to gate external input is much easier because of its greater current capability but both are available on the headers so one could use either. (Or even worse, is it *really* an AND requirement?) When the BBB is powered down will these two signals go low early enough so that input signals gated by them will be removed in time? -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Is there a 'latest stable build' of Angstrom available, and changed regularly?
On Tue, Feb 18, 2014 at 7:53 AM, c...@isbd.net wrote: John Syn john3...@gmail.com wrote: Then download the Angstrom repo and build what you want. If this is too complicated for you, then stay with Robert¹s Debian builds. Robert does an amazing job of keeping everything current and he is the best at responding to issues. I'm quite happy to build stuff myself. That's not the issue. The problem is the lack of clarity about Angstrom releases, their stability. etc. Angstrom is stable, but it isn't going anywhere. Given that the Beagle group are migrating to Debian, I like many others have made that migration also. Robert's Debian image can do everything Angstrom can do and more. OK, sounds good to me, I'd be very happy with Debian. It would be nice to see this stuff (proposed migration to Debian etc.) more upfront though. Well, if you don't read beagleboard.org/blog or the topics labeled debian: test images (date) that just can't be helped. ;) Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Detecting a Beaglebone IP Addtress
Last night I set up a VM (Ubuntu 12.04 with Virtual Box) and was able to plug my BBB in via USB, have the VM take control of the USB and then ssh 192.168.7.2 and talk to the beagle. This seems like the easiest way to set up the beagles. --Mark On Monday, February 17, 2014 10:33:10 PM UTC-5, Walter Schilling wrote: Thanks for all the ideas. This is the direction I plan on going now that I've made it work. As a side note, if you are trying this, make sure you have your VM in Bridges mode and not NAT mode. NAT will not work, but it works fine once you go into bridged mode. I just about strangled myself after I messed with it for a few hours thinking I had something really wrong with my hosts files only to change this and have it work. On Friday, February 14, 2014 10:34:22 AM UTC-6, RobertCNelson wrote: On Fri, Feb 14, 2014 at 10:22 AM, Walter Schilling schi...@msoe.eduwrote: Thanks for all of the responses. A couple of additional aspects to the problem: #1 I don't have access to the routers to adjust their setup, as that is controlled by our IT department that doesn't want to deal with configuration in that manner. #2 Students may work at home / dorms with a different network confiuration. I'm entrigued by the idea of writing the IP address to a file at boot. If I did that, then I probably could connect via usb and read that file back. I'll have to try that and see if I can get that working reliably. I've also thought about a program that blinked the lights on the board to display the ip, but I';m not sure that will be reliable either. (Hint: Maybe that would be a cool heartbeat to build into the onboard leds for this reason.) fyi: if you look closely at the debian testing images i've been pushing, the ip address is listed on the serial console above the login prompt.. However with systemd, it boots to fast, so eth0 is usually never updated (it's a race between getting ip and the init script that updates /etc/issue). Otherwise give each board a unique host name.. then user can just ssh root@unquie-hostname.local Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: When to allow inputs - after SYS_RESET or VDD_3V3B?
Gerald Coley ger...@beagleboard.org wrote: On Tue, Feb 18, 2014 at 8:08 AM, c...@isbd.net wrote: The BBB manual says both these things about applying inputs to the I/O pins:- NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES HIGH. Do not drive any external signals into the I/O pins until after the VDD_3V3B rail is up. So, do these actually mean basically the same thing, or if not, which one is actually correct? Using the VDD_3V3B to gate external input is much easier because of its greater current capability but both are available on the headers so one could use either. (Or even worse, is it *really* an AND requirement?) When the BBB is powered down will these two signals go low early enough so that input signals gated by them will be removed in time? SYS_RESET is the safest way to do it as it is a signal that can be used with enough delay to allow the 3V3B to settle. The desired requirement is after the 3V3B is up. But that is not a nice signal to track as it is a voltage rail. Easy is not always the best way. OK, it makes little odds really as there will be some sort of logic driven by either SYS_RESET or 3V3B so the current drive will be minimal. Power down is in the reverse order of power up. Once 3V3B is removed your circuitry should be powered down at that point. So if I used a device powered by the 3V3B to drive the ADC voltage input (obviously potted down to a maximum of 1.8 volts) would that be safe enough? E.g. an op-amp in follower mode? -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] fried - replacement?
Same basic design. Gmail is coming back with Connection timed out after emailing the RMA. I couldn't submit the form since I use Gmail so I emailed directly with the email address from the page source. - Grant Well, I would love to answer you, but I am not sure what you are asking for. Just wondering if a Black is less likely to die than a White. - Grant What sort of tolerances? Higher than what? Not knocking it, just looking for info. - Grant Beagleboard.org is working fine. Follow the process. http://beagleboard.org/Support/RMA The little guy seems to have magically healed himself! Is this sort of thing fairly common? Unfortunately it has crapped out again in the middle of operation. I'll submit the RMA form. Out of curiosity, is the Black designed with higher tolerances? - Grant My Beaglebone White seems to be fried. I have a spare so I popped the SD card into that one and it works fine. Can I send it in for replacement? - Grant You should use the RMA form on the on beagleboard.org site. I would post a link but beagleboard.org seems down right now and cant get the actual link without the long google search stuff added on. So just google beagleboard RMA and should be the first result. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?
what distributors accept orders when they are out of stock. On Tue, Feb 18, 2014 at 8:45 AM, Robert P. J. Day rpj...@crashcourse.cawrote: On Tue, 18 Feb 2014, Gerald Coley wrote: Pick a distributor. Place an order. Do not wait until they show stock. We are basically keeping up with the back logs at most of the distributors. As you can see we ship 700 per day and no one shows stock. Ever wonder why that is? We have 140,000 board back log at this time. A lot of those orders have only come in the last couple of months. Lead times on some parts is 26 weeks. wow ... i'm glad i have a drawerful at home. :-) rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Eric Palmer -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Issue with P8, P9 Connectors not fitting on the BeagleBoneBlack (BBB) PCB
Thank you for the speedy response Gerald. The PCB files used were those contained in Beaglebone_blackrevB4_MFG.zip Is it likely the holes were deliberately under-sized to the datasheet to give the tight fit you mention. I am yet to see the problem physically for myself. The PCB supplier is sending the board to me so I can assess. On Tuesday, 18 February 2014 13:43:18 UTC, Gerald wrote: We don't have any issues. We do look for a tight fit to prevent moving during the soldering process. We have used these same connectors for a very long time now without issue. Which PCB files did you use? Gerald On Tue, Feb 18, 2014 at 6:41 AM, lee@bibby-scientific.comjavascript: wrote: I hope someone can help with this. I am currently getting some BBB PCBs manufactured. I have used the gerber data and BoM supplied but the PCB manufacturer is reporting an issue with the specified connectors not fitting because the PCB hole size is too small to take the pins. The connector specified is: SSHS-123-D-02-GT-LF which has recommended hole size of 0.040 (1.2mm) The PCB manufacturer is telling that the hole size in the drill file is: T04 Holesize 4. = 30.00 Tolerance = +3.00/-3.00 PLATED MILS Quantity = 96 The data I have sent to them is from the file: Beaglebone_blackrevB4_MFG.zip I am unsure what has happened here. Obviously these boards can be manufactured with the data. I'd be grateful of any input and also if anyone can specify a connector that will fit holes of that size? Many 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/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: When to allow inputs - after SYS_RESET or VDD_3V3B?
That should be OK. Gerald On Tue, Feb 18, 2014 at 9:33 AM, c...@isbd.net wrote: Gerald Coley ger...@beagleboard.org wrote: On Tue, Feb 18, 2014 at 8:08 AM, c...@isbd.net wrote: The BBB manual says both these things about applying inputs to the I/O pins:- NO PINS ARE TO BE DRIVEN UNTIL AFTER THE SYS_RESET LINE GOES HIGH. Do not drive any external signals into the I/O pins until after the VDD_3V3B rail is up. So, do these actually mean basically the same thing, or if not, which one is actually correct? Using the VDD_3V3B to gate external input is much easier because of its greater current capability but both are available on the headers so one could use either. (Or even worse, is it *really* an AND requirement?) When the BBB is powered down will these two signals go low early enough so that input signals gated by them will be removed in time? SYS_RESET is the safest way to do it as it is a signal that can be used with enough delay to allow the 3V3B to settle. The desired requirement is after the 3V3B is up. But that is not a nice signal to track as it is a voltage rail. Easy is not always the best way. OK, it makes little odds really as there will be some sort of logic driven by either SYS_RESET or 3V3B so the current drive will be minimal. Power down is in the reverse order of power up. Once 3V3B is removed your circuitry should be powered down at that point. So if I used a device powered by the 3V3B to drive the ADC voltage input (obviously potted down to a maximum of 1.8 volts) would that be safe enough? E.g. an op-amp in follower mode? -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?
for North America: http://www.newark.com/circuitco/bb-bblk-000/dev-board-am3358-59-arm-mpu-beaglebone/dp/65W6016 Place an order now and you will be in the queue. I believe you won't be charged until it ships and can cancel it at anytime until it ships too. The amount that will be available when back in stock will be stock minus backorders. So it is possible for it to say 10,000 arriving on X date and then on X date there be 0 because those all went to backorders. for Europe: http://uk.farnell.com/circuitco/bb-bblk-000/beaglebone-black-cortex-a8-dev/dp/2291620 cheers, drew On Tue, Feb 18, 2014 at 9:04 AM, Eric Palmer e...@ericfpalmer.com wrote: what distributors accept orders when they are out of stock. On Tue, Feb 18, 2014 at 8:45 AM, Robert P. J. Day rpj...@crashcourse.cawrote: On Tue, 18 Feb 2014, Gerald Coley wrote: Pick a distributor. Place an order. Do not wait until they show stock. We are basically keeping up with the back logs at most of the distributors. As you can see we ship 700 per day and no one shows stock. Ever wonder why that is? We have 140,000 board back log at this time. A lot of those orders have only come in the last couple of months. Lead times on some parts is 26 weeks. wow ... i'm glad i have a drawerful at home. :-) rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Eric Palmer -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: When to allow inputs - after SYS_RESET or VDD_3V3B?
Gerald Coley ger...@beagleboard.org wrote: So if I used a device powered by the 3V3B to drive the ADC voltage input (obviously potted down to a maximum of 1.8 volts) would that be safe enough? E.g. an op-amp in follower mode? That should be OK. OK, thanks for the very quick replies. -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Build a QT/11 application for beagleboard black by cross compiling from ubuntu
Hello, so did you find a way to cross-compile Qt with X11 support for BBB with an armhf (Debian or Ubuntu) file 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/groups/opt_out.
[beagleboard] Accuracy of 1.8 volt reference on BBB?
What's the accuracy of the 1.8 volts VADC reference voltage on the BBB? Or, more to the point, what's its stability? It's easy enough to calibrate voltage measurements by using an accurate voltmeter to measure the same voltage and then scaling the result appropriately in software but if the 1.8 volts reference isn't reasonably stable then one is wasting one's time. -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] image with motion and gpio
Hi, any one could help with a image of any linux distro that could have motion (or similar) and/or gpio? I did with ubuntu but the cpu is 80% almost all the time. -- Marcus de Vasconcelos Diogo da Silva Uma montanha até um cego consegue desviar,mas é nas pedras menores que nós muitas vezes tropeçamos e caimos! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] I2C SDA spikes?
I think I have seen those on my scope during I2C transactions as well. They look like little shark fins that sometimes get high enough to be seen as a logic 1. They have no impact on the device as it's just the transition time between when the master is done transmitting the device address and starting to send data. The data line is released by the device but the master has not started to place data on the wire yet so the line starts to float back up via the pull-up. In your photo, it happens on the falling edge of the 9th clock bit and it's gone before the rising edge of the 10th clock so it's not being read as data. Stronger pull-ups will just assist the runt in rising faster since the lower resistance allows the data line capacitance to be charged faster. On the scope you'd see the shark-fin start getting taller as you reduce the resistance. Your logic analyzer is just showing the brief time that the runt was interpreted as a logic 1 by the logic analyzer. Data isn't clocked in until SCL goes from low to high. I think what you are chasing there is a red herring. The Logic analyzer shows both data values being what they ought to be. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: problems with webcams
My first question for you would be which pixel format are you capturing in? If you do a v4l2-ctl -d /dev/videoX --list-formats-ext in the command line (where X is 0, 1, ... whatever your C920 is) you can see the various pixel formats, resolutions, and frame rates supported by the camera. For YUYV, the maximum frame rate at 1280x720 is 10 fps. If you are using H.264 or MJPEG, the maximum frame rate is 30 fps. I'm doubtful that that's your problem since you are still only getting 15 fps at lower resolutions. (Can you get 30 fps at 640x480? That is the resolution I am using for my own project and might serve as a good baseline measurement.) My only other thought for now is that your actual measurement of the frame rate could be wrong. I don't have much experience with pthreads, but I know that some of the clock functions in the ctime header have to be handled differently when you are multi-threading. Those are my only ideas for now. I'll keep racking my brain and let you know if I come up with something else. - Mike On Sun, Feb 16, 2014 at 10:57 AM, qscw...@gmail.com wrote: Hello, ive been reading through the group and found i have found it very helpful. i am running an odroid u2 with ubuntu 12.11 and opencv 2.4.6.1. i used the code i found in git :/mdarling39/https://github.com/mdarling39/LinuxVision/blob/master/OCVCapture.cppto capture from a logitech c920. i ran into an issue when i set the resolution to 1280*720 the fps would not go past 10. however for any smaller resolution i am able to get 15 fps no problem. the custom capture code certainly does use less resources than the built in opencv function. i have 2 threads, the main for capturing and the second for processing both of which do not max out their cpu so i cant figure out why im getting this fps drop. any help would be appreciated. Thanks On Thursday, January 30, 2014 3:17:40 PM UTC-5, Matthew Witherwax wrote: If you bypass OpenCV and capture directly like we did, you should test to see if you can capture successfully in YUYV format. OpenCV can convert YUYV to a Mat with less than 3% cpu use. If you capture in MJPEG, you will see cpu use of 90% or more to convert the image to a Mat. This isn't so bad on the Wandboard because it only consumes one core, but can be intense on the single core BBB. I can tell you from testing with the Wandboard Quad, it can push 30 fps in YUYV over USB. However, it is only possible to stream from one camera at 30 fps in YUYV. In short it is a tradeoff. You can either saturate the USB and save processing or save bandwidth and increase processing. Something to consider depending on your needs. On Thu, Jan 30, 2014 at 12:53 PM, Michael Darling fndrpl...@gmail.comwrote: Okay, so the problem you're having has to do with bugs in OpenCV, itself. Unfortunately, the capture methods in OpenCV do not set the camera properties correctly for video4linux devices. In other words, you may write the line of code to set the frame rate to 30 fps, but the camera isn't actually getting the instruction to change the frame rate. The fix Matthew and I have used is to just use our own video4linux capture code. You might be able to modify the OpenCV source code, but the capture code is difficult to follow since there are so many layers of abstraction. (There are a lot of wrapper classes used to handle v4l2 devices, v4l1 devices, Mac, Windows so that the programmer doesn't have to handle each camera differently depending on his/her system.) Hope that explains some things for you :) - Mike -- 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/G5Xs2JuwD_4/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/G5Xs2JuwD_4/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Getting HDMI to work with Angstrom 2013.06.20
I've had very little luck trying to get HDMI to work with my BBB. When booting off the eMMC I get the BeagleBone splashscreen and then nothing after that. From reading the support forums, I gather that this is because BBB is not getting the proper resolution information from my monitor. I tried booting it with no HDMI TV attached and then plugging in the monitor after it was fully booted to try to force it into the default resolution, but that didn't work either. I was able to boot off a USB cable connection to my computer and then SSH to it, but, of course, that's not going to get me a GUI. So... I downloaded the latest image (2013.06.20) and put it on an SD card. I applied power while holding down the reset button while connected to the HDMI monitor. This time I got the splashscreen and also got the login prompt (progress, at least) Shortly thereafter it disappeared and I saw nothing further on the monitor. I assume this is because it started up the GUI interface in a resolution my monitor doesn't support. When using the June 20th image, I find that I can no longer SSH to the board. Is that because it's running X? I can think of two ways forward: 1. Get a serial FTDI cable, and do some editing as per the HDMI troubleshooting section. 2. Perhaps I could boot off the eMMC and edit some files to force a different resolution on boot? The thing is, I'm about to start marketing a TNC cape for this board and I'm now beginning to think I may be letting myself in for a huge customer support headache from people who can't get their HDMI to work. What is the most likely strategy to work here. This same HDMI monitor works perfectly with my Raspberry Pi. Thanks, John Hansen -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Getting HDMI to work with Angstrom 2013.06.20
Did you try the suggestions found at http://www.elinux.org/Beagleboard:BeagleBoneBlack_HDMI Gerald On Tue, Feb 18, 2014 at 1:53 PM, coastalc...@gmail.com wrote: I've had very little luck trying to get HDMI to work with my BBB. When booting off the eMMC I get the BeagleBone splashscreen and then nothing after that. From reading the support forums, I gather that this is because BBB is not getting the proper resolution information from my monitor. I tried booting it with no HDMI TV attached and then plugging in the monitor after it was fully booted to try to force it into the default resolution, but that didn't work either. I was able to boot off a USB cable connection to my computer and then SSH to it, but, of course, that's not going to get me a GUI. So... I downloaded the latest image (2013.06.20) and put it on an SD card. I applied power while holding down the reset button while connected to the HDMI monitor. This time I got the splashscreen and also got the login prompt (progress, at least) Shortly thereafter it disappeared and I saw nothing further on the monitor. I assume this is because it started up the GUI interface in a resolution my monitor doesn't support. When using the June 20th image, I find that I can no longer SSH to the board. Is that because it's running X? I can think of two ways forward: 1. Get a serial FTDI cable, and do some editing as per the HDMI troubleshooting section. 2. Perhaps I could boot off the eMMC and edit some files to force a different resolution on boot? The thing is, I'm about to start marketing a TNC cape for this board and I'm now beginning to think I may be letting myself in for a huge customer support headache from people who can't get their HDMI to work. What is the most likely strategy to work here. This same HDMI monitor works perfectly with my Raspberry Pi. Thanks, John Hansen -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] BBB no autoboot of uSD
I can address only the part about the Windows line endings. U-boot only
works with Unix line endings.
I had edited my uEnv.txt file on my Windows box and couldn't understand why
it was complaining
about a variable; eventually I guessed that it was because of the carriage
return. As soon as I opened
the file with vi on linux I could see them. The u-boot documentation does
caution the reader about
its fussiness.
On Monday, February 17, 2014 10:17:22 PM UTC-8, Loren Amelang wrote:
Robert,
My BBB absolutely must default to booting from the uSD. I know I
could short the boot switch, or move pull-up/down resistors, or create a
hardware switch gated from reset, but I don't want to lose hardware
compatibility with other BBB boards, or give up the option of manually
booting from eMMC occasionally. The code you suggest here sounds perfect -
but I'm not positive what to do with it. From the formatting of the text, I
suspect it is intended to be compiled into a new u-boot.img and MLO image,
but I'm not sure how to do that.
Before I spend hours learning how, is there a chance I could just insert
the basic ideas into my uEnv.txt as mmcboot=mmc dev 0; if mmc rescan ;
then ...? It does look like uEnv.txt is read before the mmcboot command
runs...
If so, does it have to be run together into a single ';' separated line,
or can I leave the '\' line continuations in to make it more readable?
I suspect uEnv.txt would not want the double-quotes? Or Windows CRLF
line endings...
If that is totally hopeless, can you suggest a tutorial on building a new
u-boot.img and MLO with this code?
Thank you for any clues,
Loren
On Thursday, January 2, 2014 2:16:47 PM UTC-8, RobertCNelson wrote:
I have mine setup as the following..
+mmc dev 0; if mmc rescan ; then \
+gpio set 54; \
+setenv mmcdev 0; \
+echo SD/MMC found on device ${mmcdev}; \
+if run loadbootenv; then \
+run importbootenv; \
+fi; \
+gpio set 55; \
+echo Checking if uenvcmd is set ...; \
+if test -n $uenvcmd; then \
+gpio set 56; \
+echo Running uenvcmd ...; \
+run uenvcmd; \
+fi; \
+echo; echo uenvcmd was not defined in uEnv.txt ...;
echo trying eMMC (BeagleBone Black) ...; echo; \
+fi; \
+mmc dev 1; if mmc rescan ; then \
+gpio set 54; \
+setenv mmcdev 1; \
+echo SD/MMC found on device ${mmcdev}; \
+if run loadbootenv; then \
+run importbootenv; \
+fi; \
+gpio set 55; \
+echo Checking if uenvcmd is set ...; \
+if test -n $uenvcmd; then \
+gpio set 56; \
+echo Running uenvcmd ...; \
+run uenvcmd; \
+fi; \
+echo; echo uenvcmd was not defined in uEnv.txt ...;
echo halting ...; echo; \
+fi; \
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: After hotplug ging USB mass storage device system hang.
You could file a bug report with ubuntu folks; it looks like something isn't right in the kernel code. Can you try it with Debian Linux installed instead of Ubuntu? On Monday, February 17, 2014 11:04:03 PM UTC-8, Kishor Dhanawade wrote: Hello, I am using a Beaglebone black board wuth ubuntu 12.04 (3.8.13-kernel). My board is working very good with eMMC as well as with with SD card. Problem is when I hotplug a USB mass storage device(pendrive) whole system getting hang. Then if I powered off and again powered ON with pendrive then its working properly and pendrive is also detecting. Problem is only during hotplug. Also I tried to debug through the serial debug port but I am newbie so I didn't get the issue. Serial debug port output is as follows. ubuntu-armhf login: tilcdc 4830e000.fb: timeout waiting for framedone usb 1-1.4: new high-speed USB device number 5 using musb-hdrc usb 1-1.4: New USB device found, idVendor=0781, idProduct=5567 usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.4: Product: Firebird USB Flash Drive usb 1-1.4: Manufacturer: SanDisk usb 1-1.4: SerialNumber: 4C5326071374 scsi0 : usb-storage 1-1.4:1.0 scsi 0:0:0:0: Direct-Access SanDisk Cruzer Blade 1.26 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA *BUG: spinlock bad magic on CPU#0, kworker/u:2/62* lock: 0xdf4cfee8, .magic: , .owner: none/-1, .owner_cpu: 0 [c0014660] (unwind_backtrace+0x0/0xe0) from [c02420e8] (do_raw_spin_lock+0x20/0x164) [c02420e8] (do_raw_spin_lock+0x20/0x164) from [c02c1278] (get_device_parent+0x84/0x18c) [c02c1278] (get_device_parent+0x84/0x18c) from [c02c1904] (device_add+0xcc/0x580) [c02c1904] (device_add+0xcc/0x580) from [c0226358] (add_disk+0x1a8/0x40c) [c0226358] (add_disk+0x1a8/0x40c) from [c02efaf8] (sd_probe_async+0xec/0x1a8) [c02efaf8] (sd_probe_async+0xec/0x1a8) from [c005f87c] (async_run_entry_fn+0xe8/0x204) [c005f87c] (async_run_entry_fn+0xe8/0x204) from [c0054b70] (process_one_work+0x240/0x3fc) [c0054b70] (process_one_work+0x240/0x3fc) from [c005514c] (worker_thread+0x258/0x370) [c005514c] (worker_thread+0x258/0x370) from [c0058d70] (kthread+0xa0/0xb0) [c0058d70] (kthread+0xa0/0xb0) from [c000d918] (ret_from_fork+0x14/0x3c) *Unable to handle kernel NULL pointer dereference at virtual address 0008* pgd = c0004000 [0008] *pgd= Internal error: Oops: 5 [#1] SMP ARM Modules linked in: binfmt_misc unix CPU: 0Tainted: GW (3.8.13-bone26 #272) PC is at get_device_parent+0x94/0x18c LR is at spin_bug+0x10/0x28 pc : [c02c1288]lr : [c04821a8]psr: 0013 sp : df3d3df8 ip : c000d918 fp : c08122dc r10: ddca98c8 r9 : c07d2408 r8 : df3d40b0 r7 : df51080c r6 : ddca98d0 r5 : df510868 r4 : df510868 r3 : df4cfee0 r2 : r1 : r0 : fffc Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 9f5f4019 DAC: 0015 Process kworker/u:2 (pid: 62, stack limit = 0xdf3d2240) Stack: (0xdf3d3df8 to 0xdf3d4000) 3de0: ddc526c0 df510868 3e00: df510870 df51080c c02c1904 df510870 c02358ac 3e20: ddca98c8 df510800 dd8e0e40 df510800 dd8e0e40 df510868 df51080c df3d40b0 3e40: c07d2408 ddb04600 c08122dc c0226358 c0225360 df510800 df00 0080 3e60: 0004 c0c76e80 df4e1c00 df510800 df4e1c00 df510800 ddca9800 3e80: ddb04608 ddb04600 c02efaf8 df4e1c00 c02efa0c 0002 df39dbc0 3ea0: ddb04608 c0812200 df03f800 c005f87c c07d0da8 c07d0da8 c0812200 df3a9600 3ec0: c0812318 0001 df39dbc0 ddb04608 c0812200 df03f800 c0812318 3ee0: c0054b70 df061e8c 0001 0003 0001 df39dbc0 3f00: c0812318 df3d2000 c07ec6b8 c0812200 c0812318 df39dbd4 0089 c005514c 3f20: df39dbc0 df3d3f54 df3d3f38 df061e74 df39dbc0 c0054ef4 3f40: c0058d70 942dff37 f93fdf65 df39dbc0 3f60: dead4ead df3d3f74 df3d3f74 3f80: dead4ead df3d3f90 df3d3f90 df3d3fac df061e74 3fa0: c0058cd0 c000d918 3fc0: 3fe0: 0013 90fc7cef 3cd6dee1 [c02c1288] (get_device_parent+0x94/0x18c) from [c02c1904] (device_add+0xcc/0x580) [c02c1904] (device_add+0xcc/0x580) from [c0226358] (add_disk+0x1a8/0x40c) [c0226358] (add_disk+0x1a8/0x40c) from [c02efaf8] (sd_probe_async+0xec/0x1a8) [c02efaf8] (sd_probe_async+0xec/0x1a8) from [c005f87c] (async_run_entry_fn+0xe8/0x204)
Re: [beagleboard] BBB no autoboot of uSD
From: Loren Amelang lorenamel...@gmail.com
Reply-To: beagleboard@googlegroups.com
Date: Monday, February 17, 2014 at 10:17 PM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] BBB no autoboot of uSD
Robert,
My BBB absolutely must default to booting from the uSD. I know I could short
the boot switch, or move pull-up/down resistors, or create a hardware switch
gated from reset, but I don't want to lose hardware compatibility with other
BBB boards, or give up the option of manually booting from eMMC occasionally.
The code you suggest here sounds perfect - but I'm not positive what to do
with it. From the formatting of the text, I suspect it is intended to be
compiled into a new u-boot.img and MLO image, but I'm not sure how to do that.
Before I spend hours learning how, is there a chance I could just insert the
basic ideas into my uEnv.txt as mmcboot=mmc dev 0; if mmc rescan ; then ...?
It does look like uEnv.txt is read before the mmcboot command runs...
If so, does it have to be run together into a single ';' separated line, or
can I leave the '\' line continuations in to make it more readable?
I suspect uEnv.txt would not want the double-quotes? Or Windows CRLF line
endings...
If that is totally hopeless, can you suggest a tutorial on building a new
u-boot.img and MLO with this code?
Thank you for any clues,
See if this helps:
http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User's_Guide
Otherwise, read the u-boot manual.
Regards,
John
Loren
On Thursday, January 2, 2014 2:16:47 PM UTC-8, RobertCNelson wrote:
I have mine setup as the following..
+mmc dev 0; if mmc rescan ; then \
+gpio set 54; \
+setenv mmcdev 0; \
+echo SD/MMC found on device ${mmcdev}; \
+if run loadbootenv; then \
+run importbootenv; \
+fi; \
+gpio set 55; \
+echo Checking if uenvcmd is set ...; \
+if test -n $uenvcmd; then \
+gpio set 56; \
+echo Running uenvcmd ...; \
+run uenvcmd; \
+fi; \
+echo; echo uenvcmd was not defined in uEnv.txt ...;
echo trying eMMC (BeagleBone Black) ...; echo; \
+fi; \
+mmc dev 1; if mmc rescan ; then \
+gpio set 54; \
+setenv mmcdev 1; \
+echo SD/MMC found on device ${mmcdev}; \
+if run loadbootenv; then \
+run importbootenv; \
+fi; \
+gpio set 55; \
+echo Checking if uenvcmd is set ...; \
+if test -n $uenvcmd; then \
+gpio set 56; \
+echo Running uenvcmd ...; \
+run uenvcmd; \
+fi; \
+echo; echo uenvcmd was not defined in uEnv.txt ...;
echo halting ...; echo; \
+fi; \
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Cross Compile Qt on BBB issue
From: Franck freedev franckfree...@gmail.com Reply-To: beagleboard@googlegroups.com Date: Tuesday, February 18, 2014 at 12:28 AM To: beagleboard@googlegroups.com Subject: [beagleboard] Re: Cross Compile Qt on BBB issue Thanks for your answer.. I think the problem is that the configure command has -embedded arm option. So it's made to work with a frame buffer and without X11.. That's why I'm trying to compile it for X11 support.. In fact, you can't use framebuffer (-qws) and X11 at the same time.. you can find a discussion here about this subject: https://qt-project.org/forums/viewthread/26578 Do you really need X11? Why not use EGLFS platform? I use this with QT5.1.1 with SGX on V3.12 kernel. Regards, John -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Android running on BBB with Linux 3.8
Hi, I have Andrew Henderson's image running with LCD4 cape but now I am trying to communicate with the serial ports. I have tried modifying the init.rc to change the UART permissions as recommended in another post but that did not help. Also, I cannot access via abd. Any suggestions? Do I need to compile my own image? Many thanks for any help. Suzanne On Monday, 17 June 2013 20:00:07 UTC-4, Andrew Henderson wrote: Hello all. I posted this information over at the Google+ group for BeagleBoard.org, but I wanted to post it here as well. I have Android running on the BBB using the Jellybean (4.2.2) source from arowboat.organd the Linux 3.8.13 kernel from my BeagleSNES project ( www.beaglesnes.org). I just added the Android drivers (Drivers - Staging Drivers - Android) into the same kernel configuration that I use for BeagleSNES. This kernel is really just a stripped down configuration (a 1.9 meg zImage) using Robert Nelson's 3.8.x kernel source tree. Instead of using the GCC cross-compiler that comes in Rowboat's current prebuilt tools, I use the 3.7 GCC that comes with Robert's kernel tree to build the entire system. I also updated the u-boot to v2013.04. Here is a video of it running: https://www.youtube.com/watch?v=yeSt1Y7FhEs Here is the download of a working Android image that can be written onto a 4GB microSD card using dd: http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2 There is no hardware accelerated video in this version, since SGX support isn't ready for the 3.8 kernel. To shut off hardware accelerated video, I pass qemu=1 as a kernel command line argument in uEnv.txt and I add debug.egl.hw=0 to the /system/build.prop file in the root file system. To get rid of that blinking cursor on the framebuffer (which I accidentally left on in the image that I made), add this to the uEnv.txt kernel command line arguments: vt.global_cursor_default=0 This build will be of interest to Android experimenters who want to use HDMI for audio and video output (rather than using an LCD cape) and who want to experiment with using the device tree. My kernel is pretty stripped down, so feel free to fetch Robert's latest kernel source for the 3.8.x branch and rebuild your own kernel to drop into the image that I have supplied. That way, you can include whatever drivers you would like in your kernel. Use a USB mouse (and a keyboard, too, if you want) to interact with the system. Thanks, and enjoy! Andrew -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Cross Compile Qt on BBB issue
Well, it's because I've got a project where I have to use some gnome programs like a virtual keyboard, or launch others programs from my application and I need a windows manager... Maybe there are other ways to do this sort of things? What do you mean by GLFS platform? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] I2C SDA spikes?
On 2/18/14, 10:49 AM, k...@cranehome.info k...@cranehome.info wrote: I think I have seen those on my scope during I2C transactions as well. They look like little shark fins that sometimes get high enough to be seen as a logic 1. They have no impact on the device as it's just the transition time between when the master is done transmitting the device address and starting to send data. The data line is released by the device but the master has not started to place data on the wire yet so the line starts to float back up via the pull-up. In your photo, it happens on the falling edge of the 9th clock bit and it's gone before the rising edge of the 10th clock so it's not being read as data. Stronger pull-ups will just assist the runt in rising faster since the lower resistance allows the data line capacitance to be charged faster. On the scope you'd see the shark-fin start getting taller as you reduce the resistance. Your logic analyzer is just showing the brief time that the runt was interpreted as a logic 1 by the logic analyzer. Data isn't clocked in until SCL goes from low to high. I think what you are chasing there is a red herring. The Logic analyzer shows both data values being what they ought to be. Unless your lines are very long, there is probably nothing wrong with your I2C signals. My guess is you have a long ground wire on your oscilloscope probe and this is causing the ringing. Use a high speed probe (small distance between measurement tip and ground pin) and I¹m sure the signals will look a lot cleaner. The long ground wire is acting like an antenna. Regards, John -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Availability - how come nobody has any BeagleBone Black to sell?
as gerald stated, circuitco is in full production of the beaglebone black and continues to ship daily to a wide range of distributors. these distributors fill back-orders first before showing stock. http://elinux.org/Beagleboard:BeagleBoneBlack#Board_Shipments Dave On Tuesday, February 18, 2014 1:46:30 AM UTC-6, anil.g...@gmail.com wrote: I have been looking for 3+ weeks and unable to find any stock anywhere. Is there a way to see the order backlog with Circuitco and current supply capability? Is the issue getting better or worse? (My anecdotal experience suggests it may be getting worse.) The current situation is frustrating. If the news is bad, let us know it early and deal with it. Right now, there is no data at all. Gerald: thanks for your timely and open updates. On Wednesday, February 12, 2014 1:25:00 AM UTC+5:30, Gerald wrote: We are focused on the community. Feel free to build it yourself however. All the materials to build it are provided for free and you don't have to pay any development costs. Gerald -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Accuracy of 1.8 volt reference on BBB?
c...@isbd.net wrote: Gerald Coley ger...@beagleboard.org wrote: [-- text/plain, encoding quoted-printable, charset: ISO-8859-1, 38 lines --] Check the datasheet of the PMIC. Of course, thanks. However the Sitara AM335x processor can use either an external or an internal voltage reference, which does it use on the BBB? -- Chris Green · -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Accidentally erased onboard Flash
Explore this: http://elinux.org/BeagleBoneBlack On Tuesday, February 18, 2014 1:26:08 PM UTC-8, JBodine wrote: So, I had the BBB running from its own flash, while connected to my laptop. I also had a micro SD inserted in my lap top, preparing to load it with an image I downloaded. My intent was to format the micro SD, instead I formatted the BBB flash, which appeared on my computer as another drive. Doh!!! Now, if I reboot, with no sd card, I only get a shell prompt. I can boot from the sd card with an image loaded but I'd like to re-image the flash.I tried loading the image on my sd that is supposed to flash the eMMC but that doesn't seem to work. Any suggestions? Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: WL1835MOD with Chip Antenna Watch
An automated TI forum email alerted me to this. Hopefully now the cape with work with the BBB, although I have yet to try this: http://processors.wiki.ti.com/index.php/Using_the_WL18xx_Cape_with_BeagleBone_Black Thanks, Markus On Wednesday, December 4, 2013 4:48:33 PM UTC-5, M Robinson wrote: Hi, Since circuitco has made the WL1835MOD with Chip Antenna http://boardzoo.com/index.php/beaglebone/beaglebone-wl1835mod-w-chip-antenna.html#.Up-hpeKQPUAin some limited quantities (and I was lucky to get an early one), and there is promise to add BB Black support for this capehttp://e2e.ti.com/support/low_power_rf/f/307/p/301373/1061878.aspx#1061878at some undetermined date, and because the amount of information is still limited on the board itself, I want to add this 'watch' thread. In the meant time I'm keeping an eye on TI's WL18xx Wikhttp://processors.wiki.ti.com/index.php/WL18xx?DCMP=wilink8HQS=wilink8wiki i. If anyone has information not available on the official sources, I think this would be a good place for that. Sincerely, Markus -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: How do I deal with the missing omap_mux directory in /sys/kernel/debug?
The BBB uses 3.8 or higher version kernel. It does not have any omap_mux, but it has Device Tree Overlays instead. For me all of the capable pins were in GPIO mode (mode 7), however you can change their modes by passing arguments to /sys/devices/bone_capemgr*/slots For example the echo cape-bone-iio /sys/devices/bone_capemgr.*/slots will enable the cape analog input mode. You can disable cape modes with echo -N /sys/devices/bone_capemgr*/slots N is the number of a particular mode. You can see them, if you cat out the slots file. If you programming with C (very good decision) you should use fprintf(FILE_pointer_to_slots, cape-bone-iio) with the popper context of course (like opening the file for reading etc...). For more info: http://elinux.org/BeagleBone_and_the_3.8_Kernel#Cape_Manager_and_Device_Tree_Overlays I see your question is old, but when I searched this problem I also read this thread... for nothing. So maybe it will helpful to others as well. On Wednesday, January 8, 2014 3:39:51 AM UTC+1, BeagleNoob wrote: So I was following another one of Derek Molloy's videos on using the BBB, this time on GPIO's: Beaglebone: GPIO Programming on ARM Embedded Linuxhttp://www.youtube.com/watch?v=SaIpz00lE84lc=JdlhUeEi_0kNlx7vRz8dghZ_nQ8L88nz0CacbSxxovw Around 8:00, he goes into a directory called omap_mux in the sys/kernel/debug directory, but I don't see it in my BBB. I've Googled around and found that a lot of people have this problem, but couldn't find a real solution. As far as I understand this directory is supposed to have all the pins for GPIO. Is that correct? How can I get around this to access GPIO? Thanks for any help with this! :-) FYI, when I run *uname -a* I get the following output: Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] BBB won't boot with sdCard in place
Howdy, I've been using on board Angstrom on my tethered BBB; rsh and can compile, set date, etc. Attached ethernet and can rsh from my laptop. Most excellent. Picked up a couple of 32B micro SDCards, but BBB won't boot with them installed: 1. Power off, insert FAT32 formated card in slot 2. Apply power (not trying to boot, no buttons pressed) 3. Get power LED, and all of the user LEDs lit. Nothiing else happens I assumed a power issue from the microUSB (attached to a MAC). Picked up a AdaFruit 276 1A power supply. Same results: * Only power supply and ethernet cable attached: 1. Boot with no sd card inserted - no problem 2. Boot with any sd card inserted - all LEDs lit, nothing happens. Am I doing something wrong? Suggestions? Randy -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: VNC on BBB from the very beginning (possible)?
Dear sir, i have tried all the above solutions but when i use vncviewer (using vncviewer 192.168.7.2:5900), I get the following error vncviewer: ConnectToTcpAddr: connect: Connection refused Unable to connect to VNC server please help. i have tried rebooting many times and i have also execute *x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth /var/run/gdm/auth-for-gdm*/database -display :0 - forever - nopw on BBB*. I am using kali linux. On Monday, May 20, 2013 2:23:38 PM UTC-4, Rob Weijers wrote: You still have to activate the command after each reboot of the BBB. To avoid this store the already used command: *x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth /var/run/gdm/auth-for-gdm*/database -display :0 - forever - nopw* *Into a file e.g. x11vncremote.sh. *Don't forget to change the file's permission to allow execution.* And add the file as a command to the startup (on the desktop: System-preferences-Statup Applications. * *Now you can connect anytime you want to the BBB without the need for Gate one.* *I already had this running, but it did not allow me to restart once the connection was closed. Thanks to Wilfredo this is solved. * *Rob.* -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: BBB won't boot with sdCard in place
Forgot to add that I can insert, mount and inspect the same card after the BBB is up and running. The issue is that I can't power on boot with a card installed. Randy -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Customizing BBB Angstrom Kernel?
I started to try to debug the board at home, and it actually did show up on my dhcp list. So I do have SSH access! Here is my /etc/network/interfaces file. auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto usb0 iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 auto wlan0 iface wlan0 inet static address 10.42.0.1 netmask 255.255.255.0 wireless-essid Capstone wireless-mode ad-hoc I guess I assumed NetworkManager was tied to /etc/network/interfaces... which I think is wrong... On Tuesday, February 18, 2014 1:28:48 PM UTC-5, Mark Hatch wrote: Thanks Richard, you really have been an enormous help in this process, and I feel much more comfortable with this. Thank you for helping, I really have already learned a lot more. Right now I'm trying to tweak the bitbake recipes a bit. I'd like to remove connman and install networkmanager instead. Connman apparently does not have ad-hoc wireless support... All I'm trying to do is get my beagles to autojoin the ad-hoc network on startup. I initially had some init.d scripts that would use ifconfig and iwconfig to set up the network, but for some reason these would not work totally correctly. The static IP would be correct, but in iwconfig it would not be set up with the ad-hoc network defined... I also followed this guide, set up the service as was discussed in the link, but it did not function correctly either. http://octopusprotos.com/?p=37 I tried removing connman with opkg and installing networkmanager, since I noticed I did not have a networking service (/etc/systemd/networking or whatever it is)... (this was a n00b mistake). I ended up losing ssh access... and now am unable to talk to the board. I guess if I had a serial cable I could debug the board, but right now it doesn't get an IP address (I checked the router's IP tables and it wasn't there) and the default USB 192.168.7.2 doesn't work either (I'm assuming connman used to set that up, but that was removed.) Right now the plan is to edit the bitbake recipes to remove connman and have networkmanager built instead. Then reflash the board. I have a feeling that there may be an easier way... Thanks again for the help, 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/groups/opt_out.
Re: [beagleboard] BBB won't boot with sdCard in place
From: Randy Merkel rmer...@acm.org Reply-To: beagleboard@googlegroups.com Date: Tuesday, February 18, 2014 at 4:31 PM To: beagleboard@googlegroups.com Subject: [beagleboard] BBB won't boot with sdCard in place Howdy, I've been using on board Angstrom on my tethered BBB; rsh and can compile, set date, etc. Attached ethernet and can rsh from my laptop. Most excellent. Picked up a couple of 32B micro SDCards, but BBB won't boot with them installed: 1. Power off, insert FAT32 formated card in slot 2. Apply power (not trying to boot, no buttons pressed) 3. Get power LED, and all of the user LEDs lit. Nothiing else happens I assumed a power issue from the microUSB (attached to a MAC). Picked up a AdaFruit 276 1A power supply. Same results: * Only power supply and ethernet cable attached: 1. Boot with no sd card inserted - no problem 2. Boot with any sd card inserted - all LEDs lit, nothing happens. Am I doing something wrong? You need a serial cable attached as a console so that you can see where the boot it is failing. Since the LEDs light up tells us that u-boot is working but little else. We need the console log to see what is wrong. Regards, John Suggestions? Randy -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Customizing BBB Angstrom Kernel?
Hi, If you want to use /etc/network/interface as a configuration file you start the network services with the command *ifup -a*. If you can define the wifi interface in /etc/network/interface then it will automatically started as well. ie I am talking about a static configuration, where the network interfaces are configured and started just after boot (using system). It is assumed the wifi dongle remains permanently plugged into the bbb. Netmanager is useful for dynamic situations. ie You want automatic detection of your wi-fi dongle whenever it is plugged in. Netmanager will allow you to specify a static IP address for the Ethernet interface. You will need to have a look at the man pages. Regards ... On Wednesday, February 19, 2014 1:57:41 PM UTC+11, Mark Hatch wrote: I started to try to debug the board at home, and it actually did show up on my dhcp list. So I do have SSH access! Here is my /etc/network/interfaces file. auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto usb0 iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 auto wlan0 iface wlan0 inet static address 10.42.0.1 netmask 255.255.255.0 wireless-essid Capstone wireless-mode ad-hoc I guess I assumed NetworkManager was tied to /etc/network/interfaces... which I think is wrong... On Tuesday, February 18, 2014 1:28:48 PM UTC-5, Mark Hatch wrote: Thanks Richard, you really have been an enormous help in this process, and I feel much more comfortable with this. Thank you for helping, I really have already learned a lot more. Right now I'm trying to tweak the bitbake recipes a bit. I'd like to remove connman and install networkmanager instead. Connman apparently does not have ad-hoc wireless support... All I'm trying to do is get my beagles to autojoin the ad-hoc network on startup. I initially had some init.d scripts that would use ifconfig and iwconfig to set up the network, but for some reason these would not work totally correctly. The static IP would be correct, but in iwconfig it would not be set up with the ad-hoc network defined... I also followed this guide, set up the service as was discussed in the link, but it did not function correctly either. http://octopusprotos.com/?p=37 I tried removing connman with opkg and installing networkmanager, since I noticed I did not have a networking service (/etc/systemd/networking or whatever it is)... (this was a n00b mistake). I ended up losing ssh access... and now am unable to talk to the board. I guess if I had a serial cable I could debug the board, but right now it doesn't get an IP address (I checked the router's IP tables and it wasn't there) and the default USB 192.168.7.2 doesn't work either (I'm assuming connman used to set that up, but that was removed.) Right now the plan is to edit the bitbake recipes to remove connman and have networkmanager built instead. Then reflash the board. I have a feeling that there may be an easier way... Thanks again for the help, 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/groups/opt_out.
Re: [beagleboard] Beaglebone Black Clone Device Tree Problems
On Tue, Feb 18, 2014 at 7:07 PM, mkip...@profireenergy.com wrote: Hey guys, I'm working on a project which is using a clone of the BBB hardware and I'm running into some issues with Device Trees. I wasn't involved with the hardware design, but as far as I know, the BBB hardware has been duplicated exactly. Specifically, the clone board will be directly connected to an LCD using the LCD data pins on the AM335x. I've never worked with Device Trees before, but after some initial research (mostly based on this summaryhttp://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/overview) I'm thinking that they are the best way to accomplish what I'm looking for (enabling the LCD pins and configuring the driver to use them). I'm not concerned about the details of implementing this right now, since I'm having issues with Device Trees in general that I need to address first. The board is booting from an SD card with two partitions: one for U-boot and one for the Angstrom (v2012.12 with 3.8.13 kernel) image, both of which are the standard images which ship with the Beaglebone. I'm not having problems getting the board to boot. It has no problem running U-boot and it can start Linux without any catastrophic failures using the default images. Once Linux boots, if I go to /sys/devices/bone_capemgr.8, there are all the files you'd find on a regular BBB *except *slots and the slots-* files. As far as I know, without these files I can't add or modify device trees for the board. I still could by rebuilding the kernel I suppose, but as far as I know this is a deprecated approach. Here's a pastebin showing the serial output of the clone while it bootshttp://pastebin.com/ZBmatVgk I only have a basic understanding of U-Boot, so the output during the boot sequence doesn't help me to much, but here are the main things I've noticed while skimming through it: 1. Right at the start of the SPL process, the magic number check in EEPROM fails. This makes sense since the cloned board has a blank EEPROM. I'm not sure if this is a problem, but the assumption in the next lines (Beaglebone LT/Black.musb-hdrc) seem to work. The board is able to get past the SPL stage so I'd figure that this assumption is accurate enough. There are some rather basic configuration components that require board detection to work. I suggest you hard-code it in the SPL/u-boot or program the EEPROM. 2. The main U-Boot process also checks the EEPROM and fails the ID check. There is no reassuring message this time (Assuming Beaglebone or something to that effect) so I'm not sure if this is a larger problem. 3. The PHY initialization fails. The only hardware difference I know of between the clone and the BBB is the PHY, so this isn't very surprising. I'm pretty sure the PHY uses a different address so I'll deal with this when it becomes an issue. 4. The uEnv.txt is being read. I originally thought this might have been a problem, but if I modify uEnv.txt U-boot reports the correct file size. In this example I'm just using the default one though. 5. U-boot mentions the device tree addresses, but I don't know if there is any significance to this. 6. While booting the kernel, U-boot throws some bone-capemgr errors relating to the EEPROM. This makes me think that the EEPROM failure might be messing up the device tree configuration through bone-capemgr but I'm not sure. There are also some GPIO mux errors but I'm not sure that they really matter for my problems right now. That's all I've got right now. As I said, this is my first time working with anything related to the BBB and I don't really have any experience with U-Boot, so unfortunately I'm mostly relying on support from you guys at this point. If you need any more information just let me know. Thanks, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Need help sorting out LCD parameters
Hello, I am working on rewriting one of the LCD overlays to work with a Cold Tear Electronics 7 TFT LCD, http://www.ebay.ca/itm/7-inch-TFT-LCD-module-800x480-SSD1963-w-touchpad-PWM-arduino-AVR-STM32-ARM-/121017488870. My Beaglebone Black must interface with an SSD1963 controller running in 8080 mode I believe. The initialization code provided by the screen suppliers with some display parameters: http://pastebin.com/2xr8r8SQ. There is also code written for arduinos that have display parameters: http://pastebin.com/rNiBqNAm. This is my current version for the LCD overlay: http://pastebin.com/F4eVPrzM . The thing that I am stuck on is that the names of the LCD parameters in the overlay do not match the ones supplied by the manufacturer, and I'm stumped trying to figure out what it all means. The screen works for an Arduino so I know it isn't broken, and the way I currently have it wired up to the beaglebone the screen backlight goes on but the pixels do not change from their default state (what it looks like for a second after I turn on the arduino before the arduino outputs something to the screen). There is also different names for pins between the beaglebone and the screen, the beaglebone has lcd_vsync, lcd_hsync, lcd_pclk, and lcd_ac_bias_en whereas the datasheet for the 8080 mode on the SSD1963 lcd controller uses D/C, WR, RD, and CS. I've also had a lot of trouble getting the overlay to actually load. I have the disable hdmi and hdmin line in the uEnv.txt but when I cat slots it says that both the hdmi and hdmin capes are loaded, so I guess that is a bug. There is no problem when I echo BB-BONE-CTE to slots, after that it shows that the hdmi, hdmin, and my new overlay is loaded. The voltage seen on some pins on the beaglebone change after I load the overlay so it is doing something. I had to follow the steps here http://hipstercircuits.com/enable-device-tree-overlay-on-startup-on-beaglebone-black/ to compile the new file into the kernel and flash it on the beaglebone. I am using the Angstrom SD card image from 2013/08/21 with the 3.8.13-bone30 kernel with the new overlay in it. Any advice or insight is greatly appreciated! Kyle -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: After hotplug ging USB mass storage device system hang.
Hello, Thank you for reply guys. I found the problem. It was silly mistake from me in kernel code. Same function called twice with different name in same code thats why this bug generated. Sorry for wasting your time. Thank you for responding to my question. Regards, Kishor. On Wed, Feb 19, 2014 at 2:09 AM, William Hermans yyrk...@gmail.com wrote: Tis is a known issue with the 3.8.x kernel. You could have found information on the groups here simply by searching. You have two options. 1) use 3.8.x and do not hotplug any USB device. 2) Move to a newer kernel such as 3.12.x On Tue, Feb 18, 2014 at 1:13 PM, Rusty Wright rusty.wri...@gmail.comwrote: You could file a bug report with ubuntu folks; it looks like something isn't right in the kernel code. Can you try it with Debian Linux installed instead of Ubuntu? On Monday, February 17, 2014 11:04:03 PM UTC-8, Kishor Dhanawade wrote: Hello, I am using a Beaglebone black board wuth ubuntu 12.04 (3.8.13-kernel). My board is working very good with eMMC as well as with with SD card. Problem is when I hotplug a USB mass storage device(pendrive) whole system getting hang. Then if I powered off and again powered ON with pendrive then its working properly and pendrive is also detecting. Problem is only during hotplug. Also I tried to debug through the serial debug port but I am newbie so I didn't get the issue. Serial debug port output is as follows. ubuntu-armhf login: tilcdc 4830e000.fb: timeout waiting for framedone usb 1-1.4: new high-speed USB device number 5 using musb-hdrc usb 1-1.4: New USB device found, idVendor=0781, idProduct=5567 usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.4: Product: Firebird USB Flash Drive usb 1-1.4: Manufacturer: SanDisk usb 1-1.4: SerialNumber: 4C5326071374 scsi0 : usb-storage 1-1.4:1.0 scsi 0:0:0:0: Direct-Access SanDisk Cruzer Blade 1.26 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA *BUG: spinlock bad magic on CPU#0, kworker/u:2/62* lock: 0xdf4cfee8, .magic: , .owner: none/-1, .owner_cpu: 0 [c0014660] (unwind_backtrace+0x0/0xe0) from [c02420e8] (do_raw_spin_lock+0x20/0x164) [c02420e8] (do_raw_spin_lock+0x20/0x164) from [c02c1278] (get_device_parent+0x84/0x18c) [c02c1278] (get_device_parent+0x84/0x18c) from [c02c1904] (device_add+0xcc/0x580) [c02c1904] (device_add+0xcc/0x580) from [c0226358] (add_disk+0x1a8/0x40c) [c0226358] (add_disk+0x1a8/0x40c) from [c02efaf8] (sd_probe_async+0xec/0x1a8) [c02efaf8] (sd_probe_async+0xec/0x1a8) from [c005f87c] (async_run_entry_fn+0xe8/0x204) [c005f87c] (async_run_entry_fn+0xe8/0x204) from [c0054b70] (process_one_work+0x240/0x3fc) [c0054b70] (process_one_work+0x240/0x3fc) from [c005514c] (worker_thread+0x258/0x370) [c005514c] (worker_thread+0x258/0x370) from [c0058d70] (kthread+0xa0/0xb0) [c0058d70] (kthread+0xa0/0xb0) from [c000d918] (ret_from_fork+0x14/0x3c) *Unable to handle kernel NULL pointer dereference at virtual address 0008* pgd = c0004000 [0008] *pgd= Internal error: Oops: 5 [#1] SMP ARM Modules linked in: binfmt_misc unix CPU: 0Tainted: GW (3.8.13-bone26 #272) PC is at get_device_parent+0x94/0x18c LR is at spin_bug+0x10/0x28 pc : [c02c1288]lr : [c04821a8]psr: 0013 sp : df3d3df8 ip : c000d918 fp : c08122dc r10: ddca98c8 r9 : c07d2408 r8 : df3d40b0 r7 : df51080c r6 : ddca98d0 r5 : df510868 r4 : df510868 r3 : df4cfee0 r2 : r1 : r0 : fffc Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 9f5f4019 DAC: 0015 Process kworker/u:2 (pid: 62, stack limit = 0xdf3d2240) Stack: (0xdf3d3df8 to 0xdf3d4000) 3de0: ddc526c0 df510868 3e00: df510870 df51080c c02c1904 df510870 c02358ac 3e20: ddca98c8 df510800 dd8e0e40 df510800 dd8e0e40 df510868 df51080c df3d40b0 3e40: c07d2408 ddb04600 c08122dc c0226358 c0225360 df510800 df00 0080 3e60: 0004 c0c76e80 df4e1c00 df510800 df4e1c00 df510800 ddca9800 3e80: ddb04608 ddb04600 c02efaf8 df4e1c00 c02efa0c 0002 df39dbc0 3ea0: ddb04608 c0812200 df03f800 c005f87c c07d0da8 c07d0da8 c0812200 df3a9600 3ec0: c0812318 0001 df39dbc0 ddb04608 c0812200 df03f800 c0812318 3ee0: c0054b70 df061e8c 0001 0003 0001 df39dbc0 3f00: c0812318 df3d2000 c07ec6b8 c0812200 c0812318 df39dbd4 0089 c005514c 3f20: df39dbc0 df3d3f54 df3d3f38 df061e74 df39dbc0 c0054ef4 3f40: c0058d70 942dff37 f93fdf65 df39dbc0 3f60: dead4ead df3d3f74 df3d3f74 3f80: dead4ead
