EVM430-FR6047: HSPLL hardware issue

Hi Thibault,

I suggest you to debug the code, and check where you get this HSPLL unlock error code. 

A probability is that you define the 'USS_APP_RESONATOR_CALIBRATE_ENABLE' in your code. And it get errors in USS_verifyHSPLLFrequency().
If that, try comment the definition of the 'USS_APP_RESONATOR_CALIBRATE_ENABLE'.

Best regards,

Cash Hao

Cash Hao said:

Hi Thibault,

I suggest you to debug the code, and check where you get this HSPLL unlock error code. 

A probability is that you define the 'USS_APP_RESONATOR_CALIBRATE_ENABLE' in your code. And it get errors in USS_verifyHSPLLFrequency().
If that, try comment the definition of the 'USS_APP_RESONATOR_CALIBRATE_ENABLE'.

Best regards,

Cash Hao

Hi Cash Hao11

Even If I remove the USS_APP_RESONATOR_CALIBRATE_ENABLE I get the error here: 

 // Invalid capture must report error
            if (USS_message_code_no_error != code)
            {
                if (USSSWLIB_USS_interrupt_status & USS_HSPLL_PLL_UNLOCK_INTERRUPT)
                {
                    printf("HSPLL error, resetting USS module.\n"); // <----------------------------- HERE
                    USS_resetUSSModule(&gUssSWConfig, true);
                    USSLibGUIApp_send_error(COMMAND_HANDLER_ERROR_FAULT_INVALID_CAPTURE,
                                                            (uint16_t) USS_message_code_HSPLL_pll_unlock_error);
                }
                else
                {
                    printf("invalid Capture.\n");
                    USSLibGUIApp_send_error(COMMAND_HANDLER_ERROR_FAULT_INVALID_CAPTURE,
                                                            (uint16_t) code);
                }

            }

Is it necessary to Calibrate the HSPLL in the program? And what else could I debug? I have tested with the default code so I still suspect hardware issue. 

Thanks again!

Best regards,
Thibault

Cash Hao said:

Hi Thibault,
You can search for each 'HSPLL error' in the project and add a break point. Run the code and see where does it get this error code.

I don't think it is necessary to calibrate the HSPLL in regular applications. And you can check if your are using the latest code and GUI version on TI website.

Best regards,
Cash Hao

Hi,

The error "USS_message_code_HSPLL_pll_unlock_error" (24) comes from here: 

		// Check if PLL was unlocked during conversion
		if(USSSWLIB_USS_interrupt_status & USS_HSPLL_PLL_UNLOCK_INTERRUPT)
		{
			return USS_message_code_HSPLL_pll_unlock_error;
		}

in the function USS_message_code commonIsconversionSuccessfull(USS_SW_Library_configuration *config) in USS_commonTriggerSingleCapture() during USS_startLowPowerUltrasonicCapture().

I noticed that if I don't have the error, I can make the error show up by touching the oscillator clock on the PCB board with my finger, with a very light pressure. The error disappears directly after releasing the finger. 

Best regards,
Thibault 

Hi Thibault,

Yes, I notice the same phenomenon. So it is more likely a hardware issue. Check the capacitors and the oscillator again.

Best regards,

Cash Hao 

Cash Hao said:

Hi Thibault,

Yes, I notice the same phenomenon. So it is more likely a hardware issue. Check the capacitors and the oscillator again.

Best regards,

Cash Hao 

Hi Cash Hao11

Thank you for confirming that. What do you want me to check? I am using your EVM board. Here is the data sheet of the component:. 

Could you please check with the hardware/electronics team if it was implemented correctly on the EVM430-FR6047 Rev B? 

Thank you!

Best regards
Thibault

Cash Hao said:

Hi Thibault,

Sure. We will check it with the team on how to improve the board.

Best regards,

Cash Hao

Hi,

Okay thank you, please come back with a suggested redesign of the HSPLL part as soon as you have found a solution!

Best regards

Thibault