Furthermore as mentioned, I eschew RPi (for lots of reasons). If I add -extra-cxxflags="-DMY_DEBUG_VERBOSE_RF24" to the configure script, then when I run a test, it includes the output:Īs to particulars of this issue, hopefully one of devs familiar with that part of code (build scripts for RPi?) stops by. When the make is running, I can see it launching g++ with -DMY_RF24_CS_PIN=37 -DMY_RF24_CE_PIN=33. When I try to change their pins using -my-rf24-ce-pin=33 -my-rf24-cs-pin=37 with the configure script, it didn't appear the change the pins as the rpi would fail to connect to the nrf24 on those pins, but could still connect with the default pins. I found that the rpi would only successfully connect to the nrf24 when I'm using the default CS and CE pins. Even I must admit that it was my first purchase, before I knew any said in Problem changing CS and CE pins on RPi gateway: This is certainly the right approach, IMO.Ĭontrary to popular opinion, I am not such a fan of RPi, but since you already have it, on we go. I found MySensors and now I think I have a new hobby Welcome to the forums, said in Problem changing CS and CE pins on RPi gateway: To be honest, I'm happy enough to just use the default pins at this stage but this might help anyone else that finds themselves in the same situation. It does some things a little different which complicates things. Which suggests that the software knows that's I've specified alternate pins to use. If I add -extra-cxxflags="-DMY_DEBUG_VERBOSE_RF24" to the configure script, then when I run a test, it includes the output: DEBUG RF24:INIT:PIN,CE=33,CS=37 The OpenSprinkler RPi PCB board and case makes it harder (but not impossible) to access the back row of pins which is why I was trying to use non-default pins in the first place. I also tried directly editing the M圜onfig.h file to explicitly define the values, but that failed to work as well. I've connected up a nrf24l01 module to the Raspberry Pi and followed the guide, but I found that the rpi would only successfully connect to the nrf24 when I'm using the default CS and CE pins. The only valid comparison between these sources is the dates.I recently set up an OpenSprinkler that's using a Raspberry Pi and thought I could use it for more, then I found MySensors and now I think I have a new hobby It's all very impressive. However, know that the the 160-bit hash values in these two sources will never match.NOTE new link for Raspberry Pi OS release notes If you want to know the latest version of the firmware, check the release notes If you want to know what version of the firmware is on your RPi, use sudo /opt/vc/bin/vcgencmd version i.e. it is 'closed-source') the compiled/binary firmware is housed in this GitHub repo. ![]() The firmware source code repo is unpublished (i.e. One of the repositories houses the source code for the RPi firmware, the other repository houses the compiled/binary version of the firmware. The Organization (and possibly their suppliers/subcontractors) maintain two repositories for the Raspberry Pi firmware. The reason these hash values do not match for any given release date is that the hash values are computed on different file sets REFERENCE: However, as at least one eagle-eyed contributor here has noted, the 160-bit hash values from the vcgencmd version command and the release notes do not match. from the RPi website: the release notes.from the command line: sudo /opt/vc/bin/vcgencmd version.There are two sources for this information: A 160-bit hash value (AFAIK, the algorithm used to compute the hash is unpublished).The firmware version seems to be identified by two pieces of information: ![]() Steve's answer is correct, but here are some more details that may be of interest.
0 Comments
Leave a Reply. |