Forum Discussion

rshal2's avatar
rshal2
Icon for Occasional Contributor rankOccasional Contributor
6 years ago

Peloader hang in clock calibration

Hello, The following function get hang in my application. I can't knows exactly why, because preloader is getting compiled with debug information (Is there a way to Turn it off)? What I see is: ...
rshal2's avatar
rshal2
Icon for Occasional Contributor rankOccasional Contributor
6 years ago

Hi,

We are using bsp-editor, with device ASXFB5 (arria V) with quartus 15.1.

I suspect that it is related to clock input clock1 ? but since debugging behaves a little tricky (I tried to remove some parts, but it behaves in-consistently), therefore I think it would be better if I build with no optimization.

Yet, It always hang cm_basic_init() routine.

I verified the following:

osc1 and osc2 are 50M with scope.

bootinfo register is 0x2b5 (bsel=0x5, csel=0x2).

What can be the reason for preloader hang in cm_basic_init?

Thanks

rshal2's avatar
rshal2
Icon for Occasional Contributor rankOccasional Contributor
6 years ago

In further debugging it seems it get hangs right here:

	/* Take all three PLLs out of bypass when safe mode is cleared. */
	DEBUG_MEMORY
	cm_write_bypass(
		CLKMGR_BYPASS_PERPLLSRC_SET(
		CLKMGR_BYPASS_PERPLLSRC_ENUM_SELECT_EOSC1) |
		CLKMGR_BYPASS_SDRPLLSRC_SET(
		CLKMGR_BYPASS_SDRPLLSRC_ENUM_SELECT_EOSC1) |
		CLKMGR_BYPASS_PERPLL_SET(CLKMGR_BYPASS_ENUM_DISABLE) |
		CLKMGR_BYPASS_SDRPLL_SET(CLKMGR_BYPASS_ENUM_DISABLE) |
		CLKMGR_BYPASS_MAINPLL_SET(CLKMGR_BYPASS_ENUM_DISABLE));

for some reason, I can't put a breakpoint in this line but if I remove the above line from code, then I get into next line and continue debugging.

Any idea what it means ?

Thanks!