Hi Lasse,
> There's nothing you can do in GAtChat at this point. Having
the
> unsolicited response handler fire and consume lines before the pending
> AT command handler won't work either. If you're not convinced, try
> handling solicited / unsolicited CREG/CGREG and friends.
Okay, good to know this, I was not aware. Perhaps I need to reconsider
the way forward with this issue, we could change the startup sequence of
different drivers and that way get around this issue.
I suggest putting devinfo on separate multiplexer channel from the one
receiving the STKI notification. Or we might have to consider extending
gatchat with 'blacklist' prefixes instead of 'whitelist'.
Regards,
-Denis