librelist archives

« back to archive

Do I have a bad controller?

Do I have a bad controller?

From:
Joe Schonbok
Date:
2015-05-18 @ 01:13
So I'm having some trouble getting my new Atreus working.  The firmware
stuff is definitely outside my experience, that's were I seem to be having
the trouble.  I have assembled the keyboard and I am trying to do the
initial update of the firmware.

I've followed the instructions in the readme, downloaded the libraries and
the latest firmware from Git.  I have tried on both a MacBook Pro
(Yosemite) and on a Raspberry Pi.  In both cases the "make upload" never
completes.  As far as I can tell, neither system can identify or enumerate
the controller, allowing it to be written to.

I have tried to identify the port using the ls /dev > /tmp/dev-on trick
outlined as well as using the system profiler on the Mac, but to no avail.

Using dmesg I get failure messages on the system identifying and
enumerating the device.  /dev/tty.usbmodem* and /dev/ttyACM* don't exist
(the A-Star documentation says these are the expected devices for the Mac
and the RPi respectively).

By doing the reset, touching the lower 2 right-hand pins twice, I can get
the yellow LED on the controller to blink.  It does not blink for 8 seconds
like the manual says it should (more like 3 or 4).  When it does blink I
get all the dmesg activity so I know something is happening, but I never
end up with something to upload to.

The RPi messages are like these (trying all kinds of device numbers):
[35955.584843] usb 1-1.2: new full-speed USB device number 55 using dwc_otg
[35956.004670] usb 1-1.2: device not accepting address 55, error -32

The Mac messages are like these (repeating several times before quitting):
USBF:    23835. 20    The IOUSBFamily was not able to enumerate a device.
USBF:    23835.857    The IOUSBFamily is having trouble enumerating a USB
device that has been plugged in.  It will keep retrying.  (Port 3 of Hub at
0xfa130000)

I've tried different USB ports, hubs, no hubs, and different cables.
Nothing seems to work.

Is there a trick to getting the thing into boot loader mode?  Do I have a
bad controller?  Am I missing some drivers?  Would some bad soldering
affect the ability to get the thing into loader mode?  Any ideas?  Many
thanks!

Joe

Re: [atreus] Do I have a bad controller?

From:
Jason Crump
Date:
2015-05-18 @ 02:25
I'm putting one together this weekend and ran into the same issues.  First
you need to install the ftdi drivers for Mac.  Search arduino Mavericks 
ftdi and you will find instructions.  




I also used the arduino ide to identify the serial port.  You might just 
install the ide and use it to identify the port.  Go to tools -> serial 
port.  Ignore the Bluetooth ones.





Second the pins to put the controller into boot loader mode are not 
described correctly in instructions.  With the keyboard face down and the 
cable facing away from you, short out the second and fifth pins on left 
twice.  The yellow light will then begin to breathe.







To burn the bootloader you will have to use the make upload 
USB=/dev/cu.usbmodemXXX for me XXX was 641





I had to start the bootloader then start the make command.




Ps if the keys are flip flopped you will need to check out the PCB-flip branch




Hope this helps.




For my build I need help figuring out why the top row doesn't work.

On Sun, May 17, 2015 at 6:14 PM, Joe Schonbok <joebok@gmail.com> wrote:

