I am attempting to use the UART pins on the Raspberry Pi 2 to interface with the console port on a Cisco Access Point.
I've stripped an old RJ45 cable to connect the right TX, RX and GND pins from the console port to the UART ports on my Pi.
I have enabled UART through raspi-config and disabled the serial console.
I know from previous tutorials that the correct baud rate from this AP is 9600, and I'm opening a console using Minicom sudo minicom -D /dev/ttyAMA0 -b 9600
Unfortunately, I only receive indecipherable characters:
I know these symptoms usually relate to incorrect baud rate setting, so I've tried all of the following to no avail:
- 300
- 1200
- 2400
- 4800
- 9600
- 19200
- 38400
- 57600
- 115200
- 230400
- 460800
- 500000 They all produce different sets of characters but none are readable.
On one occasion I did get some partially correct text but this never occurred again:
I've tried the following tasks:
- Adding
core_freq=250to/boot/config.txtand rebooting. - Adding
force_turbo=1to/boot/config.txtand rebooting. - Adding
init_uart_baud=9600to/boot/config.txtand rebooting. - Adding
init_uart_clock=48000000to/boot/config.txtand rebooting. - Using Raspi-OS instead of Ubuntu Core.
- Various combinations of parity, data bits and flow control.
- Using UART1 instead of UART0 on the same pins GPIO14 and 15 by adding into
/boot/config.txt:
dtparam=uart0=off
dtparam=uart1=on
dtoverlay=uart1,txd1_pin=14
dtoverlay=uart1,rxd1_pin=15
I also had to add 8250.nr_uarts=1 into /boot/cmdline.txt
None of these made any difference. I am out of ideas and looking for advice on further troubleshooting my UART pins in case they may be broken, or anything else that might make this work.

