OSX + Baeglebone = Nightmare

[SimuGQ]

I have wasted a whole weekend trying got connect to my BBB.

I am running 10.10 and have trawled the internet reading pages upon pages of cryptic mumbo jumbo, I have uninstalled rivers, updated drivers, replaced drivers, edited pLists, reset Pram, reset SMC, I have done EVERYTHING. I am sick of it at this stage. I have a €100 Windows 7 netbook that connects with no problem to the Beaglebone.

For the past 9 months of=r so I have used an Arduino Mega with no connection issues, so why oh why is it so difficult to get this POS board to work? Laziness perhaps?

Basically Beaglebone need to get their finger out and fix the driver issues with OS X. 

OR STOP SELLING THIS BOARD to OS X users. It just doesn't work.

My weekend has been a complete waste.

[Robert Nelson]

I'm Sorry, you sound frustrated.. Well, I'm still working on my time machine...

OS X 10.10: was released: October 16, 2014

The shipping image on the BBB Rev C was created: May 14, 2014

Jason updated the drivers for 10.10: Jan 18, 2015

https://github.com/beagleboard/beaglebone-getting-started/commits/master

Did you try, the latest "snapshot"?

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-01-27

????

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[Robert Nelson]

Jason,

I just noticed, HoRNDIS-rel7.pkg is now out..

http://joshuawise.com/horndis

The latest version available is release 7: HoRNDIS-rel7.pkg (116491
bytes) (md5sum45a1a7457966b1dc79897af2864f68e4; GPG signature). Adds
support for OS X 10.10 (Yosemite). Fixes issue where unsigned kext
would not be installed (restoring support for OS X 10.6 - 10.8).
Thanks also to David Ryskalczykfor his help in tracking down the
issues with 10.10.

Looks like rel6 was a little buggy on 10.10, and we only have rel6 in
the repo right now:

https://github.com/beagleboard/beaglebone-getting-started/tree/master/Drivers/MacOSX

[SimuGQ]

Seriously, this is a mess. I just tried those drivers AGAIN, the result AGAIN is nada, nothing, a waste of my time and energy.

Beaglebone is a disaster on OS X. "It just works" do the developers remember that phase?

I bought 5 of these boards for my team, and lots of extra adafruit add on's (GPS, accelerometers = €€€). Everything is sitting various benches now not being used. My devs are pissed off, I am pissed off. Beagle bone was a fantasy, I think we are going to go to the Rpi, it mounted straight away, no hassle.

I am sick of the "have you tried" or "I reset the" routine. Seriously, what a waste of time. This is definetly not plug and play, and NOT user friendly.

I am not an amateur, neither are the rest of the team, but none of use could get this POS to work. It has been a very expensive joke.

[Robert Nelson]

On Sun, Feb 1, 2015 at 6:16 PM, SimuGQ <garymq...@gmail.com> wrote:
> Seriously, this is a mess. I just tried those drivers AGAIN, the result
> AGAIN is nada, nothing, a waste of my time and energy.
>
> Beaglebone is a disaster on OS X. "It just works" do the developers remember
> that phase?
>
> I bought 5 of these boards for my team, and lots of extra adafruit add on's
> (GPS, accelerometers = €€€). Everything is sitting various benches now not
> being used. My devs are pissed off, I am pissed off. Beagle bone was a
> fantasy, I think we are going to go to the Rpi, it mounted straight away, no
> hassle.
>
> I am sick of the "have you tried" or "I reset the" routine. Seriously, what
> a waste of time. This is definetly not plug and play, and NOT user friendly.

Well, to be fair... I'm not "there" looking over your shoulder. So
besides "have you tried" what should i ask you?

> I am not an amateur, neither are the rest of the team, but none of use could
> get this POS to work. It has been a very expensive joke.

btw, go read some of the history on this forum. We didn't support
"windows 7" out of the box either, it took awhile to get a signed
driver for 64bit.

[SimuGQ]

By the way, I bought 5 of these boards, none of them work.

It said on the box they were OS X compatible, this was obviously a false statement. What is anyone to think if they are sold something that does not do as promised, and has various "try this" solutions that don't work.

Amateur hour.

[Robert Nelson]

They work on my OS X 10.9.5 system

[SimuGQ]

Well what are we doing wrong?

[Don deJuan]

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You need to just chill out and take a deep breath its no ones fault you "wasted" time but your own. Just cause the Rpi does X out of the box does not make the BBB a "POS" means PEBKAC 99.9% of the time. How is anyone ever supposed to help you if you hate being asked have you tried this or that, no one can read your mind or guess WTF you even have attempted? Its not like you really laid out what you tried and have not tried. Shit happens accept it and find a solution or move on thats open source, no one but yourself is to blame if YOU wasted YOUR companies money. Like Robert I have no issues on my OSX 10.9 box though I rarely ever use it cause I just hate apple products. If you are experienced as you say then stop the ranting and ask a real question where you lay out what you tried and all the info you think is relevant so others can actually try and help, frustration or not dont take it out on people who make no money off helping YOU with YOUR problem. This attitude is going to get you no where and shocked Robert has entertained your emails this long. No one is under obligation to figure out YOUR problems but they just might if you actually were not on a tyrannical rant. If you hate these so much return all the "POS crap" you bought and go have fun with that pi, then realize all the BS hype that surrounds that platform.

[Robert Nelson]

On Sun, Feb 1, 2015 at 6:36 PM, SimuGQ <garymq...@gmail.com> wrote:
> Well what are we doing wrong?

Well, apple pushed out OS X 10.10, and the 3rd party driver writers
still need to catch up.

We use kernel.org's g_multi driver as a cdc ether/serial and usb flash
drive combination when users plug in the usb-slave port.

On Linux this pretty much works out of the box.

On Windows, it works if you install the signed driver*. Luckily the
usb-flash drive just works without drivers which allows us to easily
give users the dirvers. Linux developers provide the *.inf:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/linux.inf
The rest is built-in to windows...

On Mac, we have nothing, but the work of Joshua Wise's "horndis" driver:
http://joshuawise.com/horndis

It looks like we have more testing/bug reporting we need to forward Joshua..

[Robert Nelson]

I should add, ignoring the usb-net rndis interface. (which seems to be
failing for your right now in 10.10)

There is also a cdc-serial connection on the usb-slave port enabled:

Using screen it's usually:

screen /dev/tty.usbmodemfd113 115200

Oh however it's setup at plug-in time...

Then you should see something like:

[Debian GNU/Linux 7 beaglebone ttyGS0

BeagleBoard.org Debian Image 2015-01-19

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

The IP Address for usb0 is: 192.168.7.2
beaglebone login:]

Or using the ethernet port, "ssh deb...@beaglebone.local"

Or using the raw serial port, this needs an ftdi cable, I use this 98%
of the time, but not everyone has the cable..

and "hdmi"..

Out of the box, we pretty much enabled every login possibility to make it easy..

[SimuGQ]

Good God is that it?

Seriously, you guys are selling an 'OSX compatible" product?

What % users are OSX? What profit margin have you made there? Sell product, does't work, no support = 100% user profit. Host forum, post "try this" solutions, stay calm.

I give up.

Beaglebone is a joke until these drivers are sorted.

[Peter Lawler]

On 02/02/15 11:54, SimuGQ wrote:
> What profit margin have you made there?

Mate, you clearly don't realise there's NO profit at all involved.

> Beaglebone is a joke until these drivers are sorted.

You're the one on bleeding edge, complaining that stuff that was
released and compatible BEFORE your current release isn't compatible
with a later release.

Clearly, reading docs is hard. You're the joke you're looking for.

Pete.

[h...@simplify3d.com]

hmm I should have tried to screen the /dev/ port, but I didnt. Actually most of the time when I connected the BBB to my MacBook Pro late 2013 running 10.10.2, it would cause my macbook to reboot. Luckily I got the bbb with LCD screen up and running ssh'ing with my windows laptop, got it connected to the wifi, and now I can ssh into it from my macbook through its LAN IP

[John Syn]

From: SimuGQ <garymq...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Sunday, February 1, 2015 at 4:54 PM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Re: OSX + Baeglebone = Nightmare

Good God is that it?

Seriously, you guys are selling an 'OSX compatible" product?

What % users are OSX? What profit margin have you made there? Sell product, does't work, no support = 100% user profit. Host forum, post "try this" solutions, stay calm.

I give up.

Beaglebone is a joke until these drivers are sorted.

