IMP Debug Connection fails | Telit Cinterion IoT Developer Community
December 28, 2016 - 7:34am, 5939 views
Hello,
I have BGS5 module on our own pcb board. I can send at commands via USB0 and can access ffs using MES via USB0 but cannot use IMP Debug Connection on eclipse via USB0.
Why can it be? Is there a setting or configuration to be able to use IMP Debug?
Best Regards,
Hello,
did you went through all SW installation like described in Java User Guide ?
Special Debug connection have to be present in your PC.
If you already did installation please note that you schould use the same phisical USB port on your PC to avoid module name with "#" - this mean that module schould be called ......BGS5...... not .......BGS5.....#1.
This is done by windows to distinguish if more the same modules are connected to one PC - so fist is without # second with #1, third with #2 at the end.
Best regards
Lukasz
Hello Lukasz,
Thanks for the answer.
I didn't understand what you meant with #1, #2.
I installed IMP Debug Connection software properly. Actually, I can connect to another module via this connection. But with this module which is equivalent as hardware to other one, I cannot connect. I thougt maybe a parameter, setting is different between working and unworking one.
It can be a at^scfg parameter or any other parameter.
Best Regards,
Ergün.
Hi Ergun,
I'm talking about name of module which appears in Device Manager - if you connect fist time BGS5 module you got name Cinterion BGx USB Modem. If yolu connect second module to another port it will be installed and got name Cinterion BGx USB Modem #1 . Even when you use only one module but change phisical USB port on PC/Laptop you got name Cinterion BGx USB Modem #1 . This could lead to Debug problems. So the best is to use the same port like in fist installation.
Regarding settings there is one warning in Java user guide which is for serial conenction but you can check - lines below schould be configured in this way:
AT^SCFG="GPIO/mode/DCD0","std" (enables DCD0 line for ASC0)
AT^SCFG="GPIO/mode/DTR0","std" (enables DTR0 line for ASC0)
AT^SCFG="GPIO/mode/DSR0","std" (enables DSR0 line for ASC0)
Please also compare SW version of working and not working debug - response to ATI1 command - maybe there are different version (subversion A-REV could be different ).
Best regards
Lukasz
Hi Ergun,
As I understand this is working fine with one BGS5 module and is not working with the other BGS5 module.
Please start with the advices from Łukasz. Please make sure that you are using the same USB port and that only one BGS5 module is connected. Please check if the Cinterion BGS5 Java Debug Modem USB is available under modems in Device Manager and if it is possible to send commands on this port (you could also try Diagnostics tab in device properties). Maybe there is system out redirected to USB0 and this is the reason. If not please compare the AT^SCFG? outputs. Please also compare ATI1 outputs.
Then you could also paste the debug from Eclipse or Netbeans - maybe there is some useful information.
Regards,
Bartłomiej
Hi Bartlomiej,
I checked what you offered.
I could be able to connect to unworking module at the end.
I compared scfg responses of working and unworking modules. There were 3 different settings. By testing, I discovered DTR0 setting affects the situation. If DTR0 setting is "Gpio/mode/DTR0","std", it works. It was set as "gpio" previously.
Lukazs had written about DCD0, DTR0, DSR0 on previous message. But I thougt they affects debugging via asc0 not usb.
I couldn't find a note/warning in java user guide. Do you know where it is written?
Why those signals affect the situation?
Hello Bartlomiej,
I made some additional tests.
DTR0 and DCD0 affects the behavior but DSR0 does not affect.
It seems to me that it is not reasonable DTR,DCD signals of ASC0 affects the USB0 interface behavior.
What is the explanation of this issue?
When connection fails because of DTR0 or DCD0 is set to gpio, Eclipse logs are below:
Using USB port COM14.
Connecting to module...
Initializing module for debugging...
Establishing "IP connection for remote debugging of BGSx"...
Passing control to external device emulator...
The specified port is not open.
Establishment of TCP/IP connection failed!
Check the COM connection and dial up network parameters!
*** Error ***
Device "IMP_NG_BGS5_REMOTE1" not registered!
End of debug session. Emulator is closed!
Hello,
I'm happy that it's finally working.
This information is written in the Java User's Guide. Please see chapter 10.1.2 Emulator:
"This dial-up network (DUN) connection is installed automatically together with the required modem
device during installation of the CMTK. The emulator always uses the serial port configured
for this DUN connection.
To successfully setup the DUN connection for ODD over the serial interface, the three lines
DCD0, DTR0 and DSR0 should be configured using the following AT commands:
• AT^SCFG="GPIO/mode/DCD0","std" (enables DCD0 line for ASC0)
• AT^SCFG="GPIO/mode/DTR0","std" (enables DTR0 line for ASC0)
• AT^SCFG="GPIO/mode/DSR0","std" (enables DSR0 line for ASC0)
It is possible to use any of the three serial interfaces (USB, ASC0, ASC1)..."
USB is also a serial interface here.
Regards,
Bartłomiej
Hello Bartlomiej,
Thanks for the answer.
My java user guide document was version 1 and an explanation like that didn't exist there. I read Java User guider version 4 having that explanation.
On that lines, in parenthesis, "enables *** line for ASC0" is written. (***=DCD0 or DTR0 or DSR0)
In my opinion, these at^scfg settings are for ASC0. In following lines, there is explanation about ASC1 and it is written, there can be some problems because of ASC1 has no DTR,DCD lines. If that commands were for all interfaces, there would be no need for ASC1.
On the other hand, is it possible USB uses DTR,DCD,DSR lines of another port, asc0? USB communication is provided via only RX,TX pins.
It seemed to me somewhat confusing.
Hello Ergun,
These commands configure the DCD0, DTR0 and DSR0 lines of ASC0 interface.
These lines are not used by USB interface but they are needed by the debugger (on the module) to work. This information might not have been placed in the early versions of the document. It was added later as document improvement.
Regards,
Bartłomiej
Hello Bartlomiej,
Thanks for the explanations.
Then, I'm concluding that about the issue : To be able to use online debugging over USB0 and ASC0, DCD0-DTR0-DSR0 lines is needed and they should be configured as mentioned. For ASC1, these lines are not used. Since ASC1 hasn't got DCD-DTR-DSR lines, it is not recommended to use ASC1 for this purpose.
Best Regards,
Pages