volkmarnissen

Thank you. the latest changes in targets.mk where not in my feature branch.That caused the issue. Sorry, I could have checked that first. Yes, I see, the issues seem to...

The following information are currently missing or not easy to find in doc/*.rst: Best Practise: - Which tools are most commonly used for development? - E.g. docker for all non...

Hi, I faced the same issue. Reason: It seems as if android.mk uses different different SDK/NDK than the on installed on docker image. My local build runs with this script:...

Yes, I installed Android Studio and then downloaded SDK and NDK of a matching version. BTW It is not required to run the make command with root permission.

Then you can try to find the SDK and NDK there and change the directories in the script.

You are right, this is the idea of docker, but there is a depenency of the docker image to the makefile. So, if this is not in sync, as it...

Working workaround: If a ETIMEDOUT error happens, don't close the connection. Close only after other errors or successful reads.

Thank you for the analysis. I was refering to server side. You are right, it is not a bug. When I implemented the Server, I was searching for a documentation...

I just found out, that the work around is not really working. Whenever a call to readHoldingRegister terminates with ETIMEDOUT and you close the connection afterwards, the resource is still...

Hi, destroy doesn't change the situation: This seems to be a bug. You can use the test program to reproduce it. Just connect an RS485 USB stick to /dev/ttyUSB0. There...