Any serious developer would not have updated to 10.10 for at least a year to ensure that all third party drivers are functional. It is your fault for updating to Yosemite and that is why you are wasting your time; nothing to do with BBB. In any case, we are all volunteers and donate our time to help others. We don’t get paid, so stop demanding that we get something fixed. If you listen to Robert’s advice, he will help you get up and running, but with your attitude, I don’t know why he bothers. The guy is a saint. 

Regards,

John

On Monday, February 2, 2015 at 12:47:43 AM UTC, RobertCNelson wrote:

On Sun, Feb 1, 2015 at 6:36 PM, SimuGQ <garymq...@gmail.com> wrote:
> Well what are we doing wrong?

Well, apple pushed out OS X 10.10, and the 3rd party driver writers
still need to catch up.

We use kernel.org's g_multi driver as a cdc ether/serial and usb flash
drive combination when users plug in the usb-slave port.

On Linux this pretty much works out of the box.

On Windows, it works if you install the signed driver*. Luckily the
usb-flash drive just works without drivers which allows us to easily
give users the dirvers. Linux developers provide the *.inf:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/linux.inf
 The rest is built-in to windows...

On Mac, we have nothing, but the work of Joshua Wise's "horndis" driver:
http://joshuawise.com/horndis

It looks like we have more testing/bug reporting we need to forward Joshua..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--

[Alexander Holler]

Am 02.02.2015 um 06:53 schrieb John Syn:
>
> From: SimuGQ <garymq...@gmail.com>
> Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
> Date: Sunday, February 1, 2015 at 4:54 PM
> To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
> Subject: Re: [beagleboard] Re: OSX + Baeglebone = Nightmare
>
>> Good God is that it?
>>
>> Seriously, you guys are selling an 'OSX compatible" product?
>>
>> What % users are OSX? What profit margin have you made there? Sell product,
>> does't work, no support = 100% user profit. Host forum, post "try this"
>> solutions, stay calm.
>>
>> I give up.

You just could use the cdc ethernet driver on the bbb as this seems to
be supported by the hooked fruit.

Maybe it's possible to identify these fruits or the windows by their
vendor-id of the usb. If so, one could just write an udev-rule for the
bbb which eiter loads the cdc-driver (for linux and/or fruit remotes) or
the rndis-driver for windows remotes.

Regards,

Alexander Holler

[Paulo Ferreira]

Windows 7 works with the Beaglebone, OSX 10.9 works, OSX 10.8 works, Linux x86 works. If OSX 10.10 does not work the blame is on the Beaglebone side?

As you have only "trawled the internet" for a weekend reading "mumbo jumbo", for a weekend, it seems to me that you need to spend lots of time reading more stuff.
Count on at least a month. until the mumbo jumbo starts making sense.


Yes, the Beaglebone IS NOT an Arduino!
The Arduino Mega has only a serial over USB connection, and is a 16 Mhz, 8 bit processor without any Operating system.
The Beaglebone is a 32 bit full grown computer, with network, HDMI, memory management and protection, LInux, and it is a very, very different machine.

Yes, the prices are very similar, but the value is very different.

Some people only look at "price", other can look at the value and the support and the knowledge that the guys behind the Beaglebone offer.

Hope someday you can do the latter.

[SimuGQ]

I know its not an Arduino, thats why we picked BBB, the specs are outstanding. Almost a year of Mega under our belts and we have pushed it to its limit. I also appreciate the effort everyone puts in. We are going to open source a serious amount of server motor OpenCAN code for the Arduino once all of the bugs are wiped out, we would hope to do the same for BBB.

The OS X machines we are using came with 10.10 out of the box, we added new machines just before Christmas, these are what we are working on. Frustration is caused due to the inconsistent instructions found everywhere.

If its a case of pulling a kext from a 10.9 machine to get the usb working we will look into that today and post results. It wouldn't be the first time and won't be the last that Apple in all their wisdom break stuff.

Maybe it's possible to identify these fruits or the windows by their vendor-id of the usb. If so, one could just write an udev-rule for the bbb which eiter loads the cdc-driver (for linux and/or fruit remotes) or the rndis-driver for windows remotes. 

Nothing shows up on the USB bus, so prime suspect would be an updated kext, I will be able to compare the version number from 10.10 & 10.9 later today. 

[Robert Nelson]

With 10.10, Apple requires "signed" kext's.. So depending on the 10.9
kext, you might have to enable "kext-dev-mode=1" in your apple
bootargs.

