CHIRP

Bernhard Hailer wrote:

Probieren Sie mal die folgenden Einstellungen in Chirp:
Hersteller: Baofeng
Modell: BF-888
und lassen Sie uns wissen, ob's geht!

Hello, and many thanks for the quick response.
I tested and it tells:
Radio refused to enter programming mode

So, it does not Download the Data...

Okay, that's already something. Could you please provide a debug log as described in the Wiki: "How To Report Issues"? Thanks!

No, the interesting part is actually above (the object attribute issue is a follow-up error). This looks more like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
On older MacOS versions, you must have the KK7DS Python runtime for Mac OSX installed. I don't have information yet what to do on new versions (like Big Sur).
Big Sur is a problem on its own, because basically all USB drivers need to be rewritten. FTDI is still working on it.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.

So, did the BF-888 driver do the trick?

Hello, unfortunately not so I guess it is a cheap-china-cable issue and until now, I did not buy a new one.