This is my observation :
Had he completed Harward, world wouldn't have had broken windows..
The MRE in sgi mips architecture was a break through(the entire hardware works like a pointer), supported by 80Gbps interconnect let the world watch general pupose processor generated animations, 30 yrs back. Though I am junior by all means, I too feel, innovations were sacked.
Updated an LTE board to 0.3.2 b244 just for the sake of it. I still get double entries (see my last post) but so far it doesn't show the increment behaviour but it isn't static either. I keep an eye on it.
After reading your post, I switched to Omega2+ to provide gateway service to my primary workstation. The Omega is using a Linksys WiFi as its gateway, and is powered with an expansion dock.
The connectivity is:
WS (WiFi) => Omega2+ (AP+STA) => Linksys => Internet.
It is more than 5 days since my experiment started; and the workstation was never shutdown. Here is the last dmesg line from the workstation:
[502020.417869] usb 2-1.6: USB disconnect, device number 89.
When I check the logs, I don't see any WiFi related problems. Needless to say,I never had any connectivity problems while using the workstation.
I can access the Omega2+ (and the Linksys as well), using my cellphone from about 100 feet away, two dry walls in the middle.
I use an apple A1400 power supply (5V, 1A) using the expansion dock, to power the Omega. I also used the power supply that came with a Xperia without any problems. When I used another power supply, that came with another cellphone, I had problems.
Bottom line is, Omega is stable wrt WiFi, as long as you feed it with a reputed power supply.
I would advise you to carry out the following.
1.Download the "omega2p-v0.3.2-b233.bin" from http://repo.onioniot.com/omega2/images/
It is the b233 release of the firmware for Omega2+ into your workstation.
So you have a backup for future use.
2.scp or use a sd card to transfer the fw to Omega's /tmp directory
:tmp# sysupgrade -n omega2p-v0.3.2-b233.bin
from the UART0 connection. This will upgrade and reboot the omega.
and select "1) Scan for Wifi networks". It will give the list of available WiFi APs, as below:
Scanning for wifi networks...
Select Wifi network:
5.Pick your choice and provide the key, as below:
Encryption type: psk2
That is all about the wifi setup. Once you get the prompt back, you can check the Internet connectivity by ping'ing some hosts in the Internet.
It is advisable to change the default AP key of the Omega2+. For that execute:
:/# uci set wireless.ap.key='your_new_key'
:/# uci commit
:/# /etc/init.d/network restart
If you executed, the "uci set.." command before #4, the other two commands would have been automatically executed by the wifisetup.
Let us know how it goes..
@crispyoz said in Omega2 Dash wallmount:
I've posted the details of my wall mount in Projects.
Looking great work dear, I really appreciated to you on this quality work. Nice post!!
I was pointing to a possible enhancement wrt image distribution.
Many sites distributing images such as iso, a txt file containing the checksum is usually made available. Please see the ubuntu download mirror:
The SHA256SUMS file contains the hash of the iso's.
Once we download the image with wget, we can compare the checksum in the workstation before using the image. The checksum validation is a one time process, anyways.
I always keep the images in my workstation for future use.
OpenWRT provides the checksum in the page itself:
https://archive.openwrt.org/releases/18.06.7/targets/ramips/mt76x8/ which would require redesign the Omega repo.
The ubuntu approach is simple. Whenever a new image is released, update the txt file by adding a single line entry..
@Lucas-Gozalvez Agree with @crispyoz, is there enough power available to the Omega?
Also, would be helpful to see if there's anything special about this specific wifi network. Please post the debug output from the wifi troubleshooting FAQ post if possible
@francisco-vieira Agree with @crispyoz it does look like the filesystem is corrupted on these units.
A few questions for you:
Do you have any external circuits or signals connected to the Omega's SPI pins?
Do you have any programs running on the device that write to the filesystem on a regular basis?
Could you give us an idea of what kind of environment these devices are operating in?
@luckycometdaft said in Cross Compiling OpenWrt Package:
... I have installed MQTT on board and there is a .so file in Board. Now, how do I cross-compile with this library?
Look through my first post in the manual [Manual] How to make native C/C++ application step by step. There is part of it:
... Second problem in third-party libraries - Omega; opkg manager doesn't install -dev files of libraries and it's will be a problem in your application.
You have to know OpenWRT it's a minimal disk-size system. It have no .h-files to build anything in. I think you compiled your application into the Omega board (direct compilation). In this case you had install GCC build system with common h-files, but you need append your third-party h-file for special .so library.
You have to find this and append manually. You can find your h-file from so-library repository.
But I recommend you compile via SDK. You will need it in future if touch to build native applications.
If you want to interface a lot of devices, you would typically adopt mux/demux technique, with a middle-level "device aggregator".
See this: https://www.instructables.com/id/Tims-PCA9685-Controller
One side (the micro-controller -uC- facing side) is I2C, while the "physical device" facing side is PWM. The micro-controller talks to 9685 (device aggregator), which in turn would talk to the devices connected to its 16 channels.
Note that the above URL has Atmel 8-bit uC/Arduino as the "controlling platform". The point is that, we are making use of the I2C interface which is present in almost any uC .
Further, the data sheet of the 9685 provided in the above link:
https://cdn-shop.adafruit.com/datasheets/PCA9685.pdf says that, "The
PCA9685 operates with a supply voltage range of 2.3 V to 5.5 V and the inputs and outputs are 5.5 V tolerant". So, you can drive it using 3.3v.
Picking the the right hardware to meet a "specific requirement" is an art, that takes time to get anywhere near the mastery. Getting used to the "datasheet" is the basic requirement. Luckily, the Internet has tons of resources providing implementation details of various project.
@crispyoz @Scruffy I'll second that as many, many people have been bitten by the current surge required as the WiFi modem comes on line. Capacitance across and near the power/gnd is a good thing and long wires add series inductance which is a bad thing.
@tjoseph1 This is more of a question for Onion engineers, I'm a software engineer so I can only go by what's in the OS source code. Poweroff does not turn off the power, it simply kills off processes so as to halt the system.
300 baud and then 1200 baud..? So lucky..
Read somewhere, it was the time Kevin Mitnick was doing his research .!
I was dialing into a terminal/access server situated in a data center with 256kbps backbone over G.703 copper. The days of redhat 5 (not RHEL)..