-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Alias gpio pin datatype #898
Conversation
Memory usage change @ ea66839
Click for full report table
Click for full report CSV
|
I'm assuming that report is measured in bytes. Didn't expect the ATTiny to have that much improvement! |
Nice |
7d42b3f
to
bdc8bbb
Compare
I hardware tested this on Pico SDK (while I still had the HW setup for addressing #899); test went well. I also added a follow up to the 557d165 that removed a useless I also fixed compiler warnings about the magic numbers used when the pin numbers are not passed to the RF24 c'tor. |
includes a follow up from 557d165 in which a useless RF24::spi member was declared for RP2040 platform.
This will fix RF24::isValid() and prevents overflow from using the old 0xFFFF value in the RF24 overloaded c'tor that accepts no args. It also helps to avoid "magic numbers" as was previously used.
bdc8bbb
to
832538d
Compare
I tested this on Arduino (Feather RP2040) and Linux (SPIDEV and MRAA drivers). I'm going to modify the examples to replace the "magic numbers" passed to the c'tor with defines: #define CSN_PIN 0
#ifdef MRAA
#define CE_PIN 15 // GPIO22
#else
#define CE_PIN 22
#endif
// Generic:
RF24 radio(CE_PIN, CSN_PIN); This way it is explicit what the numbers represent in the c'tor args. |
This is actually an overlooked follow up to nRF24/RF24#898 The problematic inconsistency was primarily affecting builds with the RPi driver.
This is actually an overlooked follow up to nRF24/RF24#898 The problematic inconsistency was primarily affecting builds with the RPi driver.
resolves #896