JaCzekanski
commented
3 years ago Scanning /dev works pretty good :)
int scan_ports()
{
struct dirent *ent;
char ftmp[PATH_MAX];
struct stat st;
DIR *dir = NULL;
char *link, *driver, *desc, *name;
nbports = 0;
#ifdef __APPLE__
dir = opendir("/dev");
if (!dir)
goto end;
while (nbports < MAXPORTS) {
ent = readdir(dir);
if (!ent)
break;
if (in_list(exclude_list, ent->d_name))
continue;
if (restrict_list && !in_list(restrict_list, ent->d_name))
continue;
if (strstr(ent->d_name, "cu.") != ent->d_name)
continue;
snprintf(ftmp, sizeof(ftmp), "/dev/%s", ent->d_name);
if (stat(ftmp, &st) == 0) {
serial_ports[nbports].name = strdup(ent->d_name);
serial_ports[nbports].driver = NULL;
serial_ports[nbports].desc = NULL;
serial_ports[nbports].ctime = st.st_ctime;
nbports++;
continue;
}
}
#else$ ./bin/bt -n
2 ports found, waiting for a new one...
port | age (sec) | device | driver | description
------+------------+------------+------------------+----------------------
2 | 0 | cu.usbserial-0001 | |
Trying port cu.usbserial-0001... Connected to cu.usbserial-0001 at 115200 bps.
Escape character is 'Ctrl-]'. Use escape followed by '?' for help.
Hello world!
BootTerm supports several single-character commands after the escape character:
H h ? display this help
Q q . quit
P p show port status
D d flip DTR pin
R r flip RTS pin
F f flip both DTR and RTS pins
B b send break
C c enable / disable capture
Enter the escape character again after this menu to use these commands.
Port name: cu.usbserial-0001 Speed: 115200 bps Pins: dtr RTS cts dsr cd ri
Port name: cu.usbserial-0001 Speed: 115200 bps Pins: dtr rts cts dsr cd ri
Port name: cu.usbserial-0001 Speed: 115200 bps Pins: DTR RTS cts dsr cd ri
Sent break
Not sure whether you're okay with #ifdefing parts of the code or would you rather have separate functions (scan_ports_osx, scan_ports_unix, etc) or even implementations in a separate .c file (selected in Makefile)
wtarreau
This might work, but I doubt it's worth the effort - macOS APIs often require you to write Obj-C (not sure if it also applies to kernel APIs) and in this case, we don't get any more information besides what's available by scanning
(continuation of #2)
Sadly, no :(
macOS doesn't have "Serial" hardware type in System information. Only USB devices can be listed:
but that still doesn't give us any direct info about Serial without doing VID/PID lookups.
Diff of
/devbefore and after connecting CP2102.(Weird that it is visible as two separate devices, maybe it's something related to my system setup/drivers) [edit] That was a driver issue - I had installed both Apple and Silabs kexts, uninstalling the later fixed the issue.
and here's for the FTDI
Looks like the Arduino IDE went the easy way and just lists all
^cu\.devices.