9.6 C
New York
Thursday, November 21, 2024

swap – Allied Telesis AT-9424T/SP caught in bootloop


I’m dealing with a boot loop problem with my Allied Telesis AT-9424T/SP swap. After powering it on, the system initializes and makes an attempt to decompress the appliance picture, however it will definitely throws an exception and restarts. I think the problem could be as a result of an incompatibility between the bootloader and the appliance firmware variations. Right here’s what I’ve tried and noticed to this point:
1. Console Output Throughout Boot:

Boot Loader (ROM) data:
Product Identify: ATS63_LOADER
Product Model: v3.2.1
Construct Date: Jul 1 2009
Construct Time: 11:31:24

System data:
SDRAM: 32MB
CPU velocity: 200MHz

Decompressing the Utility Picture, please wait…………………………..
…………………………………………………………………..
…………………………………………………………………..
…………………………………………………………………..

Decompressed 3255604 bytes from Flash to 11404256 bytes into RAM
Soar to 0x00000100 to begin utility

2.  Exception Message:

Initializing LoopGuard ….

FATAL – Exception
Bootloader: ATS63_LOADER v3.2.1 Cycle_A Jul 1 2009 11:31:24
Utility: ATS63 v2.11.6J Cycle_C Jul 22 2013 11:34:29
Module: Init 15:48:29 on 20-Nov-2024

GPR0 = 00004e78 GPR1 = 00d16194 GPR2 = 00ada780 GPR3 = a54b962d

Exception Vector: 00001100/Tackle error at 0062dbe8

I’ve Tried So Far:
• Tried accessing the bootloader by urgent Ctrl + B, Ctrl + C, and Esc throughout boot.
• Adjusted serial connection parameters to 460800 bps (default) and even 9600 bps for troubleshooting.
• Recognized that the variations of the bootloader (2009) and firmware utility (2013) differ, which can be inflicting the problem.
• Tried utilizing the reset button (SW1) on the board however didn’t discover any change.

My Questions:
1. Is the distinction between the bootloader and firmware variations doubtless the reason for this problem?
2. How can I drive the swap into ROM Monitor mode if no keys appear to interrupt the boot course of?
3. Can the SW1 button be used for resetting the machine or forcing it right into a restoration mode? If sure, how?
4. Is it doable to replace the bootloader by way of XMODEM or one other methodology with out accessing the appliance firmware?

I respect any insights or steering from those that’ve encountered comparable points. Thanks!

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles