When I first started working with the BBB, it was a huge learning curve. Not because I did not know Linux, but because I did not know Linux in the context of embedded systems. Once I figured out various things, I'd have to say that 99.9% of my problems are a single google session away.
This is not to say that I know every_single_thing about the hardware, or even Linux. In fact, I consider Windows my primary OS for the desktop. Having been a DOS / Windows hobbyist developer since the 90's . . . Which also happens to be approximately how long I've been using Debian. Anyway, I've been trying to tell people on this group over the last couple years. If you're going to do any serious development for the BBB; Use a Linux machine as your host machine. Personally, I think it is a bad idea to use anything other than Debian. But thats partly personal preference, and partly from lessons learned through the school of hard knocks. Now, if you're using some other OS( BSD ), or distro on your BBB. I'd probably say use that OS / distro on your host also. At which point, you probably do not need / want advice from me. I also agree with Lee on just about every aspect of OSX. Not that Windows ( software side ) is much better - Because depending which angle you're coming from. It can be worse.. However, if you're dead set on keeping your OSX development workstation, there is nothing stopping you. Setup a Debian development machine. Be it a VM or in hardware. Setup a BBB development image, use NFS file sharing. Write all your code on your MAC. Then either cross compile the code on your Linux machine, or natively on the BBB. Simple . . . Personally, I keep my rootfs on my Debian development workstation, and load that on the BBB at boot time. This way I can do all the writing to disk I want, and not have to worry about flash media going bad. I do seem to be seeing a lot of whining coming from the OSX crowd though . . ." a whole weekend blown" and "beagleboard.org needs to stop selling this product to OSX users . . ." Really?! These comments speak for themselves . . . As for the other more civil comments I will say that it is a shame x.y.z does not work for you. Then if the rPI 2 does, then great by all means use it. I will say however that we recently just implemented CAN into our hardware / software recently, and I've yet to run into any problems short of the need to change kernels. The high level protocol we're trying to communicate with is a PITA though, which has absolutely nothing to do with the hardware. Lastly, anyone here who does answer questions about the hardware / software does not get paid to do so. So if you're asking a question, and get no answer. You're possibly asking a question thats been asked 500 times already, so learn how to use the search feature of google groups. You're asking a question that is easy to figure out by spending a few seconds / minutes on your search engine of choice. You're not giving enough information. *OR* maybe you're asking a question no one knows the answer to( usually unlikely ). Or also usually very rare, you're acting like a cry baby that expects attention . . . People like me have a filter for such users. It's called the trash can " delete post " button in gmail. Don't even get me started on the fact that we're talking about an embedded SBC here that denotes *anyone* using said board should be prepared to learn. So if you're not willing to spend some time and at least learn a good bit about the board and software you're using on it. Stop wasting yours / our time and go somewhere else. For those of you who have truly invested a good bit of time with the hardware / software, and have decided to move on to something else. Well . . . that is unfortunate, and good luck. Do not however blame the community. Your project is your responsibility. On Fri, May 1, 2015 at 9:17 AM, Lee Crocker <[email protected]> wrote: > I think the original poster has a good point here: why do we bother > wasting resources trying to support OSX? No "maker" with an ounce of > self-respect would buy an Apple product. It's an inaccessible black box > totally controlled by the corporation, constantly changing, constantly > breaking compatibility with older models, all on yesterday's hardware at a > premium price. Apple clearly has no interest in working with us, so why > should we work with them? > > If you're the kind of person who wants to use a BeagleBone, get a real > computer (by which I mean Linux). "Driver"? What's that? Why do I need one? > It just works. Serial cable? Just works. Network? Just works. And even if > for some odd reason it didn't, I'd just dig into the source code and figure > out why and fix it myself. > > Yes, OSX + BBB is a disaster. But let's put the blame where it belongs. > > -- > 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
