Forum Replies Created
-
Posts
-
Would it work if I create a memory area at the same address in both linkfiles and used attribute to place the buffer in that area?
If so what variable is it that needs to be placed like this?
I understand, no worries.
Would you mind answering the following questions though? Please 🙂
When NOT using fixed heap&stack framework how is the memory for stack & heap calculated and distributed?
Where can I see this in the build outputs?Is there any tools in VisualGDB to analyze hardfaults, other than reading CFSR register and manually decoding?
What I can’t really understand is why moving a const. array (flash) should change the stack/heap usage (RAM).
If that is the case I fully understand that you can’t help me, but I would be grateful if you could just have a look at my questions and what I’ve found below.When NOT using fixed heap&stack framework how is the memory for stack & heap calculated and distributed?
Where can I see this in the build outputs?Is there any tools in VisualGDB to analyze hardfaults, other than reading CFSR register and manually decoding?
This is the calculated call stack usage
This is from running the code, stopped on just the printf that will cause a hardfault (btw. iass, the float to be printed, has a value of 0.0489999987)
As I see it there should be plenty of stack left as I don’t use any heap at all (at that time), unless the automatic stack/heap setup is strange in some way.
Or is there something I’m missing?Breaking news:
CFSR = 0x8200 => BFARVALID = 1, PRECISERR = 1
Seems like a busfault trying to access address 0xe747ae94 (From BFAR register)
Now the question is why that happensHere is a summary of the k210 features:
Ok, Sounds like a little bit more work then 😉
I’m confident you’ll work it out, I just have to hope it’s in place when I (hopefully) get the project.Best of luck.
That sounds great.
I am possibly going to use the ESP32 to an important project in about a months time.
It would be really great if you could also check out the newly implemented trace functionality (about a week old) and see if you could integrate this in a way so it works with visual studio/visual gdb.
This would help alleviate debugging with regards to the restricted breakpoint functionallity in the ESP32.Thanks in advance
