knxd 0.14.15 not starting up with tpuart

[Michael Kefeder]

Hi guys

switching from knxd-0.10.18 to knxd-0.14.15

I have a TP-UART over USB thingy from http://busware.de/tiki-index.php?page=TUL

# lsusb

Bus 001 Device 003: ID 03eb:204b Atmel Corp. LUFA USB to Serial Adapter Project

that used to work with knxd 0.10.x using "-i -b tpuarts:/dev/ttyACM0"

I now have this config file (not running systemd)

[A.tcp]

server = knxd_tcp

systemd-ignore = true

[B.tpuarts]

device = /dev/ttyACM0

driver = tpuart

baudrate = 19200

debug = debug-tpuart

[main]

addr = 0.0.1

client-addrs = 0.0.20:9

connections = A.tcp,B.tpuarts

pidfile = /run/knxd/knxd-0.pid

background = true

logfile = /var/log/knxd.log

cache = gc

[debug-tpuart]

error-level = 6

trace-mask = 0xfc

=======

which yields this output from 0.14.15

# sudo -u knxd knxd /etc/knxd.conf

Layer 3 [ 9:B.tpuarts/Conn      0.000] registerLink: 9:B.tpuarts

Layer 3 [ 9:B.tpuarts/Conn      0.000] Start: cfg:B.tpuarts

Layer 5 [ 9:B.tpuarts/Conn      0.000] down => >up

Layer 5 [ 9:B.tpuarts/Conn      0.000] Starting

E00000022: [12:B.tpuarts] low_latency /dev/ttyACM0 failed: Operation not permitted

Layer 5 [ 9:B.tpuarts/Conn      0.006] >up => down

Layer 4 [ 9:B.tpuarts/Conn      0.006] down/error

Layer 4 [ 9:B.tpuarts/Conn      0.006] is down

F00000000: [ 9:B.tpuarts] Link down, terminating

Layer 4 [ 9:B.tpuarts/Conn      0.006] Stopping

Layer 5 [ 9:B.tpuarts/Conn      0.006] down/error => >down

Layer 4 [ 9:B.tpuarts/Conn      0.006] down/error

Layer 4 [ 9:B.tpuarts/Conn      0.006] is down

Layer 2 [11:B.tpuarts/LowF      0.006] Close

Layer 2 [12:B.tpuarts/TPU_ser   0.006] Close

Any way I can debug this? looking at the code it cannot enable low-latency, which seems to be important. Is the firmware of the thing broken, or is there a workaround?

br

 mike

[Matthias Urlichs]

On 18.05.2017 11:17, Michael Kefeder wrote:
>
> E00000022: [12:B.tpuarts] low_latency /dev/ttyACM0 failed: Operation
> not permitted

Please run this with strace and tell me which system call returns EPERM.

Please open an issue on github with this.

> Any way I can debug this? looking at the code it cannot enable
> low-latency, which seems to be important. Is the firmware of the thing
> broken, or is there a workaround?
>

No, this is not a firmware problem.


--
-- Matthias Urlichs

[Michael Kefeder]

I ran it as root once while playing around with that issue, after that I cannot reproduce the problem. Because the machine is remote (as in one flight and 3h car drive away) I cannot easily do hardware disconnects to see if it can be reset.

Another problem is now coming up though: the background=true option does not seem to make knxd fork into background (I am on a non-systemd linux).

I'll file an issue when I found a way to reproduce it.

br

 mike