PLS8-E: module crash on emergency call with SIM-PIN locked | Thales IoT Developer Community
September 27, 2019 - 11:53am, 1270 views
Working with a PLS8-E running firmware version 03.017 in Linux and with ModemManager, I see that when the module has a SIM card and SIM-PIN is not yet unlocked, a call to 112 ends up crashing the module: it disappears from the USB bus in the host system and need a manual reset in the devkit to bring it back. I haven't seen the same behavior when calling 112 and there is no SIM, or when calling 112 after SIM-PIN unlock.
Is this a known issue fixed in newer firmware versions?
Relevant ModemManager logs:
ModemManager[580694]: <debug> [1569489317.271800] Setting up in-call state...
ModemManager[580694]: <debug> [1569489317.271836] Setting up in-call ports context
ModemManager[580694]: <debug> [1569489317.271862] (ttyACM1) device open ***** is 2 (open)
ModemManager[580694]: <debug> [1569489317.271907] (ttyACM1) Setting voice in-call unsolicited events handlers
ModemManager[580694]: <debug> [1569489317.271944] (ttyACM1): --> 'ATD112;<CR>'
ModemManager[580694]: <debug> [1569489317.271991] modem is now in-call state
ModemManager[580694]: <debug> [1569489317.342478] (ttyACM1): <-- '<CR><LF>OK<CR><LF>'
ModemManager[580694]: <info> [1569489317.342582] call is started
ModemManager[580694]: <info> [1569489317.342620] Call state changed: dialing -> active (outgoing-started)
ModemManager[580694]: <debug> [1569489317.342889] (ttyACM1) device open ***** is 1 (close)
ModemManager[580694]: <debug> [1569489317.759893] (ttyACM1) unexpected port hangup!
ModemManager[580694]: <debug> [1569489317.759946] (ttyACM1) forced to close port
ModemManager[580694]: <debug> [1569489317.759962] (ttyACM1) device open ***** is 0 (close)
ModemManager[580694]: <debug> [1569489317.759980] (ttyACM1) closing serial port...
ModemManager[580694]: <debug> [1569489317.760097] (ttyACM1) serial port closed
ModemManager[580694]: <info> [1569489317.763737] (tty/ttyACM0): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.765378] (tty/ttyACM1): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.767068] (tty/ttyACM2): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.769603] (tty/ttyACM4): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.769858] (tty/ttyACM3): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.775669] (net/wwan0): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <info> [1569489317.789112] (net/wwan1): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <debug> [1569489317.789162] Removing empty device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1'
ModemManager[580694]: <debug> [1569489317.789327] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.4/1-11.4.1] unexported modem from path '/org/freedesktop/ModemManager1/Modem/0'
Hello,
I don't think it is something known, at least I wasn't able to find any similar report. Can you provide ATI1 reply? Have you possibly tried with more than one SIM card? Maybe it is somehow related to the SIM that you are using. Or have you tried without modem manager - maybe it also contributes to this problem somehow by executing some logic at the same time.
Regards,
Bartłomiej