1

So recently I've been testing the official 7" touchscreen and everything went ok. But after adding the last update of the bcm2835 library to use the SPI port in order to use the MF-RC522 board, the touch interface stopped working.

So, what could this be due to? I need to use both of them at the same time.

Thanks in advance.

NOTE: I'm using a Raspberry Pi 2 Model B

goldilocks
  • 58,859
  • 17
  • 112
  • 227
user1903
  • 111
  • 1
  • I think what you mean is you can't figure out how to use both of them at the same time, not that installing libbcm2835 caused the screen to stop working. – goldilocks Apr 25 '16 at 13:51
  • That could be the problem, yes. How can I manage to use both of them at the same time? – user1903 Apr 25 '16 at 15:10
  • Have a look at this but I suspect the touchscreen driver hogs the bus so you are out of luck. I could be wrong. – goldilocks Apr 25 '16 at 15:15
  • But if the touchscreen hogs the SPI bus it will still be working. It should be the RC522 board the one which wouldn't work, don't you think? Is there any way I could check the SPI bus traffic? – user1903 Apr 25 '16 at 15:25
  • I don't know, I don't use the SPI bus, but it sounds like you are homing in further on what your real question is. My first comment was simply to point out that if simply installing libbcm2835 has disabled the touchscreen even when the other board is not in use or attached, you've made some other mistake/done some additional thing at some point. Installing the library could not, all by itself, disable the SPI bus, etc. – goldilocks Apr 25 '16 at 15:27
  • Put another way, labelling a question Raspberry Pi 7" Touchscreen not working, then implying (even if it is just sematic confusion) that it is because you installed libbcm2835 probably will not get the attention of the people who can help you, because you aren't asking the right question -- perhaps you are assuming everybody just reads everything all the way through because these are problems other people must solve (false). Hence, making an effort to be as clear and precise as you can will be of benefit to you. – goldilocks Apr 25 '16 at 15:34
  • I understand what you are saying, I just didn't know how to ask the question in a better way. Thanks @goldilocks – user1903 Apr 25 '16 at 15:36
  • I've changed your title to something more precise ;) A big reason I see an issue here is we probably get a question or two a week from people who bought a touchscreen and it doesn't work. Most of them end up being because of driver or connection issues (or just plain get ignored). Your question is very different from those. – goldilocks Apr 25 '16 at 15:40
  • Are you using different SPI channels? Did the code you are using ever work? Where is the code? – joan Apr 25 '16 at 16:29
  • The touchscreen I don´t even know the channel which is using. Fot the NFC module I'm using this library with the SPI_CE0 pin attached to the module.

    The code is the Read.py example from the lib.

     – user1903 Apr 25 '16 at 16:43
  • They can't use the same chip select. Have you tried using SPI_CE1 for your NFC module instead? – joan Apr 25 '16 at 18:06
  • Nope. I've just realised about that, tomorrow I will give it a try. Thanks man! – user1903 Apr 25 '16 at 18:40
  • That didn't work as expected, even if I disconnect the MFRC522 module, the touchscreen doesn't work anymore. – user1903 Apr 26 '16 at 15:29

0 Answers0