Skip to content
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

error: 'u1_t' does not name a type; did you mean 'uid_t'? (static const u1_t APPEUI[8] = { 0x86,....) #885

Open
T365 opened this issue Jul 18, 2022 · 3 comments
Assignees
Labels

Comments

@T365
Copy link

T365 commented Jul 18, 2022

Consider raising support questions on the forum first

There is a discussion site, forum.mcci.io, which includes a category focused on the Arduino LMIC. Unless you're sure that your problem is a bug in the LMIC, it would be great if you can try for help there first. That will keep issues focused on work that needs to be done by the developers.

Describe your question or issue

Please give a clear and concise description of the problem you're facing and what you'd like help with.

Environment

This information is very important; it's hard to help without a complete set of answers.

  • Version of LMIC being used. If using the latest github mainline, let us know, otherwise state the version.
  • Version of Arduino IDE being used:
  • Network provider (The Things Network, Swisscom, ChirpStack, etc.)
  • Region (EU868, US915, etc.)
  • Board (MCCI Catena, Adafruit Feather M0, Heltec Wi-Fi LoRa 32 v2, etc.)
  • Radio (HopeRF, SX1276, etc.)
@T365
Copy link
Author

T365 commented Jul 18, 2022

LMIC: 4.2.0.1

After update,

Suddenly I got this message:
error: 'u1_t' does not name a type; did you mean 'uid_t'?

My code:
static const u1_t APPEUI[8] = { 0x86,......}

I tried to change u1_t to uid_t
it compiles now, but my device will not connect now, I understand.

Can someone help me please ?

@terrillmoore
Copy link
Member

Changing to uid_t is not the right thing, u1_t is correct. Something is wrong with your compile environment, hard to say what it might be. u1_t is used everywhere in the LMIC and didn't change anytime recently. Sorry you're having problems!

@supcik
Copy link

supcik commented Nov 22, 2022

This is perhaps linked to the issue #914 and fixed with the current master version. @T365, can you please try with the current version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants