Sorry to hear about the issues that you’ve had with that HAT, it’s still quite new here at Core Electronics, so I don’t have any experience running it with a Pi myself yet. Out of curiosity, have you tried running it with an I2C interface yet? (I’ve linked a GitHub repo for you below that should run you through that setup) I’m going to add a temporary note on the site now to let others know about this issue with using SPI, I’ll need to test the PN532 myself to see whether we can replicate it once they’re here, but after checking with some other forums it doesn’t look like there’s a clear agreed-upon solution to this yet, I’d take a dig through there if you’re determined to run this board with an SPI interface. Also, are you getting any other error messages? Or just the channel is already in use warning when running UART?
Common issues being reported, I’d start by checking here to see whether any of their suggestions provide a fix:
Thank you for your responses; unfortunately, I couldn’t get (I2C or SPI) working on the WaveShare PN532. However, upon some testing, I was able to get UART working.
I also noticed that the RPi.GPIO Module doesn’t support SPI, I2C, hardware PWM or serial functionality on the RPi yet; if this is true, the device shouldn’t specify that it supports this ability.
After some research and trial & error, I identified that the (RuntimeWarning) was due to the minor-alterations I made in the default-script leading to a few UART error issues as described which occurred now and again. Therefore, after spending a couple of hours redesigning the script, I can now continually-run the program and generate a single RFID read-out without encountering this issue.
And you can get our latest projects and tips straight away by following us on: