OpenWrt support for Linksys MX8500

robimarko · 2024-03-11T21:34:12.495Z

Look at what logread is saying, there is probably an hostapd error

lytr · 2024-03-11T21:49:40.882Z

Thu Jan  1 03:15:18 1970 daemon.notice netifd: radio2 (5092): WARNING: Variable 'data' does not exist or is not an array/object
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: Set new config for phy phy2:
Thu Jan  1 03:15:18 1970 daemon.notice wpa_supplicant[2038]: Set new config for phy phy2
Thu Jan  1 03:15:18 1970 daemon.notice wpa_supplicant[2038]: Set new config for phy phy2
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: Set new config for phy phy2: /var/run/hostapd-phy2.conf
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: Restart interface for phy phy2
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=US ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=33 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+] op_class=134 ieee80211ac=1 vht_oper_chwidth=2 vht_oper_centr_freq_seg0_idx=47 vht_capab=[MAX-A-MPDU-LEN-EXP0] ieee80211ax=1 he_oper_chwidth=2 he_oper_centr_freq_seg0_idx=47 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_request=0 he_mu_edca_qos_info_txop_request=0 he_mu_edca_ac_be_aifsn=8 he_mu_edca_ac_be_aci=0 he_mu_edca_ac_be_ecwmin=9 he_mu_edca_ac_be_ecwmax=10 he_mu_edca_ac_be_timer=255 he_mu_edca_ac_bk_aifsn=15 he_mu_edca_ac_bk_aci=1 he_mu_edca_ac_bk_ecwmin=9 he_mu_edca_ac_bk_ecwmax=10 he_mu_edca_ac_bk_timer=255 he_
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.523019] br-lan: port 5(phy2-ap0) entered blocking state
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.523062] br-lan: port 5(phy2-ap0) entered disabled state
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.527778] device phy2-ap0 entered promiscuous mode
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.533041] br-lan: port 5(phy2-ap0) entered blocking state
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.538185] br-lan: port 5(phy2-ap0) entered forwarding state
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: phy2-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.544344] br-lan: port 5(phy2-ap0) entered disabled state
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.587664] IPv6: ADDRCONF(NETDEV_CHANGE): phy2-ap0: link becomes ready
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.587819] br-lan: port 5(phy2-ap0) entered blocking state
Thu Jan  1 03:15:18 1970 kern.info kernel: [11718.593096] br-lan: port 5(phy2-ap0) entered forwarding state
Thu Jan  1 03:15:18 1970 daemon.notice netifd: Network device 'phy2-ap0' link is up
Thu Jan  1 03:15:18 1970 daemon.notice netifd: bridge 'br-lan' link is up
Thu Jan  1 03:15:18 1970 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: phy2-ap0: interface state COUNTRY_UPDATE->ENABLED
Thu Jan  1 03:15:18 1970 daemon.notice hostapd: phy2-ap0: AP-ENABLED
Thu Jan  1 03:15:18 1970 daemon.notice netifd: Wireless device 'radio2' is now up
Thu Jan  1 03:15:19 1970 daemon.warn odhcpd[2166]: No default route present, overriding ra_lifetime!

It might be a VLP (Very Low Power) mode?

lytr · 2024-03-11T22:12:32.058Z

Sometimes during boot I'm getting this error and restart is performed:

[ 5855.192802] pcieport 0000:00:00.0: AER: Multiple Corrected error message received from 0000:00:00.0

lytr · 2024-03-11T22:17:30.377Z

Could the problem with setting gpio44 be that the PHY has id 0x00000000:

root@OpenWrt:~# mdio 9*
 DEV      PHY-ID  LINK
0x00  0x004dd0b1  down
0x01  0x004dd0b1  down
0x02  0x004dd0b1  down
0x03  0x004dd0b1  up
0x04  0x004dd0b1  down
0x05  0x04820a05  down
0x08  0x00000000  down

?

robimarko · 2024-03-11T22:27:33.161Z

AQR-s are C45 only PHY-s so they dont have a C22 address at all and that is probably confusing the probe code completely.

As far as the 6GHz support goes, I am not sure if the 6E power/regulatory commits for ath11k have been backported, have newer tried it as I dont have any boards that support 6E

lytr · 2024-03-11T22:33:03.736Z

robimarko:

