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â–’â–’â–’â–’â–’â–’â–’
Solved! Go to 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.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
You should open a formal RMA ticket for return repair.
User | Count |
---|---|
2571 | |
1365 | |
796 | |
653 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.