Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Paul_P
New Contributor

FortiAP U421EV - no boot - bad CRC - need recovery

Hi, I think I have done something wrong but I'm not sure what was the fault. I have try to authorize a fortiap u421ev on a Fortigate 60D with 6.05 OS, and after I click on the authorize button the FGT tell me connecting and after that disconnected. The problem is that the FAP unit change the led color from blinking green in permanent white, and after this was happens the wan;t boot anymore, no IP in the network, nothing. I connected the console and he is booting in a strange mode. I did not found any specs about recovery. Please help with any idea. This is what is he doing when is booting after "reset" command.   u-boot> reset resetting ... U-Boot 2012.10.esdk.7 (May 25 2016 - 23:26:43 - root@fap-bcm-dev.fortinet.com) DEV ID = 0xcf1e PCIE CFG DEV ID = 0x8025 OTP offset(0x8): 0x78f01c01 OTP offset(0x9): 0xfe200818 OTP offset(0xa): 0xc01b0 OTP offset(0xb): 0x0 OTP offset(0xc): 0x4a00000 OTP offset(0xd): 0xffede230 OTP offset(0xe): 0x1035d17f OTP offset(0xf): 0x3406 NSP25 32bit DDR SKU ID = 0x0 DDR type: DDR3 MEMC 0 DDR speed = 800MHz ddr_init2: Calling soc_ddr40_set_shmoo_dram_config ddr_init2: Calling soc_ddr40_phy_calibrate C01. Check Power Up Reset_Bar C02. Config and Release PLL from reset C03. Poll PLL Lock C04. Calibrate ZQ (ddr40_phy_calib_zq) C05. DDR PHY VTT On (Virtual VTT setup) DISABLE all Virtual VTT C06. DDR40_PHY_DDR3_MISC C07. VDL Calibration C07.1 C07.2 C07.4 C07.4.1 C07.4.4 VDL calibration result: 0x30000003 (cal_steps = 0) C07.4.5 C07.4.6 C07.5 C08. DDR40_PHY_DDR3_MISC : Start DDR40_PHY_RDLY_ODT.... C09. Start ddr40_phy_autoidle_on (MEM_SYS_PARAM_PHY_AUTO_IDLE) .... C10. Wait for Phy Ready Programming controller register ddr_init2: Calling soc_ddr40_shmoo_ctl Validate Shmoo parameters stored in flash ..... OK Press Ctrl-C to run Shmoo ..... skipped Restoring Shmoo parameters from flash ..... done Running simple memory test ..... OK DDR Tune Completed DRAM: 255 MiB WARNING: Caches not enabled NAND: iProc NAND chip could not be initialized 0 MiB MMC: iproc_mmc: 0 SF: Detected (ST)MX66l51235F with page size 64 KiB, total 64 MiB *** Warning - bad CRC, using default environment soc_pcie_hw_init : port->reg_base = 0x18012000 , its value = 0x1 PCIe port in RC mode ==>PCIE: LINKSTA reg 0xbe val 0x9012 ************** port 0 is active!! ************** membase 0x8000000 memlimit 0x10000000 00:00.00 - 14e4:43c4 - Network controller pci_iproc_init_board : hose->last_busno = 0x0 Extended Config i=0 <0> 0x14e4 0x8025 0x0146 0x0010 0x0011 0x0200 0x0000 0x0001 i=8 <8> 0x0000 0x0000 0x0000 0x0000 0x0100 0x0004 0x0000 0x0000 i=16 <10> 0x0800 0x1000 0x0001 0x0001 0x0000 0x0000 0x0000 0x0000 i=24 <18> 0x0000 0x0000 0x0048 0x0000 0x0000 0x0000 0x01a9 0x0000 i=32 <20> 0x0000 0x0000 0x0000 0x0000 0xac01 0xc803 0x2008 0x0000 i=40 <28> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 i=48 <30> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 i=56 <38> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 i=64 <40> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 i=72 <48> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 i=80 <50> 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0010 0x0042 i=88 <58> 0x8000 0x0000 0x2c10 0x0010 0x5c12 0x0065 0x0000 0x9012 i=96 <60> 0x0000 0x0000 0x0000 0x0040 0x0000 0x0001 0x0000 0x0000 i=104 <68> 0x001f 0x0008 0x0000 0x0000 0x0000 0x0000 0x0002 0x0000 i=112 <70> 0x0000 0x0000 0x0000 0x0000 0x0000 0x000Invalid Checksum - Header CRC 5aad1889 Calculated CRC 6ed01986, trx len 0xad8000, buf len 0xf00000 SF: Detected (ST)MX66l51235F with page size 64 KiB, total 64 MiB Checking TRX Image at addr 1e200000 ... TRX magic not found trx is not found boot_trx2 - boot - boot default, i.e., run 'bootcmd' Usage: boot_trx2 - No additional help available. u-boot>
4 REPLIES 4
Omar_Alhasan
New Contributor

Same here.

Did you find any answare for this problem ??

 
c5411

I am also having the same problem. Was there a solution?

 

Thanks, Tim

Paul_P
New Contributor

Nothing yet. I am very disappointed about Fortinet at this point. They have no excuse for this strange issue.

dpion
New Contributor

I have the same problem, I tried to chat with the support and no response from them, I am disappointed

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors