Read Me
Read Me
7
25 Sept. 2014
Table of Contents
1. Installation notes
2. Known issues
3. Additional software notices
4. Release notes
----------------------------------------------------------------------
1. INSTALLATION NOTES
When installing QPST, the installing user may need administration privileges.
You MUST use the QUALCOMM USB device driver or a QPST compatible
device driver on your PC if you wish to use QPST with a USB port. When
used with QPST, other drivers can cause your PC to hang when you reset
or disconnect the mobile. You will have to restart your PC to recover.
Or you may find that the phone disappears from the QPST configuration
when it resets, and not reappear until you restart QPST.
----------------------------------------------------------------------
2. KNOWN ISSUES
QPST version 2.7.410 is not compatible with QXDM. The symptom is that file-based
NV items (item number > 65535) sometimes cannot be read or appear to not be
configured. Version 2.7.410 should be replaced with version 2.7.411 if QXDM is in
use.
General:
Some SURFs and FFA mobiles support both USB and serial port connectivity.
QPST supports USB through a QUALCOMM USB device driver. You must use the
mobile's Port Mapper user interface to select either USB or a UART for
diagnostics. You can connect your PC to the mobile's serial or USB port,
but not both at the same time. Connecting QPST to more than one port of
the same mobile will cause Software Download to fail.
----------------------------------------------------------------------
http://www.apache.org/licenses/LICENSE-2.0
----------------------------------------------------------------------
4. RELEASE NOTES
"Disable sleep entire time this application is running"- this is the legacy
behavior. Sleep is disabled
when the application starts, and restored to its original state when the
application is closed.
"Disable sleep only when sending EFS commands"- disables sleep before sending
EFS commands, then restores
the original state after sending the commands.
Disabling sleep when accessing EFS is recommended because during mobile sleep
EFS commands may take an
extremly long time to complete. Small file transfers can take minutes instead of
seconds.
4) Removed prompt for SPC from EFS Explorer since SPC doesn't protect EFS contents.
5) Fixed problem where drag of a file from EFS Explorer to the host PC could cause
a QPST server crash.
6) Fixed "Pure virtual function call" crash that could, depending on QPST Server
configuration, occur after a USB disconnect.
7) QPST Server will now enable the "IP Server" function by default.
$software_download->DownloadBySettings($swdl_settings);
3) Add support to abort a Sahara memory dump that is in progress, then reboot the
device.
See notes on QPST 2.7.396. This will only have an effect if $port-
>LastSaharaEvent() returns state 20 (dump in progress).
$port->SaharaAbortDumpAndReset();
Send reset command if state machine is in Idle state. Returns 0/1 for
fail/success.
Will return failure on timeout waiting for reset response or if state machine
wasn't in the idle state.
Will return E_FAIL HRESULT if the device is not in Sahara mode.
my $result = $port->SendSaharaResetCmd();
This protocol can handle memory crash dumps and software download. On Win7
memory dumps will be stored in
C:\ProgramData\QUALCOMM\QPST\Sahara\Port_COMxx (xx = your COM port number), and
will include a dump_info.txt file
that lists the dump regions advertised by the device.
Sahara software download supports all images for flashless boot devices, and
flash programmer download for flash boot devices.
The eMMC Software Download application has been modified to support download of
the flash programmer through Sahara.
You will have to provide a full path to the Sahara XML download file in the
"Sahara XML file" edit control.
This is an example Sahara XML file. The programmer="true" attribute tells the
Sahara state machine in QPST to
exit Sahara mode after downloading this file, rather than wait for Sahara to
reply with a Done Response of 1.
In Sahara mode the download process is completely controlled by the device - it
will request images by image_id.
image_path is relative to the XML file. In this example all mbn files would be
in the same folder as the XML file.
A relative path would start with "\" or "..\".
2) Modify "Add New Port" dialog to display device description, and (if available)
the device's USB serial number.
The example does not perform a full download to a device and must be customized
by the user for the device and file paths. Please examine the
Perl script for details. At minimum you will have to modify these settings:
Set this parameter to the partition names and files you want to download. The
files must exist in one of the search directories:
$swdl_settings->SetParam("userPartitionList",
"0:DSP1=dsp1.mbn;0:DSP2=dsp2.mbn");
If the device is in Diagnostic mode, you can let QPST pick the flash programmer
(based on the device�s model number), or you can override this
behavior. See the comments in the �IsKnownConfiguration = true� branch. The
flash programmer must exist on the search path.
3) In EFS Explorer, copying the contents of an EFS file on a phone with a slow file
system can result in occasional duplication of read data.
The file read code will now check for this condition and try to read the next
file block up to 3 times. Persistent read timeouts will still cause
the read to fail.
4) NV item backup: NV item read/write timeouts have been increased. Some devices
have NV item read times that intermittently reach 2+ seconds.
5) This release provides initial support for phone subsystem restart (SSR).
6) Added a DeviceName property to the Automation server PortProxy object. This
returns the device name show in the QPST Configuration application.
example:
>emmcswdownload -l \tmp\devices.txt
>type \tmp\devices.txt
example:
Note: Use double quotes (") around a device name. Not necessary for a driver
letter.
You can get a list of devices with the -L switch.
example:
This is for blank flash programming. This mode will download partition.mbn, dbl.mbn
and osbl.mbn, and then copy files to the eMMC device.
It should go through the flash programmer steps, and then program the first mass
storage device that shows up after the device reset.
You will not see any progress bars until the application gets to the eMMC
programming.
Select the device you want to program from the list of devices.
Set Write Protection Group Size THEN Load XML def. Order is important here.
Enable any additional search paths you want, and then use browse or drag/drop of
the folder (or a file in the folder) to populate the control.
Press "Load build to EMMC device"
9/30/09 2.7.354
1) Add support for non-modem build polling command (DIAG_SUBSYS_CMD_F /
DIAG_SUBSYS_PARAMS / 3).
2) Update model IDs 14, 4036, 4037, 4038 to refer to the device as MSM instead of
QSC.
3) Add support for NV items 6486-6834.
1) During NV item backup a Microsoft file API was returning errors once the count
of stored
NV items grew above a certain limit. This limit was dynamic and unpredictable. This
QPST version
uses a different algorithm to store items in the QCN file to work around this
problem.
QCN files created with this QPST version are not compatible with QPST software
versions released
prior to version 2.7.310. This version can read NV items from pre-2.7.310 QCN
files, but QPST versions
older than 2.7.310 can not read NV items from QCN files produced by this QPST
version.
QCNView will identify new QCN files as having major version 2. The original QCN
file format used
version 1.
If you are providing QCN files produced with this QPST version to other QPST users
that have an
older QPST version installed, please also provide the installer for this version.
Since this feature replaces the 115.2 Kbps baud rate with a user-selected rate,
some
AMSS features that always run at 115.2 Kbps (such as software download) will no
longer work.
The QPST port server reads the value from the registry when it starts and uses
it in the BaudRate
member of the DCB (look up "dcb" on msdn.microsoft.com for further information).
The value you
should use for BaudRate depends on the serial port hardware and its device
driver. Some serial
port hardware implementations use switchable frequency dividers or other baud
rate encoding;
consult the serial port user guide or manufacturer for more information on the
correct encoding
of the BaudRate value. In many cases you can use a value equal to the baud rate
in bits-per-second
(e.g. use a value of 230400 for 230.4Kbps).
Use EXTREME caution when making this or any other registry change. Changing the
wrong
registry key may cause the Windows operating system or an application to
malfunction, possibly
resulting in a unrecoverable loss of data.
To change the baud rate for all users edit the key:
HKEY_LOCAL_MACHINE\Software\Qualcomm\QPST\PARAMS\PORT_SERVER
Or, to change the baud rate for just the current user, edit:
HKEY_CURRENT_USER\Software\Qualcomm\QPST\PARAMS\PORT_SERVER
For either key, create a new DWORD value in the key using the name "baud_rate_"
plus your
COM port name (e.g. baud_rate_COM1 for port COM1) and set it to the encoded baud
rate.
[HKEY_LOCAL_MACHINE\SOFTWARE\Qualcomm\QPST\2.0\Server]
"Server_INI_Files"="c:\\program files\\qpst\\bin\\"
All users must have read/write/enumerate access to this directory.
7) In PRL Editor, change the mask on UMTSGeneric and UMTSPrefGeneric Band cells to
accept 5 digits
instead of 4.
8) Modify serial port code to not open NMEA, Data, or Unknown type ports. Opening
an NMEA port can cause
QPST to freeze. On USB port restart insure port still compatible. User could
have swapped in a phone
that maps NMEA to this port.
9) Fix multiple problems in Configuration Add Port that caused the display of the
wrong port when you
selected one from the list.
10) DmProxyWin modified to accept two-digit COM port numbers.
11) Added NV items 3640-4099 to NV backup and QCNView.
12) Remove code that retries EFS2 commands that return bad status or timeout. Now
will only get the
low-level QPST server retry on timeout.
13) Update FTM application to 6.10.0.
14) Update RF NV Item Manager to 1.4.10.
15) Increase armprg size from 64k to 256k for MSM7500 Software Download.
16) Don't download PBL when trusted (secure) mode set - AMSS build won't include a
PBL file.
17) Include apps files for MSM7500 Software Download.
uses the Advanced option but doesn't terminate the path correctly.
==================================================================
==================================================================
1) Added support for 32-bit DMSS DLOAD command. QPST will choose to use the 32-bit
write
command when it detects protocol version 5 or higher.
2) Added support for sending blocks to NANDPRG in ascending order. QPST will use
this order
when the parameter request feature field indicates NANDPRG supports NAND_DL.
3) Updated NANDPRG to 05.04.00.
-Support for new spanless boot loader method.
-This NPRG6100.HEX must not be used with old boot loaders.
4) EFS Explorer can now display a progress bar during file transfer.
Use "View... File Xfer Animation" to enable/disable the old file
transfer animation, and "View... File Xfer Progress Bar" to enable/disable
the new progress bar. You can enable either, both, or neither. By default
you will get both.
5) The roaming list editor can now read an input file and generate a PRL.
6) Debug logging modifications:
-Perform logging in separate thread so disk latency doesn't slow QPST server.
-Log sync and async response times from mobile.