topic Re: 2802i flashing green + solution in Wireless

2802i flashing green + solution

patoberli — Mon, 05 Jul 2021 13:46:09 GMT

Hi All

I had a brand new 2802i which had an issue with booting up. It only showed the green LED flashing. After attaching a console and booting it again, I saw that it landed in ROM mode. I might have accidently unplugged it while it was booting up the first time, because I needed to replace the PoE adapter.

In any case, here in the Japanese Cisco forum I found the solution:

https://supportforums.cisco.com/ja/document/13217331

Thanks @kumatsum

u-boot >> boot

The boot hangs at the initialization process and doesn't proceed until one connects a console and presses enter. It will fail though, as it can't find the recovery image (nor could I locate it on the Cisco download site).

u-boot>> boot
Starting board initialization process. Proceed? [y/N]:
Aborting board initialization...
u-boot>> boot
Starting board initialization process. Proceed? [y/N]: y
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 172.22.177.16
Using egiga2 device
TFTP from server 0.0.0.0; our IP address is 172.22.177.16; sending through gateway 172.22.177.254
Filename 'board_init_barbados2k.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed

Showing the configured environment variables and showing the faulty bootcmd.

u-boot>> printenv
BOOT=part1
CASset=max
ENABLE_BREAK=1
FACTORY_RESET=0
MALLOC_len=5
MANUAL_BOOT=0
MEMORY_DEBUG=0
MPmode=SMP
autoload=yes
baudrate=9600
bootcmd=boardinit   <<<<< 
bootdelay=3
bootfile=board_init_barbados2k.img
cacheShare=no
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:xx:xx:xx
eth1mtu=1500
eth2addr=00:50:43:xx:xx:xx
eth2mtu=1500
ethact=egiga2
ethaddr=00:50:43:xx:xx:xx
ethmtu=1500
ethprime=egiga2
image_name=part.bin
initrd_high=0xffffffff
limit_dram_size=yes
loadaddr=0x02000000
loads_echo=0
mtddevname=fs
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:1m(oops),1m(reserved),-(fs)
nandEcc=nfcConfig=4bitecc
netretry=yes
partition=nand0,2
pcieTune=no
pexMode=RC
stderr=serial
stdin=serial
stdout=serial
yuk_ethaddr=00:00:00:xx:xx:xx

Environment size: 894/65532 bytes

Correcting the false bootcmd and saving and rebooting.

u-boot>> setenv bootcmd nandboot 
u-boot>> saveenv
u-boot>> boot

Here with console output.

