[feature req]restart traces after wcpu reset

IoT Modules Development tools
1

To my knowledge, enabling the gsm-stack after a at+cpof requires a restart (at+cfun=1)

but traces won’t continue after that restart without re-enabling them.
and as only a limited amount of traces is kept in local memory, getting that 3am bug is getting kinda troublesome

of-course this would need to be a selectable feature, as not everyone might want to use this behavior

2

Agreed!

If the unit restarts for any reason, it would be useful to have an automatic facility to restart tracing…

3

Already logged as an important enhancement, to be integrated ASAP.

4

my knowledge got expanded :stuck_out_tongue:
you can use at+cfun=1,0 to restart the gsm stack without resetting the module :smiley: