Hi,
i have an APX120 with a solid red light. I read other Posts on this Forum and established a serial Connection to the AP. I cant break the auto boot even with a powershell script which sends 1000 inputs per second. I read in this Post https://community.sophos.com/sophoswireless/f/discussions/142129/trying-to-unbrick-my-apx120 that you it can help to short SO/SIO1 to break auto boot. Unfortunately i dont have the necessary knowledge to know where those pins are.
The serial output says:
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-00120
S - IMAGE_VARIANT_STRING=DAABANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000021
S - Reset status Config, 0x00000010
S - Core 0 Frequency, 0 MHz
B - 261 - PBL, Start
B - 1338 - bootable_media_detect_entry, Start
B - 1677 - bootable_media_detect_success, Start
B - 1691 - elf_loader_entry, Start
B - 5068 - auth_hash_seg_entry, Start
B - 7208 - auth_hash_seg_exit, Start
B - 577087 - elf_segs_hash_verify_entry, Start
B - 694241 - PBL, End
B - 694264 - SBL1, Start
B - 785270 - pm_device_init, Start
D - 7 - pm_device_init, Delta
B - 786715 - boot_flash_init, Start
D - 52831 - boot_flash_init, Delta
B - 843686 - boot_config_data_table_init, Start
D - 3837 - boot_config_data_table_init, Delta - (419 Bytes)
B - 850891 - clock_init, Start
D - 7560 - clock_init, Delta
B - 862924 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:1,Subtype:0
B - 866336 - sbl1_ddr_set_params, Start
B - 871433 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 875815 - Pre_DDR_clock_init, Start
D - 4 - Pre_DDR_clock_init, Delta
D - 13174 - sbl1_ddr_set_params, Delta
B - 889552 - pm_driver_init, Start
D - 2 - pm_driver_init, Delta
B - 959602 - sbl1_wait_for_ddr_training, Start
D - 27 - sbl1_wait_for_ddr_training, Delta
B - 975425 - Image Load, Start
D - 152261 - QSEE Image Loaded, Delta - (297752 Bytes)
B - 1128113 - Image Load, Start
D - 1444 - SEC Image Loaded, Delta - (2048 Bytes)
B - 1138517 - Image Load, Start
D - 224050 - APPSBL Image Loaded, Delta - (458523 Bytes)
B - 1362966 - QSEE Execution, Start
D - 60 - QSEE Execution, Delta
B - 1369191 - SBL1, End
D - 676927 - SBL1, Delta
S - Flash Throughput, 2009 KB/s (758742 Bytes, 377559 us)
S - DDR Frequency, 537 MHz
U-Boot 2012.07 [Chaos Calmer unknown,unknown] (Nov 02 2018 - 08:13:09)
smem ram ptable found: ver: 1 len: 3
DRAM: 256 MiB
@machid : 0x8010100
NAND: spi_nand: spi_nand_flash_probe SF NAND ID 0:ef:ab:21
SF: Detected W25M02GV with page size 2 KiB, total 256 MiB
SF: Detected MX25L1605D with page size 4 KiB, total 2 MiB
ipq_spi: page_size: 0x100, sector_size: 0x1000, size: 0x200000
258 MiB
MMC:
In: serial
Out: serial
Err: serial
machid: 8010100
flash_type: 0
Hit any key to stop autoboot: 0
Creating 1 MTD partitions on "nand1":
0x000000000000-0x000010000000 : "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 error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Creating 1 MTD partitions on "nand1":
0x000000000000-0x000010000000 : "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 error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...
