@Don-DeGregori said in OLED character size:
Just received the OLED expansion board. It seems to work. However, don't see any way to increase character size. Probably don't want to go smaller, but a bit larger would be OK for emphasis.
What I think you need is a different font renderer. @Jonathan-Reisdorf has done some work on this and there maybe some useful information to be found in https://community.onion.io/topic/1570/big-text-on-the-oled-expansion
@Chris-Stratton said in Compiling for Omega2+ on Red Hat Linux?:
Hopefully the defaults would work.
Especially if the real goal is just to build enough to get a working toolchain rather than a complete bootable and functional system.
You should be OK with the defaults
Also, building the toolchain works and is usable - just make sure you select it in make menuconfig 
@Daniel-Boese said in Compiling for Omega2+ on Red Hat Linux?:
@Chris-Stratton
... ... ...
I suspect I'm going to have trouble enough just figuring out which kernel modules I'm going to need to include to support the Omega2+'s built-in hardware, so that I don't accidentally brick the thing. (I'm tempted to usemake menuconfigand just select /all/ the blank items to compile as modules to be on the safe side...)
Good luck with that 
Chances are that in selecting all* blank items will not work.
I have tried something similar and basically just gave up when there were several modules that:
@Chris-Stratton said in C++ raw GPIO?:
@Costas-Costas the approach chosen by Kit and now Travis won't work on standard firmware until the /dev/mem issue is fixed.
Yes, one of the many reasons that I am holding off upgrading the code to Omega2
The other main constraint (other than time availability) is that the endianess differs on the Omega1 and Omega2 and I need to check out the places where this is significant in the code (I know of at least one place)
@Travis-Hyyppa said in C++ raw GPIO?:
Hello!
I was wondering if there were a good example somewhere of just plain old pin output high/low in C or C++?
You may be interested in the suite of C/C++ libraries and programs I have published here: https://github.com/KitBishop/Omega-GPIO-I2C-Arduino - complete with reasonable documentation and instructions
Currently these are specifically for the Omega1 and will need some modifications for the Omega2 - I will be doing this at some time but not sure when
@Pierre-Rossinès said in Timer Interrupts on the Omega2:
@Kit-Bishop
Have you made your code open source ? Maybe someone else is able to make the changes necessary to make it work on the omega2. I am willing to try even if my knowledge in this field is quite limited.
Was it necessary to rebuild the full system to get interrupts on the Omega 1 ?
The code is freely available and reasonably well documented at https://github.com/KitBishop/Omega-GPIO-I2C-Arduino For what its worth, I have licensed it under GPL v3 - feel free to use it
@WereCatf said in Omega2 - LEDE or OpenWrt?:
@luz said in Omega2 - LEDE or OpenWrt?:
......
I tried to tell you, it still wouldn't be identical. .config only tracks configuration-changes that LEDE is aware of, it doesn't track any changes to the actual source-code nor any kernel-config changes outside of the pre-defined ones that LEDE-supports. So no, it still wouldn't be identical, they have made changes that the LEDE configuration-tools are not aware of and thus wouldn't be tracked in .config.
Which brings us back to an issue that has haunted us since the early days (over 1 year ago) of the Omega1 - without access to the official repository that Onion uses we are still playing catch up and trying to hack things together.
Despite numerous requests for this, no reply has been forthcoming - not even a We can't because of X Y Z
A few weeks ago there was discussion on this forum as to whether or not Onion were in breach of the terms of the open source licences on this issue. That discussion kind of petered out with no resolution on it
@Mitch-Christensen said in Cloud Compile:
Agreed @Kit-Bishop. Automating the 'copy to the Omega' within the IDE makes total sense.
At some point I was going to look into FSSM/RDIST to completely automate the copy (i.e. FSSM detects changes to the binaries and calls scp/rdist to copy them out).
Since it is meaningless to try to run an Omega program on the host machine (in my case Kubuntu), what I did was to create a small script on the system on which I run Netbeans that copies the file passed as a parameter to the Omega using scp. Then in the Run section of the Project Properties, I set the Run Command to: "<myscript> ${OUTPUT_PATH}" where <myscript> is the name of the script file for the transfer including full path to it.
@Andy-Burgess said in Console splash screen but no logon popup:
Ok It turned out my browser was the problem.
IE and Chrome just had blank Console Screens
Firefox worked great on windows 7.
Interesting. The original code for the Omega1 had problems with Firefox but worked OK with Chrome
@Chris-Stratton said in Omega2+ does not turn on:
Might want to be careful about that - unless there's level translation circuitry in there, you are putting substantial stress on the MT7688 serial pins (input especially) by connecting that 3.3v device to a 5v Arduino.
This is one of the issues I have with the Omega2 as against the Omega1. The Omega1 runs on the same 3.3v but the IO pins were explicitly stated to be 5v tolerant. They play well with Arduino and Arduino shields running on 5v.
I even produced an Arduino Expansion board that plugs in to the Expansion Dock and provides direct access from the Omega1 to Arduinos and Arduino shields (see https://github.com/KitBishop/Omega-Arduino-Expansion)
I am probably going to have to redo this to incorporate some level shifters to accommodate the Omega2 3.3v only.
That said, there are some Arduino Shields that run on 3.3v. There is also an Arduino that itself runs on 3.3v (Arduino Pro 328 - 3.3V/8MHz) while still using the standard Arduino Uno header layout (see https://www.sparkfun.com/products/10914). And finally there are instructions available to convert a standard Arduino Uno to run on 3.3v - see: https://learn.adafruit.com/arduino-tips-tricks-and-techniques/3-3v-conversion
@Mitch-Christensen Basically the same process can be done with Netbeans as well - I even have a build target that automatically transfers the resultant executable to the Omega
@Chris-Stratton I previously wrote a suite of libraries and programs for the Omega1 (see https://github.com/KitBishop/Omega-GPIO-I2C-Arduino) and amongst this is some code for I2C that includes raw access (i.e. without specifying a register) because I had some devices that required this.
Unfortunately, my code is currently only for the Omega1, it will not work as is for the Omega2. I need to make some changes for the Omega2 - I intend to do this but can't at the moment say when I will have time to do so (paid work getting in the way )
@Don-DeGregori This is really strange. For the Expansion Dock (see https://docs.onion.io/omega2-docs/expansion-dock.html) GPIO 19 (and GPIO 18) are shown as exposed next to I2C SCL/GPIO 4 but for the Power Dock (see https://docs.onion.io/omega2-docs/power-dock.html) these two same pins are shown as GND
To Onion devs: what gives? I understood that the expansion header on the Expansion Dock and on the Power Dock were supposed to be the same thing for connecting expansion boards. It is more than concerning that the documentation shows that they are different
@Patrick-Rainsberry This is pretty well what I expected except for the usage of GPIO 11 which surprises me
I have access to the circuit diagrams for the Omega1 and Expansion Dock and OLED Expansion
On these, what is marked as GPIO 11 on the pin out diagrams referenced above is used for VDD25 (i.e. 2.5Volt supply) and is used on the OLED Expansion to supply power to level shifters between the I2C signals from the Omega and the OLED display chip.
I am unable to find schematics for the Omega2 (hint to Onion devs: can we have ALL schematics for the Omega2 and related boards please ) so can't tell whether this has been repurposed for the Omega2 etc. or whether the pin out diagrams for the Omega2 etc in the Omega2 docs referenced above are wrong in this respect
@Luciano-S. Don't know who gave you a -1 on this, nor why. I generally agree with you and recently made a similar related post: https://community.onion.io/topic/1583/using-markdown-to-format-posts-for-better-clarity
@Patrick-Rainsberry The OLED uses I2C, so (as far as I am aware) the only pins you should need to connect are:
On the Omega2, the position of these pins is shown in https://raw.githubusercontent.com/OnionIoT/Onion-Docs/master/Omega2/Documentation/Hardware-Overview/img/Omega-2-Pinout-Diagram.png which comes from https://docs.onion.io/omega2-docs/omega2.html
Because the OLED is designed to plug in to the Expansion Dock, you can see where the pins are from https://raw.githubusercontent.com/OnionIoT/Onion-Docs/master/Omega2/Documentation/Hardware-Overview/img/expansion-dock-expansion-header-pinout.png which comes from https://docs.onion.io/omega2-docs/expansion-dock.html
@Chris-Stratton said in Reset Button not working on Minidock:
Arguing about markdown is pointless, the content of useful information is the same either way. If you don't want to read this thread because you find it personally annoying, then don't.
and:
What would be useful is ,,,,
I both agree and disagree with this. I agree that the content of the information is (largely) the same no matter what format it is in, but then so would a hex dump of the information, but no one would want to plough through that! I disagree because on this forum we are all pretty much unpaid and give of time freely to try to assist and the clear presentation of information will be helpful (as distinct from useful) is more likely to elicit a response if the information is clearer to to decipher.
While it is obviously up to the requester to present the information in any way, the process of communication requires clarity - the clearer the request, the more likely it is to get a response.
That said, I believe it is more than likely that many people don't know the ins and outs of presenting information via markdown (it certainly took me a while to get used to it and I still don't know it all). Consequently, I have added the following post as a pointer to formatting information using markdown: https://community.onion.io/topic/1583/using-markdown-to-format-posts-for-better-clarity
When making a post on the forum, your post can be formatted using markdown
Do so will make your post easier to read and if you are asking a question and presenting a lot of information (particularly code snippets, file contents etc.) it will make it easier to read and more likely to elicit a helpful response from others if it is well presented and clear to access - it is all about clarity of communication
If you are unclear as to how to use markdown at the top right of the window in which you type your post, you will see:
clicking on the
will take you to a reference to the page http://commonmark.org/help/ that outlines the use of markdown
@Mitch-Christensen Pretty similar to what I do. Though I use Windows and run a Kubuntu virtual box on which I have Netbeans set up and the toolchain installed and just point my Netbeans C/C++ environment to the toolchain. Even have a custom target in the Netbeans project that once the code is built, connects to the Omega and downloads the code
@Fernando-Falci Good to see people doing things and contributing.
Is there any basic documentation on what you are working on? Even a brief outline description could be useful
