Developer Studio v2.1.1


#1

Hi,

Can somebody tell me what’s new in DS version 2.1.1? There are no release notes available on the website.

thanks


#2

Hi Stefan,

You’re too fast for me :wink:

Developer Studio 2.1.1 main updates:

  • Target management has been improved with OS Awareness. This is bringing much more visibility to Open AT application execution with some insight on Task status, Stack status and peak consumption, and Heap size and current usage.
  • The ability to Record & Replay on UART which was existing on legacy TMT is now available as well with Developer Studio.
  • USB Robustness has been improved, thanks to a revamp of the USB driver.
  • JTAG configuration for some WMP customers has been improved, to ease its usage with Segger probe.
  • Conditionnal Breakpoints with embedded debugging which was already available, is now fully validated.

Download Developer Studio now and get latest release notes.

Regards,
Christophe


#3

How to prevent DS from reading “target information” from the device whilst trying to upload files? That information is never readable on my FXT009’s, previous DS disregarded that and did upload, and this one gets stuck.


#4

I have the same problem when opening a USB COM port with an FXT009. These are the error details from the error message popup:

Open and load port COM7 => ERROR: Time out: 20000ms
Open and load physical port COM7 => ERROR: Time out: 20000ms
Open port COM7 => DONE: Port opened
Load informations from target => ERROR: Time out: 20000ms
Waiting for module detection => DONE: Target detected sn:BH1230091708100 baudrate:null
Switch to Development mode and check => DONE: Success
Switch to Development mode => DONE: Success
Waiting for module detection => DONE: Target detected sn:BH1230091708100 baudrate:null
Check dev mode unlocked => DONE: Success
Load model element: IMEI => DONE: IMEI received: [353270040346407]
Load model element: Target Informations => ERROR: Time out: 20000ms
Load model element: Target Informations => ERROR: Time out: 20000ms
Load model element: Target Informations => ERROR: Time out: 20000ms

and this is what’s in the console window:

----------------- Port opened -----------------

OK
Serial Number BH1230091708100
OK
OK
+WIMEI: 353270040346407
OK
+WDM: 3
OK
+WOPEN: 6,1024,4096
OK
+WOPEN: 1
OK
+CME ERROR: 3

“- USB Robustness has been improved, thanks to a revamp of the USB driver.”

In device manager, the driver (in the modem group, not sure if this is the correct one) is still version 3.6.5 from August 2010


#5

Please go to the sierrawireless.com/Support/Downloads.aspx page, choose your AirPrime product, and grab the latest 3.8.2 USB driver (at the bottom of the page)
A new USB support page has been added to the Developer Studio online help. Please have a look and check if it helps.


#6

Please note that for handling new “from scratch” Developer Studio 2.1.1 installation, a new installer runtime is available here:
updatesite.sierrawireless.com/in … v1-3-0.exe


#7

On FXT001/002/009/Q2687 download pages USB driver v.3650 is the only available.


#8

Thanks for reporting the issue; we’re going to update these pages.
Meanwhile, please use the same one than WMP100 product (same USB driver)


#9

I downloaded the 3.8.2 driver but it made no difference, opening a port still hangs up at the stage “Load model element: Target Informations”.

I also tried it with our application off (WOPEN=0), and again with our application removed (WOPEN=4), with the same results.

Attached is a screen shot showing the results of trying to open the port.



#10

We’ve tested this now with 4 different modems, 2 FXT009 and 2 FXT 003, all running FW ver 7.46 and bootloader ver V08b11. One of the 4, an FXT003, can be opened from DS 2.1.1 every time we try it, none of the other 3 can. The key difference we see is the three that don’t work show up in device manager under the modems group, and the one that works shows up in the ports group.

In the devices tab in DS, the 3 that don’t work have type USB (Modem), while the one that does has type USB (COM). Also the 3 that don’t work don’t work if you try to connect by the serial port either. The one that works can be successfully opened using either the serial port or the USB port. 3 of the 4 modems including the one that works are brand new out of the box.


#11

On the targets which are not connecting, please can you:

  • clear the console content
  • request a refresh in the target status view
  • copy-paste the console content here?

We can see a “+CME ERROR: 3” result in your console log, please can you check if there is a difference in AT+CMEE configuration between your 3 non-working targets, and the working one?


#12

Thanks Christophe

BR,
Stefan


#13

We’ve managed to get all 4 modems working now. There were a few issues causing the difficulties:

  • The new USB driver didn’t install with the upgrade to v2.1.1 (not sure if it’s supposed to or if it always required a separate installation)
  • A couple of the modems had AT+CMEE set to 1 - opening the port times out if CMEE is 1, which I suspect is new behaviour with 2.1.1 (at least we’ve never noticed it before)
  • One of the modems had a firmware version of 7.43, where a minimum of 7.45 seems to be required for the new driver. I had assumed the modems were all running 7.46 as they came in the same shipment.

#14

Good news!

The USB driver indeed requires a separated (and manual) installation/update. We’re studying the possibility to have a notification mechanism also for the USB driver updates…

Can you remember which FW version is running when you get troubles while +CMEE=1 is active? From what we’ve tested, connection seems always successful with +CMEE=1 and FW version 7.46, but we could get trouble with former versions.

Indeed, the command used to switch USB mode (AT+WUSB) requires FW 7.45 or higher.


#15

It’s happening with all firmware versions including 7.46. Here are the contents of the error message popup after the timeout:

Reload model for port COM15 => ERROR: Time out: 20000ms
Load informations from target => ERROR: Time out: 20000ms
Waiting for module detection => DONE: Target detected sn:BH1230091708100 baudrate:null
Switch to Development mode and check => ERROR: Time out: 1000ms
Switch to Development mode => DONE: Success
Waiting for module detection => DONE: Target detected sn:BH1230091708100 baudrate:null
Check dev mode unlocked => ERROR: Time out: 1000ms
Switch to Development mode and check => DONE: Success
Switch to Development mode => DONE: Success
Waiting for module detection => DONE: Target detected sn:BH1230091708100 baudrate:null
Check dev mode unlocked => DONE: Success
Load model element: IMEI => DONE: IMEI received: [353270040346407]
Load model element: Target Informations => ERROR: Time out: 20000ms
Load model element: Target Informations => ERROR: Time out: 20000ms
Load model element: Target Informations => ERROR: Time out: 20000ms

And here’s what’s in the console window:

Serial Number BH1230091708100

OK

+WDM: 3

OK

+WDM: 3

OK

+WUSB: 1,“114F”,“SIERRA WIRELESS”,“BH1230091708100”
+WUSB: 2,0,“1000”,“USB MODEM”,192,20
+WUSB: 3,“UFLCDC”
+WUSB: 4,0

OK

+WOPEN: 6,1024,4096

OK

+WOPEN: 6,1024,4096

OK

“DWL”,“V08b11”,"",“Sierra Wireless”,55236,“122210 15:25”,“e8a16b54”,“00010000”
“FW”,“FW_SRC_746_8.Q2687RDG”,“R7.46.0.201108091301.FXT009”,“Sierra Wireless”,2216044,“080911 13:01”,“2f1beedd”,“00020000”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“FXT009”

OK

+WOPEN: 0

OK

+WOPEN: 0

OK

+CME ERROR: 3

Serial Number BH1230091708100

OK

+CME ERROR: 3

Serial Number BH1230091708100

OK

OK

+WUSB: 1,“114F”,“SIERRA WIRELESS”,“BH1230091708100”
+WUSB: 2,0,“1000”,“USB MODEM”,192,20
+WUSB: 3,“UFLCDC”
+WUSB: 4,0

OK

OK

OK

+WUSB: 1,“114F”,“SIERRA WIRELESS”,“BH1230091708100”
+WUSB: 2,0,“1000”,“USB MODEM”,192,20
+WUSB: 3,“UFLCDC”
+WUSB: 4,0

OK

“DWL”,“V08b11”,"",“Sierra Wireless”,55236,“122210 15:25”,“e8a16b54”,“00010000”
“FW”,“FW_SRC_746_8.Q2687RDG”,“R7.46.0.201108091301.FXT009”,“Sierra Wireless”,2216044,“080911 13:01”,“2f1beedd”,“00020000”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“FXT009”

OK

“DWL”,“V08b11”,"",“Sierra Wireless”,55236,“122210 15:25”,“e8a16b54”,“00010000”
“FW”,“FW_SRC_746_8.Q2687RDG”,“R7.46.0.201108091301.FXT009”,“Sierra Wireless”,2216044,“080911 13:01”,“2f1beedd”,“00020000”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“FXT009”

OK

OK

+WIMEI: 353270040346407

OK

+WDM: 3

OK

+WOPEN: 6,1024,4096

OK

+WOPEN: 0

OK

+CME ERROR: 3

Note we’ve now run into several other problems with ver 2.1.1, which seem to be the same as reported here

[url]https://forum.sierrawireless.com/t/headup-ds2-1-1-could-be-a-little-flaky/5421/1]


#16

Mmm, could be interresting to understand from which command the “+CME ERROR: 3” result is coming…
Please can you make the test again, with the ATI 1 trace level enabled, and post the trace log (in a file, please)?


#17

Please see below (note attachments of type csv,txt,and log are not allowed, and I don’t know what file types are allowed, so I’ve included the contents inline. My apologies for the length of the post).

2012/01/26;16:35:16:093;000;ATI;0;[Enabled Levels] 1
2012/01/26;16:35:27:765;001;ATI;1;AT+WMSN
2012/01/26;16:35:27:765;003;ATI;1;41 54 2b 57 4d 53 4e 1a
2012/01/26;16:35:27:781;001;ATI;1;Serial Number BH1230091708100
2012/01/26;16:35:27:781;002;ATI;1;0d 0a 53 65 72 69 61 6c 20 4e 75 6d 62 65 72 20 42 48 31 32 33 30 30 39 31 37 30 38 31 30 30 0d 0a
2012/01/26;16:35:27:812;005;ATI;1;OK
2012/01/26;16:35:27:812;006;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:28:421;001;ATI;1;at+wdm=1
2012/01/26;16:35:28:421;003;ATI;1;41 54 2b 57 44 4d 3d 31 1a
2012/01/26;16:35:28:437;005;ATI;1;OK
2012/01/26;16:35:28:437;006;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:28:953;001;ATI;1;AT+WMSN
2012/01/26;16:35:28:953;003;ATI;1;41 54 2b 57 4d 53 4e 1a
2012/01/26;16:35:28:984;001;ATI;1;Serial Number BH1230091708100
2012/01/26;16:35:28:984;002;ATI;1;0d 0a 53 65 72 69 61 6c 20 4e 75 6d 62 65 72 20 42 48 31 32 33 30 30 39 31 37 30 38 31 30 30 0d 0a
2012/01/26;16:35:29:000;003;ATI;1;OK
2012/01/26;16:35:29:000;004;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:484;001;ATI;1;at
2012/01/26;16:35:29:500;001;ATI;1;41 54 2b 54 48 41 49 1a
2012/01/26;16:35:29:500;006;ATI;1;OK
2012/01/26;16:35:29:500;007;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:593;001;ATI;1;at+wimei?
2012/01/26;16:35:29:593;003;ATI;1;41 54 2b 57 49 4d 45 49 3f 1a
2012/01/26;16:35:29:593;005;ATI;1;+WIMEI: 353270040346407
2012/01/26;16:35:29:625;001;ATI;1;0d 0a 2b 57 49 4d 45 49 3a 20 33 35 33 32 37 30 30 34 30 33 34 36 34 30 37 0d 0a
2012/01/26;16:35:29:625;006;ATI;1;OK
2012/01/26;16:35:29:625;007;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:671;001;ATI;1;at+wdm=2
2012/01/26;16:35:29:671;003;ATI;1;41 54 2b 57 44 4d 3d 32 1a
2012/01/26;16:35:29:671;005;ATI;1;+WDM: 3
2012/01/26;16:35:29:687;001;ATI;1;0d 0a 2b 57 44 4d 3a 20 33 0d 0a
2012/01/26;16:35:29:687;006;ATI;1;OK
2012/01/26;16:35:29:703;001;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:734;001;ATI;1;at+wopen=6
2012/01/26;16:35:29:734;003;ATI;1;41 54 2b 57 4f 50 45 4e 3d 36 1a
2012/01/26;16:35:29:765;001;ATI;1;+WOPEN: 6,1024,4096
2012/01/26;16:35:29:765;002;ATI;1;0d 0a 2b 57 4f 50 45 4e 3a 20 36 2c 31 30 32 34 2c 34 30 39 36 0d 0a
2012/01/26;16:35:29:781;001;ATI;1;OK
2012/01/26;16:35:29:781;002;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:812;001;ATI;1;at+wopen?
2012/01/26;16:35:29:812;003;ATI;1;41 54 2b 57 4f 50 45 4e 3f 1a
2012/01/26;16:35:29:812;005;ATI;1;+WOPEN: 0
2012/01/26;16:35:29:812;006;ATI;1;0d 0a 2b 57 4f 50 45 4e 3a 20 30 0d 0a
2012/01/26;16:35:29:812;011;ATI;1;OK
2012/01/26;16:35:29:812;012;ATI;1;0d 0a 4f 4b 0d 0a
2012/01/26;16:35:29:843;001;ATI;1;at+wdebug?
2012/01/26;16:35:29:843;003;ATI;1;41 54 2b 57 44 45 42 55 47 3f 1a
2012/01/26;16:35:29:859;001;ATI;1;+CME ERROR: 3
2012/01/26;16:35:29:859;002;ATI;1;0d 0a 2b 43 4d 45 20 45 52 52 4f 52 3a 20 33 0d 0a


#18

I have the same issues as dsk_5. See my post :

https://forum.sierrawireless.com/t/usb-driver-v3-822-hangs-downloads/5417/1


#19

Try AT+CMEE=0 and AT&W, and see if it fixes the problem, it did for us.


#20

Thank you dsk_5 and daav for your help. Dsk_5’s suggestion fixed the problem. I can’t thank you guys enough for helping me.