ESP8266 Community Forum

- Fri Jun 01, 2018 5:19 pm #76206 Any suggestions would be greatly appreciated. thanks.

delay() in promiscuous callback causes a crash.

wifi_set_promiscuous_rx_cb(promisc_cb);
void promisc_cb(uint8_t *buf, uint16_t len) {
delay(1)
}

Exception (9):
epc1=0x40104de0 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000003 depc=0x00000000

ctx: sys
sp: 3ffffd60 end: 3fffffb0 offset: 01a0

stack>>>
3fffff00: 00000000 00000000 00000020 40100ec6
3fffff10: 4010500c 00234f61 3ffee9e0 00000000
3fffff20: 3ffee320 3ffee9e0 3ffee8fc 00000000
3fffff30: 00000000 00234e29 40201340 00000001
3fffff40: 3ffee9e0 00000000 3fff06ae 3ffefc20
3fffff50: 3ffee938 3ffee938 3ffefc20 40202485
3fffff60: 0000002a 00000029 3ffee320 402012c0
3fffff70: 40228f88 3ffee2f8 3ffee320 3ffe91a8
3fffff80: 3fffdcc0 00000000 3fff0684 40221930
3fffff90: 40221b1e 3fffdab0 3ffeebac 40202fdb
3fffffa0: 3ffe91a8 40000f49 3fffdab0 40000f49
<<<stack<<<

- Fri Jun 01, 2018 6:07 pm #76208

Any suggestions would be greatly appreciated. thanks.

delay() in promiscuous callback causes a crash.

wifi_set_promiscuous_rx_cb(promisc_cb);
void promisc_cb(uint8_t *buf, uint16_t len) {
delay(1)
}

Exception (9):
epc1=0x40104de0 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000003 depc=0x00000000

ctx: sys
sp: 3ffffd60 end: 3fffffb0 offset: 01a0

stack>>>
3fffff00: 00000000 00000000 00000020 40100ec6
3fffff10: 4010500c 00234f61 3ffee9e0 00000000
3fffff20: 3ffee320 3ffee9e0 3ffee8fc 00000000
3fffff30: 00000000 00234e29 40201340 00000001
3fffff40: 3ffee9e0 00000000 3fff06ae 3ffefc20
3fffff50: 3ffee938 3ffee938 3ffefc20 40202485
3fffff60: 0000002a 00000029 3ffee320 402012c0
3fffff70: 40228f88 3ffee2f8 3ffee320 3ffe91a8
3fffff80: 3fffdcc0 00000000 3fff0684 40221930
3fffff90: 40221b1e 3fffdab0 3ffeebac 40202fdb
3fffffa0: 3ffe91a8 40000f49 3fffdab0 40000f49
<<<stack<<<

Putting something like delay() into something called by a system cb which may potentially be interrupt driven is asking for trouble; it can corrupt the stack. Why would you want a delay anyway? If what you show is a complete example, then in any case a delay is meaningless as it just delays the function exit.
When using asynchronous architecture (e.g. Callbacks) a delay makes no sense.
There is a crash/stack analysis tool available which can sometimes help - I haven't used it myself, there are references to it on this forum.

- Fri Jun 01, 2018 6:30 pm #76209 Hi,
That was my complete actual code. I just posted that for simplicity and that it self will create the crash.
Yes, I gather there is something wrong with mixing a system call back with Arduino code. But there must be an alternative.
Thanks

- Fri Jun 01, 2018 6:32 pm #76210 Sorry, I meant that wasn't...