> So I'm having some trouble getting my new Atreus working.  The firmware
> stuff is definitely outside my experience, that's were I seem to be having
> the trouble.  I have assembled the keyboard and I am trying to do the
> initial update of the firmware.
> I've followed the instructions in the readme, downloaded the libraries and
> the latest firmware from Git.  I have tried on both a MacBook Pro
> (Yosemite) and on a Raspberry Pi.  In both cases the "make upload" never
> completes.  As far as I can tell, neither system can identify or enumerate
> the controller, allowing it to be written to.
> I have tried to identify the port using the ls /dev > /tmp/dev-on trick
> outlined as well as using the system profiler on the Mac, but to no avail.
> Using dmesg I get failure messages on the system identifying and
> enumerating the device.  /dev/tty.usbmodem* and /dev/ttyACM* don't exist
> (the A-Star documentation says these are the expected devices for the Mac
> and the RPi respectively).
> By doing the reset, touching the lower 2 right-hand pins twice, I can get
> the yellow LED on the controller to blink.  It does not blink for 8 seconds
> like the manual says it should (more like 3 or 4).  When it does blink I
> get all the dmesg activity so I know something is happening, but I never
> end up with something to upload to.
> The RPi messages are like these (trying all kinds of device numbers):
> [35955.584843] usb 1-1.2: new full-speed USB device number 55 using dwc_otg
> [35956.004670] usb 1-1.2: device not accepting address 55, error -32
> The Mac messages are like these (repeating several times before quitting):
> USBF:    23835. 20    The IOUSBFamily was not able to enumerate a device.
> USBF:    23835.857    The IOUSBFamily is having trouble enumerating a USB
> device that has been plugged in.  It will keep retrying.  (Port 3 of Hub at
> 0xfa130000)
> I've tried different USB ports, hubs, no hubs, and different cables.
> Nothing seems to work.
> Is there a trick to getting the thing into boot loader mode?  Do I have a
> bad controller?  Am I missing some drivers?  Would some bad soldering
> affect the ability to get the thing into loader mode?  Any ideas?  Many
> thanks!
> Joe

Re: [atreus] Do I have a bad controller?

From:
Phil Hagelberg
Date:
2015-05-18 @ 05:44
Jason Crump <admin@workordermachine.com> writes:

> I'm putting one together this weekend and ran into the same
> issues. First you need to install the ftdi drivers for Mac. Search
> arduino Mavericks ftdi and you will find instructions.

Thanks for clarifying this. I've tested the process on Macs before, but
I guess there are a lot of different OS combinations, and I don't think
I ever got a chance to test on a fresh install. I'll see if I can get
this into the docs for the firmware.

> Second the pins to put the controller into boot loader mode are not
> described correctly in instructions. With the keyboard face down and
> the cable facing away from you, short out the second and fifth pins on
> left twice. The yellow light will then begin to breathe.

Thanks for the heads-up on this; I've corrected the assembly instructions.

-Phil

Re: [atreus] Do I have a bad controller?

From:
Joe Schonbok
Date:
2015-05-18 @ 13:14
Thanks, Jason - but still no luck.

I am not sure that the reset pins you described are correct.  I believe I
have the A-Star 32U4 - the labels on the card match the diagram which
matches the instructions - https://www.pololu.com/docs/0J61/all#3.1. When I
try to short 2-5 on the left there is no reaction.  But shorting the last 2
on the right (RST and GND) gets a reaction - blinking and the OS tries to
identify.

I've installed the Arduino utility, and I think that I've installed the
FTDI drivers.  These appear to be tricky in Yosemite - Yosemite apparently
comes with it's own version.  I've found a couple sites with detailed
instructions on how to disable and replace with the FTDI drivers - but I'm
not sure things are going the way they are supposed to be.  There is a good
page on it here:
https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/mac#yosemite

The current FTDI drivers (2.3) is signed by Apple - all the instructions
seem to reference 2.2.  Anyway, I see the FTDI .kext entry in
/System/Library/Extensions and I don't see an entry for IOUSBFamily.kext -
but IOUSBFamily is what is reported be dmesg to be trying to link when I do
the reset.  So I kind of think that the apple provided IOUSBFamily is still
lurking around, but I have no idea where or how to stop it and let the
FTDIUSBSerialDriver.kext take over.

Anyway, I believe I'm making a good-faith effort to get the FTDI drivers
installed - but I still can't connect to the board and I'm not seeing any
evidence of the tty.usbserial* or tty.usbmodem* ports anywhere.

And I fully admit that I'm *way* out of my depth on trying to figure this
out.



On Sun, May 17, 2015 at 10:44 PM, Phil Hagelberg <phil@hagelb.org> wrote:

> Jason Crump <admin@workordermachine.com> writes:
>
> > I'm putting one together this weekend and ran into the same
> > issues. First you need to install the ftdi drivers for Mac. Search
> > arduino Mavericks ftdi and you will find instructions.
>
> Thanks for clarifying this. I've tested the process on Macs before, but
> I guess there are a lot of different OS combinations, and I don't think
> I ever got a chance to test on a fresh install. I'll see if I can get
> this into the docs for the firmware.
>
> > Second the pins to put the controller into boot loader mode are not
> > described correctly in instructions. With the keyboard face down and
> > the cable facing away from you, short out the second and fifth pins on
> > left twice. The yellow light will then begin to breathe.
>
> Thanks for the heads-up on this; I've corrected the assembly instructions.
>
> -Phil
>

Re: [atreus] Do I have a bad controller?

From:
Jason Crump
Date:
2015-05-18 @ 14:22
These are the instructions i used http://forum.arduino.cc/index.php?topic=198539.0
to get rolling.


Solution (as provided by the website above)
Type the following commands into the terminal:
    cd /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns 
    sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled 
    sudo touch /System/Library/Extensions




Restart your computer

Install the original FTDI Virtual Com Port drivers found 
here: http://www.ftdichip.com/Drivers/VCP.htm









Per your data sheet GND and RESET are pins 2 and 5 (when viewed upside 
down).  Doesn’t matter as long as you can find them and get the light to 
begin breathing (not flashing)

On Mon, May 18, 2015 at 6:15 AM, Joe Schonbok <joebok@gmail.com> wrote:

> Thanks, Jason - but still no luck.
> I am not sure that the reset pins you described are correct.  I believe I
> have the A-Star 32U4 - the labels on the card match the diagram which
> matches the instructions - https://www.pololu.com/docs/0J61/all#3.1. When I
> try to short 2-5 on the left there is no reaction.  But shorting the last 2
> on the right (RST and GND) gets a reaction - blinking and the OS tries to
> identify.
> I've installed the Arduino utility, and I think that I've installed the
> FTDI drivers.  These appear to be tricky in Yosemite - Yosemite apparently
> comes with it's own version.  I've found a couple sites with detailed
> instructions on how to disable and replace with the FTDI drivers - but I'm
> not sure things are going the way they are supposed to be.  There is a good
> page on it here:
> https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/mac#yosemite
> The current FTDI drivers (2.3) is signed by Apple - all the instructions
> seem to reference 2.2.  Anyway, I see the FTDI .kext entry in
> /System/Library/Extensions and I don't see an entry for IOUSBFamily.kext -
> but IOUSBFamily is what is reported be dmesg to be trying to link when I do
> the reset.  So I kind of think that the apple provided IOUSBFamily is still
> lurking around, but I have no idea where or how to stop it and let the
> FTDIUSBSerialDriver.kext take over.
> Anyway, I believe I'm making a good-faith effort to get the FTDI drivers
> installed - but I still can't connect to the board and I'm not seeing any
> evidence of the tty.usbserial* or tty.usbmodem* ports anywhere.
> And I fully admit that I'm *way* out of my depth on trying to figure this
> out.
> On Sun, May 17, 2015 at 10:44 PM, Phil Hagelberg <phil@hagelb.org> wrote:
>> Jason Crump <admin@workordermachine.com> writes:
>>
>> > I'm putting one together this weekend and ran into the same
>> > issues. First you need to install the ftdi drivers for Mac. Search
>> > arduino Mavericks ftdi and you will find instructions.
>>
>> Thanks for clarifying this. I've tested the process on Macs before, but
>> I guess there are a lot of different OS combinations, and I don't think
>> I ever got a chance to test on a fresh install. I'll see if I can get
>> this into the docs for the firmware.
>>
>> > Second the pins to put the controller into boot loader mode are not
>> > described correctly in instructions. With the keyboard face down and
>> > the cable facing away from you, short out the second and fifth pins on
>> > left twice. The yellow light will then begin to breathe.
>>
>> Thanks for the heads-up on this; I've corrected the assembly instructions.
>>
>> -Phil
>>

