Hi With ethercat debug, I see something like this:
# ethercat reg_read -p 0 0x1000 --type uint8 [ 29.104116] EtherCAT 0: Master debug level set to 1. [ 29.147356] EtherCAT DEBUG 0-0: Processing register request, offset 0x1000, length 1... [ 29.159696] EtherCAT DEBUG 0-0: Register request successful. 0x00 0 Sometimes the hang is before the register read out is printed, sometime just after, and some times I get the prompt, and the hang is shortly after. But not enough so that I have managed to get further information (yet). A (perhaps) interesting observation, when doing this as root, the register read out is (almost) always 0x00 0, whereas when running as non-priveleged user, the readout is random garbage before the hang. As non-priveleged user, it is sometimes possible to read the register a couple of times before the hang occurs. I therefore strongly suspect that the hang occurs in the EtherCAT-IDLE thread, or some other kernel thread. /Esben Andreas Stewering-Bone <[email protected]> writes: > Hello, > > ethercat debug 1 > > Greatings > > Andreas > > > Esben Haabendal schrieb: >> Hi >> >> Andreas Stewering-Bone <[email protected]> writes: >> >> >>> Under preempt kernel the kernel itself has realtime capabilities, so >>> you can use the generic driver. >>> >> >> I know, I am "using" it. But after starting to use it beyound basic >> testing, I now look on a bug report with the mentioned bug report. >> >> >>> Please show the debugging output of the ethercat command if you read >>> the register. >>> >> >> How do I enable debug output of the ethercat command? >> >> /Esben >> _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
