Expected first printf line of software to serial output to Windows7 PC is:
main() ****** SW START Project 2016-10-30 x1
Actual serial output (at TeraTerm or PuTTY);
▒▒▒▒()` jj*jj*jj*jj*jj*j ▒▒`Ӕ▒Ҕ ▒▒▒▒▒▒▒ ` r01v-q0-30`▒q
Serial worked great with NUCLEO evaluation board. ie. Serial pc(USBTX, USBRX);
Now, I'm running the actual target board with a STM32F091RC. ie. Serial pc(SERIAL_TX, SERIAL_RX);
At 9600, some chars are correct, most are garbage.
I've tried alternate target and cables, same problem. PC's Terminal program (TeraTerm or PuTTY) set at 8,n,1.
Looked in mbed library; default config is 8 data, no parity, 1 stop.
USB/serial converter cable is: FTDIChip TTL-232R-RPi (normally for Raspberry Pi).
Expected first printf line of software to serial output to Windows7 PC is: main() ****** SW START Project 2016-10-30 x1
Actual serial output (at TeraTerm or PuTTY); ▒▒▒▒()` jj*jj*jj*jj*jj*j ▒▒`Ӕ▒Ҕ ▒▒▒▒▒▒▒ ` r01v-q0-30`▒q
Serial worked great with NUCLEO evaluation board. ie. Serial pc(USBTX, USBRX); Now, I'm running the actual target board with a STM32F091RC. ie. Serial pc(SERIAL_TX, SERIAL_RX); At 9600, some chars are correct, most are garbage. I've tried alternate target and cables, same problem. PC's Terminal program (TeraTerm or PuTTY) set at 8,n,1. Looked in mbed library; default config is 8 data, no parity, 1 stop.
USB/serial converter cable is: FTDIChip TTL-232R-RPi (normally for Raspberry Pi).