@Douglas-Kryder , I looked though all of the openly available documentation. The only document which addresses low-level stuff like peripherals and general SoC behaviour seems to be the Datasheet.

@luz , I did find that MT7628_ProgrammingGuide, but in a first look it seemed to have pretty much the same content as the datasheet... But thanks for the info, I'll be looking for stuff on both documents now,

What you said about the different market positioning is true. As a product developer the main reason for going with MT7688 (and Omega) has to be the price, which seems to be unbeatable. Unfortunately we can't have everything...

@Collin-Palmer said in Omega2+ Shuts Down and Doesn't Restart:

my Omega2+ will "shut down". I can't access the Wifi AP and the LED is off.

If you find your board in the state you described again, before you do anything with it try probing the SPI lines with a logic analyzer. If you see activity it means that your Omega2+ suffered an unexpected reboot and the SoC primary bootloader is trying to load U-Boot using 3-byte addressing, but the SPI flash is still configured to use 4-byte addressing. (refer to Omega2 reboot for more info on this issue). If this is the case you have to power-cycle the board in order to get it to boot again (which resets the SPI flash addressing to 3-byte mode)

@Douglas-Kryder , I looked though all of the openly available documentation. The only document which addresses low-level stuff like peripherals and general SoC behaviour seems to be the Datasheet.

@luz , I did find that MT7628_ProgrammingGuide, but in a first look it seemed to have pretty much the same content as the datasheet... But thanks for the info, I'll be looking for stuff on both documents now,

What you said about the different market positioning is true. As a product developer the main reason for going with MT7688 (and Omega) has to be the price, which seems to be unbeatable. Unfortunately we can't have everything...

Hello everyone.

Our company has started the development of a commercial product based on MT7688 but so far we've are very worried about support and documentation.

Being used to working with established IC providers like Texas Instruments, NXP and so on I found the documentation for MT7688 to be REALLY BAD.

The datasheet is really vague, incomplete (missing functional descriptions of most peripherals) and inconsistent. Pin naming is really bad (for example GPIO#11 pin is called GPIO0?) and pins are referred to with different names in different tables. Some terms like "watchdog" are sometimes written "watchdog" and sometimes "watch-dog", which is not a big deal but gives the impression of carelessness.

Is there better or at least more complete documentation?

On page 25 of MT7688 datasheed we can read "For more information, see the Programmer’s Guide.", but I can't seem to find this document! Does it really exist?

Thank you!

@Lazar-Demin Sorry, my mistake! Thank you for clarifying this! Can you confirm that building this will result in the exact same image provided @ http://repo.onion.io/omega2/images/ ?

Thanks!

@aobs I'm quite new to Linux development and buildsystems, so sorry for the stupid questions... I realized there is a script to set the hostname which was not selected.

For the rest, I built a new image with a custom configuration loosely based on the one found at the Docker image (since copying the docker .config and running make oldconfig didn't work) and now everything seems to be working.

I still don't understand why Onion doesn't keep their official configuration at the repo's .config, it would make customization a lot easier since we could start from the official build and add/remove what we needed.

@aobs , I was in the lede-17.01 branch, but I stupidly did not run the feed scripts... (I'm new to OpenWRT/LEDE/Buildroot so I'm still figuring out how things work).

I can now build the image correctly with wifi-warp-core, but only by cloning the repo @ https://github.com/OnionIoT/source (commit 564089f624f1eb47c20d1f4f8766f2383ce32ef9).

The Docker image is out of date AND did not compile correctly for me.
For some reason I had to manually change PKG_SOURCE_URL in libsoxr from git://git.code.sf.net/p/soxr/code to https//git.code.sf.net/p/soxr/code because git clone was failing! I'm running the compilation again but it didn't finish yet.

The image built without docker boots fine and connects to WiFi using wifi-warp-core (by entering WiFi info manually with wifisetup and selecting Type network info), but I still have the following problems:

• hostname is Omega-0000, not sure how to make it use the MAC address as in the official build
• Running wifisetup and trying to "Scan for Wifi networks" fails:

root@Omega-0000:/# wifisetup
Onion Omega Wifi Setup

Select from the following:
1) Scan for Wifi networks
2) Type network info
q) Exit

Selection: 1
Scanning for wifi networks...
Command failed: Not found
Failed to parse message data
WARNING: Variable 'results' does not exist or is not an array/object
> ERROR: Scan failed, try again

