@CAP-33 In WHAT?
Best posts made by William Scott
RE: Omega2+ Reboot Fix [Official Solution]
I'd like to test this. I'm motivated as I have field deployed units that will fail, making me very unpopular with my client.
I probably have all of the test equipment required to create an automated test that could execute tens of thousands of test permutations with no human in the loop.
Do any of the Onioneers have any interest in collaborating with me in creating a test plan and test procedure, perhaps writing a few lines of code, etc.? My up front view is to do it in public view on this forum, unless our friends at Onion suggest otherwise. If the latter, we'd collaborate in some other fashion.
RE: Omega2 / I2C / Support / Quality
See http://community.onion.io/topic/2042/openwrt-and-lede-agree-on-linux-for-routers-peace-plan/5 as @Lazar-Demin indicates open source is the current regime. You can find a link to the repository at that link.
configuration specifics for IPv6 global unicast address (GUA)
I posted a message a few weeks ago related to this topic. There were many readers of the topic, but no responders. Interesting....
Within days I'm going to design a sensor data and status reporting regime for field deployed Omega2+ (O2+) devices. Implementation would shortly follow.
It seems every device I run in my house (office is at house as well) will come up with a IPv6 GUA address, with the exception of the O2+ devices. What is the significance of this? Every device (desktops, telephones, RPi's and others) come up globally routeable. I can sit at the pub (not that I ever do that) and ssh into the Pi or one of the Linux servers using a IPv6 address with total disregard to the IPv4 NAT reality of most home and office environments. The O2+ devices are not automatically generating IPv6 GUA addresses and are therefore cannot be routed to from the outside of a NAT environment.
What config parameters need to be changed, and in which files, to "encourage" the O2+ devices to compute their IPv6 GUA addresses?
RE: Omega 2+ bricked
Here are some thoughts.
Hold off on re-flashing, if you can, until this forum has done what it can to help out. The folks here are pretty awesome!
When hooking up Tx and Rx lines, don't forget the ground/return line. This ensures the tranceivers are playing in the same playground.
Time and again I will hook up a Tx at one end that is a Tx at the other end, which of course won't work. Write down your circuit diagram and don't actually wire it up until you are happy with it....on paper.
If possible avoid soldering until you need something "permanently" connected. The double quotes to indicate sentiment, not literal behavior. Do what you need to do. Think forward.
Do you have other docks (e.g. Expansion) that may be usable in troubleshooting?