Just to say that it worked! Thanks a lot again. So if it may help others, here is what I did to compile my first C program for Onion:

• install Kubuntu 14.04 64 bits on a VirtualBox VM

• follow KitBishop guidelines (great stuff initially here : https://community.onion.io/topic/9/how-to-install-gcc/22

• Download the tool chain from https://s3-us-west-2.amazonaws.com/onion-cdn/community/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64.tar.bz2

• Unpack it to some suitable directory (referred to below as <tc_dir>)

• Set up environment variables as follows (I put this in my ~/.profile file so it was always there):

PATH=<tc_dir>/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin:$PATH

STAGING_DIR=<tc_dir>/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2

export STAGING_DIR

• Create your c program - e.g. test-prog.c

• Compile the program using (e.g.): mips-openwrt-linux-uclibc-gcc test-prog.c -o test-prog

• Transfer the output file (test-prog) to your Omega using you favourite tools.

• On the Omega in the directory you placed the file, run it by: ./test-prog - and there you are

Hi,

this message to share with you a new project I have built with an Onion Omega. Plus some metal machining and wood-working.

website: http://heliogyre.com
facebook page: http://www.facebook.com/HelioGyre - please feel free to like and share if you want to help me getting the product know (and develop Onion Omega's market footprint!)

Done. (submitted a first time by mistake while the survey was incomplete, but re-submitted completed afterwards)

Thank you both for testing on your side and reporting these remarks. So I have re-routed my PCB with GPIO23...

@Onion designers: if there is a way to clarify what are the restrictions for GPIO12, I am interested. And same for any other GPIO

Hi,

I am trying to control 2 stepper motors in a C++ program thanks to the new-gpio API (thanks again Kit!).

All is fine with GPIOs 0-1-6-7 for the first one, and 8-23-13-14 for the second.

However if I am using GPIOs 8-12-13-14, it does not work : the output of GPIO12 gives nothing (that's the reason why I tried with the next available GPIO on the board, which is GPIO 23.

Would you have any clue ? Is GPIO 12 reserved for some specific purposes (I2C, ...) ?

Thanks in advance, I have designed a PCB routing assuming I would use GPIO12,, and would like to stick on it if possible.

Just done

Hi,

needing to build my own dock, I am looking for a place where to buy the 32-pin, 2mm pitch connectors (male-female), that I would solder on my dock to plug the Omega. I would need of course 2 of them, spaced by 24.4mm, for the 2 rows.

Does anyone know where to find that? This 2mm pitch is very specific and hard to find...

Ideally a provider shipping quickly to France (excluding US-based ones unfortunately).

Thanks!

If it may help someone, here is a working piece of code to make a stepper engine rotate. The unipolar, 4-phase stepper engine is connected to pins 0, 1, 6, 7.

The program expects one argument being the microseconds to wait between 2 half-steps. In my case, below 600 it's too fast for the engine to follow, but any value higher is fine.

Thanks again KitBishop for this nice GPIO API!

Cheers

#include <cstdlib>
#include <stdio.h>
#include <unistd.h>
#include <string.h>
#include "GPIOPin.h"
#include "GPIOAccess.h"

int main(int argc, char** argv) {
int d = atoi(argv[1]);
printf("delay=%d\n", d);

GPIOPin* pins[4];
pins[0] = new GPIOPin(0);
pins[1] = new GPIOPin(1);
pins[2] = new GPIOPin(6);
pins[3] = new GPIOPin(7);
for (int i = 0; i < 4; i++) {
pins[i]->setDirection(GPIO_OUTPUT);
}
int i = 0, j = 3;
for (;;) {
pins[i]->set(1);
usleep(d);
pins[j]->set(0);
usleep(d);
j = i++;
i = i % 4;
}
return 0;
}

Hi,

this message to share with you a new project I have built with an Onion Omega. Plus some metal machining and wood-working.

website: http://heliogyre.com
facebook page: http://www.facebook.com/HelioGyre - please feel free to like and share if you want to help me getting the product know (and develop Onion Omega's market footprint!)

Done. (submitted a first time by mistake while the survey was incomplete, but re-submitted completed afterwards)

Hi,

I think I have more or less understood what happened:

• whenever I plug 5V to any GPIO, the 2.0V pin (type in my previous message : read 2.0V instead of 1.8V) outputs 3.4V, just like the GPIO17
• and in that case, the Onion does not start (the LED does not light or blink).

If instead of plugging 5V on a GPIO, I plug a 3.3V signal, then things seem to be OK, and the Omega boots.

Now I have discovered a new thing, is that despite the Omaga starts its own Wifi, the former IP (192.168.0.7 in my case) is not accessible from my home Wifi, and I had to reconfigured the Wifisetup through a Serial connection.

It looks like I have made a wrong wiring 2 days ago, where I plugged a connector of my home-made PCB the wrong direction, and my guess it has partly damaged the Omega, and make it forget its wifi settings...

Though I am not sure (I would understand it has been completely destroyed, but only very partially as it seems to be for me, seems very strange), any feedback from anyone here is welcome.

Best regards,
Frédéric

Hi,
adding another strange thing I noticed: the 1.8V pin outputs 3.4V, and it is not connected to anything. I Never measured it before, but it might give a hint to my problem.

Please help with any idea
Frederic

Hi,

My Omage has a stange behaviour since today, that was not happening before...

It looks like when there is a 4.5V voltage on GPIO 18 and 19 at boot time, the Omega does not start. At least, the LED does not light.

If I put this voltage to only one of GPIO 18 or 19, it starts.

If after the LED has lit, I put this voltage on GPIO 18 and 19, then no problem.

However in a separate post, Lazar told that he could test 5V on an input without issues (https://community.onion.io/topic/381/electrical-specs/5)

So,

1. could it be that a too high voltage on these inputs prevents the Omega to start?
2. do you have any clue why it was working until yesterday, and no more now?

Thanks for any help, I am struggling with this and don' t understand what"s wrong.

Thanks Kit.

We then agree that the code is in onion-settings-general.html.

I think there is a bug as I stated yesterday, around line 202, as zonenamePromise does not set the zone name but the time zone (redundantly to the other Promise right before it).

However, on my Omega, the Console DOES change the timezone (but not the zone name as expected with this bug).

And thanks for the Polymer tip, will check your URL.

Thanks Kit for the tests and the init cycle demystification!

Indeed, I think the /etc/init.d/system script is also called when one changes the time zone (otherwise as I was saying earlier, the new time zone is not appearing in the date command). And I am wondering what is the magic behind this. Actually it looks like the console is written with some web framework, but I don't know which one, and I don't understand who it is architectured. Might look like Symfony, but it is not.

Me again... I did investigate further, and could see that /etc/init.d/system was doing a "echo $timezone > /tmp/TZ" (and also a "date -k")

So am I correct by assuming that to properly change the timezone from command line, one should:

1. uci set system.@system[0].timezone=XYZ
2. uci commit system
3. /etc/init.d/system reload

???

(indeed, I don't understand how and when /etc/init.d/system is called when the timezone is changed from the console - if I can get an explanation for that, that would be cherry on the cake)

Thanks!

Now one question please.

[ things are going strange on my Omega: the /etc/TZ file is now present on my system, but the /etc/timezone one I was featuring a few days ago has disappared!!! Well, this is good news, since I am back to normal, but I don't understand what happened. ]

I am trying to change the timezone with the command line, by mimicking the console:

uci set system.@system[0].timezone=XYZ
uci commit system

This changes the /etc/config/system file, but /etc/TZ is not changed (it is actually a link to /tmp/TZ, which does not change).

And finally the "date" command still features the previous timezone

So, what should I do on the command line to actually change the time zone?

Thanks in advance!

(btw, when I change the timezone through the console, all is changed properly)

While browsing the files on the Onion, I wonder if there is not a bug on setting the "zonename" (as opposed to "timezone"):

1. when I change the timezone through the console, the /etc/config/system still indicates "UTC" as zonename

2. in /www/apps/services/onion-device-provider/onion-device-provider.html, line 202, the zonenamePromise seems to change the timezone, instead of the timezone. Actually it looks like the timezone is changed twice, instead of changing the timezone and the zonename. Which would explain the zonename sticks to UTC even though the timezone is changed.

Looks like the problem does not happen on Kit's Onion, maybe I have a too old build.

Hope this helps?