AQR-s are C45 only PHY-s so they dont have a C22 address at all and that is probably confusing the probe code completely.

Can this be patched easily?
This id should be added somewhere:

root@OpenWrt:/# mdio 9* mmd 8:1 3
0x1c22

?

The same PHY ids are reported in QHora-301W: Adding OpenWrt support for QNAP QHora-301W - #503 by rmandrad

So how the gpio is toggled in the case of QHora-301W?

I can read id this way:

root@OpenWrt:/# mdio 9* mmd 8:1
CTRL1(0x00): 0x2040
  flags: -reset -low-power -remote-loopback -local-loopback
  speed: 10g

STAT1(0x01): 0x0082
  capabilities: -pias -peas +low-power
  flags:        +fault -link

DEVID(0x02/0x03): 0x31c31c22

SPEED(0x04): 0x6031
  capabilities: -400g +5g +2.5g -200g -25g -10g-xr -100g -40g -10g/1g -10 +100
                +1000 -10-ts -2-tl +10g

DEVS(0x06/0x05): 0xe000009a
  devices: +vendor2 +vendor1 +c22-ext -power-unit -ofdm -pma4 -pma3 -pma2 -pma1
           +aneg -tc -dte-xs +phy-xs +pcs -wis +pma/pmd -c22

CTRL2(0x07): 0x0009
  flags: -pias -peas
  type:  10g-t

STAT2(0x08): 0xb701
  capabilities: +tx-fault +rx-fault +ext-register +tx-disable +local-loopback
                -10g-sr -10g-lr -10g-er -10g-lx4 -10g-sw -10g-lw -10g-ew
  flags:        +present -tx-fault +rx-fault

EXTABLE(0x0B): 0x40fc
  capabilities: -10g-cx4 -10g-lrm +10g-t +10g-kx4 +10g-kr +1000-t +1000-kx
                +100-tx -10-t -p2mp -40g/100g -1000/100-t1 -25g -200g/400g
                +2.5g/5g -1000-h

PKGID(0x0E/0x0F): 0x31c31c22

robimarko · 2024-03-12T09:24:22.570Z

Its not simple, as compatible pretty much accounts only for C22 ID-s and not for C45 ID-s which are not located in the usual registers 0x2 and 0x3 and those are empty on C45 only devices.

I managed to reproduce it on my 301W.

Fun thing is that reset-gpios "work" on 301W simply because bootloader will deassert the reset so they are already out of reset before booting, manually changing the reset before booting exposes the same issue.

I plan to poke around the core to see where the check is failling to see if we can add fixup it at least for our usage.

lytr · 2024-03-12T09:27:52.393Z

I've checked bootlogs for other AQR equped boards and all of them have initialization in u-boot:

Netgear RAX120v2

NAND read: device 0 offset 0x7e00000, size 0x80000
 524288 bytes read: OK
bad magic on ETHPHYFW partition
PHY ID1: 0x3a1
PHY ID2: 0xb612

ZyXEL NBG7815

device 0 offset 0x650000, size 0x80000
SF: 524288 bytes @ 0x650000 Read: OK
CRC check good on phy fw file (0x4B33)
PHYFW:Loading IRAM...........done.
PHYFW:Loading DRAM..............done.
phy fw image load good CRC-16 matches (0x6FFA)
PHY ID1: 0x31c3
PHY ID2: 0x1c12

Buffalo WXR-5950AX12

NAND read: Offset exceeds device limit
PHY ID1: 0x31c3
PHY ID2: 0x1c12

NAND read: Offset exceeds device limit
PHY ID1: 0x31c3
PHY ID2: 0x1c12

robimarko · 2024-03-12T09:29:31.310Z

NBG was moved to load firmware via kernel as well, but it seems that all of them are at least deasserting the reset in the bootloader.

I would suggest using the pinctrl to deassert the reset for now, until a more proper solution was find

lytr · 2024-03-12T09:32:15.842Z

GPIO support in u-boot for MX5300 is not configured. I'm not able to toggle gpio44 manually.

robimarko · 2024-03-12T09:33:33.520Z

There is no command, but it can be done by manually poking at the register.

lytr · 2024-03-12T09:38:14.920Z

There is a gpio command but not working:

