Mac Terminal Serial Emulator Screen Resource Busy

Hi all,

Emulator
ScreenMy Huzzah ESP8266 breakout board seems to be busy and won't talk to me. Using CoolTerm, which I've used successfully for weeks, I get 'An Error Occurred while attempting to open the port - 100: Access Denied.'

Trying to communicate to device attached to serial port on Xserve through terminal.terminal froze after first try (hardware related), however, now - after fixing hardware - when we try to connect using: screen /dev/cu.serial 115200 we get two errors in rapid succession: Cannot open line '/dev/cu.serial' for R/W: Resource Busy. Now, we need to open Hatari’s preference panel and activate modem emulation. It’s important to do this LAST because Hatari’s serial emulation code doesn’t work well with the way Macs and other BSD-type OSes handle file locking. Hatari will sometimes freeze on the Mac if you start the modem emulation too soon. This is the normal terminal emulation mode that most people use, anyway. On the Linux side, the serial line must be configured with a getty on it to start a login: shell. To do this, you need to tell init that the serial line has a terminal on it. If you have a null modem cable and a terminal program on the other side, the Mac actually has a built-in terminal program called “screen” that you can use to test the connection. Once that is up and connected (and if the serial ports are set to the same baud rate and paramters), you can type on either side and see the characters come across.


BusyMac terminal serial emulator screen resource busy softwareIn Terminal (Mac OSX) ls /dev/tty.* reveals the port, but I can't use screen in Terminal to communicate either.

Mac Terminal Serial Emulator Screen Resource Busy Software


Mac Terminal Serial Emulator Screen Resource Busy

Best Terminal Emulator Mac

I've rebooted the board, disconnected/reconnected the serial connection and even tried to reflash the board with the latest firmware. An attempt to reflash the board, which I've done a couple times updating to the latest firmware) returns '[Errno 16] Resource busy' in Terminal. A quick search here hasn't turned up a ready answer to the issue. I'm rather new to working with embedded software/hardware and suspect the problem may be an easy fix, but haven't had any luck so far. Any help re-opening communication with what appears to be a hung board would be appreciated!