This output tells us exactly what is wrong, but unfortunately, it is bad news.
What you are looking at is the
BTRM (Boot Read-Only Memory) diagnostic sequence. This is the very first, hardcoded spark of life on the processor chip, running
before any operating system or even the bootloader (apboot) loads.
Here is a breakdown of why this is happening and why you cannot type anything:
1. What the Codes Mean
The text is a step-by-step hardware check:
- BTRM V1.6: The Boot ROM version.
- CPU0, L1CD, MMUI, DATA: The processor is checking its internal caches and memory processing successfully.
- NAND: The processor is attempting to read the NAND flash memory chip (where the firmware and bootloader live).
- The Repeating Loop (IMG?, IMGL, UHD?, UHDP, RLO?, RLOP, UBI?, UBIF): This is where it fails. The processor is desperately searching the NAND flash for a valid boot image (IMG?) or U-Boot header (UHD?) to load, but it is failing (UBIF usually points to an Uncorrectable Bit Error or UBIFS failure).
Because it fails, it just loops back and tries again indefinitely.
2. Why You Cannot Type
You cannot type anything because the system never reaches the apboot stage. The apboot software is what actually turns on the console input so you can type commands like factory_reset or intercept the boot sequence. Right now, the hardware is completely deaf to your keyboard.
3. The Verdict: A "Bricked" AP
This looping 4-character BTRM output is a known indicator of a severe low-level failure on Aruba access points. It means one of two things:
- Total Bootloader Corruption: The very core partition that holds the recovery tools was wiped out.
- Physical NAND Failure: The actual flash memory chip on the motherboard has physically died (bad blocks in the critical boot sector).
Because you cannot access the apboot> prompt to push new firmware via TFTP, this AP cannot be recovered via software or console cables. It is essentially "bricked."
If this AP-515 is still covered by a support contract or lifetime warranty, your next step is to open a TAC case with Aruba/HPE and provide this exact screenshot to request an
RMA (Return Merchandise Authorization) for a hardware replacement.
Would you like me to help draft a quick technical summary of this failure that you can copy and paste into an RMA support ticket?