> ERROR: specified ssid not in the database
root@Omega-0000:/# [ 1017.277206] br-wlan: port 1(ra0) entered disabled state
[ 1017.959763] device ra0 left promiscuous mode
[ 1017.964266] br-wlan: port 1(ra0) entered disabled state
[ 1018.019989] IPv6: ADDRCONF(NETDEV_UP): br-wlan: link is not ready
[ 1018.375215] 
[ 1018.375215] _      _____   ___  ___    _________  ___  ____
[ 1018.375215] | | /| / / _ | / _ \/ _ \  / ___/ __ \/ _ \/ __/ V1.0
[ 1018.375215] | |/ |/ / __ |/ , _/ ___/ / /__/ /_/ / , _/ _/  
[ 1018.375215] |__/|__/_/ |_/_/|_/_/     \___/\____/_/|_/___/  
[ 1018.375215] 		   Onion Enhanced MT7688 WiFi Driver 
[ 1018.375215] 
[ 1018.527499] DMA Scheduler Mode=0(LMAC)
[ 1018.531374] efuse_probe: efuse = 10000012
[ 1018.535498] 1. Phy Mode = 14
[ 1018.711670] 2. Phy Mode = 14
[ 1018.714643] 3. Phy Mode = 14
[ 1018.717882] 	WTBL Segment 1 info:
[ 1018.721296] 		MemBaseAddr/FID:0x28000/0
[ 1018.725186] 		EntrySize/Cnt:32/128
[ 1018.728632] 	WTBL Segment 2 info:
[ 1018.732010] 		MemBaseAddr/FID:0x40000/0
[ 1018.735899] 		EntrySize/Cnt:64/128
[ 1018.739344] 	WTBL Segment 3 info:
[ 1018.742720] 		MemBaseAddr/FID:0x42000/64
[ 1018.746695] 		EntrySize/Cnt:64/128
[ 1018.750140] 	WTBL Segment 4 info:
[ 1018.753515] 		MemBaseAddr/FID:0x44000/128
[ 1018.757578] 		EntrySize/Cnt:32/128
[ 1026.936528] device ra0 entered promiscuous mode
[ 1026.941279] br-wlan: port 1(ra0) entered forwarding state
[ 1026.946860] br-wlan: port 1(ra0) entered forwarding state
[ 1026.952961] IPv6: ADDRCONF(NETDEV_CHANGE): br-wlan: link becomes ready
[ 1028.941473] br-wlan: port 1(ra0) entered forwarding state
[ 1030.277136] Interface apcli0 link up! (WPA2PSK AES)
[ 1032.830996] da match,0x40a36bc073f5

• opkg update fails:

root@Omega-0000:/# opkg update
Downloading http://repo.onion.io/omega2/packages/core/Packages.gz
Updated list of available packages in /var/opkg-lists/omega2_core
Downloading http://repo.onion.io/omega2/packages/core/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading http://repo.onion.io/omega2/packages/base/Packages.gz
Updated list of available packages in /var/opkg-lists/omega2_base
Downloading http://repo.onion.io/omega2/packages/base/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading http://repo.onion.io/omega2/packages/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/omega2_packages
Downloading http://repo.onion.io/omega2/packages/packages/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading http://repo.onion.io/omega2/packages/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/omega2_routing
Downloading http://repo.onion.io/omega2/packages/routing/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading http://repo.onion.io/omega2/packages/onion/Packages.gz
Updated list of available packages in /var/opkg-lists/omega2_onion
Downloading http://repo.onion.io/omega2/packages/onion/Packages.sig
Signature check failed.
Remove wrong Signature file.

Anyone has ideas why I'm getting these problems?

Thank you!!

@Stephane-Foloppe hi, I'm trying to build my own image (from https://github.com/OnionIoT/source) with wifi-warp-core.

I simply copied the folder wifi-warp-core from https://github.com/OnionIoT/OpenWRT-Packages to source/package/onion.

After doing this, Onion > WiFi > wifi-warp-core* appears in menuconfig, but when I enable it I get the following error:

 Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for wifi-warp-core:
 * 	coreutils-base64 * 
 * opkg_install_cmd: Cannot install package wifi-warp-core.
package/Makefile:60: recipe for target 'package/install' failed

I tried enabling coreutils-base64 by enabling Base system > busybox > Coreutils (after enabling Customize busybox options) > base64 in menuconfig but nothing changed...

Could anyone tell me what I'm doing wrong?

Hello everyone. Does anyone know if it is possible to use this new "WiFi Warp Core" driver with a custom build of LEDE or OpenWRT? Are there sources or binaries available?

Thank you!

@wdu , hi! Can you share with us the details? Did you just write the binary to the raw flash memory? Starting at which address? I imagine at least some part of the 32MB of flash must be partitioned with a FS (jffs2?), so we must be careful not to overwrite it, right?

Can someone point me to or share the flash's map / partitioning scheme?

@Pavel-Metrokhin , can you please confirm if building the source @ https://github.com/OnionIoT/omega2-bootloader will generate the same bootloader provided @ http://repo.onion.io/omega2/bootloader/ ? In other words, is the GitHub repo complete and up to date or you build the provided bootloader from a private repo?

Thank you!

I'm also looking for BOMs since the schematic is missing part numbers...