Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Fenix22
    @Fenix22
    ah ok
    Erik Moqvist
    @eerimoq
    There were two tasks in the SDK with very small stack
    One of my interrupt handlers overflowed these tasks stack, and the program crashed
    the source code for those tasks are not open, so I cannot change the stack size easily
    Fenix22
    @Fenix22
    memory problem of coding problem?
    ah okok
    If you test all possibility?
    8000
    Erik Moqvist
    @eerimoq
    so I manually desassembled the object code and modified a few bytes to increase the stack =)
    Fenix22
    @Fenix22
    7000
    ecc...
    oh god..
    you are crazy..
    Erik Moqvist
    @eerimoq
    =)
    so, it might be a little tricky to include the new version
    Fenix22
    @Fenix22
    I thought it was your code (the size of stack)
    Erik Moqvist
    @eerimoq
    nono
    the problem was is espressif object code
    or well, I could reduce the interrupt stack usage, but that was hard
    Fenix22
    @Fenix22
    eh...
    Erik Moqvist
    @eerimoq
    I don't like this hack, and hopefully it's not needed with new ESP SDK release
    Fenix22
    @Fenix22
    anyway i think that my logic8 is not calibrated or something similar
    Erik Moqvist
    @eerimoq
    When including the new SDK it should be as a submodule instead part of the simba repository
    ??
    Fenix22
    @Fenix22
    The SDK contains the FreeRtos you say, right?
    Simba not for default
    Erik Moqvist
    @eerimoq
    yeah
    ???
    Fenix22
    @Fenix22
    how you can make a sub module?
    if the center is in the module
    blob
    time_busy_wait_us(500000);
    lol
    who is the drunked one?
    Erik Moqvist
    @eerimoq
    Just git rm -rf 3pp/ESP8266_RTOS_SDK && git submodule add ESP8266_RTOS_SDK <path to SDK on github>.
    Fenix22
    @Fenix22
    If i try Esp explode?
    Erik Moqvist
    @eerimoq
    busy wait probably disables interrupts
    Fenix22
    @Fenix22
    nono
    i disable it
    look at the time
    500000 --> 41,34ms
    lol
    Erik Moqvist
    @eerimoq
    maybe 40 ms is the longest possible busy wait?
    Fenix22
    @Fenix22
    really?
    Erik Moqvist
    @eerimoq
    what happens if you call the function twice with 40000?
    Fenix22
    @Fenix22
    1 sec
    Erik Moqvist
    @eerimoq
    40 ms busy wait is a long time
    normally only busy wait a few us
    Fenix22
    @Fenix22
    yeah yeah i kwon
    i tried this for ensure accuracy