Hi I’m receiving an error when trying to install an application I have published
impossible to execute command 901 insufficient memory
Can anyone tell me what this means? How to resolve? And is there a list of these codes and their meanings/possible resolutions?
Any help much appreciated.
Hello,
This error means your device has not enough memory to execute the install. It’s probably because there’s no delta package available to go from the current version to the new version of the application. I suggest you create the delta version, upload it on AirVantage and try again to launch the install operation.
The update process is done using FUMO and the error code are the one defined in the FUMO specification. You can find all the OMA DM specifications we used on OMA Alliance web site: technical.openmobilealliance.org … _v1_0.aspx
I hope it help.
Don’t hesitate to come back to us if that’s still not working.
Regards,
David
Hi thanks for the reply, sorry it’s taken this long for me to investigate but I can’t see in the FUMO specification any reference to error code 901?
What kind of device do you use?
I’m using an SL6087 device running firmware version R7.52.0.201306260837
I’ve managed to clear the decks for this week to concentrate on only this issue so will be able to respond faster, apologies for the disjointed responses so far.
Just some further information. Using AirVantage I’ve uploaded a new application onto my development board and it has installed without issue, returning the following;
action [OPENAT_IDS_SW_INSTALL]
reading version
received rev: 5.0.20140614111853 decided to install FULL
install exec sent
the device accepted for processing the OMA-DM FUMO command
This is the same message I get when trying to update the field unit, with the addition of the following final message:
Impossible to execute command: 901 Insufficient memory [901 Insufficient memory]
I’ve double checked the ATI9 returns for both the dev board and the unit I’m using in the field;
ATI9 results from Dev Board;
“DWL”,“V10c05”,"",“Sierra Wireless”,62640,“051513 10:45”,“a0836b50”,“00010000”
“FW”,“FW_752_34_3.SL6087G”,“R7.52.0.201306260837.SL6087”,“Sierra Wireless”,673436,“062613 08:37”,“89796368”,“001d0000”
“MODEM”,“1.3.36”,“201306260837.SL6087”,“Sierra Wireless”,1713240,“062613 08:37”,“85a2fb97”,“00020000”
“OAT”,“5.0.20140614100914”,“SPM SSL CLient vVodafone”,“Senical”,577952,“061414 10:09”,“299ebff8”,“002a0000”
-“Developer Studio”,“2.3.1.201306241059-R11859”
-“Open AT Application Framework package”,“2.52.0.201307100830”
-“Open AT OS Package”,“6.52.0.201306271400”
-“Firmware Package”,“7.52.0.201306260837”
-“ExtendedATApplication Library Package”,“1.3.0.201306271406”
-“Internet Library Package”,“5.56.0.201305170830”
-“Security Library Package”,“2.2.0.201306261000”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“SL6087”
ATI9 results from field unit;
“DWL”,“V10c05”,"",“Sierra Wireless”,62640,“051513 10:45”,“a0836b50”,“00010000”
“FW”,“FW_752_34_3.SL6087G”,“R7.52.0.201306260837.SL6087”,“Sierra Wireless”,673436,“062613 08:37”,“89796368”,“001d0000”
“MODEM”,“1.3.36”,“201306260837.SL6087”,“Sierra Wireless”,1713240,“062613 08:37”,“85a2fb97”,“00020000”
“OAT”,“5.0.20140520111918”,“SPM SSL CLient vVodafone”,“Senical”,577896,“052014 11:19”,“c5a429d8”,“002a0000”
-“Developer Studio”,“2.3.1.201306241059-R11859”
-“Open AT Application Framework package”,“2.52.0.201307100830”
-“Open AT OS Package”,“6.52.0.201306271400”
-“Firmware Package”,“7.52.0.201306260837”
-“ExtendedATApplication Library Package”,“1.3.0.201306271406”
-“Internet Library Package”,“5.56.0.201305170830”
-“Security Library Package”,“2.2.0.201306261000”
“ROM”,“800000”
“RAM”,“200000”
“DWLNAME”,“SL6087”
Apart from the application details they are both consistent, this is as expected. The only thing I have noted that is different is the response to the AT+WOPEN=6 which returns different values for the development board and the field unit:
wopen=6 from Dev Board:
WOPEN: 6,0,1792
wopen=6 from field unit:
WOPEN=6,1024,3840
I receive an error (it just says error) if I try changing these values on the field unit using the command at+wopen=6,a,b where a and b are the new memory sizes. This is no doubt where the problem lies but I’m at a loss as to how to fix it?
Which unit do you have problem with?
On the dev kit it seems like you 0kb reserved for A&D storage which is used for the upgrade. Size of the application define how big area you need.You should not use both a and b with at+wopen=6. Correct is
AT+WOPEN=6,
Also I have discovered on one of my old units that they were not configured for FOTA/DOTA using AirVantage. You can see this by looking at the following configuration in AVMS:
OASIS SL6087 (R7.52.0.201306260837.SL6087) /System Remote Configuration/Monitoring/System/Flash/AD/DOTA and RDMS A and D storage
This config should look something like this:
0%1599159986%44758"
If the TotalSize of the RDMS section is 0 you have problems. In my case I had to download a special application with at+wdwl to resize the RDMS storage.
I have the same problem