Problem with arduino NANO EVERY and libraries

[flyx]

Hey what's up guys, I have bought my new arduino nano every like a month back now and still can't figure why are libs not working at all with it. I know that some of them are not updated yet for this new board, but there are problems with some basic ones too. I thought that some updates of the pack with this board in arduino ide might help, but still nothing and i would really like to get it running. I am little confused if it's just me, or other people too, cause I couldn't find any problems like this.
Compilation error is in attachment and btw, if it needs to solve some macro or files changes, I do not care and know how to do it - I am not a begginer

If you care, just quote me, thanks a lot for any reactions

[pert]

This is some strange looking output. What software are you using?

[david_2018]

I managed to replicate the errors using the OLED_I2C library from Rinky-Dink Electronics.

http://www.rinkydinkelectronics.com/library.php?id=79

Appears to be some direct register manipulation, so its not going to work with the atmega4809 processor used in the Nano Every.

To the original poster, you might want to look through the forum for the Uno WiFi rev 2 board, that board uses the same processor and you may find some suggestions there.  You can also try some of the other OLED libraries, you may find one that will work.

[flyx]

This is some strange looking output. What software are you using?

It is an arduino extension for microsoft visual studio on win10. It works the same, but i prefer it more and it has more accurate error output. If you need error output from arduino IDE, i'll make one, but I have been testing it and it doesn't work too

[pert]

I would prefer the output from the Arduino IDE because I'm familiar with it. I'm having trouble interpreting that output from Visual Studio because I have only used it for a very short period of time years ago. Others here may be experienced with VS and be able to work with that output easily.

[flyx]

Okay here you have it

[oqibidipo]

Rename the RTC variable, RTC is already defined in <avr/iom4809.h> (but not in <avr/iom328p.h>).

Code: [Select]

#define RTC                   (*(RTC_t *) 0x0140) /* Real-Time Counter */

[david_2018]

Rename the RTC variable, RTC is already defined in <avr/iom4809.h> (but not in <avr/iom328p.h>).

Code: [Select]

#define RTC                   (*(RTC_t *) 0x0140) /* Real-Time Counter */

That's probably because the atmega4809 has an internal RTC, although I'm not sure how accurate it is.

[flyx]

Thank you guys, but it does not solve the problem with the oled library, which is still giving error outputs. There are some undefined macros and that is little strange, isn't it?

[68tjs]

That's probably because the atmega4809 has an internal RTC, although I'm not sure how accurate it is.

The accuracy of the RTC will be that of the main oscillator.
Arduino made the (very bad) choice not to use quartz or external resonators, unlike in  his other cards, probably to save money.
The accuracy of the internal oscillator is only ± 2% between 0 C and +70 C.

Throughout the operating range it is only ± 4%.



I do not think this card is useful.

[david_prentice]

Quote which library example.
Quote which library version.  e.g. from the IDE Library Manager

You will find that you get answers on this forum.
And a "fix" might get offered to the library author.   (for the benefit of the world)

Without this information we are on a wild goose chase.
Always test library examples before attempting to write your own sketch.

David.

[erikjanssen]

Is there a way to verify a library for the new Nano boards without installing by trial and error?

[pert]

Is there a way to verify a library for the new Nano boards without installing by trial and error?

By "installing by trial and error", do you mean the process of installing a potential library, uploading to the Nano, and seeing if it works?

[david_prentice]

I don't think you have much choice.   Most libraries are intended for "all targets" as default.
Very few libraries are restricted to specific targets.

You will only find out when you try to build for a NANO-EVERY target.

If you have a problem,   post on the Forum.
If you have a fix,  send a Pull-Request to the GitHub Repository

David.

[erikjanssen]

By "installing by trial and error", do you mean the process of installing a potential library, uploading to the Nano, and seeing if it works?

Yes that is the case, my application has three NANO's at the limit of their capacity talking to a MEGA through RF24Network. When verified for and EVERY they fail on almost all libraries I use. So yes I accept the invitation to report about my findings, later in a different post.

Replacing the NANO with an EVERY is possible but requires a more work than moving to a MEGA where I had no issues.

Maybe I should abandon the idea of using an EVERY and move to a NANO IoT instead and a full re-design of my application.