Autodetect device for new projects in DS showing no ports


#1

Hi Guys,

I was wondering if you could help me find out why none of my ports are appearing in the autodetect stage of creating a new project in Developer Studio.

I have ports installed as shown in the device manager screen shot;

[attachment=1]DeviceManagerPorts.png[/attachment]

but still nothing appears in DS.

[attachment=0]NewOpenATProjectAutoDetect.png[/attachment]

Any ideas, anyone?


#2

I also cannot successfully debug my SL8082T using the dev kit (receiving AT stuff via putty works fine - and I made sure I closed putty before using DS!)


#3

Please can you post here a technical report archive (Help > Build Technical Report) in order to let us analyze the logs?


#4

Ok, hopefully this contains what you need.


#5

Thanks for the report.
Please can you confirm the issues you have:

  • in the project creation wizard, you don’t have any port displayed on the “Auto detection” tab, while the ports are correctly appearing in the Target Management perspective. Correct?
  • In the target management perspective, you see the port but you can’t even connect to it, send AT commands, etc… Correct? Do you get error messages while trying to connect? can’t see any error in the logs, actually…

#6

Ok, so I wasn’t aware of the target management perspective until you mentioned it (I had to open it from the list).

In that perspective I do see COM ports - 1, 3 and 10. I have no idea why COM3 appears as no device is assigned to that.

The interface does say ‘2 errors detected’ next to ‘Target Status & Configuration’ - but I cannot find where it actually tells you what these are.

If I try to open COM1 (motherboard serial port) I get the following error dialogue, though:

Open and load local port COM1 => ERROR: An error ocurred during HAPC AT test
Open and load physical port COM1 => ERROR: An error ocurred during HAPC AT test
Open port COM1 => DONE: Port opened
Open port COM1 => DONE: Port opened
Load informations from target => ERROR: An error ocurred during HAPC AT test
Waiting for module detection => DONE: Target detected sn:CEM0183053730 baudrate:115200
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test

The ‘Hello World from Open-AT’ periodic message is appearing on the console, however.

Trying to connect via COM10 (USB serial port for dev kit) - it just times out.


#7

The error log trends to show that the device is locked in development mode on another (device’s) port.
Give a try to send the AT+WDM=0 command, and reset the device.
From there, refresh the target status view: information loading should run fine (we have some clues to improve the detection of such a use case).
Concerning error messages, you’ll have tooltip messages explaining the errors/warnings when you pass the mouse over the “X errors” message in the view status line.


#8

I seem to have got it working on the motherboard com port after trying what you suggested and a bit more fiddling around, thanks.

I still cannot, however, get it to work on COM10 (the USB one) - also, when I monitor the hello world program via this port on PuTTY, the text is corrupted - could there be something going wrong with the USB driver, here? (My system is Win 7 Pro x64)

Is it supposed to be possible via the USB port? I ask because ideally I’d like to have the UART free to communicate with another device if this is possible (the aim is to work in target mode).


#9

OK, so the target management page is showing all the right information, but I still cannot debug the hello world project properly. Also, now when I return to target management it is once again not working. Am I doing something wrong? I’m getting fairly lost here…

EDIT - it appears I needed to restart DS and push the reset button on the dev kit to get the target management console working again. I will continue to try to get it to debug…


#10

After restarting both - if I start DS and connect in the target management perspective in development mode (using COM1, the motherboard serial port - I cannot get COM10, the USB one, to work), all the fields are populated properly and the TMConsole shows the hello world messages with no problems.

If I then go to the applications perspective and select debug for the hello world project (using COM1) I get the following error:

Preparing the target for launch => ERROR: An error ocurred during HAPC AT test
Open and load physical port COM1 => ERROR: An error ocurred during HAPC AT test
Open port COM1 => DONE: Success
Open port COM1 => NO NEED TO DO IT: Success
Load informations from target => ERROR: An error ocurred during HAPC AT test
Waiting for module detection => DONE: Target detected sn:CEM0183053730 baudrate:115200
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test

After this error, if I return to the target management perspective, the functions like refresh and sync the RTC no longer function and if I close and try to reopen the port I get the following error:

Open and load local port COM1 => ERROR: Time out: 20000ms
Open and load physical port COM1 => ERROR: Time out: 20000ms
Open port COM1 => DONE: Port opened
Open port COM1 => DONE: Port opened
Load informations from target => ERROR: Time out: 20000ms
Waiting for module detection => ERROR: Time out: 20000ms

For the sake of completeness - this is the error I get when I try to open COM10 before trying to debug:

Open and load local port COM10 => ERROR: Time out: 20000ms
Open and load physical port COM10 => ERROR: Time out: 20000ms
Open port COM10 => DONE: Success
Wait for USB port to reconnect => NO NEED TO DO IT: Success
Open port COM10 => DONE: Port opened
Pause : 1000 milliseconds => NO NEED TO DO IT: Success
Load informations from target => ERROR: Time out: 20000ms
Waiting for module detection => ERROR: Time out: 20000ms

And after trying to debug:

Open and load local port COM10 => ERROR: An error ocurred during HAPC AT test
Open and load physical port COM10 => ERROR: An error ocurred during HAPC AT test
Open port COM10 => DONE: Success
Wait for USB port to reconnect => NO NEED TO DO IT: Success
Open port COM10 => DONE: Port opened
Pause : 1000 milliseconds => NO NEED TO DO IT: Success
Load informations from target => ERROR: An error ocurred during HAPC AT test
Waiting for module detection => DONE: Target detected sn:CEM0183053730 baudrate:null
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Production mode and check => NO NEED TO DO IT: Success
Waiting for module detection => NO NEED TO DO IT: Success
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Production mode and check => NO NEED TO DO IT: Success
Waiting for module detection => NO NEED TO DO IT: Success
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test
Switch to Development mode and check => ERROR: An error ocurred during HAPC AT test
Switch to Production mode and check => NO NEED TO DO IT: Success
Waiting for module detection => NO NEED TO DO IT: Success
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => ERROR: An error ocurred during HAPC AT test


