@luz said

unfortunately, after a seemingly perfect start with the patches from 20 days ago, the mt76 again behaves erratically for me as well.

Some days it works fine without a hitch for a long time, and then other days (like yesterday) performance is extremely poor and there are a lot of lengthy connection dropouts - without any change in the setup or wifi environment (as far as I can tell).

This is a guess based on a hunch ... looking at a discussion at the Linux wireless patch, referenced by the LEDE developers you sited - I see some code that changes a value based on the wifi channel. Perhaps some of these channel dependent values are bad code ...? Or, I have often seen Omegas jump to another wifi channel in the boot process when wifi is initialized. Here I used the free Android app Wifi Analyzer and sometimes see the Omega2 change it's AP wifi channel during the boot. Have you observed if firmware with the Mt76 patch might work fine on some wifi channel and not well on another? Perhaps there is a bug here, could that channel related value be wrong if and when the Omega2 switches the wifi channel?!

If you see some merit in this hypothesis, during the Omega boot you can observe the wifi channel behavior and assignment using an app like Wifi Analyzer, running on your phone or other tablet.

@luz Hi,

Finally, I had some time to capture the boot process.GPIO17 and UART TX lines were connected to Saleae Logic's inputs. I recorded the waveform from issuing the reboot command on previously booted system, through U-boot, until the next kernel boot (official Omega2 image).

Since I was not able to upload the captured file to this comment (although the zipped file was smaller than the 2MB limit), I put in on my Google Drive: omega2_boot.logicdata - if any of you interested in.

There are three spot where GPIO17 changes its state:

In U-boot at Resetting MT7628 PHY:

Where it is switched to Ethernet (there is a short period when it seems to configured as GPIO output (for ~70us)).

During kernel boot around MTD partitions check:

This takes ~700us.

And finally, SD init set those pins to normal GPIOs as I figured it out previously:

There are three voltage levels:

~2.5V (I assume this is when the pin is GPIO input and the logic analyzer pulls somewhat down the pin) ~1.5V (when the pin is configured for Ethernet) ~3.3V (probably the pin is configured as GPIO output)

So, based on the above, I suppose, it is proven that U-boot changes the state from normal GPIO to Ethernet.

/sza2

Citation: http://m.slashdot.org/story/309223

We have waited for so long. Please give a update.