I'm quite confident the problem is that the Pi does not have an RS232 interface, while the display has.
The Pi has an (LV-)UART interface, its TX-pin outputs 0V for a logical 0
and 3.3V for a logical 1
. This is quite easy to implement, since 3.3V is already available on the Pi. But this only works for communications on a single PCB or within a single device.
For communication between devices over longer distances, a system less prone to interfering signals like RS232 is used. While the logical structure of the waveform (bitrate, timing, start-, stop-, parity- and data-bits) is the same as for UART, the voltage levels are -15V...-3V for a logical 1
and +15V...+3V for a logical 0
. This means, there are not only higher (and negative) voltages, their meaning is also inverted.
So, if the display expects RS232 levels and gets that 3.3V levels from the Pi, it mostly doesn't recognize the data, and if it does, it's often just garbage.
And of course, if you connect RX and TX of the same interface, you get what you expect.
But: If the RS232 TX output is not current limited, it could even damage your Pi!
There are UART to RS232 converter boards out there, but if you like to solder, the boards just contain a MAX3232 (plus four capacitors). This IC also generates the higher (and negative) voltage levels from the 3.3V supply voltage from the Pi.
The more common is the MAX232 (guess why it's called so), but it is for 5V, not 3.3V operation.
Finally, because the UART and the RS232 use the same logical structure, it's often not distinguished between both of them, especially by software (programmers). They are often also just called "serial interface", though there are other interfaces like I²C and SPI, which are a type of serial interface, but never considered to be "the" serial interface.
Best Answer
Didn't tried it myself, but I've found this information on the coreboot wiki (https://www.coreboot.org/GRUB2#On_a_USB_serial_or_USB_debug_adapter)
To enable serial, first find out the name of your usb serial port trough:
The terminal_output command should print it:
Then add the following on top of your grub.cfg:
The following chips/protocols are supported:
The Wiki is outdated, but the answer seems legit.