#11

Another new error message.

Wiped the workspace, started fresh, new project with hello world example created. When I try to debug it I get the following error/warning dialogue:

“Connected module seems to be blocked in bootloader mode. Developer Studio won’t be able to perform any checks before launching the download. Please press OK to launch the download procedure.”

Is there someone I can call for real-time support? If I cannot get started on development soon then the project will fail…


#12

More info:

After playing with the demo code I can tell when the device has and has not been programmed properly, and it seems even when the target management connection or the debug fails - the result is generally a success (ie either the traces come through or the module appears to actually be programmed with the new software). This suggests that it is the verification parts of the communication that fail rather than anything - is some crucial data being corrupted…

If I connect via COM10 (USB) on PuTTY the text data is certainly corrupted, and in early tests sending text messages (SMS) via AT commands over COM10 also resulted in corrupted text…


#13

Which FW version is currently running on your device?
Can you just copy/paste the ATI9 command answer here?


#14

interesting point - it seems to be case sensitive on that command, so only ‘ati9’ worked.

Here is what I get:

“DWL”," S4_1_0_7BT R1431 CNSZXD00000155 2012/11/19 16:06:52","",“Sierra Wireless”,0,"",“00000000”,“00000000”
“FW”,“FW_750_20_A1_25.SL808Fx”,“R7.50.0.A1.201212171435.SL8082T”,“Sierra Wireless”,1670256,“121712 14:35”,“648de921”,“10002020”
“MODEM 3G+”,“Revision: S4_1_0_7AP R1431 CNSZXD00000155 2012/11/19 16:06:52”
“OAT”,“1.0.0.20130708170259”,“hello_world Sample”,“The University of Manchester”,69216,“070813 17:04”,“8a53fc86”,“10700000”
-“Developer Studio”,“2.3.1.201305211601-R11859”
-“Open AT Application Framework package”,“2.50.0.A1.201302131145”
-“Open AT OS Package”,“6.50.0.A1.201302051441”
-“Firmware Package”,“7.50.0.A1.201302131100”
-“ExtendedATApplication Library Package”,“1.20.0.A1.201302130931”
-“Internet Library Package”,“5.53.0.A1.201211071132”
-“Location Library Package”,“1.4.2.201211191040”
-“Security Library Package”,“1.15.0.A1.201302081338”
“ROM”,“8400000”
“RAM”,“4000000”
“OATRAM”,“b00000”
“DWLNAME”,“SL808x”

EDIT: Bizarre addendum - today the target management will only work with the USB connection and I cannot get the module to respond on the physical port (COM1)… It times out at the ‘waiting for module detection’ phase… I also cannot get the AT uns messages and traces from the hello world program any longer…

When I listen on COM1 via PuTTY I get corrupted messages - could this be an alignment problem? The hello world program is set to every 5 seconds, and I get new gibberish every 5 seconds, so it looks like it’s executing the program now…

An example of the gibberish, although I don’t think the bit pattern will be preserved when pasting text:

Foæ$sk5³ÄbÆÃ8×!)o7È@óNoç5ÇbbÆ8×!)o7ȳþFoæ$sk5³ÄBoÌH§¤årübÆ$§¤åó9fþ


#15

If I can only get one response per day for this problem then the project is sure to fail and I must consider alternative modules for this product development…


#16

More information: I’m not sure if this is relevant, but I checked everything was up to date.

Whilst DS says everything is up to date when I check for updates, I had a look in the repository (updatesite.sierrawireless.com/developerStudio) by selecting install new software.

When checking ‘hide items that are already installed’ and ‘show only the latest versions of available software’ there were a number of packages that showed up, many of them with the name ‘Source for…’ followed by relevant parts of DS like target management, etc.

All but one of them installed fine, but the one named “Source for Open AT projects management - 2.3.1.201305211544-R11859” will not install with the following error:

An error occurred while collecting items to be installed
session context was:(profile=M2StudioProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,com.wavecom.openat.ide.devenv.branding.source,2.3.1.201305211544-R11859.
Error reading signed content:C:\Users\Antony\AppData\Local\Temp\signatureFile2023200758426420832.jar
An error occurred while processing the signatures for the file: C:\Users\Antony\AppData\Local\Temp\signatureFile2023200758426420832.jar

Could this be at all relevant?


#17

I found this thread: https://forum.sierrawireless.com/t/hapc-at-test-error/5984/1

My problems are the same - also, I cannot communicate using COM1 and I get scrambled output from PuTTY as explained above…

This is whilst using the basic hello world app (with a global var added to count the hello messages in the trace).

I can program the module but after most steps like this, the only way I can find to get communication between DS and the module to work again is to restart both.


#18

The running FW version seems a little bit outdated.
Anyway, SL8 module software is still not available in its final stable official version.
You should get in touch with your distributor in order to get more recent updates, and more reactive support: this forum area is dedicated to generic tooling troubleshooting, and you are clearly experiencing deeper problems…


#19

The firmware im using is the only one available that I am aware of (a beta repository link provided in this forum).

We dont yet have a distributor as we have only just started using the development kit bought directly from the Sierra Wireless estore…

We will have to find one - I don’t know if you guys can recommend a supplier in the UK that might be best suited?

You mention that there is not yet a stable release for the SL808x firmware - is there a planned timescale on when a stable release should be available?


#20

The stable SL8 Firmware release is currently planed for end of Q3 2013.