Anscheinend Treiberproblem nach Update auf bullseye-armhf-lite

Rund um die Software von Revolution Pi
Post Reply
User avatar
Ingo
Posts: 267
Joined: 10 Nov 2016, 21:56
Answers: 1
Location: Luth.Wittenberg

Anscheinend Treiberproblem nach Update auf bullseye-armhf-lite

Post by Ingo »

Hallo

Nachdem ich das Update auf die Aktuelle Version gemacht habe und alles wieder eingespielt hatte musste ich festellen das ich ein großes Problem habe
hier der Auszug der Debug datei

Code: Select all

TIDf7d6a040: Portable IEC 61131-3 RT Scheduler 
TIDf7d6a040: OS-Layer: Linux
TIDf7d6a040: Vendor: KUNBUS Revolution Pi
TIDf7d6a040: Platform: ARM11
TIDf7d6a040: AdditionalInfo: 
TIDf7d6a040: Version: 3.14.0 
TIDf7d6a040: Build timestamp: 2017-05-15 16:46:21
TIDf7d6a040: Git commit: d4d65588ce77f3a2f4574c32ad7656850d147adb
TIDf7d6a040: Scheduling mode: application timer/timer-tick preserving
TIDf7d6a040: Copyright logi.cals(R) 1994 - 2017. All rights reserved.

TIDf7d6a040: rtk_init_rt_state()
TIDf7b5e440: RTOS:clock resolution is 0s,500us
TIDf7d6a040: RTMAIN: set base path to .//../PLC
TIDf7d6a040: Serial ******************
TIDf7d6a040: LICENSE: RTS/httpd
TIDf7d6a040: LICENSE: licensed to RevPiCustomer
TIDf7d6a040: LICENSE: operating system Linux/ARM11/KUNBUS Revolution Pi
TIDf7d6a040: LICENSE: activated feature RTS
TIDf7d6a040: LICENSE: activated feature MODBUS
TIDf7d6a040: LICENSE: date issued 18-03-09
TIDf7d6a040: RTS: scheduler flags set to 0x00000000
TIDf7d6a040: RTS: scheduler flags set to 0x00000007
TIDf7d6a040: RTSS_DIAG loaded, system service registered successfully
TIDf7d6a040: RTSS_MQTT loaded, system service registered successfully
TIDf7d6a040: RTSS_SYSTEM loaded, system service registered successfully
TIDf7d6a040: RTSS_IPC_NS loaded, system service registered successfully
TIDf7d6a040: RTSS_PERSISTENCE loaded, system service registered successfully
TIDf7d6a040: RTSS_Auth loaded, registering system service
TIDf7d6a040: RTSSAuth: password database './/../PLC/passwd' is either empty or does not exist.
TIDf7d6a040:           Any user authentication will FAIL.
TIDf7d6a040: RTSS_TCF:init
TIDf7d6a040: RTSS_TCF:start
TIDf7061440: RTSS_TCF:TCF thread started
TIDf7d6a040: rtsTcf loaded, system service registered successfully
TIDf7061440: RTS_TCF:services initialized
TIDf7d6a040: RTSS_IO loaded, registering system service
TIDf7d6a040: IOSS: Init Device 1 (Service RTSS_REVPI_IO, 536870978) at index 0 with 4096 intputs, 4096 outputs and 0 marker
TIDf7d6a040: RTSS_REVPI_IO loaded, system service registered successfully
TIDf7d6a040: IOSS: Init Device 1 (Service RTSS_REVPI_IO, 536870978) at index 0 with 4096 intputs, 4096 outputs and 0 marker
TIDf7d6a040: RTS: Resource: started at .//../PLC
TIDf6285440: RTS: service thread started
TIDf5a84440: RTRM: thread started: 
TIDf5a84440: RTRM: thread only listening
TIDf7d6a040: RTS: Resource: activating initial code image ".//../PLC/RTSCode.so"
TIDf7d6a040: RT_SS_IPC_NS: Using end point '/tmp/IPC_NS_Socket.uds'
TIDf519b440: RT_SS_IPC_NS: Garbage collector thread started.
TIDf7d6a040: RT_SS_IPC_NS: Created server for resource Resource
TIDf7d6a040: RTS: Resource: performing cold init
TIDf7d6a040: RTSS_PERSISTENCE: Persistent data for retain variables collected
TIDf7d6a040: IOSS: Collect information about unresolved I/O
TIDf7d6a040: IOSS: Physical address %MB1.123 beyond segment size, I/O data exchange for VAR_GLOBAL.OUTPUTPWMFREQUENCY not possible  // [b]Behoben[/b]
TIDf7d6a040: IOSS: 106 inputs, 240 outputs initialized
TIDf7d6a040: IOSS: Physical address %MB1.123 beyond segment size, I/O data exchange for VAR_GLOBAL.OUTPUTPWMFREQUENCY not possible // [b]Behoben[/b]
TIDf7d6a040: IOSS: 106 inputs, 240 outputs initialized
TIDf7d6a040: RTS: Resource: Starting Application Tasks...
TIDf7d6a040: RTS: scaling thread priority 38229 to [0,65535]
TIDf7d6a040: RTS: Resource: Application Tasks started
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
Ich habe mich mit Logicals in Verbindung gesetzt aber dort sagen sie das dies bei Kunbus liegt.

Ich habe auch die Pictory auf Ver. 2.2.2
ich habe es auch mit einem leeren Programm getestet und in der Pictory nur den Core3 und ein DIO modul verwendet die Ausgabe bleibt die gleiche
TIDf4119440: RTSS_REVPI_IO: could not write to device: 'Inappropriate ioctl for device'.
User avatar
nicolaiB
KUNBUS
Posts: 877
Joined: 21 Jun 2018, 10:33
Answers: 8
Location: Berlin
Contact:

Re: Anscheinend Treiberproblem nach Update auf bullseye-armhf-lite

Post by nicolaiB »

Hallo Ingo,

ich kenne logi rts jetzt nicht im Detail und kann daher mit der Meldung nicht viel anfangen. Eine kurze Suche nach RTSS_REVPI_IO fördert aber folgende Anleitung von logirts zu Tage:

https://help.logicals.com/display/LC3Us ... +umstellen

Gruß Nicolai
Post Reply