search

pguyot / st25r391x

ST25R3916/7 Linux driver
GNU General Public License v2.0
9 stars 1 forks source link

Kernel error messages #5

Open f-laurens opened 2 years ago

f-laurens commented 2 years ago

After activation of the st25r391x driver, the following types of messages appear in a rabbit's kernel log:

Jun 29 15:04:27 Hazel kernel: nfc nfc0: st25r391x_turn_field_on: Failed to turn oscillator on: -1

Jun 29 15:05:33 Hazel kernel: nfc nfc0: st25r391x_turn_field_on: Time out waiting for interrupt bit (adjust regulators command)

Jun 29 15:12:57 Hazel kernel: st25r391x 1-0050: st25r391x_perform_collision_avoidance: time out waiting for interrupt bits
Jun 29 15:12:57 Hazel kernel: nfc nfc0: st25r391x_turn_field_on: Failed to perform collision avoidance: -1 (will not abort)

Can these be avoided?

f-laurens commented 2 years ago

Also got this one:

Jun 29 17:50:28 Bunny kernel: st25r391x 1-0050: st25r391x_load_fifo: read FIFO status registers, but value mismatch. Got 0, expected len = 2
Jun 29 17:50:28 Bunny kernel: st25r391x 1-0050: st25r391x_load_fifo: read FIFO status registers, but value mismatch. Got 0, expected len = 4
pguyot commented 2 years ago

Not sure what the problem is here.

f-laurens commented 2 years ago

Note that tag handling (read/write) in Pynab works fine, despite these 'errors' (whose appearance in the log seems mostly unrelated to tag operations).

f-laurens commented 2 years ago

Also, the most frequent messages:

nfc nfc0: st25r391x_turn_field_on: Failed to turn oscillator on: -1
nfc nfc0: st25r391x_turn_field_on: Time out waiting for interrupt bit (adjust regulators command)

appear at a much higher rate on Pi Zero (where they make most of the kernel log) than on Pi Zero 2.

f-laurens commented 2 years ago

Given the high volume of log generated on Pi Zero, what I fear here is the tear and wear induced on the SD card, when /var/log is not a RAM based filesystem (e.g. Raspbian/RaspiOS).