LP-MSPM0L2228: Garbled text in tera term

Bhavpreeta Charan

Part Number: LP-MSPM0L2228
Other Parts Discussed in Thread: MSPM0L2228

Tool/software:

Hello experts,

Using out of box example in LP-MSPM0L2228, my customer would like to check communication with MSPM0 (ADC, UART, etc.) but observing the tera term text to be garbled.

Port setting is just like explained in readme file. Please tell me what is wrong here and how to resolve this?

(downloaded out_of_box_mspm0l2228 from CCS and also tested different text encoding but cannot resolve this)

6 days ago

0 Helic Chi 5 days ago

TI__Mastermind 19397 points

Bhavpreeta Charan said:
but observing the tera term text to be garbled.

Not all the text is garbled, you can still get the running function information.

You COM port config is correct.

Since there is no available L2228_OOBD now, I can not verify this using GUI.

But these garbled doesn't influence the key function running at LP-L2228.

0 Takashi Hirobe 4 days ago in reply to Helic Chi

Prodigy 30 points

Thank you. Even though I can read part of sentence, I can't understand serial output data completely.
Do you have any tool recommendation?

0 Helic Chi 4 days ago in reply to Takashi Hirobe

TI__Mastermind 19397 points

There are also some garbled test at my side, when you try to using Hex, you can find there are some invalid ASCII from the COM port, I guess it's for OOBD, but I didn't verify that.

Here is another COM port assistant that I found from Google:

XCOM V2.31.exe.zip

0 Takashi Hirobe 4 days ago in reply to Helic Chi

Prodigy 30 points

Thank you. I also confirmed some garbeled data in your recommendated tool.
I will proceed validation by reading part of correct data.

0 Helic Chi 4 days ago in reply to Takashi Hirobe

TI__Mastermind 19397 points

You can change the language in the settings.

0 Bruce McKenney 4 days ago in reply to Helic Chi

Guru 99545 points

If the question marks are the concern, I think what's sent over the UART isn't expected to be human-readable; rather it's a structured packet (see GUIcomm_mpack.c) that the GUI knows how to decode.

0 Helic Chi 4 days ago in reply to Bruce McKenney

TI__Mastermind 19397 points

Bruce McKenney said:
I think what's sent over the UART isn't expected to be human-readable; rather it's a structured packet (see GUIcomm_mpack.c) that the GUI knows how to decode.

Yes~ But I didn't got time to test it

But there is no L2228 OOBD now.

Maybe need to test out of box demo based on G3507 or other OOBD available device.

0 Takashi Hirobe 4 days ago in reply to Helic Chi

Prodigy 30 points

Thank you. I could change to English display.
I tried all types of encoding in tool but all failed.

Fortunately, HEX data is clear. I will try to encode by refering datasheet.