Well, we use the serial port to test the board in production so I can only assume it is good, otherwise it would have failed.
Are you setting it to the correct baud rate?
I have not tested that device, so it is not on approved list. This one is however https://www.sparkfun.com/products/9717
Did you check the list of cables before you bought it?
http://circuitco.com/support/index.php?title=BeagleBone_Black_Accessories#Serial_Debug_Cables
Gerald
Hi Gerald,
Well, we use the serial port to test the board in production so I can only assume it is good, otherwise it would have failed.
Are you setting it to the correct baud rate?
Yes, I’m using 115200, 8 bits, No parity, 1 bit stop, No flow control as documented in http://circuitco.com/support/index.php?title=BeagleBone_Black_Accessories
I have not tested that device, so it is not on approved list. This one is however https://www.sparkfun.com/products/9717
It is the same FTDI 232 chip, just in a different form factor. Since only the ground, rx and tx pins are used, it should make no difference.
Did you check the list of cables before you bought it?
Yes, but since I have similar parts laying around from other projects, I did not found it productive to spend another $20 on a cable.
http://circuitco.com/support/index.php?title=BeagleBone_Black_Accessories#Serial_Debug_Cables
Interestingly enough, hooking up a logic analyzer captured the “- Boot SPL 2013.04-rc1-14237-g90639fe…” text, so the pin seems to be sending the right message…
It is interesting - I tried two different FTDI adapters (the sparkfun and OSEPP-FTDI) and both behaved in the same way: junk on the screen, framing errors…
florin
Sometime the terminal emulators loose their mind. It happens to me often when plugging in the cable. I suggest you plug in the cable and restart the terminal emulator and see if it clears up…
Gerald