@Costas-Costas I actually followed the guide written by @Kit-Bishop which you can find here. I don't have any packages installed on the omega and no weird dependencies. This is for the omega 1.
I'm still toying with everything, but I've put what I have right now on github for you. The cmake file links paths to my local system, so that'd need to be changed for sure.
@Kit-Bishop Using your code I think I've boiled it down to the bare minimum required to get an led to toggle. Sharing in case anyone else may need an idea (if that's okay with you?)
https://gist.github.com/thyyppa/48605ae390aabf3397580408ddbca471
(keep in mind i'm new to C++ so this might break a ton of rules and leak memory like a sieve!)
I have a few Omega 1s that work just fine on my network, but each Omega2+ that i've tried absolutely will not connect (I've tried three now, one of which just arrived in the mail yesterday). Going through the initial setup i'm able to connect as a client of the device, but on the networking section of the web interface it will either hang up right off the bat or actually list ssids and then hangs up when trying to connect.
SSHing in 192.168.3.1 to try wifisetup yields the same results. I had hoped it was a firmware issue, but scp-ing over 0.1.9 b159 and flashing with -n didn't change anything.
I've tried to connect to three different routers, each a mikrotik running routeros. Is there a known issue with these routers? I've checked and they are not using TKIP.
Does anyone have any suggestions? I would love for these to work, they are incredible devices, but I'm totally out of ideas here.
Thank you in advance!
Travis
Edit:
Just tried with a freshly-reset d-link, no security, no password, both wifisetup and web client, still no dice. "Unable to connect to dlink. Please try again."
Edit2:
I am able to get an IP address and ping the internet when using the ethernet expansion.
Edit3:
Here's my /etc/config/wireless
config wifi-device 'ra0'
option type 'ralink'
option mode '9'
option channel 'auto'
option txpower '100'
option ht '20'
option country 'US'
option disabled '0'
config wifi-iface
option device 'ra0'
option network 'wlan'
option mode 'ap'
option encryption 'psk2'
option key '12345678'
option ApCliEncrypType 'AES'
option ssid 'Omega-2C11'
option ApCliEnable '1'
option ApCliSsid 'MySSID'
option ApCliPassWord '******'
option ApCliAuthMode 'WPA2PSK'
config wifi-config
option ssid 'MySSID'
option encryption 'WPA2PSK'
option key '******'
and /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd1d:48c4:7633::/48'
config interface 'wlan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.3.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
config interface 'wwan'
option ifname 'apcli0'
option proto 'dhcp'
@Costas-Costas I actually followed the guide written by @Kit-Bishop which you can find here. I don't have any packages installed on the omega and no weird dependencies. This is for the omega 1.
I'm still toying with everything, but I've put what I have right now on github for you. The cmake file links paths to my local system, so that'd need to be changed for sure.
@Chris-Stratton Yeah, I'm not sure if it will work on every device, mine is a fresh out of the box Omega 1 that hasn't had its firmware updated.
@Kit-Bishop Using your code I think I've boiled it down to the bare minimum required to get an led to toggle. Sharing in case anyone else may need an idea (if that's okay with you?)
https://gist.github.com/thyyppa/48605ae390aabf3397580408ddbca471
(keep in mind i'm new to C++ so this might break a ton of rules and leak memory like a sieve!)
@Chris-Stratton Ah, I hadn't considered the fact that a "file system" based approach could be portable. That could be a plus! I suppose if I abstracted the bit flipping enough later down the line I could swap it out for raw memory access.
@Kit-Bishop I actually looked through your code before posting and it was the closest thing to what I was looking for. Very clean stuff, but it's polished and abstracted to the point of feeling like a full library - I couldn't prune the dirty bits out of it. hah GPIOAccess seems like where I would find that raw pin access? My eyes kind of glazed over when I hit line 106.
#define WRITEREG(regOff, regVal) (*(regAddress + regOff) = regVal)
#define READREG(regVal, regOff) (regVal = *(regAddress + regOff))
#define SETBIT(regVal, bit, val) (regVal ^= (-val ^ regVal) & (1 << bit))
#define GETBIT(regval, bit) ((regval >> bit) & 0x1)
Is very very close to what I'd like to do, I just don't know where to find the registry addresses.
Thank you both for your replies!
Hello!
I was wondering if there were a good example somewhere of just plain old pin output high/low in C or C++? I read through the fast-gpio code and almost almost could see what was going on, but there were so many layers of abstraction and other things that I don't need right now (input, pwm, irq, etc). I'd like to not use a library and just have a bare bare bones example to work from. Admittedly I'm new to C/C++ but am doing this project to learn a bit more; this is a stumbling block. I'm able to cross compile and run hello worlds all that, and I do want to use C++ over Python or shell scripts - this is a learning project. : )
In the end what I'm trying to do is write a driver for those old sparkfun cell phone lcds, basically bit banging a few pins high low high low high low - I know it's not the most efficient way of doing it, but that seems like the best place to start tinkering. Even an address map or something would be helpful. On RISC devices I've always liked how I could just point a pointer to an address and flip a pin on or off. That may not be the case here, but it's all I know right now.
Thank you so much for taking the time to read this!
,Travis