• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 251 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0L1306: MSPM0L1306SRHBR

Chintan Patel
Prodigy 10 points
Part Number: MSPM0L1306
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Dear Support Team,

We are encountering an issue where the code gets stuck in the clock initialisation section. Out of 110 units, 10 units are affected by this problem.

This issue arises after flashing the firmware onto the device and then powering it on using the power button. However, the device functions correctly if powered on by plugging in the charger.

Details:

  • MCU: MSPM0L1304SRHBR
  • SDK Version: mspm0_sdk_1_30_00_03
  • CCS Version: 12.6.0.00008

Hardware Design:

Clock Configuration:

Could you please assist us in identifying the root cause and guide on resolving this issue?

  • 0
    TI__Mastermind 20122 points

    Hi Chintan,
    Can you share the schematics to your local sales representative? I think we can review it and see if there's anything wrong with it

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 10 points

    Hello

    Let me check with our team and get back to you.

    We are assuming that the reset signal goes high as soon as the MCU receives power.
    Ideally, the reset signal should remain low until the MCU's Clock stabilizes. Once the MCU's Clock is stable, the reset signal should assert high.

    Could you please provide the duration for which the MCU reset signal should remain low during power-on?
    Additionally, apart from the MCU reset signal, are there any other signal dependencies required to make the MCU fully functional?

    Thanks,

    Chintan

  • 0 in reply to Chintan Patel
    TI__Mastermind 20122 points

    Hi Chintan,
    The NRST pin should be pulled high for the MCU to start the boot process, so in theory, it can be as low as you guys want until you pull it high so the device starts working. I don't think the M0 needs any time to "stabilize" the internal clock unless you mean the time that a clock signal outside the M0 needs to stabilize itself, in which case it will depend on the crystal or oscillator you are using (I recommend that device's datasheet/ ask their team to find out more about it.) Apart from NRST, if you look into the 9.1.1 Schematic in the datasheet, that should give you the overall idea of what you need to procure the MCU's promoted functionality.
    Best Regards,
    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 10 points

    Hello 

    I  would like to understand the default configuration from the clock generator in the SDK.

    In our design, we are not using an external or internal low-frequency oscillator. Should we wait for stabilization during the initialization process?

    Based on your input, it seems we don't need to wait for the stabilization of the internal clock.

    Please confirm if my understanding is correct.

    Thanks,
    Chintan

  • 0 in reply to Chintan Patel
    TI__Mastermind 20122 points

    Hi Chintan,
    I'm looking into a regular empty projec in our SDK and I can't seem to find the configuration that calls the CLK init() that you have. Can you share the sysconfig file so I can take a look at it?

    Best Regards,

    Diego Abad

  • 0 in reply to Chintan Patel
    TI__Mastermind 20122 points

    Hi Chintan,
    Is it possible to share that SYSCONFIG file? If not, can you tell what other configurations are you making?

    Best Regards,

    Diego Abad