This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0G3507: SYSOSC clock trim/tune

Part Number: MSPM0G3507

Tool/software:

I recently had a test MSPM0G3507 UART output start producing corrupt characters on my serial console at all baud rates I tested.  It used to work error free at 115200.  I traced the problem to SYSOSC running at 29.68 MHz. Spec says sysosc is factory trimmed to 32 MHz +/- 2.5% so 29.68 very much out of spec.  Any suggestions as to what happened to my part?  My first guess is the trimming is not some permanent laser trim but instead storing correction/tuning values in BCR/BSL FLASH and I did something that erased that flash?  Yet I can not find where in documentation the trim process is described.  Any suggestions?  Can I retune it?  or easier to scrap and replace it?  My main concern is that I have thousands of these in the field and want to make sure this does not happen to one of those, so need to understand root cause.

  • Hi,

    I do not know what happens and causes the issue.

    The calibration data is saved in factory region. It is not saved in NONMAIN. 

    You can retune in the application code. There should have a demo code which configures SYSOSC  to 4Mhz. You can refer to it.

    If you want to know the root cause, I would suggest you to request a customer return and they will help you to analyze the root cause. 

    Best regards,

    Cash Hao