[Alexander Holler]

>> Nothing shows up on the USB bus, so prime suspect would be an updated kext,
>> I will be able to compare the version number from 10.10 & 10.9 later today.
>
> With 10.10, Apple requires "signed" kext's.. So depending on the 10.9
> kext, you might have to enable "kext-dev-mode=1" in your apple
> bootargs.

Is that kext necessary for the cdc-driver (or usb-storage) too? I've
read the cdc-driver is part of the system, so it should be already signed.

Regards,

Alexander Holler

[SimGQ]

So, plugging the BBB into a Mac that was upgraded from 10.9 to 10.10 worked... The plot thickens.

I have pulled IOUSBFamily.kext from this machine, I will compare the versions of the kexts inside to that of the machine that won't boot the BBB, specifically AppleUSBXHCI.kext and AppleUSBFTDI.kext to see what Apple have updated.

Will report back later.

[Robert Nelson]

It should only affect the usb-ethernet (RNDIS).

usb-storage & cdc-serial are built-in..

https://www.kernel.org/doc/Documentation/usb/gadget_multi.txt

A CDC ECM (Ethernet) function may be turned on via a Kconfig option
and RNDIS can be turned off. If they are both enabled the gadget will
have two configurations -- one with RNDIS and another with CDC ECM[3].

In 3.8:

CONFIG_USB_G_MULTI=m
CONFIG_USB_G_MULTI_RNDIS=y
# CONFIG_USB_G_MULTI_CDC is not set

in 3.14.x:

CONFIG_USB_G_MULTI=m
CONFIG_USB_G_MULTI_RNDIS=y
CONFIG_USB_G_MULTI_CDC=y

Wish i wasn't going on vacation in 24 hours... Anyone want to rebuild
v3.8.x and with CONFIG_USB_G_MULTI_CDC and see if they can just get
10.10 (i still need to upgrade my hackintosh) working with just
cdc-ether?

[Robert Nelson]

Scratch that, my "jessie" build has v3.14.x with that configuration,
so no rush to rebuild..

Flasher:
http://rcn-ee.net/rootfs/bb.org/testing/2015-02-01/lxqt-4gb/BBB-eMMC-flasher-debian-jessie-lxqt-4gb-armhf-2015-02-01-4gb.img.xz

microSD:
http://rcn-ee.net/rootfs/bb.org/testing/2015-02-01/lxqt-4gb/bone-debian-jessie-lxqt-4gb-armhf-2015-02-01-4gb.img.xz

Can someone with 10.10 test these out (without HoRNDIS installed) and
see if cdc-ether works out of the box?

[John Syn]

From: SimGQ <garymq...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Monday, February 2, 2015 at 5:49 AM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: [beagleboard] Re: OSX + Baeglebone = Nightmare

So, plugging the BBB into a Mac that was upgraded from 10.9 to 10.10 worked... The plot thickens.

I have pulled IOUSBFamily.kext from this machine, I will compare the versions of the kexts inside to that of the machine that won't boot the BBB, specifically AppleUSBXHCI.kext and AppleUSBFTDI.kext to see what Apple have updated.

Will report back later.

Why don’t you use a ethernet switch/hub and do all this over ethernet? You can use ssh/sftp/nfs for all your development and it works out of the box. 

Regards,

John

[SimGQ]

So we made a bit of progress, managing to get the BBB connected on all of the the new iMac's (Early 2014) running 10.10.2. In the end, it seemed that resetting PRAM & SMC after doing a repair of the disk permissions was all that was required. Why this worked is beyond me, it makes no sense. One of the five boards would work out of the box on all machines, all of them have the same image, so again it makes no sense unless its some strange voltage / USB timing issue?

The only mac giving problems now is an early 2011 iMac 27, its also running 10.10.2, it utilises the AppleUSBEHCI.kext (version 705.4.14) within IOUSBFamily.kext (Version 710.4.14) to drive the USB2 bus.

A machine still running 10.9.6 (Late 2012 Mini) uses AppleUSBEHCI.kext (version 686.4.1) within IOUSBFamily.kext (Version 660.4.0), it has USB3.

We tried moving the 10.9 IOUSBFamily.kext to the 10.10 machine, but nothing happened, the USB ports work fine but the BBB is not picked up. After the update, the USB is listed as "USB High Speed Bus" i.e. USB2.

