<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4931965#M261140</link>
    <description>&lt;P&gt;I had luck after downloading and installing LWAP version 15.3.3-JPN1 then upgrading to ME 8.10.on 3800 &amp;amp; 2800 APs.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good Luck ..&lt;/P&gt;</description>
    <pubDate>Sat, 30 Sep 2023 16:32:29 GMT</pubDate>
    <dc:creator>razelle</dc:creator>
    <dc:date>2023-09-30T16:32:29Z</dc:date>
    <item>
      <title>Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED)</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4447493#M232124</link>
      <description>&lt;P&gt;Ok guys so i noticed on all the wave 2+ APs cisco are now using the U-boot bootloader and documentation for it is little to none.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have a good amount of experience recovering and restoring APs. When i deploy APs for clients i prefer to format the flash and reinstall the newest IOS from scratch via TFTP or Xmodem send file command.&lt;BR /&gt;&lt;BR /&gt;Ive been searching through some of the U-Boot commands and see it is possible to set environment variables just like the old SET command and i also see tftp boot options etc....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;So it seems to be it is very possible to reflash the new APs using UBOOT and it looks like this bootloader is even more capable than the old one.&amp;nbsp; This is a pretty important procedure for me to learn and i will be on this issue till i get it solved hopefully. Ive seen a few post and others complaining about the new bootloader commands. Some of them getting further than others.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;I have found a very helpful Youtube video on the bootloader from the Linux foundation but other than that i cant seem to find much.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Going to be going through this video and playing with commands for a bit.&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Currently looking for how to format the internal flash via U-BOOT if anyone knows the process please let me know it will save me alot of time.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Anyway i know some of you have gotten further than others on this.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;I will be actively updating this topic with advances i found in restoring bricked APs with UBOOT&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;I figured out some of the TFTP commands but iam looking still looking for how to format the flash.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;I will also be making a tutorial on this process as soon as i have it figured out.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&lt;A href="https://www.youtube.com/watch?v=INWghYZH3hI&amp;amp;t=6s" target="_blank" rel="noopener"&gt;https://www.youtube.com/watch?v=INWghYZH3hI&amp;amp;t=6s&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Available commands in&amp;nbsp;air-cap3802i-b-k9 that i have obtained (believed to be TAC unlocked) 9/11/2021&lt;/P&gt;&lt;P&gt;SatR - Sample At Reset sub-system&lt;BR /&gt;active_units- print active units on board&lt;BR /&gt;askenv - get environment variables from stdin&lt;BR /&gt;base - print or set address offset&lt;BR /&gt;bdinfo - print Board Info structure&lt;BR /&gt;boardinit- Downlod and execute board initialization script&lt;BR /&gt;boot - boot default, i.e., run 'bootcmd'&lt;BR /&gt;bootd - boot default, i.e., run 'bootcmd'&lt;BR /&gt;bootelf - Boot from an ELF image in memory&lt;BR /&gt;bootm - boot application image from memory&lt;BR /&gt;bootp - boot image via network using BOOTP/TFTP protocol&lt;BR /&gt;bootvx - Boot vxWorks from an ELF image&lt;BR /&gt;bootz - boot Linux zImage image from memory&lt;BR /&gt;bubt - bubt - Burn an image on the Boot flash device.&lt;/P&gt;&lt;P&gt;chpart - change active partition&lt;BR /&gt;clear_board_env- Clears board env&lt;BR /&gt;cmp - memory compare&lt;BR /&gt;coninfo - print console devices and information&lt;BR /&gt;cp - memory copy&lt;BR /&gt;crc32 - checksum calculation&lt;BR /&gt;date - get/set/reset date &amp;amp; time&lt;BR /&gt;ddrPhyRead- ddrPhyRead - Read DDR PHY register&lt;/P&gt;&lt;P&gt;ddrPhyWrite- ddrPhyWrite - Write DDR PHY register&lt;/P&gt;&lt;P&gt;dhcp - boot image via network using DHCP/TFTP protocol&lt;BR /&gt;dma - dma - Perform DMA using the XOR engine&lt;/P&gt;&lt;P&gt;dump_board_env- Dump board env&lt;BR /&gt;dump_emserial- Dump EM unique serial number&lt;BR /&gt;echo - echo args to console&lt;BR /&gt;editenv - edit environment variable&lt;BR /&gt;efuse - eFuse manipulation subsystem for secure boot mode&lt;BR /&gt;env - environment handling commands&lt;BR /&gt;exit - exit script&lt;BR /&gt;ext2load- load binary file from a Ext2 filesystem&lt;BR /&gt;ext2ls - list files in a directory (default /)&lt;BR /&gt;ext4load- load binary file from a Ext4 filesystem&lt;BR /&gt;ext4ls - list files in a directory (default /)&lt;BR /&gt;ext4write- create a file in the root directory&lt;BR /&gt;false - do nothing, unsuccessfully&lt;BR /&gt;fatinfo - print information about filesystem&lt;BR /&gt;fatload - load binary file from a dos filesystem&lt;BR /&gt;fatls - list files in a directory (default /)&lt;BR /&gt;fdt - flattened device tree utility commands&lt;BR /&gt;fipsalgval- run algorithm validation on test vector bibnar in memory, default:20 00000 (0x02000000)&lt;BR /&gt;fsinfo - print information about filesystems&lt;BR /&gt;fsload - load binary file from a filesystem image&lt;BR /&gt;go - start application at address 'addr'&lt;BR /&gt;help - print command description/usage&lt;BR /&gt;i2c - I2C sub-system&lt;BR /&gt;iminfo - print header information for application image&lt;BR /&gt;imxtract- extract a part of a multi-image&lt;BR /&gt;init_aquantia_phy-&lt;/P&gt;&lt;P&gt;init_aquantia_phy -- DEFAULT AQ_FW_LOADADDR=0x4000000&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ir - ir - reading and changing MV internal register values.&lt;/P&gt;&lt;P&gt;itest - return true/false on integer compare&lt;BR /&gt;ledstate- Set Led State&lt;BR /&gt;loadb - load binary file over serial line (kermit mode)&lt;BR /&gt;loads - load S-Record file over serial line&lt;BR /&gt;loadx - load binary file over serial line (xmodem mode)&lt;BR /&gt;loady - load binary file over serial line (ymodem mode)&lt;BR /&gt;loop - infinite loop on address range&lt;BR /&gt;ls - list files in a directory (default /)&lt;BR /&gt;map - map - Display address decode windows&lt;/P&gt;&lt;P&gt;md - memory display&lt;BR /&gt;me - me - PCIe master enable&lt;/P&gt;&lt;P&gt;mm - memory modify (auto-incrementing address)&lt;BR /&gt;mp - mp - map PCIe BAR&lt;/P&gt;&lt;P&gt;mtdparts- define flash/nand partitions&lt;BR /&gt;mtest - simple RAM read/write test&lt;BR /&gt;mvEthPortCounters- Port counter&lt;/P&gt;&lt;P&gt;mvEthPortMcastShow- Port multicast counter&lt;/P&gt;&lt;P&gt;mvEthPortRegs- Neta register values&lt;/P&gt;&lt;P&gt;mvEthPortRmonCounters- Port RMON counter&lt;/P&gt;&lt;P&gt;mvEthPortUcastShow- Port unicast counter&lt;/P&gt;&lt;P&gt;mvEthRegs- Neta register values&lt;/P&gt;&lt;P&gt;mvNetComplexNssSelect- Neta register values&lt;/P&gt;&lt;P&gt;mvNetaGmacRegs- Neta register values&lt;/P&gt;&lt;P&gt;mvNetaPortRegs- Neta register values&lt;/P&gt;&lt;P&gt;mvNetaPortStatus- Neta register values&lt;/P&gt;&lt;P&gt;mvsource- mvsource - Burn a script image on flash device.&lt;/P&gt;&lt;P&gt;mw - memory write (fill)&lt;BR /&gt;nand - NAND sub-system&lt;BR /&gt;nandboot- boot Linux from NAND partition&lt;BR /&gt;nboot - boot from NAND device&lt;BR /&gt;neta_dump- Neta register values&lt;/P&gt;&lt;P&gt;netboot - boot Linux from network using TFTP/bootp&lt;BR /&gt;nfs - boot image via network using NFS protocol&lt;BR /&gt;nm - memory modify (constant address)&lt;BR /&gt;pci - list and access PCI Configuration Space&lt;BR /&gt;pciePhyRead- phyRead - Read PCI-E Phy register&lt;/P&gt;&lt;P&gt;pciePhyWrite- pciePhyWrite - Write PCI-E Phy register&lt;/P&gt;&lt;P&gt;phyRead - phyRead - Read Phy register&lt;/P&gt;&lt;P&gt;phyWrite- phyWrite - Write Phy register&lt;/P&gt;&lt;P&gt;phy_fw_down_to_ram- phy_fw_down - Downloads x3220/3310 Ethernet transceiver PHY firmware to ram. Use .hdr file.&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;phy_type- phy_type - Return PHY type at port index&lt;/P&gt;&lt;P&gt;ping - send ICMP ECHO_REQUEST to network host&lt;BR /&gt;printenv- print environment variables&lt;BR /&gt;prog_emblacklist- Program EM blacklist&lt;BR /&gt;prog_emcookie- Download and program EM cookie&lt;BR /&gt;prog_emeeprom- Program EM EEPROM with raw binary data&lt;BR /&gt;prog_emignore- Program EM ignore&lt;BR /&gt;prog_emserial- Program EM unique serial number&lt;BR /&gt;prog_emwhitelist- Program EM whitelist&lt;BR /&gt;prog_flags- Program board env flags&lt;BR /&gt;prog_phyfw- Download and program PHY firmware&lt;BR /&gt;progpid - Program PID cookie&lt;BR /&gt;pxe - commands to get and boot from pxe files&lt;BR /&gt;rcvr - rcvr - Start recovery process (with TFTP server)&lt;/P&gt;&lt;P&gt;reset - Perform RESET of the CPU&lt;BR /&gt;resetenv- resetenv - Erase environment sector to reset all variables to default.&lt;/P&gt;&lt;P&gt;run - run commands in an environment variable&lt;BR /&gt;saveenv - save environment variables to persistent storage&lt;BR /&gt;se - se - PCIe Slave enable&lt;/P&gt;&lt;P&gt;setenv - set environment variables&lt;BR /&gt;sf - SPI flash sub-system&lt;BR /&gt;sg - sg - scanning the PHYs status&lt;/P&gt;&lt;P&gt;showvar - print local hushshell variables&lt;BR /&gt;sleep - delay execution for some time&lt;BR /&gt;source - run script from memory&lt;BR /&gt;sp - scan and detect all devices on PCI-e interface&lt;BR /&gt;sspi - SPI utility command&lt;BR /&gt;switchCountersRead- switchCntPrint - Read switch port counters.&lt;/P&gt;&lt;P&gt;switchPhyRegRead- - Read switch register&lt;/P&gt;&lt;P&gt;switchPhyRegWrite- - Write switch register&lt;/P&gt;&lt;P&gt;switchRegRead- switchRegRead - Read switch register&lt;/P&gt;&lt;P&gt;switchRegWrite- switchRegWrite - Write switch register&lt;/P&gt;&lt;P&gt;sysboot - command to get and boot from syslinux files&lt;BR /&gt;temp - temp - Display the device temperature.&lt;/P&gt;&lt;P&gt;tempCmd0- tempCmd - This command allocated for monitor extinction&lt;/P&gt;&lt;P&gt;tempCmd1- tempCmd - This command allocated for monitor extinction&lt;/P&gt;&lt;P&gt;tempCmd2- tempCmd - This command allocated for monitor extinction&lt;/P&gt;&lt;P&gt;tempCmd3- tempCmd - This command allocated for monitor extinction&lt;/P&gt;&lt;P&gt;test - minimal test like /bin/sh&lt;BR /&gt;tftpboot- boot image via network using TFTP protocol&lt;BR /&gt;training- training - prints the results of the DDR3 Training.&lt;/P&gt;&lt;P&gt;trainingStability- training - prints the results of the DDR3 Training.&lt;/P&gt;&lt;P&gt;true - do nothing, successfully&lt;BR /&gt;ts_report- ts_report - report touch screen coordinate&lt;/P&gt;&lt;P&gt;ts_test - ts_test - test touch screen&lt;/P&gt;&lt;P&gt;ubi - ubi commands&lt;BR /&gt;ubifsload- load file from an UBIFS filesystem&lt;BR /&gt;ubifsls - list files in a directory&lt;BR /&gt;ubifsmount- mount UBIFS volume&lt;BR /&gt;ubifsumount- unmount UBIFS volume&lt;BR /&gt;verify_bl- Cisco Bootloader signature verify&lt;BR /&gt;verify_lx- Cisco Image signature verify&lt;BR /&gt;version - print monitor, compiler and linker version&lt;BR /&gt;whoAmI - - reading CPU ID&lt;/P&gt;&lt;P&gt;xsmiPhyRead- xsmiPhyRead - Read Phy register through XSMI interface&lt;/P&gt;&lt;P&gt;xsmiPhyWrite- xsmiPhyWrite - Write Phy register through XSMI interface&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Updated 9/11/2021&lt;/P&gt;&lt;P class="lia-align-left"&gt;Setting environment variables to configure IP address prior to TFTP flash&lt;/P&gt;&lt;P class="lia-align-left"&gt;setenv ipaddr 77.77.77.30&amp;nbsp; &amp;nbsp;(Sets IP of AP)&lt;/P&gt;&lt;P class="lia-align-left"&gt;setenv serverip 77.77.77.3&amp;nbsp; (Sets IP and netmask of server for file transfers)&lt;/P&gt;&lt;P class="lia-align-left"&gt;setenv bootfile&amp;nbsp;AIR-AP1850-K9-8-10-162-0.tar (sets the filename for the tftp boot command)&lt;/P&gt;&lt;P class="lia-align-left"&gt;tftpboot (starts loading specified file from a running tftp server)&lt;/P&gt;&lt;P class="lia-align-left"&gt;rcvr (Starts recovery process with tftp server, requires variables to be set)&lt;BR /&gt;setenv rcvr_image (Needed for rcvr to work properly)&lt;/P&gt;&lt;P class="lia-align-left"&gt;set loadaddr (I believe 0x2000000 is the value that is supposed to be used when using rcvr, need confirmation)&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Experience with Rcvr command&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Variables set&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;setenv loadaddr&amp;nbsp;&amp;nbsp;0x2000000&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;setenv rcvr_image&amp;nbsp;AIR-AP3800-K9-ME-8-10-162-0.tar&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;setenv serverip 77.77.77.3&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;setenv ipaddr 77.77.77.209&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;So after setting the 4 variables, rcvr seems to properly executing the command.&amp;nbsp; But it ends in signature verification..... any ideas?&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Sep 2021 04:43:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4447493#M232124</guid>
      <dc:creator>FIX A PC</dc:creator>
      <dc:date>2021-09-12T04:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together.</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4447499#M232125</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/754922"&gt;@FIX A PC&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;&lt;SPAN&gt;I have a good amount of experience recovering and restoring APs. When i deploy APs for clients i prefer to format the flash and reinstall the newest IOS from scratch via TFTP or Xmodem send file command.&lt;/SPAN&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;APs with classic IOS were very easy to re-flash or re-load the IOS.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco has made it very difficult to do the same with APs running Cheetah OS.&amp;nbsp; A lot of the u-boot functions require TAC to generate a challenge token and when one is the field, it can take some time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My rule-of-thumb for Cheetah OS APs with corrupt OS is:&amp;nbsp; Contact Cisco TAC and RMA.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Aug 2021 04:56:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4447499#M232125</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2021-08-11T04:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4464103#M233233</link>
      <description>&lt;P&gt;Ok guys i have obtained about 4 air-cap3802i-b-k9 APs, 2 of them being TAC unlocked i believe.......&lt;/P&gt;&lt;P&gt;So i have been working with the rcvr command and have made some progress.....&amp;nbsp;&lt;/P&gt;&lt;P&gt;when attempting to use loadaddr 0x3f9f8bb0 rcvr seems to stop during 15% of the file transfer and freeze.&lt;/P&gt;&lt;P&gt;when attempting to use the load addr 0x2000000 rcvr tftp seems to accept the file just file, it than starts booting but than eventually fails on signature verification.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know iam getting close here but iam not sure if iam using the correct load addr and or if the command is compatible with a tar file containing a full mobility image, i have also tried a light weight image as well.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Sep 2021 04:48:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4464103#M233233</guid>
      <dc:creator>FIX A PC</dc:creator>
      <dc:date>2021-09-12T04:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4598768#M241184</link>
      <description>&lt;P&gt;Did you ever solve this I am at the same point with a 3802e&lt;/P&gt;</description>
      <pubDate>Sun, 24 Apr 2022 21:56:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4598768#M241184</guid>
      <dc:creator>razelle</dc:creator>
      <dc:date>2022-04-24T21:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4599081#M241193</link>
      <description>&lt;P&gt;RMA it, you have 10 years of warranty typically on those models.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 09:29:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4599081#M241193</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2022-04-25T09:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4754358#M250398</link>
      <description>&lt;P&gt;I hope you could resolve this issue.&lt;BR /&gt;&lt;BR /&gt;Im trying to resolve too, I will let you know inmediatly.&lt;BR /&gt;&lt;BR /&gt;I see you dedication i this problem, is awsome XD.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 15:37:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4754358#M250398</guid>
      <dc:creator>frankpicaport</dc:creator>
      <dc:date>2023-01-13T15:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4931951#M261135</link>
      <description>&lt;P&gt;Hi did we all resolved this section. I have 4800 series in capwap 8.7.106 which I wanted to move &amp;nbsp;away to mobility based. I downloaded the software but when I try to ap-type mobility or archive commend it always says the file corrupted. I tried all versions. In the beginning it says some same issue and I think we need to erase the flash format and load capwap other image like 8.3 or 8.5 and then convert to mobility image. I need some help how to delete existing portion reflash and start fresh from uboot. Can some one help&lt;/P&gt;</description>
      <pubDate>Sat, 30 Sep 2023 14:57:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4931951#M261135</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-09-30T14:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4931965#M261140</link>
      <description>&lt;P&gt;I had luck after downloading and installing LWAP version 15.3.3-JPN1 then upgrading to ME 8.10.on 3800 &amp;amp; 2800 APs.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good Luck ..&lt;/P&gt;</description>
      <pubDate>Sat, 30 Sep 2023 16:32:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4931965#M261140</guid>
      <dc:creator>razelle</dc:creator>
      <dc:date>2023-09-30T16:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4932824#M261212</link>
      <description>&lt;P&gt;thanks for your time to write on this. i tried different versions and for everything it says, the file is not authorized to run. when i check the date of the access in u-boot prompt, uboot&amp;gt;&amp;gt;date (enter)&amp;lt;-|&lt;/P&gt;&lt;P&gt;I get Date: 2036-09-18 (Thursday) Time 18:42:05&lt;/P&gt;&lt;P&gt;when i try to change the date with date comment and syntax is date [MMDDhhmm][[CC]YY][.ss] and I am in central and to change to current date and time i execute date 100211432023.21 but what i get again is&amp;nbsp;&amp;nbsp;&amp;nbsp;2036-09-18 (Thursday) Time 18:42:05&lt;/P&gt;&lt;P&gt;i am not able to chnage it. if we understand the images are signed and created with date validy and will that be an issue here and i am not able to change the date of the ap in U-Boot&amp;gt;&amp;gt; prompt. is there any thoughts and advise please? also i do not have contract with CISCO and can you share me the 15.3.3-JPN1 and my id is &lt;A href="mailto:diva.varadam@gmail.com" target="_blank"&gt;diva.varadam@gmail.com&lt;/A&gt;. thanks and appreicate your help.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2023 16:46:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4932824#M261212</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-10-02T16:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4932861#M261221</link>
      <description>&lt;P&gt;hi - are you able to fix your issue? thanks and provide some background if you have fixed it? i have the same issue.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Oct 2023 17:31:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4932861#M261221</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-10-02T17:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4940697#M261716</link>
      <description>&lt;P&gt;hi Razelle - can you please share me 15.3.3-JPN1 if possible to my email id? i do not have the support and unable to download. thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 15 Oct 2023 23:27:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4940697#M261716</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-10-15T23:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941195#M261751</link>
      <description>&lt;P&gt;Hi, I can't do that you must have a valid service contract with Cisco. Sorry&lt;/P&gt;</description>
      <pubDate>Mon, 16 Oct 2023 15:42:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941195#M261751</guid>
      <dc:creator>razelle</dc:creator>
      <dc:date>2023-10-16T15:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941471#M261758</link>
      <description>&lt;P&gt;Finally I am able to figure out the issue and resolved it. my AP was running 8.7.106 CAPWAP and when I try to upgrade to 8.10.XXX any version, it was throwing disk space error, insufficient space in part2 and unable to extract the tar file and the migration fails. So finally what I did upgraded the device to ap3g3 15.3.3.jpj3a and then to ME 8.10.185 and all went fine. i am able to configure the controller and the ap now and everything works fine. But in this process I bricked one the of 4800 while I upgrade the firmware and that AP is completely dead and no display however in POE switch port, i am able to see that the device is getting the power from the switch and some oneboard LED's are blinking while i connect the power. I am sure I screwed the UBOOT loader and is there any way that i can restore it? i tried all the reset factory options nothing worked. is there any hardware shop method to recover the flash and reflash it? the access point is 4800.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Oct 2023 01:28:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941471#M261758</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-10-17T01:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941472#M261759</link>
      <description>&lt;P&gt;thanks for the response and i am able resolve it now. thanks, how much normally that would cost to get a smart net support for individual account for only wireless devices. my existing authorization from my corporate account does not have that specific privilege for that models..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Oct 2023 01:30:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4941472#M261759</guid>
      <dc:creator>DivakaranV</dc:creator>
      <dc:date>2023-10-17T01:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4947737#M262094</link>
      <description>&lt;P&gt;How did you manage to upgrade when the device does not boot?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Oct 2023 12:37:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/4947737#M262094</guid>
      <dc:creator>matemat</dc:creator>
      <dc:date>2023-10-25T12:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5035397#M267772</link>
      <description>&lt;P&gt;Those those who were still having this issue.&amp;nbsp; I was able to resolve this.&amp;nbsp; Press ESC to get into uboot.&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;printenv BOOT &lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt; Check the current configuration&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;setenv BOOT part2 &lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;part1 part2=&lt;/SPAN&gt;&lt;SPAN class=""&gt;""&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt; Change to another partition&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;saveenv &lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt; Save configuration&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;boot &lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt; Reload the AP&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;lt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;/part1&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Once it booted back up I installed ME AIR-AP3800-K9-ME-8-5-161-0.tar and then upgraded to the lastest version using the GUI with no issues.&amp;nbsp; Hope this helps.&amp;nbsp; &lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 06 Mar 2024 21:51:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5035397#M267772</guid>
      <dc:creator>TL2K</dc:creator>
      <dc:date>2024-03-06T21:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5046669#M269021</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;
