EHS5-E not responding. How to restore to default? | Thales IoT Developer Community
August 26, 2015 - 1:37pm, 6721 views
Hi guys!
Can anyone tell me how to reset the EHS5-E module on the B80 Starter Kit. I had initially loaded the HelloWorld sample code without providing support for the AT command library. So there is no response for AT commands set. Every time I power on the device, I get the following message on the COM port. (in hex) 3F 3F 0A 10 14 FA 3F 3F 0A 02 50. Please do revert.
Thanks
SRN7
Are you sure you have set the proper baudrate on this interface? What about other USB interfaces (USB4, USB5..) ? Are you able to send AT commands there? What interface you are using for now?
Best regards,
Michał
Hi Michal,
I am using the ASC0 USB interface. I have tried with different baud rates. I have also tried a firmware upgrade of the chip.
But the firmware upgrade failed midway and now I am not able to receive anything on the COM ports too.
I have not tried on other USB interfaces. How can I do that? I am not receiving any responses for the AT commands whatsoever.
Thanks
SRN7
I was wondering if there is some way whereby I can short a few pins on the board to put it into some kind of bootloader **** and then somehow wipe everything back to factory ****?
Hi,
Can you tell more about the FWs versions which you are using? What was the original FW what version you are doing for update? In the current state what happens when you connect the module via the USB to the PC.
I understand that you are using ASC0 for the update? Can you try to do it with the smaller baudrate? (e.g. 115200)
Best regards,
Michał
Hi,
I am using the firmware revision 03.001. Before turning into a brick, this is what I used to get on ATI command.
In the current state, the board is being recognized as a COM port (COM3). But I get no response from it. No reply to any commands. Firmware update fails. I cannot load the code using Eclipse IDE. I get the error message "Failed to turn ON module".
Yes I am using ASC0 for the update.
I have tried it with the baudrate 115200 with no success.
Thank you for the reply!
SRN7
It is normal that when the module does not contain an integral FW on it, it will not accept any SW from the IDE.
As for the FW update. When you are using gWinSwup, you have a module switched ON or OFF? If off, does it power on by the swup app, after starting the update?
What do you mean by ", the board is being recognized as a COM port (COM3)" if the module is connected with the ASC0 you should have a com port permanenly enabled on the PC, because it is an internal PC's port. PC should not react in any kind when pluging or upluging module.
Could you also descrive the HW setup which you are using? How the module is connected to the PC? Are you using any USB-RS232 converters?
Best regards,
Michał
Hi Michał,
When I am using gWinSwup, the module is switched ON by me. If it is switched OFF, it is not being powered ON by the swup app. After starting, the update fails.
This is the error that is received. This is the view under device manager:
I am connecting the Cinterion EHS5-E on Starter Kit B80 using ASCO port to the PC via USB Y-cable.
No I am not using any USB-RS232 converters. Neither am I using the other USB ports or ASC1 port.
Thanks
SRN7
Hello,
Were you able to execute at command on the ASC0 interface before the problem happened?
HelloWorld application is just a sample which send some AT commands and it does not affect the possibility of sending AT commands from the terminal on the HW interfaces.
If you had some problems with accessing ASC0 interface this may be a reason why gWinSwup failed and maybe it also didn't manage to delete the firmware.
Have you tried to connect to USB interface on the board instead of ASC0?
BR,
Bartłomiej
Hello,
I was able to execute the AT commands before the problem happened.
What are the steps to be performed after connecting the board to the USB interface. I am able to see the USB ****m when connecting using USB port :
Please explain the steps as much as possible.
Thanks,
SRN7
Hello,
Please double click the Debug Modem USB to check the port name and try to communicate with the module on that port.
You should also see some new port under Ports.
Just you need to disconnect all USB connections while you reset the module to have the possibility to connect after reset.
You may also try to load the firmware over Debug Modem USB connection.
Regards,
Bartłomiej
Pages