So, the difference is that this Mac has USB2 not USB3, all of the new macs use the AppleUSBXHCI.kext (10.10 version) to drive their USB3 hubs and not AppleUSBEHCI.kext.

We will keep plugging away at it as a lunchtime / coffee break project to see if we can get it to work.

[Jesse Cobra]

Like Jon said, why don't you just ssh into the beaglebones from an Ethernet switch? Every OS works with BBB that way...
Seems silly to use USB anyways...

I have used serial cables and Ethernet cables to develop with dozens of beaglebones with every OS from windows to Linux to osx...

Why use USB drivers at all...

[William Hermans]

Ok, so like if OSX does not work, and you bought 5, for some purported embedded "project" FFS get a real support system. Honestly !!! Meanwhile, back at the ranch, many users on these groups using OSX 10.10, and do not have the same issues you're having. So, cause ? That "lump" that rests between the keyboard, and chair. . . . Get off your butt, and learn how to use your OS already.

--

[SimGQ]

Thank you for that constructive comment William, very grown up. I'll bet my European arse is a lot smaller than your American butt... Its a bit like this thread, one of the first I read about BBB https://groups.google.com/forum/#!searchin/beagleboard/hermans/beagleboard/951nWp_Jcnc/ZZV0GPwB3z8J

Eye opening, anyone asks a question or queries anything and they get flamed along the lines of "We developed this board for free and you expect our knowledge for free" yet there is no option to get any knowledge other than as you and other point out in that thread "Google". You guys seem to be offended if someone doesn't want to use the command line vis ssh. You do realise its 2015?

We or any BBB newbie are not asking for our hands to be held, just a few pointers. The work we did on the Arduino is now being packaged as open source, thats a fully working implementation of CanOpen geared specifically towards motor / servo control, it will save devs months of work.

Anyway, I do understand the OS, no need for the snide superior attitude, we are prototyping, you surely understand the concept? Spend little, develop fast, then invest in custom PCB's etc. The BBB has a fairly powerful CPU and CAN bus, it ticks a lot of boxes for us. We are a start up not Microsoft or Tesla, FFS (to paraphrase you). We were just a little surprised to find basic issues with running off a 5v supply, has to be a very clean supply, not just any 5V 2A supply. Basically we had a lot of teething problems, which we have mostly had to work around, not solve.

The issue of USB connectivity: its a lot more convenient for us to just use USB for demo / mobility purposes, rather than having two cables plugged into the BBB, ethernet & USB. For our fixed machines, I agree it's not a problem, but for those using laptops, its a bit of a nuisance.

Forgive me for complaining about the lack of documentation. Case in point:

Take the LSM303, finding coherent instructions was difficult. I bought Derek Molloy's book and we are now tearing ahead, his instructions are consistent. Infant we bought heaps of books (all I could find) on the BBB, if you go through them, there are discrepencies even in basic set up.

As a wise man once said, "If you don't have anything constructive to say, don't speak".

[William Hermans]

As a wise man once said, "If you don't have anything constructive to say, don't speak".

I do not think I could have put it better myself.

--

[liyaoshi]

Another choice
You can donate your MAC to me

[janszyma...@gmail.com]

Hi,

Did you have any luck solving this?

If yes, can you share it as I have the same problem.

Jan

On Monday, February 2, 2015 at 10:47:59 AM UTC+11, SimGQ wrote:

[SimGQ]

Jan,

The first thing to do, and it proved to be the simplest is use a good quality short cable, honestly in most of the connection issues we had it turned out to be cables / drivers / OS version in that order. Other than that we had one DOA board. It turns out the BBB is very temperamental about its power supply, we found it impossible to battery power it, something that took minutes to do on a RPi.

We decided to move to RPi 2 in the end anyway.

The BBB's are now performing various domestic duties for the team, we are all happy with them when working on them in our free time. I like the BBB, didn't like the support.

[Bill Traynor]

On Fri, May 1, 2015 at 8:41 AM, SimGQ <garymq...@gmail.com> wrote:
> Jan,
>
> The first thing to do, and it proved to be the simplest is use a good
> quality short cable, honestly in most of the connection issues we had it
> turned out to be cables / drivers / OS version in that order. Other than
> that we had one DOA board. It turns out the BBB is very temperamental about
> its power supply, we found it impossible to battery power it, something that
> took minutes to do on a RPi.
>
> We decided to move to RPi 2 in the end anyway.
>
> The BBB's are now performing various domestic duties for the team, we are
> all happy with them when working on them in our free time. I like the BBB,
> didn't like the support.