Re: [atreus] Do I have a bad controller?

From:
Joe Schonbok
Date:
2015-05-19 @ 13:00
Jason, are you on Yosemite or Mavericks?

I've followed those steps on two different systems (both Yosemite) with the
same results - board is not recognized and I am not convinced that the real
FTDI drivers are being used.

What I am seeing is that the FTDI drivers (2.3) install to
/Library/Extensions but everything else seems to be in
/System/Library/Extensions - including IOUSBFamily.kext.  I don't see that
they are ever loaded (using kextstat).  I seem to be able to manually load
them via kextload, but still when I plug the Atreus in and do the reset to
get the LED "breathing" to indicate the boot-loader state, it is not
recognized.  The expected ports are never visible in /dev or through the
Arduino app.

When I look at the messages when plugging in the Atreus, they are all about
the IOUSBFamily failing to figure anything out.  I am wondering, do the
FTDI drivers, or a link to them, need to be in
/System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins ?  That is
where the disabled Apple FTDI drivers are - why shouldn't the real FTDI
drivers be there?  I have no idea what I am doing so I don't want to nuke
my system accidentally - so I was curious where your
FTDIUSBSerialDriver.kext ended up and if it or a link to it is in your
IOUSBFamily plugins folder?

Thanks!

Joe

On Mon, May 18, 2015 at 7:22 AM, Jason Crump <admin@workordermachine.com>
wrote:

> These are the instructions i used
> http://forum.arduino.cc/index.php?topic=198539.0
> to get rolling.
>
> Solution (as provided by the website above)
> Type the following commands into the terminal:
>     cd /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns
>     sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
>     sudo touch /System/Library/Extensions
>
> Restart your computer
>
> Install the original FTDI Virtual Com Port drivers found here:
> http://www.ftdichip.com/Drivers/VCP.htm
>
>
> Per your data sheet GND and RESET are pins 2 and 5 (when viewed upside
> down).  Doesn’t matter as long as you can find them and get the light to
> begin breathing (not flashing)
>
>
>
>
> On Mon, May 18, 2015 at 6:15 AM, Joe Schonbok <joebok@gmail.com> wrote:
>
>> Thanks, Jason - but still no luck.
>>
>> I am not sure that the reset pins you described are correct.  I believe I
>> have the A-Star 32U4 - the labels on the card match the diagram which
>> matches the instructions - https://www.pololu.com/docs/0J61/all#3.1.
>> When I try to short 2-5 on the left there is no reaction.  But shorting the
>> last 2 on the right (RST and GND) gets a reaction - blinking and the OS
>> tries to identify.
>>
>> I've installed the Arduino utility, and I think that I've installed the
>> FTDI drivers.  These appear to be tricky in Yosemite - Yosemite apparently
>> comes with it's own version.  I've found a couple sites with detailed
>> instructions on how to disable and replace with the FTDI drivers - but I'm
>> not sure things are going the way they are supposed to be.  There is a good
>> page on it here:
>> https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/mac#yosemite
>> 
<https://learn.sparkfun.com/tutorials/how-to-insta%0D%0A%20ll-ftdi-drivers/mac#yosemite>
>>
>> The current FTDI drivers (2.3) is signed by Apple - all the instructions
>> seem to reference 2.2.  Anyway, I see the FTDI .kext entry in
>> /System/Library/Extensions and I don't see an entry for IOUSBFamily.kext -
>> but IOUSBFamily is what is reported be dmesg to be trying to link when I do
>> the reset.  So I kind of think that the apple provided IOUSBFamily is still
>> lurking around, but I have no idea where or how to stop it and let the
>> FTDIUSBSerialDriver.kext take over.
>>
>> Anyway, I believe I'm making a good-faith effort to get the FTDI drivers
>> installed - but I still can't connect to the board and I'm not seeing any
>> evidence of the tty.usbserial* or tty.usbmodem* ports anywhere.
>>
>> And I fully admit that I'm *way* out of my depth on trying to figure this
>> out.
>>
>>
>>
>> On Sun, May 17, 2015 at 10:44 PM, Phil Hagelberg <phil@hagelb.org> wrote:
>>
>>> Jason Crump <admin@workordermachine.com> writes:
>>>
>>> > I'm putting one together this weekend and ran into the same
>>> > issues. First you need to install the ftdi drivers for Mac. Search
>>> > arduino Mavericks ftdi and you will find instructions.
>>>
>>> Thanks for clarifying this. I've tested the process on Macs before, but
>>> I guess there are a lot of different OS combinations, and I don't think
>>> I ever got a chance to test on a fresh install. I'll see if I can get
>>> this into the docs for the firmware.
>>>
>>> > Second the pins to put the controller into boot loader mode are not
>>> > described correctly in instructions. With the keyboard face down and
>>> > the cable facing away from you, short out the second and fifth pins on
>>> > left twice. The yellow light will then begin to breathe.
>>>
>>> Thanks for the heads-up on this; I've corrected the assembly
>>> instructions.
>>>
>>> -Phil
>>>
>>
>>
>

