We actually experience the problem that the address of the SysTick_Handler is read incorrectly from the memory address of the SysTick ISR in the memory. This leads to a memory management error when the system counter reaches 0 and the SysTick interrupt is fired. When reading the memory, there is the correct address for the Systick_Handler displayed, as shown in the following screenshot.
However, when the SysTick interrupt is fired, the system crashes as shown in the following screenshot, although the address in the memory does not change.
I also found out, that reading out the ISR table as shown in the following screenshot, the address for the SysTick_Handler is not read correctly. But this only happens for the memory cell of the SysTick_Handler.
I also tried to write random values to this memory address and it does not work properly as well. Only the lower two bytes are written correctly the upper 2 bytes remain unchanged. This seems to be the common symptomatic: upper 2 byte are not read correctly, while the lower 2 bytes are ok. Which then leads to the memory fault when the interrupt is called.
Anyone any suggestions or help why this is happening? I would really appreciate this.
