Best posts made by Patryk Wychowaniec

Hey, fellow Omega programmers

I've been working on a PCD8544 driver last few days and thus I had to control GPIO pins from inside my C++ application - I didn't found any generic library for Omega 2 and so I've decided to roll my own one:

https://github.com/Patryk27/Omega2-GPIO

I've taken the mechanics from the fast-gpio tool and refactored it so it was down to two files and Arduino-like nomeclature (it has pinMode, digitalWrite, digitalRead and shiftOut).

I hope it gets useful for someone

I've included one simple example there and maybe tomorrow (depending on my free time) I'll post my PCD8544 driver - it will most likely be more useful than just this GPIO toggling tool, but it's always something to start with.

Where did you get the 0x10000600 number from?

Take a look at my GPIO management code:
https://github.com/Patryk27/Omega2-GPIO/blob/master/gpio.h

@volkan-ünal

Hi!

I have already responded you on GitHub, but to keep conversation here complete, I am also copy-pasting that response (https://github.com/Patryk27/Omega2-GPIO/issues/3) here:

I initially followed code written by the Omega team (https://github.com/OnionIoT/fast-gpio/blob/master/include/fastgpioomega2.h#L12) and I haven't really faced it with the documentation.

I believe the reason is that later we're doing a mmap call, which has to be page-aligned (which 0x10000600 is not), but it could be also a mistake in the MT7688's documentation.

Omega is not really a solution if you plan using it with other power source than USB adapter.
I would recommend going for the AVRs and if you need for example Wi-Fi, you might consider connecting AVR to ESP8266 and so on.

Properly prepared AVR-ESP stack can be ran on standard batteries for many weeks, even months (of course it strictly depends on your project).

Post some logs when it's restarting, otherwise it'll be hard to guess.