The MFRC522 chip as well as the board supports multiple protocols. That the chip AND board run on SPI requires pin 1 to be connected to GND. I do no expect this not to be, but one never knows... and it may be configurable on your version of the board.
In your hardware setup I miss the connection of NSS/CS that selects the board... An open input could be the issue. You though say in your last post #8 that you tied it to either LOW and HI, and you still get spurious emissions of the error. Tie it to an Espruino pin and let it control... Even though I do not expect that the signal change / edge just before and after the communication makes a difference, it could be.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Michael
The MFRC522 chip as well as the board supports multiple protocols. That the chip AND board run on SPI requires pin 1 to be connected to GND. I do no expect this not to be, but one never knows... and it may be configurable on your version of the board.
In your hardware setup I miss the connection of NSS/CS that selects the board... An open input could be the issue. You though say in your last post #8 that you tied it to either LOW and HI, and you still get spurious emissions of the error. Tie it to an Espruino pin and let it control... Even though I do not expect that the signal change / edge just before and after the communication makes a difference, it could be.