Other Parts Discussed in Thread: HALCOGEN, SEGGER
I'm trying to debug what triggered the prefetch abort.
Weirdly, the INSTRUCTION FAULT ADDRESS is 0x96699668, which is in a memory region.
Any help would be appreciated.
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.
Hi Gabriel,
Please refer to the FAQ:
Did you initialize the SRAM using memoryInit(0x1U)?
Did you perform the PBIST to SRAM using pbistRun(0x00300020U, (uint32)PBIST_March13N_SP)?
Hi QJ,
Thanks to your helpful FAQ I manage to "resolve" my prefetch entry problem.
I'm now stuck on a data abort inside __vla_dealloc.
How is this possible?
I would understand a data abort in a vla alloc; but dealloc is completely strange to me.
I've tried to understand the allocator's internals but without success.
How can a deallocation raise a data abort?
Is there a document so I can understand how the vla malloc works? I want to tweak the heap size without using the "trial-an-error" method.
DFSR: 0x0000 040
To my understanding, the Fault status is b'11001, which implies parity/ECC error
R14_ABT: 0x0002 AC84
Which points to sys_selftest.c
How do I trigger this fault
Starting SEGGER SystemView.
This is weird, because the system has been started for a while (more than 5 sec)
Thanks for your support!
After a lot of work, I realized that a function SEGGER SystemView was sometimes called in an ISR.
The FreeRTOS port did not support being called by an ISR.
Adding logic to execute the proper function depending on the execution context solved this issue.
Thanks for your support.