This topic is really just a continuation on Getting "disk not ejected properly" in OSX http://forum.micropython.org/viewtopic.php?f=2&t=287 but I wanted to post a new topic to ask a more general question - is there anyone using the pyboard with OSX for whom everything is working perfectly?
In the past there were several reported cases of various problems under OSX. Many of them turned out to be the result of faulty micro-USB cables, but some of these issues may have gone unresolved with the users reporting them moving on:
OSX device not listed: http://forum.micropython.org/viewtopic.php?f=2&t=157
OS X, board not appearing as Mass Storage Device: http://forum.micropython.org/viewtopic.php?f=2&t=78
Nasty MicroUSB cables: http://forum.micropython.org/viewtopic.php?f=6&t=105
I can confirm that the problem reported by @LarryTru is also a problem on my (7 year old) MacBook Pro and also on another much newer MacBook which I have tested. The thing is that it is an easy enough issue to work around - the Mass Storage volume is usable for a few minutes every time you plug in or do a hard reset, and can also be cleanly unmounted within that time - so I am wondering if it is actually stable for other users or if they have been working around it as well. Note that my question is specific to OSX; I have used my boards a little bit on both Linux and Windows and Mass Storage seems stable enough under those operating systems.
I'm hoping just to hear a few users offer a simple 'works fine for me' or 'seeing same problem here' to get a sense how big the problem is. My biggest worry is that other OSX users have just gotten frustrated and moved on. Is there any way to use the board to contact users directly via email to ask this question?
Mass Storage problems with OSX
Re: Mass Storage problems with OSX
I confirmed that the problem occurs on all three of the macs in my household: 2 MacBook Pros and a Mac Mini
Larry
Larry
Re: Mass Storage problems with OSX
I get the same problem.
I partially solve the problem by a reset (not ideal) and then ctrl-j reset ctrlj and go back into the shell.
Dom
I partially solve the problem by a reset (not ideal) and then ctrl-j reset ctrlj and go back into the shell.
Dom