-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation problem with the TFT_eSPI library #145
Comments
@JVRMTS - I just did the same thing and was going to post about it. However I still have a problem that when my CC1101 is connected at same time as the TFT, calling the init locks my program up. It can not init the CC1101 - did you have a similar problem? |
Yes, I have the same problem. |
@JVRMTS for what it's worth, I found a different issue thread here that said use a diff SPI config. If you're using an ESP32 like I am you can pretty much use ANY pins for the SPI config just pass them to the function. I'm using an MH-ET Live ESP32 MiniDevKit for my project (https://doc.riot-os.org/group__boards__esp32__mh-et-live-minikit.html) , I'm using these pins:
The TFT, Touch and SD card all work perfectly and so does the CC1101 now it's on it's own SPI bus! |
I have solved it by connecting a 100 microF capacitor and a 10K resistor in series with the CC1101 power supply, to delay the CC1101 power supply and when I restart it I no longer have any problem |
@JVRMTS is yours working well? As soon as I use it kills the TOUCH part of my code. Touch no longer responds. If I don't use those (so basically the cc1101 does nothing but the init) then touch works great. As soon as either of those 2 run, it stops responding. The TFT itself still works and responds/updates it's just the touch stops working :( So annoying - and my CC1101 isn't even on the same SPI as the touch |
I keep doing tests, when I have something clear I will post it |
Solution in esp32: `#define aliCC1101 25 //CC1101 power // Activamos la transmision en el pin correspondiente . // Configuramos el CC1101 en modo transmisión. // Seleccionamos el protocolo de transmisión. // Seleccionamos tiempo del pulso en la transmisión. // Numero de repeticiones de transmisión. En mi caso con 2 es suficiente. I power the CC1101 through the GPI025, and delay it 100 milliseconds in the setup They are both on the same SPI |
Other solution: in void setup(){ // then load the CC1101 configuration This is how everything also works in the same SPI |
@JVRMTS I Appreciate the help and comments :) My current issue is that, for the most part it works, my screen shows what I want, and it continues to update the screen with information. The CC1101 is receving the information correctly and then displaying the results on screen. My problem is that as soon as it handles a packet of data it received (using For what it's worth too, I'm only receiving in my use case scenario, I'm not transmitting anything |
To send and receive I use the RCSwitch library, it can be downloaded from the Arduino library manager |
I will take a look thanks. I'm using the CC1101 (868 module not 433 movule) to read IZAR packets from water meter so the decoding of data etc is custom stuff I've written. I will look at the RCSwitch library to see if I can make use of it - my problem will be if it uses the same FIFO function from this lib I will probs still have the same problem I suspect. |
UPDATE: Ok, I managed to get it all working perfectly (albeit using CC1101 on it's own SPI). SmartRC-CC1101-Driver-Lib-JT.zip Following the ESP32 SPI example found here: Which talks about different SPI busses etc, I modified the library to make use of the otherwise unused "HSPI" |
This library conflicts with TFT_eSPI, to solve it I had to change the "spi" variable to "ccspi" in the library, since it conflicted with the spi class of TFT_espi, if you modify it it will help many people who use both libraries.
The text was updated successfully, but these errors were encountered: