USB-to-Serial Cable for Mac running Windows?

[noobforlife]

Can anyone recommend a USB-Serial cable to use on a Mac running Windows?

My Keyspan USA-19 works perfectly running under the OS X and on Windows machines. But, when I try downloading firmware from our Mac Pro running Windows to a board my son and I are messing with, I get validation errors. (For various reasons I don't fully understand, I need to be doing this download from Windows. I have tried doing it from OS X and no go).

Thanks!

 

[Guiyon]

Anything based off of the Prolific PL-2303 or FTDI FT232* series chipsets should work without any issues; these are the two I primarily use for serial communication with several different boards.

Here is one (newegg.com) that uses the Prolific chipset.

 

[operator207]

ac-usbs by airlink has been my "get into any console" device for the last 3 years. Mainly cisco equipment, and its worked fine in windows, but on a windows laptop, not on my MBP. I only have XP in VMware, not native, so I am not sure how me testing it would help. If you want though, tell me, and I will test it at work tomorrow on some cisco equipment. I imagine it will pass for what I use it for. I am not sure how it would work with what your doing though.

 

[noobforlife]

Operator:

Here is the link to what we are making:

http://blog.makezine.com/archive/2007/09/make_a_pocket_led_cube_we_1.html

The critical step is when we "make program-ledcube". The Mac's c-compiler does not support the binary format used in their code. Below is an array of bits showing what to turn on in a 3 x 3 cube of LEDs (the last field is the duration).

{ 0b000, 0b000, 0b000, 0b000, 0b110, 0b110, 0b000, 0b110, 0b110, 50000 },

for my Mac Pro running windows and Keyspan usb-serial converter, I get a validation error: the program written does not match the program read.

If there's a way for you to test that, awesome. But, don't spend too much time on it.

Thanks!

 

[Guiyon]

What are you using to compile the code with? I'm assuming it's WinAVR since the source looks like pretty standard AVR-based C. Could you post more of the output from AVRDUDE when it's failing?