In U-Boot, serial console output is not coming properly and initial Linux boot messages are not coming, i.e. it shows the garbage values at this booting time.
Before and after Linux login prompt, the serial console works fine, i.e. gets the input from user and outputs the cmd.
Speed is set to 115200, 8 bits, 1 stop bit, no parity. For some of the output to be correct, the speed is probably already set correctly. If you have the settings available see if you have CTS/DTS flow control. Note that there is a tiny amount of “garbage” text during u-boot load, but that text is only a tiny bit of one line…the rest should be good. Flow control would help as cable lengths increase or noise in the environment gets in the way.
What kind of cables and/or adapters are you using? For example, regular serial cable won’t work, it needs to be a NULL-modem cable. If there is a USB serial UART involved, power may need to be applied once before it works.
Yes. It is null-modem cable.
Yes. USB-Serial UART is involved.
power may need to be applied once before it works. What is the meaning of it?
And
Installed L4T-2.0, in directory Linux_for_Tegra_tk1/bootloader, fastboot.bin and u-boot.bin binaries are
available, programmed these files and in board, serial output is garbage values.
Could not find out the reason for this? Please help.
Even if well-behaved, power on most of those serial UARTS is supplied by the host, but may have some kind of “detect” for target and “sleep” when not in use. So if power is on your host, the UART is powered…but is it sleep mode or active? There may be cases where it helps to do this in order:
Run serial UART on host...power it up.
Run the target board.
Reboot the target JTK1 momentarily, or unplug/plug the JTK1 power, or remove/add the 9-pin connector connection.
If this fails you may just need to get a different brand of serial UART. Even if the serial UART is not the issue, you’d need to do that to rule it out.