CHIRP

Ah, Mike I think I see the problem. I still want to see a debug log, but I think the problem is that it wasn't able to determine your port and then didn't clean up. Did it say "Unable to determine port" as the last step? If that's the case, you might need to find the port in a different way. Also, RTSystems cables are sometimes not compatible with non-RTSystems software without reprogramming the firmware in the cable. I'd definitely recommend a generic cable instead of that one, but I suspect that's the problem.

In your port box, do you have only "Custom" and "Help Me" options? If so, that's almost definitely the problem - that your RTSystems cable isn't actually exposing a port.

Yes, it looks like I would expect if the cable does not expose a serial port. Note that I've fixed (for tomorrow) the bug that causes it to give you a cryptic error message. However, that won't fix your actual problem, of course.

I can give you a more definitive answer if you do the following:

1. Unplug your cable
2. Plug in your cable
3. Immediately run journalctl -k > kernel.log

Attach the kernel log and I can tell you for sure.

Hi Mike,

Yep your kernel log confirms it: no serial port from that cable. You could ask on the mailing list, but if you're willing to get a different cable that will absolutely be easier. I recommend cables from https://bluemax49ers.com/ . They have a cable finder, they use top-quality USB chips, and they will make sure you get sorted.

Hey Dan,
Thanks for your help, and the information on the cable company. I am going to purchase a couple of new cables. You can close this ticket.

--
Thanks,
Mike W.
Meridian, ID