Omega2+ unreachable when Wifi shut down
-
@Denis-Gluhak said in Omega2+ unreachable when Wifi shut down:
- tried the same with serial pins connecting it serial port = no serial connectivity
As long as the Omega2+ isn't dead, serial-pins should work. You did use a 3.3V-level serial-port? And connected RX to TX and TX to RX?
-
@Denis-Gluhak said in Omega2+ unreachable when Wifi shut down:
- having no expansion modules I connected Ethernet cable with its RX's and TX's directly to expansion header corresponding pins on PowerDock = no ethernet connectivity
Not a good thing to do...
https://community.onion.io/topic/1184/ethernet-expension
-
@fossette Thx for info. I somehow missed this topic. Now I know that Omega2+ Ethernet is not IEEE 802.3 compliant without additional hw.
-
@WereCatf
This was my last resort after previous unsuccessful attempts. But I did not use 3.3v level serial port but serial port via USB adapter. Connecting was done by pairing my port RX with Omega2+ TX and vice versa.
-
@Luciano-S.
Thx for reminder there is SD card slot. Will investigate available options.
-
@dgluhak4 said in Omega2+ unreachable when Wifi shut down:
@WereCatf
This was my last resort after previous unsuccessful attempts. But I did not use 3.3v level serial port but serial port via USB adapter. Connecting was done by pairing my port RX with Omega2+ TX and vice versa.USB-based serial-port is still a serial-port and it still has a voltage-level, so my point stands: what was the voltage-level? If it's a 5V-adapter, then you just fried your Omega's serial-port!
-
@WereCatf I am having the exact same problem with my Omega 2+: wifi is gone, taking all connectivity with it. I only have a power dock, so there is no ethernet available.
As per this thread, I tried connecting a USB serial port to the power dock's TX1 and RX1 pins. I get no response from the Omega2+. I know that my USB serial connection is wired for 3.3V, and I know that the serial converter board works.
I am pretty sure that the button on the power dock is not a reset button, but a button to manually tell the PMIC (power management IC) on the power expansion board to start working, as per the PMIC data sheet. That would explain why pushing it for 10 seconds didn't do anything resembling a reset operation.
I did make a bit of progress though. To get around the lack of a reset button, try the following:
- remove the LiPo battery (if any was connected)
- power down the Omega via power switch
- insert a jumper wire between the RST and GND connections on the expansion board connector. This should act the same as pushing the reset button on expansion boards that actually have a reset button.
- power on the Omega
- wait about 10 seconds
- remove the jumper wire, allowing the system to boot
- wait for system to boot (flashing LED transitions to solid LED in my case)
At this point, I can now see the Omega2+ acting as a wireless access point again using its default SSID: Omega-XXXX.
Sadly, I cannot connect to the Omega via that access point. The authentication fails every time using the default password "12345678".
In addition, the serial port still doesn't work for me.
Am I missing something obvious here? It wouldn't be the first time...
-
@Robin-Hodgson The serial should work. Try swapping RX and TX around.
-
@WereCatf Tried that. Tried every baud rate between 9600 and 115200. Nothing. Should I be seeing boot messages spewing out of the serial port?
-
@Robin-Hodgson Yup, you should.
-
@WereCatf I am connecting to the Power Expansion board TX1 and RX1 connectors. My assumption is that these signals connect to the Omega2 TX1 and RX1 signals, but I can't find a schematic for the power expansion board.
I am using a generic CP2012 USB to serial board, where I know that its TXO means TX Output and RXI means RX Input, so I am connecting CP2102TXO to Omega RX1, and CP2201RXI to Omega TX1. But like I said, I swapped them and it didn't help.
I just broke out the big gun: during boot, the oscilloscope shows no serial activity on the expansion board TX1 (or RX1, for that matter). When I type in my own serial terminal, I can see myself sending chars that arrive on CP2102TX0.
-
@WereCatf I just ohmed the connection from the Omega RX/TX to the expansion board RX1/TX1. They are connected as one would expect.
My scope shows no serial activity during boot from the Omega.
-
@Robin-Hodgson OK, some more progress. After reading a bunch of docs, it turns out that there is a simple explanation, although not a simple fix.
The Power Expansion board breaks out TX1 and RX1. However, those are NOT associated with the UART device in the Omega 2+ that is used to access the console. The console port is located on RX0 and TX0. Sadly, those connections are not available on a Power Expansion board.I hooked my scope to TX0 on the Omega, and do I see it chattering away during the boot process.
My takeaway is that the Power Expansion board is not the board you want to get started with. It has no reset button, and it provides no console serial access to the Omega. If you make a mistake that involves losing the WiFi connection, the Power Expansion board will not be your friend anymore
I will try to solder some wires to TX0 and RX0 because I'm still confused why a factory reset results in a system that puts out the default access point SSID again, but is not authenticating the default WiFi password.
-
@Robin-Hodgson Well, crap. I take it back: grounding the RST signal to the GND signal on the Power Dock expansion connector seemed to help, but it does NOT reset the Omega to factory defaults. I finally got a console serial connection to the power dock by soldering some wires to the header where the Omega2+ mounts. Poking around in the file system makes it very clear that the Omega is not back to what came from the factory. For example, the file /etc/config/wireless is not reverted back to the original version since it contains references to the router in my house. Or maybe I don't need factory defaults, I need a reflash of the entire factory firmware so I can start over. Is that possible?
-
@Robin-Hodgson You can flash firmware from a USB-drive and that will also wipe out any current settings, but you still need working serial to do that: http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved
-
This post is deleted!
-
@dgluhak4 Success! After getting control of the console serial by adding the wires to the Power Dock, I found that typing "wifisetup" would allow me to re-enter the required data for the Omega2+ to re-establish the wireless connection to my router. My system is responding normally again, and I can finally get back to the Omega configuration page:
Here is how I added the wires:
-
This post is deleted!
-
@MookieDog
Finally!
I followed MookieDogs's instructions and was able to recover my Omega2+.
In short:- solder RX0 and TX0 on PowerDock to extend Omega2+ serial0 (console serial) RX and TX lines
- cross connect RX0 and TX0 line with respective TX and RX on 3.3v level serial port. I used Raspberry PI serial and minicom.
- on Raspberry PI (or another Omega) use serial port with "minicom -b 115200 -D /dev/ttyAMA0" command
- now you are able to connect to Omega2+ console and configured it as you wish. I did manual factory reset using info on https://docs.onion.io/omega2-docs/factory-reset.html
All thanks go to MookieDog.
-
@dgluhak4 OFF
Excuse me if my post is entirely off-topic.Omega2+ v0.1.9-b150 without Dock
Raspberry Pi 2 Model B V1.1
up-to-date Raspbian Jessie
minicom version 2.7 (compiled Jan 12 2014)Formerly I also tried this 3.3V logic level 'Null Modem' connection between my O2+ and a RPi .
(Omega_RX0---RPi_TXD0, Omega_TX0---RPi_RXD0, GND---GND)I always got garbaged characters up to the 'console [ttyS0] enabled' line(s):
____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/" Board: Onion Omega2 APSoC DRAM: 128 MB relocate_code Po)¥ÉY device id 2°LN¡È¹Ìlash: MX2µÌ²µ¶³MQ¡ø*** Warning - âX-¤(ª( QÍ¥¹Èefault env©¹Ë««åÑ) o628_MP (Port5<->Îïîå© C(ªTOOÏÏÏÏÏêêêêêêêR5=¹¥½¹mega2 UBoot ÖY®®ÖËK¢rrrR5µµ[------------------KKKKKKKKKKKKKKKË©©©©© ¤Ô% AUÌreq = 575 MHÚ CQ.W«+EÚemory size = L&RJÑÍ)Resetting MT7¶TRVI¨øInitializé·©u²ÂÂ:A%=æystem.C+5¡Æomponent: SPI Flá.¨Ñéct 18 2016 T5 C%%%%%%%%¥IIIIIIIIIIIIIIIIIIIIRRRRRRRR5©old Reset buttïî æï²[Kßptions * ***ªªªªªª%%%%%%%%%%%%%%%%%%%%¥IIIII¨H¨H¨H¨Hõ½Ñinux from Flash Î %UQ RESSED. ## Booté·)«+uÂt bc050000 ... R[XVÈ*Õé@ MIPS LED ¦Z«áµi.4.42 K Uncompreó®ëZɹ±mage ... ÝÇontrol ©rj ) Load Address: 800°L*¹ÑÉå oint: 80°Ar¢r¢B2 [ 0.00°W TëÑ ± MU set to è·¬Ëɽ±5[ 0.000°°°Ý k¢åÁé@MediaTek MT·HWK*½éd5§tarting kernel ®®®Ã[ 0.000000] Linu¸»Y®®ÕË Ë [ 0.0°LW$¬ë½¹Í½±[early0] enabledp0000000) ¡h4:¥Ù¥¹Øinux mems©½Y¤- [ KLL&&&RAUÁ@revision Z.')ʲªªBj%AMe4KEc) [ 0.00°W * 5¥j ¡¥¹is Onion Omega2+ [ 0.000000] Deteò[Z«Gáhysical RAM mBªÍ ±¥ ÛHL ê@memory: 08°LLH($& [ º2u5[ 0.000°W¤êË ±ôone start foòYX,ëS5[ 0.000000ÝQX.+Ûemory node rangr¹ ѱäegister=000´YC¡+elistsrê¤eadback ErrCtl råVkÑÉõa004000fpagesº ³²µ±C¡+rêernel command ìZ«§½¹Í½±õètyS0,115200 ¹ëÍÑåÁõæq+É [ 0.000000] Íåíïò¹L¦SSiê)ºZÂvailable (3012ËË«ÅÆode, 143K rwdata¬Zåodata, 208K init, ±NÓ %Íͱ@5520K reserved, °)ÒV+ÕÍÉÙ¥ [ 0®°°° DÙ¥ÑÉ5[ 0.00000°W¤(Ujëk³éA580MHz 6 [ 0.000°W¤,ëkµÍ½ÕÉ}Áɽé@no matching clo㮫ÉÍÌound 1 [ 0.0746³NW¤ê«¹ÑµÆache hash tabìå YÉ¥Íé@1024 (orderº °¬ ´NJ+ÑÍ¥¬ [X¯±}¹Íé@6590553²¶´ î³C¡+rêæched_clock: 32 âZ¯.RJÊj!é±@resolutioë [ 0.0¸Nêountpoint-cache haó´ºX,«*¹ÑÉ¥Íé@1024 (oräY.' EʲåÑÍ¥ 6 [ 0.133428] mô)úÁ¥½b0000600.gpio: òYVkÑÉ¥¹f2 gpiosÍé@0xffffffff, má¼±}¹Íé@19112604462750°[®Hø[ °®±°¦êáinctrl core: é·Z¯,+Kàin [ 0.138966] mt762±uÁ¥½c0000600.gpio: regi³ºY®ë:Á¥½Í5[ 0®±´´´°W¤Ýi21_gpio 10000¶°°®ç°ZK¥ÍÑÉ¥¹f2 gpios [ 0.150¹LMW¤-¦¬©Ýi21 10000900.i5±½Í½ÕÉMIPS re-start ·çupport ) [ 0.189000] UÄÐ ´X.WJ«*¹ÑÉ¥ÍéA256 (order: 0¬ ´°¹¶±^®Ö+©HhrÊ¢²j©DP-Lite èX.WJ«*¹ÑÉ¥Íé 256 (order: 0, 4096 ±^¯Ö+©Hø[ 0.200945§Q+ë 0 [ 0.2³·°²´®WWj¡Íé@version 4®° ¨²°N zJ¡¥±±¥Áougher [ 0.2´SRÍÉt version 2.2 ¨§PBU55Ie¥@(LZMA) (RÔRSQJ$¥¨êRõ%{I%Qe¥@(c) 2001-2006 Reä¤X/ å¹ 5¡ªrݵéAError appk [ 0.2962´MW¤ª++Ãé@8250/16550 driöY. E½ÉÑͱ@IRQ sharing äZ®«E5[ 0.3038±W¤¬Ëk½±¶ttyS0] disablå²C¡+rº¢¢êc0000c00.uartlite: tô^*R¨ª*ê [ rºÊªjät2880-piní].$®kEɱé@could not reqõY.ìò¥¥¹b8 (io18) from grï].$®WËëÅlaim for 100°M&&& ݵ5[ 0®²·³´¸NW$. Âj¥¹µÕááinctrd [ 0.316025] console [ttyS0] enabled [ 0.323020] bootconsole [early0] disabled [ 0.323020] bootconsole [early0] disabled [ 0.331702] 10000d00.uart1: ttyS1 at MMIO 0x10000d00 (irq = 29, base_baud = 2500000) is a 16550A [ 0.341199] 10000e00.uart2: ttyS2 at MMIO 0x10000e00 (irq = 30, base_baud = 2500000) is a 16550A ...Was your serial communication fully perfect?
