@m5stack any ideas about this? I shouldn't have any issues using other devices that use SPI should I?
Hey @tonywestonuk. I tried using the TFT_eSPI library that you mentioned (I'm having issues with nRf24L01 and LCD working together). When you specified the pins for CS/CE did you use the "D8" node-mcu type pin names or just "27"? If so I wouldn't mind knowing what values (I know which GPIO pins I should be using).
Ah, I think I got it. Guessing it's going to be related to this line (in /src/utility/Display.h): https://github.com/m5stack/M5Stack/blob/fdedf5fd901963068a0ec6a4b2270c239a21b29e/src/utility/Display.h#L60
Should get back to work... looking forward to having a hack tonight :)
Been reading some of the issues in the RF24.h git repo and someone is having similar-ish issues. It was suggested that I write the LCD CS high (disable) high before using the RF24, then write the LCD CS pin low again (or maybe write LCD CS low-high when I want to update the LCD display).
I should also point out that the M5Stack device is the master, and the slave is receiving the data ok, the M5Stack device is just not getting the ACK/getting the reply.
Created a protoboard with a nRF24L01 board on it which uses SPI.
RF24 board is close to 100% successful before I include the M5Stack library, now it it's maybe 3% successful. When I "disable" the LCD and TFCard (by conditionally removing the code in the M5Stack library) then the RF24 is good again.
I'm wondering if the LCD is "locking" the SPI bus?
I am running the SPI devices in parallel and have set the RF24 CS/CE pins to GPIO5 and GPIO17.
Any ideas? Thanks! ... love your stuff!
Hey @Stanszal ... I just got one of these and had issues with getting the uploading working. I found that if I reset the device and got the timing right then it would work. You just reset it while the "...____" message is writing. I can't tell you when to do it specifically, you just have to guess.
与 M5Stack Community 的连接断开，我们正在尝试重连，请耐心等待