We have found the cause of all our trouble, it was the binary of our application. After recompiling it with the latest developer studio, and overwriting this version of the binaries in our devices (Through hyperterminal/xmodem) all the errors dissapeared.
So nothing was wrong with developer studio Thank you for your time!
I built my prototype PCB and the Q2687 that I use looks fully functional. I managed to receive and send phone calls, and also to run the Hello World example included in Sierra’s IDE Studio. Since there is a new version of the firmware I would like to download it on the module in order to be up to date. The current firmware version is 7.45.1, DS version 2.2.1, and I use serial connection with 115200-8-none-1-hardware. The firmware 7.51 is included in the Studio, but I keep getting the following error when I try to download it:
Download file R7.51.0_q2687RD.dwl to port COM6, reload informations and check => ERROR: An error occurred during download
Download file R7.51.0_q2687RD.dwl to port COM6, reload informations and check => ERROR: An error occurred during download
Open port COM6 => DONE: Success
Open port COM6 => NO NEED TO DO IT: Success
Waiting for module detection => DONE: Target detected sn:AZ2130024308520 baudrate:115200
Switch to Development mode and check => DONE: Success
Switch to Development mode => DONE: Success
Pause : 300 milliseconds => DONE: Success
Check dev mode unlocked => DONE: Success
Enable persistent development mode => DONE: Success
Show a CONFIRM dialog with message => NO NEED TO DO IT: Success
DWL File parsing => DONE: Success
Show a CONFIRM dialog with message => NO NEED TO DO IT: Success
Load model element: Target Informations => DONE: Target Informations received: [dwlBean=size=55236, buildDate=122210 15:25, version=V08b11, checksum=-392074412, startAddress=65536, fwBean=size=2203572, buildDate=052511 06:00, version=R7.45.1.201105250600, checksum=1927520038, startAddress=131072, modemBean=, appBean=size=68648, buildDate=070112 10:40, version=1.0.0, checksum=-629385692, startAddress=2490368 components={WIP Plug-in Package=5.41.0.201102280815, Developer Studio=2.2.1.201206182209-R9667, Location Plug-in Package=1.1.0.201103021409, ExtendedATApplication Plug-in Package=1.1.0.201103081445, Open AT Embedded Software Suite package=2.35.0.201103111042, Security Plug-in Package=1.5.0.201102282015, InBandModem Plug-in Package=1.0.1.201101271648, GR Plug-in Package=2.10.0.201103090635, Firmware Package=7.45.0.201102220653, Open AT OS Package=6.35.0.201102280758}, name=hello_world Sample, companyName=MyCompany, , totalRAMSize=8388608, totalFlashSize=8388608, maxOatAppFlashSize=4194304, maxADFlashSize=786432, appStarted=false, localPortID=1, Q2687RDx, Q2687RD, com.wavecom.spm.model.wpkg.impl.FirmwareImpl@22eb3e20 (persistedModelVersion: 1.0.0, relativePath: C:/Program Files (x86)/Sierra Wireless/Embedded Software/com.wavecom.openat.ide.spm.fw.model.7.45.1.201105250600-3_7.45.1.201105250600-3/resources, mainTocReference: …/com.wavecom.spm.model/tocFW.xml#openAtFwDoc, pluginPathOffset: resources, externalPath: null, resourcesHash: 73288256081698) (appFlows: [ADL, LLH, HLH], heapOverheadSize: 16), false, 1000]
Check pre-condition before download => DONE: Success
Check if target WCPUID is compatible with application => DONE: Could not retrieve project for WCPUID compatibility check
Check if the Open AT area size is enough => DONE: Success
Check application overwrites the current flash mapping => DONE: No flash mapping
Check total flash size of the Open AT application => DONE: Success
Check if the file already has been downloaded on target => DONE: File is different from the target one.
Check start addresses => DONE: Success
Check memory size => DONE: Success
Copy DWL file R7.51.0_q2687RD.dwl to temporary path => DONE: Success
Download file R7.51.0_q2687RD.dwl to port COM6 => ERROR: An error occurred during download
I use CTS and RTS. Could it be the version of DS or something else?
Before upgrading from 7.4X to 7.5X, you shall first upgrade the bootloader to the latest version (the one packaged with 7.51 FW).
Actually, this is something to do every time you want to upgrade a firmware (not for downgrade; it is not recommended to go back to former bootloader versions).
So, I did upgrade the bootloader and then I was able to upgrade the firmware without problems.
I have two questions. It would be great if you could answer then please:
I might need to downgrade to 7.35. Will I be able to do that without risking breaking anything? Will I be able to use the latest bootloader to install back the older firmware?
When I go to project properties -> Open At Application in the Package Selection I can see many incompatibilities between version of Framework, OS, Firmware, and, at the very end, Libraries. For example, if I use the latest Open AT framework (2.51) then the library SMS-PDU is not compliant with the framework. In addition if I go to Package Manager perspective, I can see that the 2.51 Framework doesn’t include the SMS-PDU library. Considering that this is a very basic library that I am planning include SMS capabilities in my project, what options do I have? Do I need to downgrade to framework 2.35 that includes the specific library, or is there a way to install the libraries under the latest framework?
You can use the latest bootloader to roolback to the former Firmware, that’s OK.
Even if DS raises warnings for your SMS-PDU lib usage with Open AT Application Framework 2.51, it doesn’t mean it won’t work. That’s just a warning because this lib is not part of the Open AT AF global package anymore. I’ll check with the right people to have more info about this lib roadmap.
Thank you for your time!