Hello,
my APX320 was Bricked.
With Sophos Flash Tool I have installed the Firmware.
Probably I have installed an Wrong Image.
In directory /lib/firmware/IPQ4019/hw.1 are only APX120 exists.
In fact of this my APX320
- Boot with green LED
- Get an IP from DHCP
but I can see it in my UTM9 Home or XGS Home.
This is console Log
<Code>
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00108
S - IMAGE_VARIANT_STRING=DAABANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000021
S - Reset status Config, 0x00000000
S - Core 0 Frequency, 0 MHz
B - 261 - PBL, Start
B - 1338 - bootable_media_detect_entry, Start
B - 1678 - bootable_media_detect_success, Start
B - 1692 - elf_loader_entry, Start
B - 5068 - auth_hash_seg_entry, Start
B - 7212 - auth_hash_seg_exit, Start
B - 578517 - elf_segs_hash_verify_entry, Start
B - 694693 - PBL, End
B - 694717 - SBL1, Start
B - 785052 - pm_device_init, Start
D - 7 - pm_device_init, Delta
B - 786577 - boot_flash_init, Start
D - 57404 - boot_flash_init, Delta
B - 848127 - boot_config_data_table_init, Start
D - 3844 - boot_config_data_table_init, Delta - (419 Bytes)
B - 855609 - clock_init, Start
D - 7586 - clock_init, Delta
B - 867368 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:6
B - 870782 - sbl1_ddr_set_params, Start
B - 875878 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 880260 - Pre_DDR_clock_init, Start
D - 5 - Pre_DDR_clock_init, Delta
D - 13174 - sbl1_ddr_set_params, Delta
B - 893573 - pm_driver_init, Start
D - 3 - pm_driver_init, Delta
B - 964133 - sbl1_wait_for_ddr_training, Start
D - 27 - sbl1_wait_for_ddr_training, Delta
B - 980377 - Image Load, Start
D - 138343 - QSEE Image Loaded, Delta - (269176 Bytes)
B - 1119154 - Image Load, Start
D - 1441 - SEC Image Loaded, Delta - (2048 Bytes)
B - 1129475 - Image Load, Start
D - 220020 - APPSBL Image Loaded, Delta - (450356 Bytes)
B - 1349894 - QSEE Execution, Start
D - 60 - QSEE Execution, Delta
B - 1356110 - SBL1, End
D - 663472 - SBL1, Delta
S - Flash Throughput, 2007 KB/s (721999 Bytes, 359616 us)
S - DDR Frequency, 672 MHz
U-Boot 2012.07 (Dec 05 2017 - 16:05:06)
smem ram ptable found: ver: 1 len: 3
DRAM: 512 MiB
machid : 0x8010006
NAND: ONFI device found
ID = 9590dcc2
Vendor = c2
Device = dc
SF: Detected GD25Q32 with page size 4 KiB, total 4 MiB
ipq_spi: page_size: 0x100, sector_size: 0x1000, size: 0x400000
516 MiB
In: serial
Out: serial
Err: serial
machid: 8010006
flash_type: 0
Configurate GPIO setting
Configurate TPM reset from low to high.
Configurate BLE reset from low to high.
Net:
PHY ID = 0x4dd072, eth0 found AR8035 PHY
MAC0 addr:7c:5a:1c:2:d0:b8
eth0
Creating 1 MTD partitions on "nand0":
0x000000000000-0x000020000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: attached mtd2 to ubi0
UBI: MTD device name: "mtd=0"
UBI: MTD device size: 512 MiB
UBI: number of good PEBs: 4096
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 4
UBI: available PEBs: 2068
UBI: total number of reserved PEBs: 2028
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 39/1
SF: Detected GD25Q32 with page size 4 KiB, total 4 MiB
Hit any key to stop autoboot: 0
Read 0 bytes from volume image to 88000000
No size specified -> Using max size (67170304)
## Booting kernel from FIT Image at 88000000 ...
Using 'config@1' configuration
Trying 'kernel@1' kernel subimage
Description: ARM OpenWrt Linux-3.14.43
Type: Kernel Image
Compression: uncompressed
Data Start: 0x880000e4
Data Size: 16077860 Bytes = 15.3 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80208000
Entry Point: 0x80208000
node name: signature@1
Sign algo: sha256,rsa4096
Sign value: 9a06c47d5fec5f2dfd23d4cc2c4b376ae74322367ba176189f737f51f376aa0cb9aba6a39c6380e8ae84bc881752b58c95b6df72c2ce5e80a8412b57d3a36e22530491a92bffa182755fd8a171787c7e95ed08f2be9acd04ab9d08e46c44a663658c543ddfbd0cd3ae3e5f93757c7a3850b2104f5b7d7c6334c2cb642cbea12d77d66e2deef0156564fc12b564b1f05bf31f0871b2ed1e8187387bf133577dc1c19485a82eafdb6f640959eaf9029b75846653b56d9010ad513d0ff83d52321f0cd881aac56664241ac0a9dc0532fc012a7a8b9cfe607215884f7c471b178e0b5b01eaf8b4751a6a812f30bb6c7787f2106694503fcb3cda274545df5538b7e2ff883d34d9c29457e59d540f5bc1c3ed4aa23ea87ffe4f17cf2d8c5761e30b12767248ddf0de48d799297254c5c7bd9fa3dfc4c6c0d304831bb8eb67c58425e09b42a7de02f537d409187543ccacbde113af4f97b582c2b536a0709f9678c976e28cad59dab8acc25285cbd3d5db4b024c831f358f46752809299449d2549a9c0de34fbee4c363a95de3e4c8aa0a8f8c117a8d63ab6fa9d9e9ea5242b7ad7b18984f6373f72ca05ed14931c5cd6c4676293cdb8ef5bac2d3e8ef004364f3ab19ee83e6ae5eb43d0f7aeb0fd37f132503ed7a0bad235b0033257b036b2587b009f3397a88811fb8476f396d5280fce99a8c6cf983b0193dc7c066bae853c11016
Verifying Hash Integrity ... sha256+ OK
## Flattened Device Tree from FIT Image at 88000000
Using 'config@1' configuration
Trying 'fdt@1' FDT blob subimage
Description: ARM OpenWrt Sophos-APX device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x88f5584c
Data Size: 35149 Bytes = 34.3 KiB
Architecture: ARM
node name: signature@1
Sign algo: sha256,rsa4096
Sign value: 99f91f7dc7567667f228d9cb47bf977f660b452317c2d86671d50e890369fa56dc7122c40700713e4cd2bc77b0f879ff3307855be8f43f1f8e7116e419f62fbee38ba643dfeaaa1d5208f3697de5bdedadc97a23aa031220e0d37087e6f631b8865f2a4b4e5d636eedab5afed950d0c68fa29b3b4d28e80afa8312055cf03cadaf80dabf608adac87d8bef5815c838dff7d939ce4b68306495ff5f6a11edff98952a4eda578b758b255882a10c197f9f0654b8822e54c2c6de28db3ffb004307833e521acc543c476b92c8815576737201e873d27ce98f756ce10bac5adbe418f290376504b89047cff6fb410c632bb705956400c34361c7f6a0ac5a08bacc84dcbc26491d628e31c1fb1d9354b3ed34d947c5d7e80def8d3f84a9784b399e5d244d6ef9a52be5bd78204c8574e80ec221221fba108fe218495c8d6d4381ae76f14500450d14afcf5f0c5f1ad917c3038e11d03879d2c122fed97a4cef2875c0c6f3ac3732b9aa41b7b045435e124da0c4c8c207bca4ef102f405887eda148d94af4c20ad7c4c9996c73089ca621ac1fadc08c2418ba6549d01e6780b64fde13b4a3b79b1f36849d6396c30840584910a1b2a888bd9309ba5bab8c8163b36eb234cbd276438d084c56a5959da84203fb86c49e36d828276fb1778de536a4343f01f515c829d03f0b98f13d4381f919bfc6fdec5dbcd7c63361b757349810c054
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x88f5584c
Loading Kernel Image ... OK
OK
Loading Device Tree to 871e3000, end 871ee94c ... OK
Using machid 0x8010006 from environment
Starting kernel ...
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
Please press Enter to activate this console.
Booting. (Version: task/CWIFI-9469-1002)
Checking The AP model
Starting network configuration for ethernet interface over DHCP.
dnsserver entries are missing
Cloud certificate validation pending.
UTM certificate validation pending.
dnsserver entries are missing
dnsserver entries are missing
Ethernet autoconfiguration (bound): IP:192.168.102.102/24, gateway:192.168.102.251, nameservers:192.168.102.251
Ethernet link state changed to: up, Speed: 100, Duplex: full
[cloudclient] Last AP reboot was triggered by:
</Code>
Added TAGs
[edited by: Erick Jan at 5:01 AM (GMT -8) on 12 Jan 2024]
