MSPM0G1106: Clock not working with PG2 samples

Asiel Trejo

Part Number: MSPM0G1106
Other Parts Discussed in Thread: MSPM0G3507,

Hi, I recently received PG2 samples of the MSPM0G3507. It is supposed to be the superset of the MSPM0G1106. Both in the 32 pins version.

I'm having an issue that I didn't have before. It is very unstable regarding to the clock. It sometimes flashes, sometimes don't. When it flashes, it mostly gets stuck in the clock verification functions, like the following ones:

Also it takes long to boot and stays here

And finally the console says this:

The configuration is set to have an XTAL of 16 MHz and run only on the external. I have programmed it as a G1106 and also as an G3507 and in either case it makes the same problem. Additional to this I have tested 4 samples and each one of them has the same problem.

We hand-soldered the microcontroller, so it may be an issue, but at least the crystal paths seem to be connected to the microcontroller (Continuity test), so it makes me think it may be a software issue.

It doesn't have this problem when using the internal oscillator. Using the SYSOSC works like charm.

Hope to see your reply soon.

Thanks

Asiel T.

over 2 years ago

0 Brandon Fisher94 over 2 years ago

TI__Mastermind 28070 points

Hi Asiel,

What version of the SDK and CCS are you using with the PG2 (production) devices?

Can you also check your support package version? You can do this by going to Help -> About Code Composer Studio -> Installation Details and then type MSPM0 into the search bar with the installed software tab selected.

Best Regards,
Brandon Fisher

0 Asiel Trejo over 2 years ago in reply to Brandon Fisher94

Prodigy 90 points

I'm using tha latest ones, CCS 12.3 and SDK 1.01.03. As for the support package I have the 1.0.1.01

0 Brandon Fisher94 over 2 years ago in reply to Asiel Trejo

TI__Mastermind 28070 points

Hi Asiel,

Those software versions look okay for production silicon. What are your SYSPLL Settings? Specifically your QDIV and PDIV settings.

Best Regards,
Brandon Fisher

0 Asiel Trejo over 2 years ago in reply to Brandon Fisher94

Prodigy 90 points

I'll post the screenshots. I'm using a 16 MHz external crystal, so I guess I'm good with the Wait States

+1 Brandon Fisher94 over 2 years ago in reply to Asiel Trejo

TI__Mastermind 28070 points

Hi Asiel,

What is the total size of your program code? Is this based on one of our examples?

Have you tried increasing your startup time? I'm not sure what's appropriate for your crystal, but it can vary. For testing purposes something arbitrarily long like 255 might be appropriate to try here.

Best Regards,
Brandon Fisher

0 Asiel Trejo over 2 years ago in reply to Brandon Fisher94

Prodigy 90 points

Hi Brandon

Thanks a lot. It was it. I put 255 and it is working good now. That solved my issue. Do you know where do I get that number?

0 Brandon Fisher94 over 2 years ago in reply to Asiel Trejo

TI__Mastermind 28070 points

Asiel,

The datasheet recommends roughly half a milisecond, but that value depends a lot on your crystal and loading. With 255 you are allowing about 16.32ms for startup. You could try and step it back a bit to see where you start failing and then add some margin if you want.

What is the expected Cload value for your crystal and what cap values are you using? Sometimes designers forget to account for the pin capacitance of the MCU and that can make crystals oscillate slightly off frequency or have a hard time oscillating all together.

Best Regards,
Brandon Fisher

0 Asiel Trejo over 2 years ago in reply to Brandon Fisher94

Prodigy 90 points

Brandon

The crystal is 16 MHz and the capacitors are 33 pF. And you're right, the star-up time the datasheet says is 0.5 ms (equivalent to 8). I tested with 8 and it doesn't work, so I guess I'll find through trial and error.

Thanks a lot,

Asiel Trejo

0 Brandon Fisher94 over 2 years ago in reply to Asiel Trejo

TI__Mastermind 28070 points

Asiel Trejo said:
The crystal is 16 MHz and the capacitors are 33 pF

I'd assume this is an 18pf crystal based on those values, is that correct? If so it sounds like your cap values are fine.

Best Regards,
Brandon Fisher

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G1106: Clock not working with PG2 samples