u-boot>> setenv bootcmd nandboot
u-boot>> saveenv
Saving Environment to SPI Flash...
Erasing SPI flash....Writing to SPI flash.....done
u-boot>> boot
Creating 1 MTD partitions on "nand0":
0x000000200000-0x000010000000 : "mtd=2"
UBI: attaching mtd1 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: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=2"
UBI: MTD device size:            254 MiB
UBI: number of good PEBs:        2024
UBI: number of bad PEBs:         8
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     8
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 2024
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 198/104
UBIFS: mounted UBI device 0, volume 0, name "part1"
UBIFS: mounted read-only
UBIFS: file system size:   65646592 bytes (64108 KiB, 62 MiB, 517 LEBs)
UBIFS: journal size:       8888320 bytes (8680 KiB, 8 MiB, 70 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root:  0 bytes (0 KiB)
Loading file 'part1/part.bin' to addr 0x02000000 with size 18584351 (0x011b931f)...
Done
SF: Detected N25Q32A with page size 64 KiB, total 4 MiB
Checking image signing.
This could take up to 40 seconds. Please wait...
Image signing verification success, continue to run...
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Barbados Firmware Image
   Created:      2016-09-27  10:38:44 UTC
   Image Type:   ARM Linux Multi-File Image (uncompressed)
   Data Size:    18583343 Bytes = 17.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Contents:
      Image 0: 4033488 Bytes = 3.8 MiB
      Image 1: 14534391 Bytes = 13.9 MiB
      Image 2: 15447 Bytes = 15.1 KiB
   Verifying Checksum ... OK
## Loading init Ramdisk from multi component Legacy Image at 02000000 ...
## Flattened Device Tree from multi component Image at 02000000
   Booting using the fdt at 0x031b5318
   Loading Multi-File Image ... OK
OK
   Loading Device Tree to 00ff9000, end 00fffc56 ... OK

   Starting Device Tree update ('fdt_skip_update' = no)

Limit DDR size at 3GB due to power of 2 requirement of Address decoding
Updating device tree successful

Starting kernel ...

[01/01/1970 00:00:05.2900] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
[01/01/1970 00:00:05.4000] Memory: 1016064K/1048576K available (5584K kernel code, 362K rwdata, 2412K rodata, 343K init, 465K bss, 32512K reserved, 0K highmem)
[01/01/1970 00:00:05.5700] CPU1: Booted secondary processor
[01/01/1970 00:00:05.6300] buginf tty flushing thread started, ttyport=bf0e7000
[01/01/1970 00:00:05.7500] m25p80 spi1.0: found n25q032a, expected n25q032
[01/01/1970 00:00:05.9700] i2c i2c-0: of_i2c: modalias failure on /soc/internal-regs/i2c@11000/chan2
[01/01/1970 00:00:07.0800] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 20, need 32
[*01/01/1970 00:00:07.2318] buginf() enabled.

I had this exact problem on

brandorsens — Mon, 22 May 2017 20:57:01 GMT

I had this exact problem on three 3802i APs and this solution saved my bacon.

Thanks!

Re: 2802i flashing green + solution

JPLAURORA — Thu, 01 Feb 2018 13:43:04 GMT

As always the Cisco Support Communities is the first stop to check when having an issue. I had this exact problem on a Cisco 3802I AP and performed the steps from the U-Boot CLI and the AP rebooted with no further issues.

Thank You for posting the solution!!

James

Re: 2802i flashing green + solution

Saravanan Lakshmanan — Mon, 05 Feb 2018 18:56:14 GMT

its yet to get fixed.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvd54349

Bug Search

CSCvd54349

Help | Feedback

2800/3800 not booting up "Error: Unable to download image board_init_barbados3k.img"

CSCvd54349

Description

Symptom:
COS APs don't boot up when out of the box. Console outputs show u-boot loads but error message comes up as:

mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed
Using egiga2 device
TFTP from server x.x.x.x; our IP address is x.x.x.x
Filename 'board_init_barbados3k.img'.
Load address: 0x2000000
Loading: *
TFTP error: 'Access violation.' (4)
Starting again

mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed
Using egiga2 device
TFTP from server x.x.x.x; our IP address is x.x.x.x
Filename 'board_init_barbados3k.img'.
Load address: 0x2000000
Loading: *
TFTP error: 'Access violation.' (4)
Starting again

mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed

Abort
Error: Unable to download image board_init_barbados2k.img // For 2800 APs
Error: Unable to download image board_init_barbados3k.img // For 3800 APs

This occurs because the AP is trying to boot from a tftp server and is not falling back to booting from flash when not found. A command must be run to tell the AP to load its image from flash instead.

Conditions:
N/A

Workaround:
From u-boot, run the commands:

u-boot>> set bootcmd nandboot
u-boot>> saveenv
u-boot>> boot

Was the description about this Bug Helpful?

(0)

Details

Last Modified:

Dec 19,2017

Status:

Open

Severity:

3 Moderate

Product:

(1)

Cisco Aironet 3800 Series Access Points

Known Affected Releases:

(1)

all

Known Fixed Releases:

(0)

Download software for Cisco Aironet 3800 Series Access Points

Re: 2802i flashing green + solution

roger.t01 — Fri, 13 Apr 2018 06:52:20 GMT

I could configure bootcmd by above commands but on ever reload the ap stops at,

BootROM - 1.78
Booting from SPI flash, Secure mode
BootROM: RSA Public key verification PASSED
BootROM: CSK block signature verification PASSED
BootROM: Boot header signature verification PASSED
BootROM: Box ID verification PASSED
BootROM: JTAG is disabled

General initialization - Version: 1.0.0
Detected Device ID 6920
Master bootloder version 1.1e

Please choose one of the following boards:
1. 3K
2. 2K (new)
3. 2K (proto)
4. Milos
5. 2KH
6. 3KVE (v-sku)
7. 3KH/3KA
init>>

What can be done to skip this part

Re: 2802i flashing green + solution

patoberli — Fri, 13 Apr 2018 10:59:18 GMT

Try option 1 (no guarantee!) and see if it boots. But I guess your AP requires a re-flash through TAC.

Re: 2802i flashing green + solution

Lileight8 — Thu, 13 Dec 2018 21:42:55 GMT

I too have the same problem on a 3800 AP the above mention CLI after done allowed me to move further along in the boot process and had the AP attempting to download the needed software from WLC. However never progressed to a registered state in WLC. Any updates on resolve for this problem? Thanks

I am left with a " init>> " prompt and option to choose the following boards:

Please choose one of the following boards:
1. 3K
2. 2K (new)
3. 2K (proto)
4. Milos
5. 2KH
6. 3KVE (v-sku)
7. 3KH/3KA
init>>

after selecting option 1 and going through processes I was held up on the CLI of WAP asking for username and password?

my error message now is:

(write) Unable to open I2C device interface (/dev/act2) for ACT2 (file = -1)

(ACT2Boot) Hardware is NOT Cisco (c) authentic 😞

System will reboot in 10 seconds

WAP reboots and I am prompted once again to choose from the following boards.

Re: 2802i flashing green solution

patoberli — Thu, 13 Dec 2018 21:59:07 GMT

In this case you best RMA it. You have 10 years hardware warranty on it and I think that would include your error.
In my case the AP was working again after the I outlined in my first post.

Re: 2802i flashing green + solution

Cisco4Avanir — Wed, 03 Mar 2021 17:44:56 GMT

Hi Team,

I am having this problem in AP3802i. After I have changed the boot command bootcmd=nandboot, still having the boot image failure issues

u-boot>> printenv
BOOT=part2
CASset=max
ENABLE_BREAK=1
FACTORY_RESET=2
MALLOC_len=5
MANUAL_BOOT=0
MEMORY_DEBUG=0
MPmode=SMP
autoload=yes
baudrate=9600
bootargs=console=ttyS0,9600 activepart=part2 activeboot=0 bootver=0x106 boardid=0x20 nss_emac_map=0x3 wired0=0 phy0=aq nfcConfig=4bitecc mtdparts=armada-nand:1m(oops),1m(reserved),-(fs) ubi.mtd=fs wired1=1 phy1=mvl
bootcmd=nandboot
bootdelay=3
cacheShare=no
consoledev=ttyS0
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:5d:4e:18
eth1mtu=1500
eth2addr=00:50:43:5d:ab:18
eth2mtu=1500
ethact=egiga2
ethaddr=00:50:43:ab:4e:18
ethmtu=1500
ethprime=egiga2
filesize=607A00
image_name=part.bin
initrd_high=0xffffffff
limit_dram_size=yes
loadaddr=0x02000000
loads_echo=0
mtddevname=fs
mtddevnum=2
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:1m(oops),1m(reserved),-(fs)
nandEcc=nfcConfig=4bitecc
netretry=yes
nss_emac_map=0x3
partition=nand0,2
pcieTune=no
pexMode=RC
stderr=serial
stdin=serial
stdout=serial
wired0=0
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 1154/65532 bytes
u-boot>> boot
Unmounting UBIFS volume part2!
UBI: mtd1 is detached from ubi0
Creating 1 MTD partitions on "nand0":
0x000000200000-0x000010000000 : "mtd=2"
UBI: attaching mtd1 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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 254 MiB
UBI: number of good PEBs: 2024
UBI: number of bad PEBs: 8
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 8
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 2024
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 21/1
UBIFS: mounted UBI device 0, volume 1, name "part2"
UBIFS: mounted read-only
UBIFS: file system size: 65646592 bytes (64108 KiB, 62 MiB, 517 LEBs)
UBIFS: journal size: 8888320 bytes (8680 KiB, 8 MiB, 70 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 0 bytes (0 KiB)
Loading file 'part2/part.bin' to addr 0x02000000 with size 6322688 (0x00607a00)...
Done
Checking image signing.
This could take up to 40 seconds. Please wait...
Image signing verification failure, not allowed to run...
u-boot>>

Re: 2802i flashing green + solution

patoberli — Thu, 04 Mar 2021 07:59:59 GMT

Then you might have a broken flash or image. There are some image recovery procedures, but you're probably quicker making an RMA for the AP.

Re: 2802i flashing green + solution

Dan4171 — Tue, 20 Jul 2021 04:13:36 GMT

Patoberli,

would you mind share these image recovery procedures?

Dan

Re: 2802i flashing green + solution

patoberli — Tue, 20 Jul 2021 07:19:54 GMT

Hi Dan
Not sure what you need, they are described in my first post.
Maybe your AP is just broken? Don't forget, most models have 10 years of warranty.

2802i flashing green + solution

Dan4171 — Thu, 05 Aug 2021 16:11:11 GMT

patoberli

would you mind share these image recovery procedures?

Dante

Re: 2802i flashing green + solution

patoberli — Fri, 06 Aug 2021 07:20:29 GMT

Can you elaborate on your specific problem? What is the AP doing while booting it up?

Re: 2802i flashing green + solution

DivakaranV — Sat, 30 Sep 2023 16:14:56 GMT

Hi Patoperli can you share the image recovery procedure pls for 4800 ap

Re: 2802i flashing green + solution

DivakaranV — Sat, 30 Sep 2023 16:19:05 GMT

I wanted to reflash and format partition to reload the image. The reason is that I have 4800 in capwap mode and trying to migrate to mobility and it say same issue or file corrupted. I tried 8.10.185 and lower versions. I have 8.7.106 currently. I am thinking of downgrading the image from 8.7.106 to other version reflash and format partition and proceed.I tried many other images different version checked the checksum with md5sum and sha512.

Re: 2802i flashing green + solution

patoberli — Wed, 04 Oct 2023 19:54:15 GMT

Because of an expired certificate problem, you must use 8.10.185.0 or later. You could also adjust the date/time before the downgrade to a date around November 2022.

Anyway, unless you have exactly this error, I suggest you open a fresh thread for the problem.

Re: 2802i flashing green + solution

AJarvy — Fri, 10 Jan 2025 16:27:20 GMT

This was clutch. I was hitting the same "board selection" prompt. My bootcmd was good, but I noticed my bootfile was missing. Added the bootfile for my board and it fixed the problem.