Hey, just got my order for both of these devices and I'm pleased with them.

In my journey yesterday I've tried the Fast-GPIO with the out-of-the-box firmware and it worked on both the 2 and the 2+.

However, later on I discovered the Console and it suggested I upgrade the firmware, so I did it on both devices. After doing some modifications (installing PHP, Node-RED, etc) I discovered that the Fast-GPIO program doesn't work anymore.

No matter what I do, read/write/pwm.. it just throws a "segmentation fault". Now, first thing I did was some research, and I found out it's a bug with /dev/mem not existing, which I confirmed by doing a "cat /dev/mem" which returned that it doesn't exist.

Of course, a simple fix would be downgrading the firmware, which I did. I actually tried b141 all the way to b152 and the problem persists in ALL of them. How is this possible? It's even acknowledged as an official bug but it wasn't addressed in any of these versions?

I know I could use gpioctrl, but I don't know how to make it return (in the serial terminal -- for PHP) just a LOW/HIGH or 0/1, which Fast-GPIO was able to do..

So my questions are:

1. Is there a way to manually fix /dev/mem (installing a package or enabling a kernel module somehow), without recompiling a custom firmware. If yes, how?
2. Does your Fast-GPIO work? If yes, what's the full version that you run? (ex. 0.19 bXYZ)

@Costas-Costas Oh, so just the PCB

I actually thought that someone managed to get a vendor that would print out a full dock cheaper than the official ones.

Oh well..

Hey, do the panel contain all the electronic components already soldered if we order from PCBs.io or do we have to source the components and solder ourselves?

@Shashi-Alabur Got your EXACT issue. It used to work with my current power supply and now it just reboots.

Can you post a picture of what your powersupply / wiring looks like? I'd like to replicate it and see if it fixes my problem as well..

After installing Node-RED I checked out all the available nodes from the Palette Manager and I didn't notice one that will allow me to control the Omega2/2+ GPIO pins from there.

Am I missing it, or is one not developed yet?

If someone developed one for his personal use, I'd appreciate if we'd get a link for that. I'm just looking for basic input/output (no pwm or other fancy stuff)..

@Chris-Stratton I have to try it. I'm not looking to anything close to real-time. ~500ms delays are ok.

I'll have to give it a go tomorrow. Thanks for the hint!

Hey, just got my order for both of these devices and I'm pleased with them.

In my journey yesterday I've tried the Fast-GPIO with the out-of-the-box firmware and it worked on both the 2 and the 2+.

However, later on I discovered the Console and it suggested I upgrade the firmware, so I did it on both devices. After doing some modifications (installing PHP, Node-RED, etc) I discovered that the Fast-GPIO program doesn't work anymore.

No matter what I do, read/write/pwm.. it just throws a "segmentation fault". Now, first thing I did was some research, and I found out it's a bug with /dev/mem not existing, which I confirmed by doing a "cat /dev/mem" which returned that it doesn't exist.

Of course, a simple fix would be downgrading the firmware, which I did. I actually tried b141 all the way to b152 and the problem persists in ALL of them. How is this possible? It's even acknowledged as an official bug but it wasn't addressed in any of these versions?

I know I could use gpioctrl, but I don't know how to make it return (in the serial terminal -- for PHP) just a LOW/HIGH or 0/1, which Fast-GPIO was able to do..

So my questions are:

1. Is there a way to manually fix /dev/mem (installing a package or enabling a kernel module somehow), without recompiling a custom firmware. If yes, how?
2. Does your Fast-GPIO work? If yes, what's the full version that you run? (ex. 0.19 bXYZ)

I have the same problem. Has anyone found a fix for it?