Just out of curiosity, how do you see the RPi support differing from
the BBB support? And how is the RPi support better?

>
>
> On Friday, May 1, 2015 at 12:05:59 PM UTC+1, janszyma...@gmail.com wrote:
>>
>> Hi,
>>
>> Did you have any luck solving this?
>> If yes, can you share it as I have the same problem.
>>
>> Jan
>>
>> On Monday, February 2, 2015 at 10:47:59 AM UTC+11, SimGQ wrote:
>>>
>>> I have wasted a whole weekend trying got connect to my BBB.
>>>
>>> I am running 10.10 and have trawled the internet reading pages upon pages
>>> of cryptic mumbo jumbo, I have uninstalled rivers, updated drivers, replaced
>>> drivers, edited pLists, reset Pram, reset SMC, I have done EVERYTHING. I am
>>> sick of it at this stage. I have a €100 Windows 7 netbook that connects with
>>> no problem to the Beaglebone.
>>>
>>> For the past 9 months of=r so I have used an Arduino Mega with no
>>> connection issues, so why oh why is it so difficult to get this POS board to
>>> work? Laziness perhaps?
>>>
>>> Basically Beaglebone need to get their finger out and fix the driver
>>> issues with OS X.
>>>
>>> OR STOP SELLING THIS BOARD to OS X users. It just doesn't work.
>>>
>>> My weekend has been a complete waste.
>>>
>>>

[SimGQ]

Probably the biggest difference is the user base and their attitude.

Asking questions on this forum that have a very simple answer (to somebody who knows) can result in some extreme responses, almost mocking the person asking for not knowing, the thread above and the one I referenced being an example.

With us it was a perception that we were spending more time finding answers than getting anything done, especially once we managed to overcome the gargantuan struggle of just getting the board to communicate with our machines.

When we discovered the anomalies with the power supply, trying to power off a battery, it was a lesson in frustration, with very disjointed documentation and no clear answers as to what was going on. When we tried to implement OpenCAN, we gave up.

With RPi, better hardware add ons, friendlier user base = less hassle and happier users.

Until RPi 2 came out, we would have soldiered on, but once that happened it was pointless.

[Lee Crocker]

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.

[William Hermans]

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.

[janszyma...@gmail.com]

Hi Lee,

 You're not trying to tell me that BBB is for elite "makers with self respect" only, while RPi is for everyone, are you?

At university we have students using their own computers - running OSX, Windows and (very few) Linux.

They all want to learn and they expect to receive help if needed.

The labs do not have enough Ethernet points for them, so you see my interest in RNDIS.

I own MBP, not only because I think it is a quality product, but as well I need to test project on different platforms (for example nodejs webserver)

I understand your frustration with Apple and possibly some people from TI should take the matter in their hands to solve it.

The interoperability is very important and we need to accept variety of operating systems.

There is a huge interest in embedded Linux platforms.

The big advantage of BBB over RPi is that it is able to run out of the box with a single cable.

Losing that for many people will lead into frustration and disappointment and as you can see moving somewhere else. 

Regards

Jan

[Robert Nelson]

Rndis & osx Yosemite is a problem for any linux board. With windows we have signed driver. For Mac... Well... If you have a Mac, we have the work done by the horndis developer...

http://joshuawise.com/horndis

Regards,

[William Hermans]

Rndis & osx Yosemite is a problem for any linux board. With windows we have signed driver. For Mac... Well... If you have a Mac, we have the work done by the horndis developer...

http://joshuawise.com/horndis

Regards,

And of course many( most ? all ? ) Android devices to boot. Don't ask me how I know this as a Windows / Linux user except that it's only been ongoing since ~AUG last year, and is only listed as the top 7 hit from a google search . . .

But somehow, it's the beagleboard.org google groups fault . . .riiiiiight.

[jelli...@gmail.com]

i have solved the problem of always having to enable flash player.

Go to

chrome://flags/#enable-ephemeral-flash-permission

Set enable ephemeral to disabled

Log out and then all should be good