Hello Katie Elliott,
This is the same question as case 00119803 which you created.
Thank you for your interest in NXP Kinetis product, I would like to provide service for you.
KL17Z128 can't refer to FRDM-KL27 board, it should refer to the FRDM-KL43 board.
When KL17 flash larger than 128K, it should refer to FRDM-KL43 board, when the KL17 flash is lower than 64K, it should refer to FRDM-KL27 board.
About your attached code, I have test it on my FRDM-KL43.
1. when use *((uint32_t*)0) = 0; generate a hardfault.
The code can enter without problem.
2. Your SysTick_Config(48000000); is wrong.
As you know, the systick is just 24 bit counter.
__STATIC_INLINE uint32_t SysTick_Config(uint32_t ticks)
{
if ((ticks - 1UL) > SysTick_LOAD_RELOAD_Msk)
{
return (1UL); /* Reload value impossible */
}
SysTick->LOAD = (uint32_t)(ticks - 1UL); /* set reload register */
NVIC_SetPriority (SysTick_IRQn, (1UL << __NVIC_PRIO_BITS) - 1UL); /* set Priority for Systick Interrupt */
SysTick->VAL = 0UL; /* Load the SysTick Counter Value */
SysTick->CTRL = SysTick_CTRL_CLKSOURCE_Msk |
SysTick_CTRL_TICKINT_Msk |
SysTick_CTRL_ENABLE_Msk; /* Enable SysTick IRQ and SysTick Timer */
return (0UL); /* Function successful */
}
From the sysTick_config function, you can get that if your make ticks=48000000, it is larger than 0xffffff, then it will return 1, it won't configure the systick any more.
If I define it like this:
sysTick_Config(48000), the code will enter SysTick_Handler.
Now, describe your problem.
When you put a break point in code:
SystemCoreClockUpdate();
Can you enter it?
Please also check your NMI pin, did you add a external 4.7K to 10K pull up?
Please check these points at first.
Besides, give me your chip full name!
Have a great day,
Kerry
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Further update. We created a tiny example project that exhibits the problem. Below is a screenshot of what happens after we trigger a hard fault (line 12). We never break in the hardfault ISR in startup_MKL17Z4.s (part of the SDK). When we halt the processor we are somewhere in the boot ROM.