&lt;P&gt;i'm having the same issue; my ap is giving me:&lt;/P&gt;
&lt;P&gt;u-boot&amp;gt;&amp;gt; date 010100002024.00&lt;BR /&gt;Date: 2010-01-11 (Monday) Time: 16:01:15&lt;/P&gt;
&lt;P&gt;how did you set the correct time?&lt;/P&gt;
&lt;P&gt;Many Thanks&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;f&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 13:33:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5046669#M269021</guid>
      <dc:creator>FatjonCelaj</dc:creator>
      <dc:date>2024-03-21T13:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5078970#M270731</link>
      <description>&lt;P&gt;If you corrupt the flash in these things by messing with uboot, is there NO way to recover ?.&lt;/P&gt;&lt;P&gt;I unpacked the tar file into our tftpserver.&lt;/P&gt;&lt;P&gt;netboot most files results in&lt;/P&gt;&lt;P&gt;Image signing verification failure(-2), not allowed to run...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can get more signs of life with&lt;/P&gt;&lt;P&gt;netboot part.bin&lt;/P&gt;&lt;P&gt;which does start the Linux kernel, but then it promptly crashes when it can't find the inintrd.&lt;/P&gt;&lt;P&gt;[*01/01/1970 00:00:03.9214] UBIFS error (pid 1): ubifs_mount: cannot open "/dev/ubivol/storage", error -22&lt;BR /&gt;[*01/01/1970 00:00:03.9214] mount_ubifs: mounting ubifs storage: Invalid argument&lt;BR /&gt;[*01/01/1970 00:00:03.9216] bootsh mini ramfs not found, file =(null)&lt;BR /&gt;[01/01/1970 00:00:04.2000] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If this was a standard EFI loader with a standard Linux kernel, I could pass it a tftp command to fetch the initrd (Which I assume is the ramfs_data_cisco.cpio.lzma file in this case).&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 04:35:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5078970#M270731</guid>
      <dc:creator>matthewgeier</dc:creator>
      <dc:date>2024-04-26T04:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5079034#M270735</link>
      <description>&lt;P&gt;Call TAC and organize for an RMA.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2024 06:29:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5079034#M270735</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-04-26T06:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: Lets figure out the U-BOOT flash procedure together. (TAC UNLOCKED</title>
      <link>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5202140#M276142</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;do you found any soloution for your problem?&amp;nbsp;I'm stuck in the same place.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I don't have a Cisco contract, so unfortunately an RMA is not a possible option for me.&lt;/P&gt;&lt;P&gt;Are there still options or do I have a few new paperweights?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 06:40:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/lets-figure-out-the-u-boot-flash-procedure-together-tac-unlocked/m-p/5202140#M276142</guid>
      <dc:creator>ConsoleJOE5783</dc:creator>
      <dc:date>2024-10-02T06:40:11Z</dc:date>
    </item>
  </channel>
</rss>

