Skip to content

ipq40xx: add support for Linksys EA6350v3 #1716

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from
Closed

ipq40xx: add support for Linksys EA6350v3 #1716

wants to merge 6 commits into from

Conversation

NoTengoBattery
Copy link
Contributor

This is a series of 6 commits with the aim of supporting a new device.
Each commit is clearly explained, so it is not necessary to add more to the PR message.

This commit adds 1 (one) extra 'regulatory domains' for sanitize. This
regulatory domain is found in the Linksys EA6350v3 EEPROM and it's
invalid. The source code provides a function 'ath_regd_sanitize' which
sanitizes invalid regulatory domains.

This modification to the ath_regd_sanitize function is needed to sanitize
the invalid 'regulatory domain' in the device's EEPROM. Without this
patch, the ath10k-ct will refuse to load the interfaces. With this patch,
the wireless device works as expected.

WARNING: the 'regulatory domain' WILL be set to "World". You may be
requiered by law to modify your settings in accordance to your regional
legislation.

Signed-off-by: Oever González <notengobattery@gmail.com>
This commit adds support for the Linksys EA6350v3 device in the ipq-wifi
target. Without this patch, the Linksys EA6350v3 won't be hable to have
fully functional wireless interfaces.

Signed-off-by: Oever González <notengobattery@gmail.com>
This commit adds support for the Linksys EA6350v3 device in the ipq40xx
target. Without this patch, the Linksys EA6350v3 will not be able to
access the uboot environment.

Signed-off-by: Oever González <notengobattery@gmail.com>
This commit adds the object 'linksys_bootcount.o' to the ipq40xx target.

This is needed for the Linksys EA6350v3 device. Without this patch, the
device will switch-back between the current and the last flashed firmware
every 3 (three) reboots. With this patch, the device works as expected.

Signed-off-by: Oever González <notengobattery@gmail.com>
This commit adds the 'Build/linksys-image' and the 'linksys-image.sh'
script to the build system.

This change is needed for generating factory images for the Linksys
EA6350v3 device. Without this patch, only sysupgrade images can be
generated. With this patch, users can flash the device without the
need of physical access or disassembly.

Signed-off-by: Oever González <notengobattery@gmail.com>
Specifications:
SOC: Qualcomm IPQ4018
RAM: 256 MiB Samsung K4B2G1646F-BYK0
FLASH1: MX25L1605D 2 MB
FLASH2: Winbond W25N01GV 128Mb
ETH: Qualcomm QCA8075
WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n 2x2
WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11n/ac W2 2x2
INPUT: WPS, Reset
LED: Status - Green
SERIAL: Header at J19, Beneath DC Power Jack
1-VCC ; 2-TX ; 3-RX; 4-GND;
Serial 115200-8-N-1.

Tested and working:
- USB (requieres extra packages)
- LAN Ethernet (Correct MAC-address)
- WAN Ethernet (Correct MAC-address)
- 2.4 GHz WiFi (Correct MAC-address)
- 5 GHz WiFi (Correct MAC-address)
- Factory installation from Web UI
- OpenWRT sysupgrade
- LED
- Reset Button

Not Working:
- Some devices have a bad regional domain in the EEPROM. For those
  devices, the ath10k driver will refuse to load.

Need Testing:
- WPS button
- ath10k bad regional domains values

Install via Web UI:
- Attach to a LAN port on the router.
- Connect to the Linksys Smart WiFi Page (default 192.168.1.1) and login
- Select the connectivity tab on the left
- In the manual update box on the right
- Select browse, and browse to
  openwrt-ipq40xx-linksys_ea6350v3-squashfs-factory.bin
- Click update.
- Read and accept the warning
- The router LED will start blinking. When the router LED goes solid, you
  can now navigate to 192.168.1.1 to your new OpenWRT installation.

Recovery (Automatic):
- If the device fails to boot after install or upgrade, whilst the unit is
  turned on:
1 - Wait 15 seconds
2 - Switch Off and Wait 10 seconds
3 - Switch on
4 - Repeat steps 1 to 3, 3 times then go to 5.
5 - U-boot will have now erased the failed update and switched back to the
    last working firmware - you should be able to access your router on
    LAN at 192.168.1.1

Recovery (Manual):
- The steps for manual recovery are the same as the generic u-boot tftp
  client method.

Signed-off-by: Ryan Pannell <ryan@osukl.com>
Signed-off-by: Oever González <notengobattery@gmail.com>
@chunkeey chunkeey added build/scripts/tools pull request/issues for build, scripts and tools related changes core packages pull request/issue for core (in-tree) packages target/ipq40xx pull request/issue for ipq40xx target labels Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build/scripts/tools pull request/issues for build, scripts and tools related changes core packages pull request/issue for core (in-tree) packages target/ipq40xx pull request/issue for ipq40xx target
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants