at^sjmsec command on PLS62-W throwing error ^SJMSEC: 1,"wrong command format". Any ideas? | Telit Cinterion IoT Developer Community
August 21, 2019 - 10:47am, 2010 views
Hi all,
I am trying to connect to amazon aws, and I am running into an issue when installing the certificates onto the PLS62W board. The command I am executing is as follows:
at^sjmsec="File","AddHttpsClientCertificateUntrusted.bin"
^SJMSEC: 1,"wrong command format"
ERROR
And even if I remove the quotes around the filename as I have seen others on this forum do, it still throws the same error
at^sjmsec="file",AddHttpsClientCertificateUntrusted.bin
^SJMSEC: 1,"wrong command format"
ERROR
My sjmsec? is:
at^sjmsec?
^SJMSEC: 1,0,1,0,0,0
OK
and at^scfg?
at^scfg?
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","rsv"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","rsv"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/HWAKEUP","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","std"
^SCFG: "Gpio/****/SYNC","std"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","PLS62-W"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/CregRoam","0"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
^SCFG: "MEopMode/Prov/AutoSelect","off"
^SCFG: "MEopMode/Prov/Cfg","attus"
^SCFG: "MEopMode/RingOnData","off"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MeOpMode/SRPOM","0"
^SCFG: "Radio/Band/2G","0x00000074"
^SCFG: "Radio/Band/3G","0x0004019B"
^SCFG: "Radio/Band/4G","0x080E08DF"
^SCFG: "Radio/Mtpl/2G","0"
^SCFG: "Radio/Mtpl/3G","0"
^SCFG: "Radio/Mtpl/4G","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "RemoteWakeUp/Ports","current"
^SCFG: "RemoteWakeUp/Ports","powerup"
^SCFG: "Serial/Ifc","0"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","005B","Cinterion Wireless Modules","PLSx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "Urc/Ringline","local"
^SCFG: "Urc/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","usb1",,,,"off"
^SCFG: "Userware/Watchdog","0"
OK
Any ideas? I am stumped.
Hello,
Probably there's some problem with the certificate file. It must be incorrect.
I have just reproduced this error by uploading some dummy text file instead of a certificate.
Best regards,
Bartłomiej
Hi,
Thanks for the reply. I am following the instructions provided in https://iot-developer.thalesgroup.com/showcase/concept-board-connection-amazon-aws-iot-cloud-mqtt-protocol.
The Files are downloaded directly from AWS, and I have not modified them. Could it be the tool that I am using to convert to bins? Are those tools specific to a board?
CA certificates from: https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html#server-authentication
Where I am using https://www.amazontrust.com/repository/AmazonRootCA1.pem
The private file and key are from the 1-click download on aws.
Regards,
Gareth
Apologies, I forgot to mention that I am using the EHSx tools that are for the concept board, despite the fact I am using the PLS62-W board.
Kind regards,
Gareth
Hello,
As far as I know It should not matter - I have successfully been using single certificate files on different platforms. The source certificate file should be binary encoded.
Could you paste example log of all the steps you do?
Regards,
Bartłmiej