There's a GPIO that resets all PCIE devices. I've tried it in the past, it only crashes everything. 
OK I am done with it for now. Here is a sort of video that could maybe help others come to terms with it. Thanks again.
1 Like
I've been reading about the ARTS problem and it seems what actually happens is Openwrt tries to find the partition and load it itself. There is a working framework in place for the 10k that could maybe also work for the 9k but it is not happening, or not usually needed thus it does not work anyway.
11-ath10k-caldata
root@PUMA:/etc/hotplug.d/firmware# cat *
#!/bin/sh
[ -e /lib/firmware/$FIRMWARE ] && exit 0
. /lib/functions/caldata.sh
find_nvram_mmc_part() {
local DEVNAME PARTNAME
local TMPMOUNT="$1"
for DEVNAME in /sys/block/mmcblk0/mmcblk*p*; do
PARTNAME="/dev/$(basename $DEVNAME)"
mount $PARTNAME $TMPMOUNT > /dev/null 2>&1
if [ $? -ne 0 ]; then
# can't mount
continue
fi
if [ -f $TMPMOUNT/cal/calData_11ac.bin ]; then
# caldata found!
return 0
fi
# caldata not found
umount $TMPMOUNT 2>&1 > /dev/null
done
return 1
}
case "$FIRMWARE" in
"ath10k/cal-pci-0000:03:00.0.bin")
TMP=$(mktemp -d)
if ! find_nvram_mmc_part $TMP; then
caldata_die "Can't find caldata files on any partition"
fi
TMPF=$(mktemp -t /tmp/calDatabin.XXXXXX)
cp $TMP/cal/calData_11ac.bin $TMPF || caldata_die "Can't copy caldata to temp file"
umount $TMP 2>&1 > /dev/null
caldata_sysfsload_from_file "$TMPF" 0x0 0x844
rm $TMPF 2>&1 > /dev/null
;;
*)
exit 1
;;
esac
root@PUMA:/# find | grep -ai caldata
./etc/hotplug.d/firmware/11-ath10k-caldata
./lib/functions/caldata.sh
./rom/etc/hotplug.d/firmware/11-ath10k-caldata
./rom/lib/functions/caldata.sh
./tmp/tmp/calDatabin.FmIPfk
root@PUMA:/# cd /tmp/tmp
root@PUMA:/tmp/tmp# ls -l
-rw-r--r-- 1 root root 2116 Aug 1 03:39 calDatabin.FmIPfk
root@PUMA:/tmp/tmp# ls -l /boot/cal
-rw-r--r-- 1 root root 2116 Jan 1 2000 calData_11ac.bin
-rw-r--r-- 1 root root 1088 Jan 1 2000 calData_11n.bin
I am confident the 5G is TOTALLY fine. But the 2 well I am getting close to giving up on it. There is something called owl loader that does not seem to work right away.
I opened it up to try a few things because I was afraid sysupgrade could brick it. No dice on 2Ghz, but I did improve my build a bit. I do not seem to have 9k firmware because I think it does not exist?
Yes, the ath10k is something I had to do in order to make it work, because the kernel driver for it was complaining about a missing calibration file. The ath9k in your case just refuses to load, might be because of a missing calibration file. In any case, this device doesn't use the "art" partition at all, never had one.
The /etc/hotplug.d/firmware/11-ath10k-caldata is what I came up with to provide the ath10k kernel module with the calData_11ac.bin.
In theory it could be copied to a new file and modified to add support for the ath9k, but I have no idea which file the ath9k is asking for (see on that script that I have ath10k/cal-pci-0000:03:00.0.bin hardcoded). If we could know where that file needs to be placed, we can copy it for a temporary workaround. Maybe on /lib/firmware/something, not sure.
And yes, since this ath9k is the PCIe version (NOT USB, which is the ath9k-htc), it doesn't seem to require a firmware (it must be already on the wifi chip itself already).
It is possible there is something else wrong like mine is a weird version of chip. The owl loader looked very promising, but it is supposed to print strings about what it is doing, and just outputs nothing. No big deal, it just bugged me I could get it working almost.
I installed atheepmgr and this is what the calData_11n.bin has in it.
.----------------------.
| Chip init data |
'----------------------'
Blob has no chip initialization data
.----------------------.
| EEPROM Base Header |
'----------------------'
Version : 2
RegDomain1 : 0x0000
RegDomain2 : 0x001F
MacAddress : 8C:0F:6F:B8:DD:98
TX Mask : 0x0007
RX Mask : 0x0007
Allow 5GHz : 0
Allow 2GHz : 1
Disable 2GHz HT20 : 0
Disable 2GHz HT40 : 0
Disable 5Ghz HT20 : 0
Disable 5Ghz HT40 : 0
Big Endian : 0
RF Silent : 0
BT option : 0
Device Cap : 0
Device Type : PCIExpress
Power Table Offset : 0
Tuning Caps1 : 30
Tuning Caps2 : 0
Enable Tx Temp Comp : 1
Enable Tx Volt Comp : 0
Enable fast clock : 1
Enable doubling : 1
Internal regulator : 0
Enable Paprd : 0
Driver Strength : 0
Quick Drop : 0
Chain mask Reduce : 0
Write enable Gpio : 6
WLAN Disable Gpio : 0
WLAN LED Gpio : 8
Rx Band Select Gpio : 255
Tx Gain : 0
Rx Gain : 0
SW Reg : 0
Customer Data in hex:
58 42 31 31 32 2d 30 33 35 00 69 6e 67 5f 63 6f |XB112-035.ing_co|
6e 74 72 6f |ntro |
.----------------------.
| EEPROM Modal Header |
'----------------------'
2G
Ant Chain 0 : 336
Ant Chain 1 : 336
Ant Chain 2 : 336
Antenna Common : 272
Antenna Common2 : 139810
Antenna Gain : 0
Switch Settling : 44
xatten1DB Ch 0 : 0
xatten1DB Ch 1 : 0
xatten1DB Ch 2 : 0
xatten1Margin Chain 0 : 0
xatten1Margin Chain 1 : 0
xatten1Margin Chain 2 : 0
Temp Slope : 50
Volt Slope : 0
spur Channels0 : 164
spur Channels1 : 0
spur Channels2 : 0
spur Channels3 : 0
spur Channels4 : 0
NF Thresh 0 : -1
NF Thresh 1 : 0
NF Thresh 2 : 0
Quick Drop : -51
TX end to xpa off : 1
Xpa bias level : 0
txFrameToDataStart : 14
txFrameToPaOn : 14
TX frame to xpa on : 14
TxClip : 3
ADC Desired Size : -30
PAPD Rate Mask HT20 : 0xc80c080
PAPD Rate Mask HT40 : 0x80c080
.----------------------.
| EEPROM Power Info |
'----------------------'
[2 GHz per-freq power cal. data]
.-------------- Chain 0 -----------..-------------- Chain 1 -----------..-------------- Chain 2 -----------.
| Tx : Rx || Tx : Rx || Tx : Rx |
Freq, MHz PwrDelta Volt Temp NF Pwr Temp PwrDelta Volt Temp NF Pwr Temp PwrDelta Volt Temp NF Pwr Temp
2412 3.5 0 150 0 0 0 10.0 0 148 0 0 0 6.5 0 151 0 0 0
2437 4.5 0 149 0 0 0 11.5 0 148 0 0 0 7.5 0 150 0 0 0
2462 6.0 0 150 0 0 0 12.5 0 148 0 0 0 8.0 0 150 0 0 0
[2 GHz CCK per-rate target power]
Freq, MHz: 2412 2472
------------------------ ---- ----
1-5 mbps (L), dBm: 26.0 26.0
5 mbps (S), dBm: 26.0 26.0
11 mbps (L), dBm: 26.0 26.0
11 mbps (S), dBm: 26.0 26.0
[2 GHz OFDM per-rate target power]
Freq, MHz: 2412 2442 2472
------------------------ ---- ---- ----
6-24 mbps, dBm: 26.0 26.0 26.0
36 mbps, dBm: 23.0 23.0 23.0
48 mbps, dBm: 20.0 20.0 20.0
54 mbps, dBm: 20.0 20.0 20.0
[2 GHz HT20 per-rate target power]
Freq, MHz: 2412 2442 2472
------------------------ ---- ---- ----
MCS 0,8,16, dBm: 26.0 26.0 26.0
MCS 1-3,9-11,17-19, dBm: 26.0 26.0 26.0
MCS 4, dBm: 23.0 23.0 23.0
MCS 5, dBm: 22.0 22.0 22.0
MCS 6, dBm: 21.0 21.0 21.0
MCS 7, dBm: 20.0 20.0 20.0
MCS 12, dBm: 23.0 23.0 23.0
MCS 13, dBm: 22.0 22.0 22.0
MCS 14, dBm: 21.0 21.0 21.0
MCS 15, dBm: 20.0 20.0 20.0
MCS 20, dBm: 23.0 23.0 23.0
MCS 21, dBm: 22.0 22.0 22.0
MCS 22, dBm: 21.0 21.0 21.0
MCS 23, dBm: 20.0 20.0 20.0
[2 GHz HT40 per-rate target power]
Freq, MHz: 2422 2447 2462
------------------------ ---- ---- ----
MCS 0,8,16, dBm: 26.0 26.0 26.0
MCS 1-3,9-11,17-19, dBm: 26.0 26.0 26.0
MCS 4, dBm: 23.0 23.0 23.0
MCS 5, dBm: 22.0 22.0 22.0
MCS 6, dBm: 21.0 21.0 21.0
MCS 7, dBm: 20.0 20.0 20.0
MCS 12, dBm: 23.0 23.0 23.0
MCS 13, dBm: 22.0 22.0 22.0
MCS 14, dBm: 21.0 21.0 21.0
MCS 15, dBm: 20.0 20.0 20.0
MCS 20, dBm: 23.0 23.0 23.0
MCS 21, dBm: 22.0 22.0 22.0
MCS 22, dBm: 21.0 21.0 21.0
MCS 23, dBm: 20.0 20.0 20.0
[2 GHz CTL data]
FCC 2GHz CCK:
Edges, MHz: [2412 2417 2457] 2462
MaxTxPower, dBm: 22.0 24.0 24.0 22.0
FCC 2GHz OFDM:
Edges, MHz: [2412 2417 2457] 2462
MaxTxPower, dBm: 18.0 23.0 23.0 17.0
FCC 2GHz HT20:
Edges, MHz: [2412 2417 2457] 2462
MaxTxPower, dBm: 18.0 23.0 23.0 16.0
FCC 2GHz HT40:
Edges, MHz: 2412 2427 [2447 2452
MaxTxPower, dBm: 14.0 18.0 18.0 13.0
MKK 2GHz CCK:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
MKK 2GHz OFDM:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
MKK 2GHz HT20:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
MKK 2GHz HT40:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
ETSI 2GHz CCK:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
ETSI 2GHz OFDM:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
ETSI 2GHz HT20:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
ETSI 2GHz HT40:
Edges, MHz: [2412 2417 2472] 2484
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
The 5Ghz one
.----------------------.
| EEPROM Base Header |
'----------------------'
Length : 0x0844
Checksum : 0xAABA
EEP Version : 3
Template Version : 1
MacAddress : 8C:0F:6F:B8:DD:A0
RegDomain1 : 0x0000
RegDomain2 : 0x0000
Allow 5GHz : 1
Allow 5GHz HT20/HT40 : 1/1
Allow 5GHz VHT20/VHT40/VHT80 : 1/1/1
Allow 2GHz : 0
Allow 2GHz HT20/HT40 : 0/0
Allow 2GHz VHT20/VHT40 : 0/0
Cal Bin Ver : 0x0000
TX Mask : 0x07
RX Mask : 0x07
Tx Gain : 0
Rx Gain : 0
Power Table Offset : 0
CCK/OFDM Pwr Delta, dB : 0
40/20 Pwr Delta, dB : 0
80/20 Pwr Delta, dB : 0
Customer Data in hex:
63 75 73 32 32 33 2d 35 32 30 2d 6e 31 37 32 35 |cus223-520-n1725|
00 00 00 00 |.... |
.----------------------.
| EEPROM Modal Header |
'----------------------'
5G
Antenna Ctrl Chain 0 : 0x10
Antenna Ctrl Chain 1 : 0x10
Antenna Ctrl Chain 2 : 0x10
Antenna Ctrl Common : 0x220
Antenna Ctrl Common2 : 0x11111
Antenna Gain : 0
NF Thresh : 33
.----------------------.
| EEPROM Power Info |
'----------------------'
[5 GHz OFDM per-rate target power]
Freq, MHz: 5240 5260 5320 5500 5600 5745
------------------------ ---- ---- ---- ---- ---- ----
6-24 mbps, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
36 mbps, dBm: 21.0 21.0 21.0 21.0 21.0 21.0
48 mbps, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
54 mbps, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
[5 GHz HT20/VHT20 per-rate target power]
HT MCS VHT MCS | Freq, MHz: 5240 5260 5320 5500 5600 5745
---------------------------- ---- ---- ---- ---- ---- ----
0 0, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
1-2 1-2, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
3-4 3-4, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
5 5, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
6 6, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
7 7, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
8, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
9, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
8 10, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
9-10 11-12, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
11-12 13-14, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
13 15, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
14 16, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
15 17, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
18, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
19, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
16 20, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
17-18 21-22, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
19-20 23-24, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
21 25, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
22 26, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
23 27, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
28, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
29, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
[5 GHz HT40/VHT40 per-rate target power]
HT MCS VHT MCS | Freq, MHz: 5240 5260 5320 5500 5600 5745
---------------------------- ---- ---- ---- ---- ---- ----
0 0, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
1-2 1-2, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
3-4 3-4, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
5 5, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
6 6, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
7 7, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
8, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
9, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
8 10, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
9-10 11-12, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
11-12 13-14, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
13 15, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
14 16, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
15 17, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
18, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
19, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
16 20, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
17-18 21-22, dBm: 24.0 24.0 24.0 24.0 24.0 24.0
19-20 23-24, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
21 25, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
22 26, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
23 27, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
28, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
29, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
[5 GHz VHT80 per-rate target power]
HT MCS VHT MCS | Freq, MHz: 5240 5260 5320 5500 5600 5745
---------------------------- ---- ---- ---- ---- ---- ----
0 0, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
1-2 1-2, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
3-4 3-4, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
5 5, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
6 6, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
7 7, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
8, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
9, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
8 10, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
9-10 11-12, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
11-12 13-14, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
13 15, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
14 16, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
15 17, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
18, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
19, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
16 20, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
17-18 21-22, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
19-20 23-24, dBm: 23.0 23.0 23.0 23.0 23.0 23.0
21 25, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
22 26, dBm: 20.0 20.0 20.0 20.0 20.0 20.0
23 27, dBm: 19.0 19.0 19.0 19.0 19.0 19.0
28, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
29, dBm: 18.0 18.0 18.0 18.0 18.0 18.0
[5 GHz CTL data]
FCC 5GHz OFDM:
Edges, MHz: [5180 5200 5260 5500 5720] [5745 5765 5825
MaxTxPower, dBm: 22.0 22.0 19.0 19.0 19.0 23.0 24.0 23.0
FCC 5GHz HT20:
Edges, MHz: [5180 5200 5260 5500 5720] [5745 5765 5825
MaxTxPower, dBm: 22.0 23.0 19.0 19.0 19.0 23.0 24.0 22.0
FCC 5GHz HT40:
Edges, MHz: 5190 5230 5270 5310 5510 5550 5755 5795
MaxTxPower, dBm: 17.0 24.0 19.0 18.0 18.0 19.0 21.0 22.0
FCC 5GHz VHT20:
Edges, MHz: [5210 5290] [5530 5610] [5690 5775
MaxTxPower, dBm: 15.0 14.0 16.0 16.0 16.0 16.0
MKK 5GHz OFDM:
Edges, MHz: 5180 [5240 5260 5320] [5500 5520 5680] [5700
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
MKK 5GHz HT20:
Edges, MHz: 5180 [5240 5260 5320] [5500 5520 5680] [5700
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
MKK 5GHz HT40:
Edges, MHz: [5190 5230] [5270 5310] [5510 5550 5630] [5670
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
MKK 5GHz VHT20:
Edges, MHz: [5210 5290] [5530 5610]
MaxTxPower, dBm: 30.0 30.0 30.0 30.0
ETSI 5GHz OFDM:
Edges, MHz: 5180 [5260 5280 5500 5700] [5720 5745 5825]
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
ETSI 5GHz HT20:
Edges, MHz: 5180 [5260 5280 5500 5700] [5720 5745 5825]
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
ETSI 5GHz HT40:
Edges, MHz: 5190 [5270 5310] 5510 [5670 5710] [5755 5795]
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0 30.0 30.0
ETSI 5GHz VHT20:
Edges, MHz: [5210 5290] [5530 5610] [5690 5775]
MaxTxPower, dBm: 30.0 30.0 30.0 30.0 30.0 30.0
Yes, those were used (somehow) by the stock firmware. My particular unit doesn't require the .bin for the ath9k.
@slh sorry to bother you, but do you know who can we ask about the ath9k issue that @msuffidy is having? My unit doesn't need any cal file (or partition), but my ath10k did (that's why I created a hotplug.d file for the file it requested), but I don't see any requested file for his ath9k.
This suggests there is a nvmem interface for the ath9k, and I dont have /sys/bus/nvmem
On most embedded ath9k devices (like range extenders,
routers, accesspoints, ...) the calibration data is
stored in a MTD partitions named "ART", or "caldata"/
"calibration".
Since commit 4b361cfa8624 ("mtd: core: add OTP nvmem provider support"):
All MTD partitions are all automatically available through
the nvmem subsystem. This feature - together with an nvmem cell definition
in the device-tree - allows drivers like ath9k to get the data necessary
for starting the WIFI, without having to wait around for the filesystem
and userspace to do the extractions.
Yes, but I don't have that either and it works. "art" or "caldata" or "calibration" are partitions on mtd devices on other devices, not on this particular one. It was always a file. Maybe mine has it already fused or something. Loading it would be easy (copying the same mechanism for the ath10k, but modifying some names). The problem is that I don't know which file the module is requesting, thus why I don't know what to modify on the file.
Let's try the following, add this file as /etc/hotplug.d/12-test:
#!/bin/sh
[ -e /lib/firmware/$FIRMWARE ] && exit 0
. /lib/functions/caldata.sh
logger -s -t "fw" "Trying to load $FIRMWARE"
exit 1
Do a chmod +x /etc/hotplug.d/12-test and reboot. Then, run logread | grep "fw"
I am not getting any result from that.
is this supposed to be like this?
. /lib/functions/caldata.sh
No. if you don't get anything, it means that any kernel module is not requesting any firmware, including the ath9k. Which I'd assume the problem is not related to calibration data
I see this option that I hope is not the problem.
Force Atheros drivers to respect the user's regdomain setting
is set to yes.
If that affected it, is is just because it was missing that data that was not loaded.
Really I should have tried your binaries and seen if whatever you did made it work but I can't remember and I'd have to open it again.
I tried to force the owl loader to use my pci device and load my eeprom, which was likely not the correct file. So far it did not seem to work so I am giving up for now.
I just curious is there something that happens if you hold the resent switch, like it clears overlay as a kind base files fhing? What about the button on top?
Reset button is hardwired to the reset signal of the CPU, so, it will only reset the modem while you're holding it
I got another of those 3848s for $15. I was going to try putting your binaries on it to see if I get ath9k this time. Unfortunately I have run into a problem, the command 'cpc' seems to be missing or different and I just get errors
shell> cpc set boottype 1
Error: Invalid command.
shell> cpc set docddroff 0x1fffffff
Error: Invalid command.
shell> cpc docddroff 0x1fffffff
Error: Invalid command.
yes help no longer has cpc. So I was thinking if I backup the flash and then overwrite the flash with the backup for the other (working) unit it would probably make the version correct, but I can't shut down the atom core before running linux off of a stick to do these things. Well it seemed kinda reliable enough to get me there. I have backed up the non-working flash and p6 to a usb stick. SO MY QUESTION WOULD BE IS IT OK TO USE THE WORKING IMAGE TO REPROGRAM THE NON-WORKING MMC0? (then I would restart the install process again) The printout says they are a different silicon revision and build.
this is the help
shell> help
bootata - Boots from the primary master ATA device.
ymodem - Receive a file from serial using YMODEM.
lspci - Displays PCI device info.
ord[2|4] - Read or write to memory.
pci[2|4] - Read or write to PCI configuration space.
port[2|4] - Read or write to I/O port.
goto - goto to specific IP to run code.
crc32 - compute crc32 sum of a bulk memory
netserver - net server service for external clients
ramdisk - set ramdisk start address and length
delay - delay some time
mmap - Displays a system memory map.
bootkernel - Boot Linux kernel from flash.
mfh - manage the MFH on flash devices
sha - Calculate a SHA sum for an input data string.
md5 - Calculate a MD5 sum for an input data string.
emmc - Auxiliary shell command to handle eMMC
spi_flash - Auxiliary shell command to handle SPI Flash
aid - manage the Active Image Designator
8051 - 8051 specific commands
svmem - Perform SV memory test
ata-map - Sets the ATA geometry mapping.
cache - Manipulate the processor cache.
ping - Ping destination [Ping count number]
tftp - Download/upload file from/to server via TFTP.
ip - Configure CEFDK static IP address, Subnet Mask and Gateway address.
settings - BIOS Settings
i2c - I2C buses read and write (SV ver).
script - Switch on/off the automatic shell script.
hwmutex - Auxiliary shell command to help check hw mutex status
load - load from storage meida.
sleep - Suspend and resume utilities
gpio - gpio commands
fll - flash layout list according to settings.
iosf - Read/write 32 bit register on IOSF sideband port.
wdt - Configure watchdog timers.
help - Displays this screen.
exit - Stops the shell.
ok I was pretty sure no one would have a great idea so I threw the switch and I have a shell still with cpc now so that was that. I'm guessing what happens is the ARM core keeps trying to access the mmc but it eventually dies out like it wanted something and then you can do stuff properly. It was then that I backed up the whole mmc and p6 and put the prior unit backup on mmc and rebooted. Big gulp hurray.
OK some data
So I used Cocus binaries. Bottom line is exact same behaviour in every regard. Only the ath10k works, but it in fact does with the (non working cpc firmware's config data). I was a little confused because there was not a wireless network device yet, but you configure it and it is there. Lots of errors doing some kind of block erase during overlay format. So I am calling it what I expected and now have 2 of them! Thanks
I tried to compile python3 on the router but when I did the make install I could not get past problems with zlib. Also it complained about SSL version. It was not clear or not if I could make yt-dlp work with it, which was the point. I doubt I will have the cell data limits that made that a plan in the past.
OK so I got a 3rd unit (for free again), which was mostly useful for testing the luci firmware update, which worked with the efi squash combined. What I did was work on the idea that the wireless 2Ghz had an empty eeprom or none and started looking into nvmem or driver modding. I modded a few lines in ath9k/init.c and it works now and loads a filename I hardwired.
actually it is just (frmw) not (frmw/ath9k) that is looks:
1 Like