Posts made by Dave M

Got it! FW-RST/GPIO38 is active HIGH! I had just enough jumpers to hook up my separate UART-TX so I could type, and also pull FW-RST high during boot. I'm flashing omega2.bin from USB right now, and will be able to get my own (fixed!) firmware installed shortly. Phew!

I have a very old Omega2+...probably first rev or thereabouts. It mostly works, and the pins mostly line up with the current pinout diagrams, but on a MiniDock (also probably first rev) the Reset GPIO and the UART Rx pins are messed up.

Using the USB-UART chip on the MiniDock, I can see boot messages, but I can't type anything. If I use a separate TTL USB cable connected to RX0/TX0 (GPIO12-13) I can talk to the Omega2+ (the same output goes through the USB-UART chip too.)

And my current critical problem: the reset button on the MiniDock is not recognized during the UBoot startup. (I broke my kernel so I need to do a USB re-flash, but I can't interrupt the boot process to tell it to do that.) I've also tried grounding the FW-RST pin (GPIO38, right next to TX0) but that doesn't do it either.

I know this Omega2+ can be boot-interrupted because I have a Power Dock that does it, but I'm on a biz trip and only have the MiniDock with me. So I need to find a pinout of the early Omega2+ to figure out which pin to ground to interrupt the boot process.

Any help?

I'd like to make a custom firmware configuration (different packages than stock Omega2 firmware, etc.) I've built OpenWRT and LEDE many times in the past, and I have a stock LEDE running on an old Omega (plus I can get both stock LEDE and the Onion LEDE from https://github.com/OnionIoT/source.git built and running on my Omega2P) but I can't figure out how to get the WiFi driver built and running.

Is there any way to get the "Warp Core" MT7688 driver built and running in an otherwise vanilla LEDE build? The boot-up message appears to be in the mt_wifi.ko module, but that doesn't get built from LEDE or OnionIoT/source.git.

@Janus-Sanders Huh, weird. I clipped on 3.3V with an ammeter (I was trying to see what the draw was). The board drew ~200mA and my 3.3V was solid (didn't dip) but the light never started blinking and the board didn't connect to WiFi. I guess I'll try again this weekend...

@Janus-Sanders: but also pull-down on RST, right?

@Lazar-Demin: I was powering 3V3 and grounding both GND, but RST was floated. I'll try grounding it and see what happens. Thanks!

After poking around through tags, I found the schematics at Github:

https://github.com/OnionIoT/Onion-Hardware

I suspect I need to pull the reset line up or down but not 100% sure yet. The schematic symbol for the reset switch suggests a NC switch pulled up to 3.3v, with a 1k/3k divider, and on the Omega, a 10k pulldown with a bypass cap. So without the Mini-Dock, it's a 10k pulldown, and with, it's a 1k pullup vs. a ~2.7k pulldown. None of that smells right, since reset is usually active low. I'm guessing there's some fancy chip-specific stuff going on with boot modes based on the state of RESET_L and GPIO11. Anybody know the real scoop?

I'd like to feed power directly into the Onion board, rather than via the Dock or Mini-Dock. However, when I do (3.3V & GND on the appropriate pins) nothing happens. (The board is still OK: when I put it back on a Mini-Dock, it boots up and runs.)

I would look at the board schematics and figure it out myself, but those are not accessible (the wiki link to the schematic PDF at https://wiki.onion.io/create/Documentation/Hardware/Schematics/Omega.pdf says "Forbidden. This wiki is set to no-edit mode.")

Can anybody explain how to feed in power directly, or else get the schematics un-protected somehow?

Thanks!