Re: [atreus] Do I have a bad controller?

From:
Jason Crump
Date:
2015-05-19 @ 14:13
Sorry Joe,




I’m not at my shop computer and won’t be for about a week and a half, 
going on vacation, so I can’t look up the location of that file.




I am on Yosemite but had the same issue with mavericks and the solution 
was the same for both.  I’m sorry you haven’t had an luck yet.  The 
controller is arduino compatible and there is a lot more support for 
arduino devices, you might try installing the arduino IDE and getting that
working as there are a lot more resources for arduino.




Good luck

On Tue, May 19, 2015 at 6:01 AM, Joe Schonbok <joebok@gmail.com> wrote:

> Jason, are you on Yosemite or Mavericks?
> I've followed those steps on two different systems (both Yosemite) with the
> same results - board is not recognized and I am not convinced that the real
> FTDI drivers are being used.
> What I am seeing is that the FTDI drivers (2.3) install to
> /Library/Extensions but everything else seems to be in
> /System/Library/Extensions - including IOUSBFamily.kext.  I don't see that
> they are ever loaded (using kextstat).  I seem to be able to manually load
> them via kextload, but still when I plug the Atreus in and do the reset to
> get the LED "breathing" to indicate the boot-loader state, it is not
> recognized.  The expected ports are never visible in /dev or through the
> Arduino app.
> When I look at the messages when plugging in the Atreus, they are all about
> the IOUSBFamily failing to figure anything out.  I am wondering, do the
> FTDI drivers, or a link to them, need to be in
> /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins ?  That is
> where the disabled Apple FTDI drivers are - why shouldn't the real FTDI
> drivers be there?  I have no idea what I am doing so I don't want to nuke
> my system accidentally - so I was curious where your
> FTDIUSBSerialDriver.kext ended up and if it or a link to it is in your
> IOUSBFamily plugins folder?
> Thanks!
> Joe
> On Mon, May 18, 2015 at 7:22 AM, Jason Crump <admin@workordermachine.com>
> wrote:
>> These are the instructions i used
>> http://forum.arduino.cc/index.php?topic=198539.0
>> to get rolling.
>>
>> Solution (as provided by the website above)
>> Type the following commands into the terminal:
>>     cd /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns
>>     sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
>>     sudo touch /System/Library/Extensions
>>
>> Restart your computer
>>
>> Install the original FTDI Virtual Com Port drivers found here:
>> http://www.ftdichip.com/Drivers/VCP.htm
>>
>>
>> Per your data sheet GND and RESET are pins 2 and 5 (when viewed upside
>> down).  Doesn’t matter as long as you can find them and get the light to
>> begin breathing (not flashing)
>>
>>
>>
>>
>> On Mon, May 18, 2015 at 6:15 AM, Joe Schonbok <joebok@gmail.com> wrote:
>>
>>> Thanks, Jason - but still no luck.
>>>
>>> I am not sure that the reset pins you described are correct.  I believe I
>>> have the A-Star 32U4 - the labels on the card match the diagram which
>>> matches the instructions - https://www.pololu.com/docs/0J61/all#3.1.
>>> When I try to short 2-5 on the left there is no reaction.  But shorting the
>>> last 2 on the right (RST and GND) gets a reaction - blinking and the OS
>>> tries to identify.
>>>
>>> I've installed the Arduino utility, and I think that I've installed the
>>> FTDI drivers.  These appear to be tricky in Yosemite - Yosemite apparently
>>> comes with it's own version.  I've found a couple sites with detailed
>>> instructions on how to disable and replace with the FTDI drivers - but I'm
>>> not sure things are going the way they are supposed to be.  There is a good
>>> page on it here:
>>> https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/mac#yosemite
>>> 
<https://learn.sparkfun.com/tutorials/how-to-insta%0D%0A%20ll-ftdi-drivers/mac#yosemite>
>>>
>>> The current FTDI drivers (2.3) is signed by Apple - all the instructions
>>> seem to reference 2.2.  Anyway, I see the FTDI .kext entry in
>>> /System/Library/Extensions and I don't see an entry for IOUSBFamily.kext -
>>> but IOUSBFamily is what is reported be dmesg to be trying to link when I do
>>> the reset.  So I kind of think that the apple provided IOUSBFamily is still
>>> lurking around, but I have no idea where or how to stop it and let the
>>> FTDIUSBSerialDriver.kext take over.
>>>
>>> Anyway, I believe I'm making a good-faith effort to get the FTDI drivers
>>> installed - but I still can't connect to the board and I'm not seeing any
>>> evidence of the tty.usbserial* or tty.usbmodem* ports anywhere.
>>>
>>> And I fully admit that I'm *way* out of my depth on trying to figure this
>>> out.
>>>
>>>
>>>
>>> On Sun, May 17, 2015 at 10:44 PM, Phil Hagelberg <phil@hagelb.org> wrote:
>>>
>>>> Jason Crump <admin@workordermachine.com> writes:
>>>>
>>>> > I'm putting one together this weekend and ran into the same
>>>> > issues. First you need to install the ftdi drivers for Mac. Search
>>>> > arduino Mavericks ftdi and you will find instructions.
>>>>
>>>> Thanks for clarifying this. I've tested the process on Macs before, but
>>>> I guess there are a lot of different OS combinations, and I don't think
>>>> I ever got a chance to test on a fresh install. I'll see if I can get
>>>> this into the docs for the firmware.
>>>>
>>>> > Second the pins to put the controller into boot loader mode are not
>>>> > described correctly in instructions. With the keyboard face down and
>>>> > the cable facing away from you, short out the second and fifth pins on
>>>> > left twice. The yellow light will then begin to breathe.
>>>>
>>>> Thanks for the heads-up on this; I've corrected the assembly
>>>> instructions.
>>>>
>>>> -Phil
>>>>
>>>
>>>
>>

Re: [atreus] Do I have a bad controller?

From:
Joe Schonbok
Date:
2015-05-23 @ 04:14
Okay - so I can now confirm I had a bad controller.  I tried connecting to
it on 4 computers, 3 different OSs - all failed to properly detect the
device after the drivers had been installed.  I ordered a new one which
arrived today - I plugged it in and it connected immediately and I was able
to identify the port and upload the firmware.

So I replaced the bad one with the good one - not an easy task after all
they keys are soldered in (I was pretty optimistic!).  I ended up cutting a
hole through the key plate so I could access both sides of the controller.
There is room under the little nose on the top plate so the hole won't
show.  It might be a good option to put an official hole there so a person
can more easily get to the controller.

But now I'm facing the same issue Jason did - the entire top row is not
responsive, but all the other keys are... so I'll see about tackling that
tomorrow.

On Tue, May 19, 2015 at 7:13 AM, Jason Crump <admin@workordermachine.com>
wrote:

> Sorry Joe,
>
> I’m not at my shop computer and won’t be for about a week and a half,
> going on vacation, so I can’t look up the location of that file.
>
> I am on Yosemite but had the same issue with mavericks and the solution
> was the same for both.  I’m sorry you haven’t had an luck yet.  The
> controller is arduino compatible and there is a lot more support for
> arduino devices, you might try installing the arduino IDE and getting that
> working as there are a lot more resources for arduino.
>
> Good luck
>
>
>
>
> On Tue, May 19, 2015 at 6:01 AM, Joe Schonbok <joebok@gmail.com> wrote:
>
>> Jason, are you on Yosemite or Mavericks?
>>
>> I've followed those steps on two different systems (both Yosemite) with
>> the same results - board is not recognized and I am not convinced that the
>> real FTDI drivers are being used.
>>
>> What I am seeing is that the FTDI drivers (2.3) install to
>> /Library/Extensions but everything else seems to be in
>> /System/Library/Extensions - including IOUSBFamily.kext.  I don't see that
>> they are ever loaded (using kextstat).  I seem to be able to manually load
>> them via kextload, but still when I plug the Atreus in and do the reset to
>> get the LED "breathing" to indicate the boot-loader state, it is not
>> recognized.  The expected ports are never visible in /dev or through the
>> Arduino app.
>>
>> When I look at the messages when plugging in the Atreus, they are all
>> about the IOUSBFamily failing to figure anything out.  I am wondering, do
>> the FTDI drivers, or a link t o them, need to be in
>> /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins ?  That is
>> where the disabled Apple FTDI drivers are - why shouldn't the real FTDI
>> drivers be there?  I have no idea what I am doing so I don't want to nuke
>> my system accidentally - so I was curious where your
>> FTDIUSBSerialDriver.kext ended up and if it or a link to it is in your
>> IOUSBFamily plugins folder?
>>
>> Thanks!
>>
>> Joe
>>
>> On Mon, May 18, 2015 at 7:22 AM, Jason Crump <admin@workordermachine.com>
>> wrote:
>>
>>> These are the instructions i used
>>> http://forum.arduino.cc/index.php?topic=198539.0
>>> to get rolling.
>>>
>>> Solution (as provided by the website above)
>>> Type the following commands into the terminal:
>>>     cd /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns
>>>     sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
>>>     sudo touch /System/Library/Extensions
>>>
>>> Restart your computer
>>>
>>> Install the original FTDI Virtual Com Port drivers found here:
>>> http://www.ftdichip.com/Drivers/VCP.htm
>>>
>>>
>>> Per your data sheet GND and RESET are pins 2 and 5 (when viewed upside
>>> down).  Doesn’t matter as long as you can find them and get the light to
>>> begin breathing (not flashing)
>>>
>>>
>>>
>>>
>>> On Mon, May 18, 2015 at 6:15 AM, Joe Schonbok <joebok@gmail.com> wrote:
>>>
>>>> Thanks, Jason - but still no luck.
>>>>
>>>> I am not sure that the reset pins you described are correct.  I believe
>>>> I have the A-Star 32U4 - the labels on the card match the diagram which
>>>> matches the instructions - https://www.pololu.com/docs/0J61/all#3.1.
>>>> When I try to short 2-5 on the left there is no reaction.  But shorting the
>>>> last 2 on the right (RST and GND) gets a reaction - blinking and the OS
>>>> tries to identify.
>>>>
>>>> I've installed the Arduino utility, and I think that I've installed the
>>>> FTDI drivers.  These appear to be tricky in Yosemite - Yosemite apparently
>>>> comes with it's own version.  I've found a couple sites with detailed
>>>> instructions on how to disable and replace with the FTDI drivers - but I'm
>>>> not sure things are going the way they are supposed to be.  There is a good
>>>> page on it here:
>>>> https://learn.sparkfun.com/tutorials/how-to-install-ftdi-drivers/mac#yosemite
>>>> 
<https://learn.sparkfun.com/tutorials/how-to-insta%0D%0A%20ll-ftdi-drivers/mac#yosemite>
>>>>
>>>> The current FTDI drivers (2.3) is signed by Apple - all the
>>>> instructions seem to reference 2.2.  Anyway, I see the FTDI .kext entry in
>>>> /System/Library/Extensions and I don't see an entry for IOUSBFamily.kext -
>>>> but IOUSBFamily is what is reported be dmesg to be trying to link when I do
>>>> the reset.  So I kind of think that the apple provided IOUSBFamily is still
>>>> lurking around, but I have no idea where or how to stop it and let the
>>>> FTDIUSBSerialDriver.kext take over.
>>>>
>>>> Anyway, I believe I'm making a good-faith effort to get the FTDI
>>>> drivers installed - but I still can't connect to the board and I'm not
>>>> seeing any evidence of the tty.usbserial* or tty.usbmodem* ports anywhere.
>>>>
>>>> And I fully admit that I'm *way* out of my depth on trying to figure
>>>> this out.
>>>>
>>>>
>>>>
>>>> On Sun, May 17, 2015 at 10:44 PM, Phil Hagelberg <phil@hagelb.org>
>>>> wrote:
>>>>
>>>>> Jason Crump <admin@workordermachine.com> writes:
>>>>>
>>>>> > I'm putting one together this weekend and ran into the same
>>>>> > issues. First you need to install the ftdi drivers for Mac. Search
>>>>> > arduino Mavericks ftdi and you will find instructions.
>>>>>
>>>>> Thanks for clarifying this. I've tested the process on Macs before, but
>>>>> I guess there are a lot of different OS combinations, and I don't think
>>>>> I ever got a chance to test on a fresh install. I'll see if I can get
>>>>> this into the docs for the firmware.
>>>>>
>>>>> > Second the pins to put the controller into boot loader mode are not
>>>>> > described correctly in instructions. With the keyboard face down and
>>>>> > the cable facing away from you, short out the second and fifth pins
>>>>> on
>>>>> > left twice. The yellow light will then begin to breathe.
>>>>>
>>>>> Thanks for the heads-up on this; I've corrected the assembly
>>>>> instructions.
>>>>>
>>>>> -Phil
>>>>>
>>>>
>>>>
>>>
>>
>

Re: [atreus] Do I have a bad controller?

From:
Phil Hagelberg
Date:
2015-05-23 @ 09:10
Joe Schonbok <joebok@gmail.com> writes:

> Okay - so I can now confirm I had a bad controller.  I tried connecting to
> it on 4 computers, 3 different OSs - all failed to properly detect the
> device after the drivers had been installed.  I ordered a new one which
> arrived today - I plugged it in and it connected immediately and I was able
> to identify the port and upload the firmware.

Yikes; I'm sorry to hear that. Send me an email and I'll get you a
refund to cover the cost of the replacement controller.

It sounds like now you're on the right track. If you have trouble
or if the same steps outlined in that other thread aren't doing the
trick just let me know and I can step you through further debugging.

-Phil