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.

MSP430FR6047: Ceramic Resonator for HSPL in MSP430FR6047 is not working

Part Number: MSP430FR6047
Other Parts Discussed in Thread: EVM430-FR6047

Tool/software:

Dear Engineers,

I'm using a EVM board for MSP430FR6047 to use its build in USS module for measuring the water volume. In the USS mode I noticed there is an crystal (Ceramic Resonator) as follows for making high frequency around 80 MHz form a 8MHz clock by using PLL:

In the reference design it is mentioned that the part number that has been use for the Y3 in the EVM is "AWSCR-8.00CV-T", it the datasheet of this module I see that it is mentioned that this Ceramic Resonator has built-in load capacitors:

So, why do we need extra load capacitors in the schematic for Y3 based on he reference design in the EVM? as we can see in the picture we have these capacitors assembled on the PCB:

I noticed we I program the un-touched firmware from TI, then I get an error for HSPL as follows:

Would you please let me know if these extra capacitor could be the routes cause if the issue? and what is the reason that we have these capacitors in the reference design?

Regarding R15 (22 Ohm):

 What is the reason of using R15(22 Ohm), do we need it at all? and why? based on the datasheet: abracon.com/Resonators/AWSCR_CV.pdf it is mentioned a 1Mohm resistor should be used in parallel? right? 

Regards,

 

  • Hi,

    The build in cap is not enough for the MCU HFXT port to drive this resonator. 

    If you are seeing error code 24, it could related to the external cap. By default, it uses 12pF on the C7 and C8. You can try replace those with a higher cap value like 30pF. 

    About the 22Ohm resistor, I am not sure what role it plays in this circuit. I will check on it later.

    Best regards,

    Cash Hao

  • Dear Cash,

    Thank you very much for your update:

    This is the signals that I see before the R11 and after R11:

    This signal is very slow, do you think the ceramic resonator is not functioning well?

    Regards 

  • Hi,

    The signal seems very weak. Could you directly put the probe between USSXOUT and GND? It should get a better view of the signal this way. 

    Best regards,

    Cash Hao

  • Hi Cash,

    This signal is what you are referring to:

    Regards 

  • Hi,

    This signal does not look correct from my side. It seems that the resonator is not functionally. Do you test it on your board or you tested it on the Ti EVM board? 

    Best regards,

    Cash Hao

  • HI

    I'm using EVM board, with the following firmware:

    Regards 

  • Hi,

    Check for the status here. 

    You are testing on EVM430-FR6047 board. And you received error code 24 which is HSPLL unlocked under default EVM hardware. So, you check the HFXT related hardware. 

    Any test result after suggest you to replace the C7 and C8 to 30pF?

    Best regards,

    Cash Hao

  • Hello Cash,

    Thank you very much for the reply. Yes, Finally I received my caps and I did changed it but still it is not working.

    Frankly speaking I spent a lot of time on this issue, but still is is not working. Would you  please let me know if I can return this board and get a working system instead? We are based in Belgium, maybe would you please connect me will a responsible person for this issue? In this way at least I am sure that I will a have a working hardware.

    Regards,

  • Hi,

    Do you buy the EVM board on the TI website. If so, you can try return or refunds in your order history. 

    Best regards,

    Cash Hao

  • Hello Cash,

    I bought it from Mouser website, then how we can communication in way that I can also have your confirmation that the board is not working? then it will be clear for them that they need to replace it for me.

    Best regards 

  • Hi,

    I understand your situation. However, I found the return policy for EVM boards from TI side in this link. https://www.ti.com/ordering-resources/faqs/returns/policy.html

    I am not sure if Mouser has similar policy. So, from my point, we can focus on how to fix this issue on your board and make it work again.

    Best regards,

    Cash Hao

  • Hi cash,

    Thank you very much.

    Ok, then would you please let me  know what would be the next steps to fix the issue on the board?

    Regards 

  • Hi,

    Could you send a picture of your board first. We can check on the hardware first to see if there is anything wrong on the hardware. 

    Best regards,

    Cash Hao

  • Hi,

    This picture shows the ceramic resonator area:

    The board:

    The whole setup:

    Best regards 

  • Hi,

    About the transducer connection, it looks like you only connect one pin of the transducer to the board. 

    You need to connect two pins to the board. The red line of the transducer should connect to CH0/1. The white line should connect to GND.

    Best regards,

    Cash Hao

  • Hi Casho,

    Thanks fir the comment. 

    The exact picture looks like this:

    In fact the white wire is not involved in the connections, then I connect the red wire to signal and the shielding (black wire) to GND, so I think the connection of the sensor is fine. A question that came to my mind is the can this can sensor issues cause this problem? or it is purely related to HSPL? 

    In fact the issue is that the C program can not pass this code:

    USS_runAlgorithms(&gUssSWConfig,&algResults);

    And it fact the code is locked in this line.

    Regards

  • Hi Cash,

    The Demo firmware represents this:

    Regards,

  • Hi,

    The transducer connection should not related to the the HSPLL issue. I just checked the hardware and find what looks abnormal from my side. 

    Which demo code you are using? Have you ever change the default parameters in the demo project and cause this issue? 

    Best regards,

    Cash Hao

  • Hi

    I use the following code:

    Regarding this question "Have you ever change the default parameters in the demo project and cause this issue?", no I have not changed it yet.

    Regards

  • Hi, 

    Okay. So, in default project. You can find this parameter USS_HSPLL_TOLERANCE_PERCENT in USS_userConfig.h. 

    You can modify it to 10 and download the project to the EVM board. And check if it can stop reporting this error. 

    Best regards,

    Cash Hao

  • Hi,

    I changed it to 10 as follows:

    And I got the same result:

    Regards 

  • Hi,

    Emm, could you also change the USS_DIAGNOSTIC_MODE to USS_diagnostics_mode_0 in the USS_userConfig.h.

    Could you also send your USS_userConfig.h file here? So, after you download the project to EVM board. When you connecting USS GUI, you do not use update parameters function on the GUI, right?

    Best regards,

    Cash Hao

  • Hi

    I just test it, but still we have the HSPL error. Please see the requested file:

    Configuration.c
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    /* --COPYRIGHT--,TI
    *MSP Source and Object Code Software License Agreement
    *
    *
    ***IMPORTANT - PLEASE CAREFULLY READ THE FOLLOWING LICENSE AGREEMENT, WHICH IS LEGALLY BINDING. AFTER YOU READ IT, YOU WILL BE ASKED WHETHER YOU ACCEPT AND AGREE TO ITS TERMS. DO NOT CLICK "I ACCEPT" UNLESS: (1) YOU WILL USE THE LICENSED MATERIALS FOR YOUR OWN BENEFIT AND PERSONALLY ACCEPT, AGREE TO AND INTEND TO BE BOUND BY THESE TERMS; OR (2) YOU ARE AUTHORIZED TO, AND INTEND TO BE BOUND BY, THESE TERMS ON BEHALF OF YOUR COMPANY.
    *
    *
    ***Important - Read carefully: This Source and Object Code Software License Agreement ("Agreement") is a legal agreement between you and Texas Instruments Incorporated ("TI"). In this Agreement "you" means you personally if you will exercise the rights granted for your own benefit, but it means your company (or you on behalf of your company) if you will exercise the rights granted for your company's benefit. The "Licensed Materials" subject to this Agreement include the software programs and any associated electronic documentation (in each case, in whole or in part) that accompany this Agreement, are set forth in the applicable software manifest and you access "on-line", as well as any updates or upgrades to such software programs or documentation, if any, provided to you at TI's sole discretion. The Licensed Materials are specifically designed and licensed for use solely and exclusively with MSP microcontroller devices manufactured by or for TI ("TI Devices"). By installing, copying or otherwise using the Licensed Materials you agree to abide by the provisions set forth herein. This Agreement is displayed for you to read prior to using the Licensed Materials. If you choose not to accept or agree with these provisions, do not download or install the Licensed Materials.
    *
    ***Note Regarding Possible Access to Other Licensed Materials: The Licensed Materials may be bundled with software and associated electronic documentation, if any, licensed under terms other than the terms of this Agreement (in whole or in part, "Other Licensed Materials"), including, for example Open Source Software and/or TI-owned or third party Proprietary Software licensed under such other terms. "Open Source Software" means any software licensed under terms requiring that (A) other software ("Proprietary Software") incorporated, combined or distributed with such software or developed using such software: (i) be disclosed or distributed in source code form; or (ii) otherwise be licensed on terms inconsistent with the terms of this Agreement, including but not limited to permitting use of the Proprietary Software on or with devices other than TI Devices, or (B) require the owner of Proprietary Software to license any of its patents to users of the Open Source Software and/or Proprietary Software incorporated, combined or distributed with such Open Source Software or developed using such Open Source Software.
    *
    ***If by accepting this Agreement, you gain access to Other Licensed Materials, they will be listed in the applicable software manifest. Your use of the Other Licensed Materials is subject to the applicable other licensing terms acknowledgements and disclaimers as specified in the applicable software manifest and/or identified or included with the Other Licensed Materials in the software bundle. For clarification, this Agreement does not limit your rights under, or grant you rights that supersede, the terms of any applicable Other Licensed Materials license agreement. If any of the Other Licensed Materials is Open Source Software that has been provided to you in object code only under terms that obligate TI to provide to you or show you where you can access the source code versions of such Open Source Software, TI will provide to you, or show you where you can access, such source code if you contact TI at Texas Instruments Incorporated, 12500 TI Boulevard, Mail Station 8638, Dallas, Texas 75243, Attention: Contracts Manager, Embedded Processing. In the event you choose not to accept or agree with the terms in any applicable Other Licensed Materials license agreement, you must terminate this Agreement.
    *
    ***1. License Grant and Use Restrictions.
    *
    ***a. Licensed Materials License Grant. Subject to the terms of this Agreement, TI hereby grants to you a limited, non-transferable, non-exclusive, non-assignable, non-sublicensable, fully paid-up and royalty-free license to:
    *
    * i. Limited Source Code License: make copies, prepare derivative works, display internally and use internally the Licensed Materials provided to you in source code for the sole purpose of developing object and executable versions of such Licensed Materials, or any derivative thereof, that execute solely and exclusively on TI Devices, for end use in Licensee Products, and maintaining and supporting such Licensed Materials, or any derivative thereof, and Licensee Products. For purposes of this Agreement, "Licensee Product" means a product that consists of both hardware, including one or more TI Devices, and software components, including only executable versions of the Licensed Materials that execute solely and exclusively on such TI Devices.
    *
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards,

    Behnam,

  • Hi,

    Okay, the .h file looks good from my side. 

    Could you also try add below code before you call USS_runAlgorithms(&gUssSWConfig,&algResults); function?

    gUssSWConfig.pllConfiguration->pllOutputFreq  = USS_HSPLL_output_clk_freq_72_MHz;

    Best regards,

    Cash Hao

  • Hi Cash,

    Thank you for the update.

    Yes, sure I did it and it seems the error is still there.

    Can it be that the ceramic resonator is malfunctioning and it not working at all?

    Regards 

  • Hi,

    Well, I think the chance of the ceramic resonator broken is very low. If it is a hardware issue. A ESD hazard on the HFXT pin of the MCU is more likely to happen in some cases on my side. So, I would suggest to use a new FR6047 MCU to replace the one on your EVM board. You can also replace the ceramic resonator and check if these will work. 

    Best regards,

    Cash Hao

**Attention** This is a public forum