AIR-CAP3502i: need to run again RAM calibration fix

Unanswered Question
Sep 11th, 2013
User Badges:

Hello everyone, here's full story ...


I just purchased a lot of three 2nd hand AIR-CAP3502i-E-K9, that were previously set as lightweight. Since I needed autonomous APs, I loaded a 12.4 IOS first, then upgraded to 15.2(4)JA1.


On first device, turning LWAPP to Autonomous set a 'boot system flash' variable of corresponding image. Device booted fine, had 12.4(23c)JA bootloader, everything was fine.


I erased flash, loaded 15.2(4)JA1 image, all went fine.


Then, I reloaded device, but I forgot to change 'boot system flash' variable. My big mistake ... Hopefully, I did not forget to remove boot variable for the two other devices, and everything happened on two others as it should (upgrade process went smoothly).


Output (hopefully, Putty logs everything ):


: Vendor 0x7C08, Device 0x3A6

******** AUTOMATIC DDR CALIBRATION UPGRADE LOGIC *********

=== 1. Is original FCS bootloader in BS:?  If not, skip upgrade ===

    ---> original FCS bootloader was detected at bs:

=== 2. Has upgrade logic already ran once? (flag!=0xffffffff)

    ---> upgrade logic has not run yet

=== 3. Read 0x1e0/0x210 EEPROM values ===

=== 4. Are 0x1e0 EEPROM signatures found?

    ---> eeprom signatures were not found

=== 5. Writing MICRON static values to eeprom at addr 0x210

    ---> write to eeprom complete

=== 6. Copy u-boot to BB:

flash:/ap3g1-k9w7-mx.124-25d.JA2/u-boot.bin: no such file or directory

    ---> error on u-boot copy -- skip upgradeBoot CMD: 'boot  flash:/ap3g1-k9w7-mx.124-25d.JA2/ap3g1-k9w7-xx.124-25d.JA2;flash:/ap3g1-k9w7-mx.152-4.JA1/ap3g1-k9w7-mx.152-4.JA1'

Loading "flash:/ap3g1-k9w7-mx.124-25d.JA2/ap3g1-k9w7-xx.124-25d.JA2"...flash:/ap3g1-k9w7-mx.124-25d.JA2/ap3g1-k9w7-xx.124-25d.JA2: no such file or directory



Error loading "flash:/ap3g1-k9w7-mx.124-25d.JA2/ap3g1-k9w7-xx.124-25d.JA2"



Interrupt within 5 seconds to abort boot process.

Boot process terminated.



The system is unable to boot automatically.  The BOOT

environment variable needs to be set to a bootable

image.



On that first device, calibration process started, but was halted since IOS didn't find new image (obviously, boot variable was set to former image ...)


I now have a device that ***seems*** to work, but I wanna avoit spurious reloads/crashes/watchdog timeouts, thus my need to redo from start calibration.


What I did:


-Downgraded image to an older 12.4 -> no avail, as advertized.

-Turned back AP to LWAPP. Bootloaded downgraded to 12.4(23c)JA (as before failed attempt), but turning back to 12.4 Autonomous then 15.2 did not solve the issue...

-Tried PRIV command in rommon, but this one is no longer available.


What I now get when this AP boots:


Radio 3 : Vendor 0x7C08, Device 0x3A6

******** AUTOMATIC DDR CALIBRATION UPGRADE LOGIC *********

=== 1. Is original FCS bootloader in BS:?  If not, skip upgrade ===

    ---> original FCS bootloader was detected at bs:

=== 2. Has upgrade logic already ran once? (flag!=0xffffffff)

    ---> upgrade logic has already ran once, skip upgrade

Boot CMD: 'boot  flash:/ap3g1-k9w7-mx.152-4.JA1/ap3g1-k9w7-xx.152-4.JA1'


And:


ap#show soap | include DDR

*ORIGINAL* DDR Calibration values detected in EEPROM at 0x0


What I get on other working devices (serial are all close to each others):


Radio 3 : Vendor 0x6, Device 0xB22D

******** AUTOMATIC DDR CALIBRATION UPGRADE LOGIC *********

=== 1. Is original FCS bootloader in BS:?  If not, skip upgrade ===

    ---> original FCS bootloader not detected -- skip upgrade

Boot CMD: 'boot  flash:/ap3g1-k9w7-mx.152-4.JA1/ap3g1-k9w7-xx.152-4.JA1'


And:


ap#show soap | include DDR

*NEW* DDR Calibration values detected in EEPROM at 0x1E0


Very strange how production team coded this update, by setting flag at the very beginning of update instead after being updated, thus leading to this issue ...


I noticed in directory file 'ap3g1-boot-m_upg' - perhaps I should try to trigger it manually like times we had to upgrade bootloader of 1200 devices a long ago (command like 'copy tftp://.../c1200-boot-m... bs')


Obvously, I don't want to RMA this device, since it has no contact - and I don't plan to pay for a smartnet for an AP, especially for home use, BTW.


If someone has an idea/a set of commands, a hammer, even a soldering iron to sort that out, this is very welcome!


Thanks!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode