@fossette Yeap that was it. I figured out the relay I had on these pins was causing a massive Amps' draw for a few milliseconds. That of course cause Omega to reboot due to "power loss".

Thanks anyway!

Hi there,

My Omega keeps rebooting after I do a few "fast-gpio set 15 0" and "fast-gpio set 15 1".
The same happens with Pin 16, 17 and pretty much all available pins...

Is there a workaround?

Thanks!

Final version!

Non of the above work!

From the documentation:
Display a Specific Network's Information
Display a JSON-formatted table of all info for specified network
wifisetup info -ssid <ssid>

Well if you actually run the above you get a:
ERROR: Invalid Argument: info

It seems to me that either the argument has not been properly configured in the script or the scripts does not support it yet (older version maybe?)

Also, "wdb40setup" does not exist!

Hi!

Thanks for the immediate reply Lazar. My updated wdb40 did the trick

I will try to compile again and I'll let you know soon....

All the best,
George D.

Hi guys!
Nice work with the new update.... but I am here unfortunately to provide you with some feedback on issues I found.

When I am trying to recompile my own kernel and building the "world" I get this:
Checking out files from the git repository...
Cloning into 'wdb40'...
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Also, the same module ("wdb40"), breaks my wifisetup utility plus the UCI infrastructure, causing it to timeout no matter how or when I call it!

See:
Command failed: Request timed out
Failed to parse message data
WARNING: Variable 'results' does not exist or is not an array/object

OK, so I have some bad news.

After 20 flashes my Omega is now dead!

The funny thing is that Atheros is making a strange noise. It "whistles" persistently in a high frequency pitch. Is there any logical explanation for that feedback? Is it maybe a burned-out capacitor or the crystal inside the clock? Is there any chance there is some sort of thin metal that conducts with anything inside the chip and makes it produce that noise?

It's sad but very challenging to understand why this has happened and if this noise makes any sort of sense...

I just wanted to share.

Cheers.

Basically I found another problem as well. This verion of NodeJS does not support lambda (anonymous) functions. So, do not try to call anything or use inline functions. It will crash and burn, LOL.

It works!!!

I am running version 0.0.6 (b266)

But I saw there is a new firmware. Let me try updating first