IPQ807x# help
?       - alias for 'help'
aes_256 - AES 256 CBC/ECB encryption/decryption
aq_load_fw- LOAD aq-fw-binary
aq_phy_restart- Restart Aquantia phy
base    - print or set address offset
bdinfo  - print Board Info structure
bootipq - bootipq from flash device
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootz   - boot Linux zImage image from memory
canary  - test stack canary
chpart  - change active partition
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
dcache  - enable or disable data cache
devinfo - devinfo - devinfo handling commands
dhcp    - boot image via network using DHCP/TFTP protocol
dm      - Driver model low level access
echo    - echo args to console
env     - environment handling commands
erase   - erase FLASH memory
exectzt - execute TZT

exit    - exit script
false   - do nothing, unsuccessfully
fdt     - flattened device tree utility commands
flash   - flash part_name 
	flash part_name load_addr file_size 

flasherase- flerase part_name 

flinfo  - print FLASH memory information
fuseipq - fuse QFPROM registers from memory

go      - start application at address 'addr'
gpio    - control gpio pin
help    - print command description/usage
i2c     - I2C sub-system
icache  - enable or disable instruction cache
imxtract- extract a part of a multi-image
ipq_mdio- IPQ mdio utility commands
is_sec_boot_enabled- check secure boot fuse is enabled or not

itest   - return true/false on integer compare
loop    - infinite loop on address range
md      - memory display
mfg     - Diagnostic tools for MFG (mfg gpio/led/btn/badblk/usb/rtc)
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
mtdparts- define flash/nand partitions
mtest   - simple RAM read/write test
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
runmulticore- Enable and schedule secondary cores
saveenv - save environment variables to persistent storage
secure_authenticate- authenticate the signed image

senv    - senv handling commands
setenv  - set environment variables
sf      - SPI flash sub-system
showvar - print local hushshell variables
sleep   - delay execution for some time
smeminfo- print SMEM FLASH information
source  - run script from memory
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
true    - do nothing, successfully
uart    - UART sub-system
ubi     - ubi commands
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version

robimarko · 2024-03-12T09:41:36.614Z

Yes, as QCA doesnt register a proper GPIO driver at all

lytr · 2024-03-12T09:46:53.129Z

robimarko:

NBG was moved to load firmware via kernel as well

This move was made so that newer firmware could be loaded from a file?
Should a firmware package for AQR be created?

robimarko · 2024-03-12T09:48:36.952Z

It can be loaded from file or more preferably via NVMEM from storage.

AQR FW licensing is unclear so it cannot be redistributed for now

lytr · 2024-03-12T09:51:04.564Z

Can be qcom,smem-part used with nvmem-layout?
I was trying this configuration but it's not working:

&qpic_nand {
	status = "okay";

	pinctrl-0 = <&qpic_pins_new>;

	nand@0 {
		reg = <0>;

		nand-ecc-strength = <4>;
		nand-ecc-step-size = <512>;
		nand-bus-width = <8>;

		partitions {
			compatible = "qcom,smem-part";

			partition-0-ethphyfw {
				compatible = "fixed-partitions";
				label = "0:ethphyfw";
				read-only;
				#address-cells = <1>;
				#size-cells = <1>;

				nvmem-layout {
					compatible = "fixed-layout";
					#address-cells = <1>;
					#size-cells = <1>;

					aqr_fw: firmware@0 {
						/* Skip the QCOM MBN Header of 40 bytes */
						reg = <0x28 0x5f82a>;
					};
				};
			};
		};
	};
};

robimarko · 2024-03-12T09:52:28.973Z

NVMEM should work with SMEM partitions, there should be an example already.

lytr · 2024-03-12T09:58:08.486Z

Funny thing, if I stop bootloader I can see:

PHY ID1: 0x4d
PHY ID2: 0xd0b1
PHY ID1: 0x31c3
PHY ID2: 0x1c22

and after run boot command AQR PHY is working

robimarko · 2024-03-12T09:58:53.296Z

Yes, because if you interrupt boot then it will initialize networking, but it will not do it if just autobooting

lytr · 2024-03-12T10:01:30.604Z

What could be wrong that there is no transmission on QCA8075 ports? After removing the AQR port from dts, the ports work.

After modify bootcmd and use aq_load_fw all ports work.

Is some additional configuration needed like in this script: OpenWrt support for Linksys MX8500 - #24 by lytr ?