Closed jacek12345 closed 1 year ago
Is this ust a normal Rainmaker project with your own params and the Provisioning timeout reduced to 2 min, with no other changes?
Generally yes. + nimble for communication with sensors. No changes in RainMaker core. Only using available RainMaker API. Also using own NVS for devices and params storage. With no POP. And this change https://github.com/espressif/esp-rainmaker/issues/222#issuecomment-1396806804
without change #222 i have stack overflow when Debug enabled and this is a few rows earlier than last assert failed (that was with #222 added) so think that both are lack of memory issues. If disable Debug logging (free some memory) it works again (meaby on the "bleeding edge")
D (15095) protocomm_nimble: UUID did not match... 51
D (15095) protocomm_nimble: UUID (0x51) matched with proto-name = prov-session
D (15105) security1: Request to handle setup0_command
D (15115) gdma: new group (0) at 0x3fcc2634
D (15115) gdma: new pair (0,0) at 0x3fcc2670
D (15125) gdma: new
***ERROR*** A stack overflow in task ble has been detected.
Increased nimble stack and seems to be good now also with #222 and with debug enabled
I also have this problem, how to solve it?
Increase memory for nimble stack
Everything works for some time. Since some moment i can't make provisioning. The only thing that fix it is erase-flash command. Then it works for some time. I enabled Debug in menuconfig and see
assert failed: spinlock_acquire spinlock.h:123 ((result == SPINLOCK_FREE) == (lock->count == 0))
Whole log: