init>> prompt on 3802i Access Point

[dilshan2563]

Hi Everyone,

please help me to set the default program boards. there is no option to set on cisco ap3802i.

u-boot>> dump_board_env
Board env is unconfigured

[marce1000]

        - (Changed reply) ; review this thread for hints : https://community.cisco.com/t5/wireless/init-gt-gt-prompt-on-2802i-access-point/td-p/4104855

 M.

[dilshan2563]

thank you for your feedback.

i have an issue with boot process. while booting  its opening init and asking to select the board 

init>>

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/4K
8. Duplo

if I select ap will boot and keep cycling. would like to know how to set board and new image to boot.

[dilshan2563]

Hi 

i have checked these steps but cannot see the progid to set. now I'm stuck on to set program id and. boot the image via tftp.

u-boot>>
? - alias for 'help'
boardinit- Downlod and execute board initialization script
boot - boot default, i.e., run 'bootcmd'
bubt - bubt - Burn an image on the Boot flash device.

clear_board_env- Clears board env
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
dump_board_env- Dump board env
dump_emserial- Dump EM unique serial number
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
exit - exit script
false - do nothing, unsuccessfully
fdt - flattened device tree utility commands
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
ir - ir - reading and changing MV internal register values.

itest - return true/false on integer compare
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
nand - NAND sub-system
nandboot- boot Linux from NAND partition
netboot - boot Linux from network using TFTP/bootp
pci - list and access PCI Configuration Space
pciePhyRead- phyRead - Read PCI-E Phy register

pciePhyWrite- pciePhyWrite - Write PCI-E Phy register

phyRead - phyRead - Read Phy register

phyWrite- phyWrite - Write Phy register

phy_fw_down_to_ram- phy_fw_down - Downloads x3220/3310 Ethernet transceiver PHY firmware to ram. Use .hdr file.

phy_fw_down_to_spi- phy_fw_down - Downloads x3220/3310 Ethernet transceiver PHY firmware to spi. Use .hdr as app and .bin file as slave

phy_type- phy_type - Return PHY type at port index

ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
prog_emblacklist- Program EM blacklist
prog_emcookie- Download and program EM cookie
prog_emeeprom- Program EM EEPROM with raw binary data
prog_emignore- Program EM ignore
prog_emserial- Program EM unique serial number
prog_emwhitelist- Program EM whitelist
prog_flags- Program board env flags
prog_phyfw- Download and program PHY firmware
rcvr - rcvr - Start recovery process (with TFTP server)

reset - Perform RESET of the CPU
resetenv- resetenv - Erase environment sector to reset all variables to default.

run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
temp - temp - Display the device temperature.

test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
verify_bl- Cisco Bootloader signature verify
verify_lx- Cisco Image signature verify
version - print monitor, compiler and linker version
whoAmI - - reading CPU ID

(u-boot)> ubi part fs 
(u-boot)> ubi remove part1  (or part2 if corrupted image is in part2) 
(u-boot)> ubi create part1  (or part2 if corrupted image is in part2) 
(u-boot)> boot

I followed the below steps as well  

[Rich R]

Open a TAC case and RMA the AP.

[dilshan2563]

Hello 

RMA is not support for this device

[Rich R]

https://www.cisco.com/c/en/us/products/collateral/wireless/aironet-3800-series-access-points/datasheet-c78-741682.html#Warrantyinformation

Warranty information

The Cisco Aironet 3800 Series Access Points come with a limited lifetime warranty that provides full warranty coverage of the hardware for as long as the original end user continues to own or use the product. The warranty includes 10-day advance hardware replacement and ensures that software media are defect-free for 90 days. For more details, visit https://www.cisco.com/go/warranty.

[ripclap]

I ran into this exact problem on my 2802i and solved it by loading an earlier bootloader image. For the 3802i. For the 3802i, I believe the Board ID is 3K. Below are the steps I followed:

1. Download the legacy firmware
   Grab an older Cisco firmware bundle—for example, for a 2802i I used ap3g3-k9w8-tar.153-3.JC15.tar.

2. Extract the U-Boot binary

   • Unpack the .tar file.

   • Open btdlr.img (7-Zip works well) and extract the U-Boot file:
     named something like u-boot-barbados3k-abraxas-signed_*_REL.bin.

   • Rename it to u-boot.bin.

3. Configure your TFTP settings in U-Boot

   u-boot> setenv serverip 10.80.21.253
   u-boot> setenv netmask 255.255.254.0
   u-boot> setenv ipaddr 10.80.21.100

4. Flash the older U-Boot

   u-boot> bubt
   Using default filename "u-boot.bin" TFTP from server 10.80.21.253; our IP address is 10.80.21.100
   Loading: [##########] 7.4 MiB/s Bytes transferred = 1023524 (0xF9E24)
   Override Env parameters to default? [y/N] y
   Erasing 0x100000 - 0x110000: [Done]
   Erasing 0x0 - 0x100000: [Done]
   Writing image to flash: [Done]

5. Reboot into the legacy U-Boot
   

   u-boot> reset

6. Use progpid to set the correct Board-ID. (2k for 2802i and 3k for 3802i)

   u-boot> help progpid
   progpid - Program PID cookie
   
   Usage: progpid 3k | 2k | 2kp1 | milos | 2kh
   u-boot> progpid 2k
   u-boot> reset

After reboot, you’ll no longer be prompted at boot to select the Board ID—and the AP will correctly identify itself.