davidmroth / stm32flash

Automatically exported from code.google.com/p/stm32flash
0 stars 0 forks source link

Get "Error probing interface "serial_posix"" on Mac #68

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. stm32flash -b 115200 -m 8n1 -f -e 0 -w firmware.bin 
/dev/tty.usbserial-A402V525

What is the expected output? What do you see instead?

stm32flash 0.4

http://stm32flash.googlecode.com/

Using Parser : Raw BINARY
Error probing interface "serial_posix"
Cannot handle device "/dev/tty.usbserial-A402V525"
Failed to open port: /dev/tty.usbserial-A402V525

What version of the product are you using? On what operating system?

stm32flash 0.4.  Mac OS X 10.8.5

Please provide any additional information below.

I stepped through the code.  The problem is happening in serial_setup() here:

    if (settings.c_iflag != h->newtio.c_iflag ||
        settings.c_oflag != h->newtio.c_oflag ||
        settings.c_cflag != h->newtio.c_cflag ||
        settings.c_lflag != h->newtio.c_lflag)
        return PORT_ERR_UNKNOWN;

The CRTSCTS settings in c_cflag can't be turned off, so this comparison fails.

If I just comment out the settings.c_cflag != h->newtio.c_cflag check, then 
everything works.

Original issue reported on code.google.com by j...@google.com on 13 Jan 2015 at 10:15

GoogleCodeExporter commented 9 years ago
I got the same issue on Mac Yosemite 10.10.1, and I have never faced this issue 
when working on ubuntu.

My chip is FT232. 

Commenting out the code does help me to success once, but never again ...

Original comment by Weihong....@gmail.com on 25 Jan 2015 at 3:49

GoogleCodeExporter commented 9 years ago
Thanks a lot for tracking down this issue. Is it documented anywhere that 
CRTSCTS in c_cflag is not settable on Mac OS X / Darwin?

Original comment by lists.to...@gmail.com on 24 Feb 2015 at 8:54

GoogleCodeExporter commented 9 years ago
Same on Mavericks

Original comment by kravv...@gmail.com on 22 Mar 2015 at 10:10

flabbergast commented 9 years ago

I can confirm this behaviour on Yosemite, also that the "fix" (commenting out the test) works.