CHIRP

I'm not sure if this is related, but I'm running into the same issue with a UV-5R EX I just bought on Amazon. It doesn't work with an FTDI cable that works fine with my BF-F8HP on Linux. I get the same behavior using 20180906 and also using a git snapshot. The FTDI serial port is visible in /dev, and running stty on the port shows that some of its settings are being changed by the software, so I'm pretty certain this is a radio communications issue.

I'm pretty sure the cable is seating far enough in, but it could be a bad radio, or maybe this particular radio isn't working with my particular cable (but the older radio is). Or maybe there is a new firmware out there. If I power on holding 3 I get ver BFS001. I have no idea whether this is normal.

I updated to a Windows 10 PC. Installed the latest build of Chirp. When I connect the Baofeng UV5R or the Baofeng UV5R5, connecting the cable makes the radio enter transmit mode. I can't get the radio to respond either.

I figured out the problem or at least for getting it to connect to the chirp software. The answer was actually in rthe paper instructions included with the baofeng genuine cable. The walkie end plugs need to be pushed quite hard and will make a hard click sound. As for the proper port setting, the usb serial one is the proper one, not the bluetooth, in the pulldown menu.
Hope this helps.