Can't access GPIO on EHS6 | Thales IoT Developer Community
November 5, 2014 - 10:15am, 10834 views
Hi all,
Until few days ago I had no problems reading and writing IO's using the AT commands on my evaluation board and my own board.
After using my latest midlet version, I can't access the GPIO on both boards.
Here are some traces from commands I've tried already:
Normal 0 false false false EN-US X-NONE HE MicrosoftInternetExplorer4
/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"***** New Roman","serif";}
at OK
AT^SGIO=6 ERROR
AT^SCPIN=? ERROR
at OK
AT^SCPIN=? ERROR
AT^SCPIN=1,4 ERROR
AT+CMEE=2 OK
AT^SCPIN=1,4 +CME ERROR: Unknown
AT^SCPIN=0,4 +CME ERROR: Unknown
AT^SCPIN=0,4 ERROR
^SYSINFO: 200
AT^SCPIN=? ERROR
AT^SCPIN=1,4 ERROR
AT^SCPIN=1,4,0 ERROR
AT^SCPIN=1,4,1 ERROR
AT^SCFG=? ^SCFG: "Call/ECC",("0"-"255")
^SCFG: "Gpio/****/ASC1",("std","gpio","rsv")
^SCFG: "Gpio/****/DAI",("std","gpio","rsv")
^SCFG: "Gpio/****/DCD0",("std","gpio","rsv")
^SCFG: "Gpio/****/DSR0",("std","gpio","rsv")
^SCFG: "Gpio/****/DTR0",("std","gpio","rsv")
^SCFG: "Gpio/****/FSR",("std","gpio","rsv")
^SCFG: "Gpio/****/HSIC",("std","gpio","rsv")
^SCFG: "Gpio/****/PULSE",("std","gpio","rsv")
^SCFG: "Gpio/****/PWM",("std","gpio","rsv")
^SCFG: "Gpio/****/RING0",("std","gpio","rsv")
^SCFG: "Gpio/****/SPI",("std","gpio","rsv")
^SCFG: "Gpio/****/SYNC",("std","gpio","rsv")
^SCFG: "GPRS/AutoAttach",("disabled","enabled")
^SCFG: "Ident/Manufacturer",(25)
^SCFG: "Ident/Product",(25)
^SCFG: "MEopMode/SoR",("off","on")
^SCFG: "MEShutdown/Fso",("0","1")
^SCFG: "Radio/Band",("1"-"511")
^SCFG: "Radio/OutputPowerReduction",("0","1","2","3","4")
^SCFG: "Serial/Interface/Allocation",("0","1","2","3"),("0","1","2","3")
^SCFG: "Serial/USB/DDD",("0","1"),("0"),(4),(4),(4),(63),(63),(4)
^SCFG: "Tcp/IRT",("1"-"60")
^SCFG: "Tcp/MR",("1"-"30")
^SCFG: "Tcp/OT",("1"-"6000")
^SCFG: "Tcp/WithURCs",("on","off")
^SCFG: "Trace/Syslog/Otap",("0","1"),("null","asc0","asc1","usb","usb1","usb2","usb3","usb4","usb5","file","udp"),("1"-"65535"),("0"-"125"),("buffered","secure"),("off","on")
^SCFG: "Userware/Autostart",("0","1")
^SCFG: "Userware/Autostart/Delay",("0"-"10000")
^SCFG: "Userware/DebugInterface",,("0"-"255"),("0"-"225"),("0","1")
^SCFG: "Userware/DebugMode",("off","on")
^SCFG: "Userware/Passwd",("0"-"8")
^SCFG: "Userware/Stdout",("null","asc0","asc1","usb","usb1","usb2","usb3","usb4","usb5","file","udp","system"),("1"-"65535"),("0"-"125"),("buffered","secure"),("off","on")
^SCFG: "Userware/Watchdog",("0","1","2")
OK
Thanks in advance,
Shaul
Could be that GPIO's all allreday used by some other midlet? Or that you use them before AT commands here?
Thanks for the response.
I don't have any other midlet installed but my own(3GApplication) and the default:
AT^SJAM=4 ^SJAM: "a:/3gApplication.jad","3gApplication MIDlet Suite","MIDlet Suite Vendor","1.0.0",1,263285,0
^SJAM: "a:/JRC-1.50.9.jad","Java Remote Control MIDlet Suite","Cinterion","1.50.9",1,669007,0
Sry, don't know what else could be producing error because only time when I got Error on such calls was, when I allready defined GPIO's before.
Can you post all AT commands that you issue? Just cheking but you probably started with AT^SPIO=1?
Reagrds
Jure
Thanks!
I did, also an error:
AT+CMEE=2 OK
AT^SPIO=0 +CME ERROR: Unknown
AT^SPIO=1 +CME ERROR: Unknown
Also your SCFG that you posted isn't ok. You should call it like this:at^scfg? not like at^scfg=? because AT command and after it =? will allways return you set of options and not what the current options are. But unfortunaly I don't know what other problem could it be.
Regards
Jure
Hi Shaul,
Please provide some more information.
First issue at^scfg? command and paste the result. Some GPIO lines are shared with other interfaces. For example GPIO4 is shared with Fast Shutdown line, and GPIO6 with Pulse Width Modulation. You will find more in the AT Commands Specification document.
Is your MIDlet running when you try to issue these commands? What is your application doing? Does it use GPIO, change any module configuration or use some hardware interfaces?
Regards,
Bartłomiej
Hi Barttomiej,
The midlet is not running, I'm trying to acces the GPIO using terminal (AT commands) after I saw the GPIO is not working.
My midlet is opening a soket and connect to our server. I did change hardware interfaces (sdtou to ASC1).
For this example I've tried to read almost every GPIO, they all returned an error.
This is the latest scfg:
at^scfg? ^SCFG: "Call/ECC","0"
^SCFG: "Gpio/****/ASC1","rsv"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","std"
^SCFG: "Gpio/****/DSR0","std"
^SCFG: "Gpio/****/DTR0","std"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/HSIC","std"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","std"
^SCFG: "Gpio/****/SPI","rsv"
^SCFG: "Gpio/****/SYNC","gpio"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","0","0"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/Otap","0"
^SCFG: "Userware/Autostart","0"
^SCFG: "Userware/Autostart/Delay","100"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","0"
Hi Shaul,
You have disabled autostart. In this case none of the installed MIDlets is started automatically including the Cinterion Java Remote Control MIDlet, which realizes some of the module's functionality. And that is probably why you have problems with GPIO.
Please enable autostart: "at^scfg="Userware/Autostart","","1"", restart the module and test the GPIO again.
Best regards,
Bartłomiej
Thanks, it works, but the reason I've turned off auto start it's because I'm having a problem with the auto start.
Every time I'm running my application in auto start the midlet is running but couldn't connect to the server and when I'm running the same midlet without auto start it's able to connect to the server.
I would appreciate some help on that manner.. Thanks!
This is the trace with the auto start on (unable to connect to the server):
01/01/04 00:03:33.289 - Connecting To : [socket://212.199.160.161:9999;bearer_type=gprs;access_point=internetg;timeout=1200] attempt number 1 from 5
01/01/04 00:03:33.295 - Start open, connection URL: socket://212.199.160.161:9999;bearer_type=gprs;access_point=internetg;timeout=1200
01/01/04 00:03:33.313 - ** Profile could not be activated
This is the trace with the auto start off:
01/01/04 00:02:33.811 - Connecting To : [socket://212.199.160.161:9999;bearer_type=gprs;access_point=internetg;timeout=1200] attempt number 1 from 5
01/01/04 00:02:46.740 - Start open, connection URL: socket://212.199.160.161:9999;bearer_type=gprs;access_point=internetg;timeout=1200
01/01/04 00:03:40.117 - ConnectData:
Shaul
If you don't want midlet autostarting, you can change midlet descriptor where you have autostart option.
Is it posible that midlet on autostart is trying to connect even before connects to cell phone network? You can try to set delay for autostart midlet.
Pages