MrZANE

Forum Replies Created

Log In Register Lost Password
Viewing 8 posts - 16 through 23 (of 23 total)
1 2
  • Author
    Posts
  • January 10, 2020 at 13:59 in reply to: Adding additional memory segment crashes if I don't use Fixed-size stack &Heap #27015
    MrZANE
    Participant

    Thanks for the info about the stack.

    Hopefully I will sort out the rest myself.

     

    Kind regards

    Jimmy

    January 9, 2020 at 18:15 in reply to: Adding additional memory segment crashes if I don't use Fixed-size stack &Heap #27013
    MrZANE
    Participant

    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?

    January 9, 2020 at 18:09 in reply to: Adding additional memory segment crashes if I don't use Fixed-size stack &Heap #27011
    MrZANE
    Participant

    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 happens

    January 9, 2020 at 10:28 in reply to: Adding additional memory segment crashes if I don't use Fixed-size stack &Heap #27006
    MrZANE
    Participant

    After changing to software floating point I got some more info in the callstack:

    Callstack

    December 6, 2019 at 15:26 in reply to: Get CPU device from code (build defines) #26762
    MrZANE
    Participant

    That works just fine.

    Thanks for your help.

    Kind regards

    Jimmy

     

    April 25, 2019 at 14:08 in reply to: Request: support for Kendryte K210 (Sipeed M1 modules) #24779
    MrZANE
    Participant

    Here is a summary of the k210 features:

    https://loboris.eu/forum/showthread.php?tid=878

    May 1, 2017 at 22:25 in reply to: ESP32 Toolchain Update #11122
    MrZANE
    Participant

     

    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.

    May 1, 2017 at 20:49 in reply to: ESP32 Toolchain Update #11120
    MrZANE
    Participant

    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

  • Author
    Posts
Log In Register Lost Password
Viewing 8 posts - 16 through 23 (of 23 total)
1 2