Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Cellular Hardware > Problematic behavior of GPIO4 in the EHS5

Problematic behavior of GPIO4 in the EHS5 | Telit Cinterion IoT Developer Community

Like
0
5
interbin's picture
interbin

April 3, 2019 - 12:01pm, 2676 views

Hello,

After powering the EHS5, GPIO4 is HI and after 1 second goes LOW.
It occurs in Rev3. Not in Rev2.

This is problematic because I use this pin for hardware reset trigger, and I need Rev 3

Is there any solution to change that GPIO4 behavior?

5
Comment
Log in or register to post comments
Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Apr 3 2019 - 4:18pm

Hello,

This line is shared between GPIO4 and fast shutdown functionality which both are mutually exclusive. However this design is the same for revision 2 and 3. Please check AT^SCFG? output to verify if the line is configured properly. Please also send ATI1 reply. Is any hardware connected to this line while you make the test? It might also be possible that this hardware is causing such problems. Was the design changed? 

Best regards,

Bartłomiej

interbin's picture
interbin
Apr 4 2019 - 9:53am

Thanks for reply.

I unconnected any external hardware from GPIO4 for test.
The GPIO4 still goes LOW after second from powering.
Rel2 and Rel3 behave different on the same EHS5.

Rel2 is OK, Rel3 not.


ati1
Cinterion
EHS5-E
REVISION 03.001
A-REVISION 00.000.42



at^scfg?
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Ecall/AckTimeout","5000"
^SCFG: "Call/Ecall/Callback","0"
^SCFG: "Call/Ecall/CallbackTimeout","43200000"
^SCFG: "Call/Ecall/Msd","0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
^SCFG: "Call/Ecall/Pull****","0"
^SCFG: "Call/Ecall/SessionTimeout","20000"
^SCFG: "Call/Ecall/StartTimeout","5000"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","std"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","std"
^SCFG: "Gpio/****/DSR0","std"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","std"
^SCFG: "Gpio/****/SPI","rsv"
^SCFG: "Gpio/****/SYNC","gpio"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS5-E"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Dormancy","0","0"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","147"
^SCFG: "Radio/Mtpl","0"
^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: "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","null",,,,"off"
^SCFG: "Userware/Watchdog","1"

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Apr 5 2019 - 1:34pm

Hello,

Are you going to use rev3 modules for your project? Currently we have revision 4. I'd suggest you to contact your local technical sales.

I've tried this on rev3 and I've also seen a line toggling on start. For now I can't see a way to get rid of this behavior. But I don't see this toggling on rev4. If you're going to use rev3, you can choose some other GPIO line if it is possible for you. 

I can see that this problem was also reported to the support line. Please also keep track on it there. 

Best regards,

Bartłomiej

interbin's picture
interbin
Apr 5 2019 - 1:55pm

Thanks for your help.

We reported this problem to the support line but this problem  was not resolved, so I decided write about this here.

I can't change GPIO line because we have a lot of manufactured modems.

Changing revision is also very problematic for us.

Regards

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Apr 8 2019 - 4:40pm

Hello,

Revision 4 requires the new hardware so it is not the option if already have the devices and modules.

As for the support line the problem is analyzed - if you have access to SF, please write any question or additional information that might be helpful. Or please ask your TS if you don't have a direct access.

Regards,

Bartłomiej