C9105 access point corrupt OS image

[silverdoor12]

I have one C9105 access point.

While upgradeing the C9105 OS, the OS became corrupted and when rebooted, characters became break. (meaningless foreign language)

Is there any way to enter u-boot mode forcely?

I have normal OS in boot2 section, so I want to restore this AP.

Please help me.

---------------------------------------------------------------------------

Boot Strap Register: 0x7ffffb7b
Applying trim code 0x2 reg 0x8 from otp to LDO controller...
NVRAM memcfg 0x101610
MCB chksum 0xa00ca018, config 0x101610
DDR4-2133 CL15 total 2048MB 2 8bits part[s] %1 SSC

DDR test done successfully
CFE 32-bit Version: 06
Verifying MASTER U-Boot...
UBOOT_CFG ffdff000: 4f435343 00000000
UBOOT_MAP 00ffff00: 4f435343 00000000 00000003 00000000 00000062 00000000
Launching MASTER U-Boot version 0x0062 ...

____ _
/ ___|(_) ___ ___ ___
| | | |/ __| / __|/ _ \
| |___ | |\__ \| (__| (_) |
\____||_||___/ \___|\___/
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|

U-Boot 2017.09 (Sep 01 2023 - 07:36:59 -0700) Broadcom BCM47622

Board: SOMERSET-I-ME
I2C: ready
DRAM: 2 GiB
NAND: NAND ECC BCH-8, devId 0x2cd390a6 page size 4096 bytes, spare size used 216 bytes
1024 MiB
MMC:
SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB

ήLLLLO CPU0 L1CD MMUI ZBBS

[marce1000]

 - FYI  : https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html#anc8

 M.

[silverdoor12]

Thank you for answering, but I can't enter u-boot mode. 

after this log 'SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB'

there are no response.

Should I RMA this device?

[marce1000 · Accepted solution]

           - Yes (RMA) , 

 M.

[Rich R]

Before you RMA ...

The default console baud rate has changed from 9600 baud to 115200 baud.
You can expect to see this when AP config is reset to factory default on latest code versions.

So try your terminal at 115200 and you might find there's nothing wrong with the AP.