FortiAP 221E brick after upgrade

[serx]

After firmware update 221E bricked. Trying to connect thru console pin (j44) inside AP. Maybe some information how to repair this ap.

from console i can see only:

▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒▒▒▒f▒▒f▒`~`▒▒▒▒▒▒f▒▒▒▒▒▒▒

[adambomb1219]

Look like your baud rate is not set correctly.  

[serx]

I tried all baud rate. No success. What can be different from normal console port ?

[serx]

I trying to use these pins.

[adambomb1219]

Why do have the AP open?  Did you open a TAC case if you suspect an issue with the upgrade?

[serx]

Why not ?

[sw2090 · Accepted solution]

hm I saw similar output from a FortiExtender Console when the baud rate was incorrect.

Also parity and stop bit could be a culprit.

Also keep in mind that the pins onboard usually are a TTL serial header so you will need a level converter like MAX232 between it and pc. Also you must connect GND.

VCC (Circuit Power) Pin only needs to be connected when the AP does not have any other power supply connected.

Also do not forget about crosswiring: rx pin on board needs to connect tx on the other side and tx on board needs to conenct rx on other side.

[serx]

thanks.with TTL works ;)

[amilojevic]

hello, 

I have same problem, but I made connection and kernel wont start. Have you seen problem like this. 

I connected to device and get this:

Booting kernel from FIT Image at 84000000 ...
Using 'config@4' configuration
Trying 'kernel@1' kernel subimage
Description: ARM OpenWrt Linux-4.4.60
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x840000e4
Data Size: 3832120 Bytes = 3.7 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80208000
Entry Point: 0x80208000
Hash algo: crc32
Hash value: 7e6e3257
Hash algo: sha1
Hash value: faadc880cc39a5ce97c34c6d44d485d093bccb57
Verifying Hash Integrity ... crc32+ sha1+ OK
## Flattened Device Tree from FIT Image at 84000000
Using 'config@4' configuration
Trying 'fdt@4' FDT blob subimage
Description: ARM OpenWrt qcom-ipq40xx-ap.dkxx device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x843bd410
Data Size: 19136 Bytes = 18.7 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 66facfd1
Hash algo: sha1
Hash value: afb6f8b04356c59168c655e28930e2ff06f0bdfc
Verifying Hash Integrity ... crc32+ sha1+ OK
Booting using the fdt blob at 0x843bd410
Uncompressing Kernel Image ... OK
Loading Device Tree to 86ff8000, end 86fffabf ... OK
eth0 MAC Address from ART is not valid
eth1 MAC Address from ART is not valid
Using machid 0x8010000 from environment

Starting kernel ...

[imadias1]

Hi, I'm having the same problem.

I can already connect to the IAP, but I can't interrupt the boot.
It gives the idea that it does not accept the press any key