To capture the serial-output of the boot log you need a serial-adapter tool like this:
https://thepihut.com/products/usb-to...r-raspberry-pi
When you plug in this device into your computer, it shows up as a new serial-port and you can then connect to the serial-port in the computer with a terminal-emulator like Tera Term or Putty.
You then hook up the headers of the serial-adapter to the correct pins on the device under test.
USB GND - to - DUT GND, obviously. (black)
USB RX - to - DUT TX, this is how you receive data from the DUT to your terminal window. (white)
USB TX - to - DUT RX, this allows you to transmit typed commands into the DUT. (green)
The red header you can ignore, it's for powering IoT devices.
This product with the blue case appears to be the real deal from Adafruit so it should have a brand controller in it which means the Windows driver will work with it.
If you find some alternative that's cheaper than this one, then it's probably built on a pirated controller chip and the Windows driver will detect that and refuse to work.
The pirated versions still work fine in Linux, though.
You will still have to mess around a bit with the speed setting in the terminal software, if you get garbage characters or just a single garbage character then you are probably set to the wrong speed and you should try some other speeds.
115200 and 57600 are a couple of likely choices, and keep the other settings at "8N1", meaning "8-bit, no parity, 1 stop bit", you will find this all under "port settings" or similar in the terminal software.

Just passively catching the boot log only requires hooking up the black and the white headers (GND and RX), but it sounds from Diah that you need to type some command, that means that you need to hook up the green header too (TX).
Leave a comment: