-
Notifications
You must be signed in to change notification settings - Fork 212
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
'const lmic_pinmap' has no non-static data member named 'rxtx_rx_polarity' #56
Comments
Update: I searched back and installed exactly the specified version: 2.1.0. The error is still there and same for later versions. |
Sorry you're having problems. Let me take a look; I don't usually use the examples, and we don't have CI set up, so it's possible that we missed updating this during the revision that completed the support for hte Murata module. |
Hi again, I researched this. Very sorry, this is a documentation error. The file I strongly suggest you update to 2.1.4, because there are some important minor changes. If you're using our board support package, also update to v1.0.8 (if using Linux or macOS -- v1.07 will work well for Windows). Sorry for the inconvenience. I'll update the docs now. --Terry |
Fix #56: erroneous pinmap name in README.md
Thanks very much for your report. Docs are updated and new release posted. |
Thanks for getting into this and solving it so quick! Now it all makes sense. I already wondered why I couldn't find "rxtx_rx_polarity" in the source code at all. |
When I try to compile an LMIC example sketch with the suggested settings for the Catena 4551 board, I am getting the following error:
const lmic_pinmap' has no non-static data member named 'rxtx_rx_polarity
I have read in the Catena Arduino Lora Wan lib that I should install LMIC 2.1 version of the library to avoid this issue.
But when I followed the link there, I ended up in this repo, which does not seem to contain the correct version? Or at least the error is (still) there when I try to compile an example sketch.
The text was updated successfully, but these errors were encountered: