Posts made by Johan Simons

Hi,

Can you make your project available for download so we can try it !?

thx

@Joshua-Cataldi
I also had an issue with the wifi in the past. Solution was to wait long enough, I think about 5mins, for the AP to become active again.

Or press the reset button >10secs for a complete reset

I have not seen this issue anymore in more recent firmwares, maybe I didn't create that situation again. Anyway, I would suggest to upgrade the firmware to the latest

Found the solution.... use an I2C IO expander like the MCP23008 used on the relay expansion.

This has a power-on-reset circuit that provides controlled power up

Mosquitto is an MQTT broker (server), and the main purpose of a server is to be available as much as possible. What is wrong with that ?

I am driving an external relay board, where I need to pull the driving line to gnd to put the relay in the on state

The input stage of the relays is an optocoupler with the anode tied to VCC through a 1K resistor, and the cathode side goes through a led to the driving input coming from the Omega.

To be stable during boot and initialisation I need a pullup resistor on that driving input, but:

• to which voltage should I pullup... 3V3 or 5V?
• which would be a good pullup resistor value? 10K, 100K, 200K

thx

@Kit-Bishop

Removing the sigaddset(&irqSigset, SIGINT); did NOT solve the problem of CTRL+C not working.

I compile the fast-gpio sources in my own C++ app, so it is all in my executable, no libraries linked, no external apps called or processes spawned.

@Kit-Bishop

I was just using set pin direction and get/set pin value, so it was quite a large difference in memory usage between fast and new GPIO.

But as you state, your code is more extensive and provides more functionality.

For my application the extra memory is no problem as it will be the sole app running on the Onion. My eye fell on it while debugging a memory leak.

Anyway, it would be great to have the CTRL+C issue fixed.

Thx for the effort

@Kit-Bishop Thx for looking into it.

I also noticed that my app uses 4% system memory with the fast GPIO libs... and 10% with your new GPIO lib. Guess that has to do with the usage of threads in your lib.

Seems like my framework was doing just fine... but I was using the new GPIO library from Kit Bishop !?

Once I backed out this library and used the fast GPIO instead, CTRL+C worked as expected.

Possibly the new GPIO library also sets a hook for CTRL+C

Does anybody have a sample how to connect and program an SPI device using C++

Hi,

I have this C++ framework that compiles across Win32 and Linux on x86/ARM/MIPS.. so far so good.

To be able to trap the user pressing CTRL+C I have installed following signal handlers that work fine under Linux on x86 and ARM (Raspberry) platforms.

signal(SIGINT, sigproc);
signal(SIGQUIT, quitproc);

Unfortunately these don't seem to work on OpenWRT/Omega

Anybody an idea which signals I should use?

thx

Still no news on the docking dimensions???

http://www.aliexpress.com/item/Free-Shipping-10pcs-2mm-40-Pin-Male-Single-Row-Pin-Header-Strip/32327259863.html?spm=2114.30010308.3.1.OSreCh&ws_ab_test=searchweb201556_3,searchweb201644_1_10001_10002_10005_301_10006_10003_10004_62,searchweb201560_5,searchweb1451318400_6150,searchweb1451318411_6448

This one https://community.onion.io/topic/332/picorouter-baseboard/2

I think it was the size of the omega itself, not the dock

Hi,

I'm looking for technical documentation, dimensions and mounting hole locations of the docks and expansions.

thx, Jo

Great, I'll have a look at the code.
thx

Still some questions:

1. where can I find the C/C++ source code to drive the relay and PWM expansion
2. and the schematics for these expansions, would be great to built my own expansions

thx

Hi Alexander,

Below are in a few steps my way to success in building my cross platform apps:

1. I run a CentOS 6.5 linux box (32bit)

2. download the 32bits mips toolchain for Onion to /usr from this link https://s3-us-west-2.amazonaws.com/onion-downloads/openwrt/OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-i686.tar.bz2

3. unpack this toolchain using:
   cd /usr
   tar -xvf OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-i686.tar.bz2

4. move the extracted dir to a shorter name:
   mv OpenWrt-Toolchain-ar71xx-generic_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-i686 onion

5. in your app directory create Makefile.onion with following contents:

CC = /usr/onion/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-uclibc-g++
LD = /usr/onion/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-uclibc-ld
CFLAGS = -I /usr/onion/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/include
LDFLAGS = -L /usr/onion/toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2/lib

EXEC= hello.onion

THREADLIB = -lpthread
RTLIB = -lrt
DLLIB = -ldl

IFLAGS = -I..
LDFLAGS += ${THREADLIB} $(RTLIB) $(DLLIB)

all: clean $(EXEC)

OBJS=
hello.o

$(EXEC): $(OBJS)
$(CC) -o $(EXEC) $(OBJS) $(LDFLAGS)

clean:
rm -rf $(OBJS) $(EXEC)

.c.o:
$(CC) -c -o $@ $(DEBUG) $(CFLAGS) $(IFLAGS) $<

.cpp.o:
$(CC) -c $(CFLAGS) $(DEBUG) $< -o $@ $(IFLAGS)

hello.o: ../hello.cpp
<<<
6) make your hello app: make -f Makefile.onion

1. copy hello.onion to Onion and give it exec rights

@Kit-Bishop
HI Kit,

Great work, a kickstart for me as a C++ programmer.

Could you also provide the makefiles for the library and gpiotest, I am always interested in how other people do things and see how I can improve my own makefiles (not an expert in that)

thx, Jo