RSD Lite Version 4.9 User Manual & Release Notes
09/15/2010
Document Version: 4.9
August 15, 2010
RSD Lite User Manual & Release Notes
Version 4.9
Table of contents
3RSD Lite
3User Manual Section
4Highlights of changes in this version of RSD Lite
4Installation of Motorola Drivers
4RSDLite feature details:
4Command Line Usage details
6ODM Usage details
7TI Blank Flash Usage Details
7Additional options in RSDLite.ini file
10DeviceID Allocation Usage Details
10Online Version Check Details
11Set the length of Die ID details
12Input SPC code for each device
14Windows OS Details for RSD Lite
14PC/HW Requirements
15Do’s / Don’ts with RSD Lite
15RSD Lite Component Details
16Debugging, Logging and Error Messages in RSD Lite
19Support Limitations and known issues
20Support Contact(s)
21RSD Lite
21Release Notes Section
22Build Information
RSD Lite
User Manual Section
Highlights of changes in this version of RSD Lite
· Added OMAP4430 support
· Added NVIDIA Everest support
· Added Olympus security
· Droid2WE, Venus2 BP Bypass flash support
· Added support for chipset MSM7225S
Installation of Motorola Drivers
Moving forward in RSD Lite, there will be no device drivers installed along with the tool.
Regarding which driver version should be used, please check the phone software release notes.
To install latest Motorola driver, please use the web link at:
1) For market/service-center users, please download latest Motorola driver package which passed WHQL certification at: http://compass.mot.com/go/motoroladriverinstaller
2) For internal engineers, please download latest Motorola driver package which support all the shipped and under-development products at: http://compass.mot.com/go/motoroladriverinstallerprerelease
RSDLite feature details:
Command Line Usage details
RSDLite can be launched by the command line method. The usage of command line has the syntax as following:
[RSDLite Launching path] [-f] [Flash/Flex file path] {[Option parameter]…}
Option parameter = [Option command line parameter] {value}
The details of description of command line parameters are below:
“-f”: It is mandatory in the command line method and used to separator the application path and flash/flex file path.
“-t”: It is an optional parameter and the followed parameter must specify the time out value which is used to decide when to start flash/flex operation. If the value is less than the default value defined in RSDLite.ini file or even not specified, the default value will be used.
“-s”: It is an optional parameter and it means that it should suppress all prompts of RSDLite.
“-c”: It is an optional parameter and it means that RSDLite should be closed automatically when it finishes flash/flex operation.
“-h”: It is an optional parameter and the followed value designates the action after flash. Otherwise the default action in PST.ini file will be used.
“-x”: It is an optional parameter and the followed value designates the action after flex. Otherwise the default action in PST.ini file will be used.
“-p”: It is an optional parameter and it specifies the value for MFF loop feature. Otherwise the default action in PST.ini file will be used.
“-m”: It is an optional parameter and it specifies the work mode. Otherwise the default action in PST.ini file will be used.
“-n”: It is an optional parameter and it will enable “TI Blank Flash” option of RSDLite.
“-o”: It is an optional parameter and it will enable “ODM_Serial” option of RSDLite.
“-d”: It is an optional parameter and it needs to detect all devices designated by the input, and then start flash/flex automatically after the time delay specified by “-t”.
“-w”: It is an optional parameter which specifies the maximum detecting time. It depends on the setting of “-d”, that means it will be ignored if “-d” is not set. If the maximum detecting time is out, but the number of phones’ arrival is less than the one specified by “-d”, RSD Lite will pipe out the time out information to the user and close automatically if “-c” is set, or RSD Lite will send out a time out message if “-c” is not set. If all the phones specified by “-d” arrive within the maximum detecting time, RSD Lite will go on to do the flash/flex operation immediately after a the time delay specified by “-t”.
“-i”: It is an optional parameter and it specifies how many phones need itself SPC code and indicate the SPC code for each phone. This parameter only works for flex.
The parameters can combine freely. The order of the parameter is not cared in the command line.
As to the application file path and flash/flex file path, they can be expressed as in the way either the relative path or the absolute path. The formats are as following:
· .\..\XXX\SDL.exe
· ..\XXX\XX\..\XX\xx.sdf
· D:\XXX\XXX\SDL.exe
An example for command line of RSDLite is as follwing:
D:\SDL.exe -f D:\abc.shx –t 10 –s –c –h 1 –x 0 –p 2 –m 1 –i 2 0:123456 1:000000
ODM Usage details
The following ODM serial phones are being supported as of now:
· Tango – Serial Phone based on TI-Locosto chipset
Other ODM USB phones supported as of now for flashing are:
· Borneo
· Lipari MT
· Salina HT
ODM Serial Drivers: Please install the ODM drivers, as needed for the ODM phones. The serial drivers are to be obtained from the ODM teams handling the project. For ODM-Serial driver issues, please contact the appropriate teams.
Click on the ODM-Serial checkbox for ODM Serial phones, as shown below.
Connect the ODM phone (Serial or USB) and start flashing the phone by pressing the start button.
For non-ODM/ODM USB phones, please uncheck the ODM-Serial Checkbox provided in RSD Lite and run the tool.
TI Blank Flash Usage Details
TI OMAP, Locosto USB phones can be blank flashed using this option. Following are the steps to use the Blank Flash option
· Select the check box
· Connect the phone
· The phone will be enumerated in Blank flash mode
· Select appropriate file and click start button.
Additional options in RSDLite.ini file
The RSDLite.ini file is installed in the RSD Lite folder. Users can configure the following settings by modifying the RSDLite.ini file settings.
MFFLoopFeature
Users can perform flash or flex operations in a continuous loop. The number of iterations of flashing/flexing to be done can be specified here. Aftelr every iteration RSD Lite will continue as if the user clicked the start button until the number of loops specified in this option is performed.
MaxFlashLogFileSize
This option is to configure the maximum size of flash module log file size.
FlashLog
Enable (1) or Disable (0) Flash log.
MaxLogFileSize
This option controls the maximum size of the RSD Lite log file. Once the log file reaches the maximum size, a new log file will be created to continue logging.
LogType
Enable (1) or Disable (0) RSD Lite log.
WorkMode
PST Framework work mode. This decides the type of devices that the tool is going to be used with.
Option Values
Meaning
MODE_NONE =0x00
No mode is selected
MODE_USB =0x01
Enable work on USB only
MODE_SERIAL =0x02
Enable work over Serial only
MODE_SIMULATOR =0x04
Enable work on Socket for simulator
MODE_NETWORK =0x08
Enable work on network only
MODE_DETECTION_OFF =0x10
Disable driver notifications
Mode combinations
MODE_USB_SERIAL =0x03
Enable work on USB + Serial
MODE_USB_SERIAL_SOCKET =0x07
Enable work on USB + Serial + Socket
MODE_USB_NETWORK =0x09
Enable work on NETWORK over USB
MODE_USB_SERIAL_SOCKET_NETWORK =0x0F
Enable work on USB + Serial + Socket + Network over USB
MODE_ALL_NO_SERIAL =0x0D
Enable work for all modes except Serial
MODE_ALL =0x0F
Enable work for all modes
AfterFlexOption
Options for post-flex operations
0 - Restart the phone
1 - No action needed
AfterFlashOption
Options for post-flash operations
Option Values
Meaning
E_POWERDN_SYNCHRONOUS=0,
Power down all phones synchronously
E_RESTART_SYNCHRONOUS=1
Restart all phones synchronously
E_POWERDN_ASYNCHRONOUS=2
Power down the individual phone which has completed flashing and not wait for other phones
E_RESTART_ASYNCHRONOUS=3
Restart the individual phone which has completed flashing and not wait for other phones
E_SYNC_NOACTION_NEEDED=4
No more action required after flashing. The method will wait for all devices completing operation synchronously and return.
E_ASYNC_NOACTION_NEEDED=5
No synchronization for multiple devices. The method will return without waiting for other device. No more action required after flashing.
E_RESTART_SYNC_NOWAITFORREENUM=6
Synchronized restart commands only, but will not wait for device re-enumeration. The method will return without waiting for re-enumeration.
E_RESTART_ASYNC_NOWAITFORREENUM=7
Asynchronous restart command, but will not wait for device re-enumeration. The method will return without waiting for re-enumeration.
E_PDN_AFTANY_ERROR_RESTART_ASYNC =8
Power down after any error restart asynchronous- needed for GNPO
E_PDN_AFTANY_ERROR_PDN_ASYNC =9
Power down after any error. Pdn. asynchronous- needed for GNPO
E_RESTART_AFTANY_ERROR_RESTART_NOWAIT_SYNC =10
Restart after any error. Restart no wait synchronous - needed for GNPO
E_RESTART_AFTANY_ERROR_RESTART_NOWAIT_ASYNC =11
Restart after any error. Restart no wait asynchronous- needed for GNPO
Note that if it runs a loop test, only the value 1, 3 and 8 are supported.
TIROMBlankFlash
Options for post-flex operations
0x00 - TI OMAP, Locosto USB phones can not be blank flashed
0x01 - TI OMAP, Locosto USB phones can be blank flashed
Following are the steps to use the Blank Flash option
· Set the entry in RSDLite.ini file
· Start RSDLite
· Connect the phone
· The phone will be enumerated in Blank flash mode
· Select appropriate file and click start button.
DeviceID Allocation Usage Details
Suggested Steps to Enable DeviceID Allocation Functionality:
· Use DeviceIdAllocationTool.exe to allocation DeviceID, please refer the “DeviceID Allocation Tool UserManual” for details.
· Close DeviceIdAllocationTool.exe, launch RSDLite.
· Select Menu: Config-> DeviceId Options
· Select one mode you want, click “OK” to finish it or “Cancel” to cancel this operation.
If following Dialog box is popup, it means the RSDLite should be closed and re-launched to make the DeviceID option selection take effective.
Online Version Check Details
If version is not the latest, following dialog will pop up when RSDLite starts up:
Select “Don’t show this prompt next time” can disable this function and don’t show the prompt.
From menu “Help”->”Check for update” can enable this function.
Set the length of Die ID details
Steps to change the length of Die ID from GUI of RSD Lite when getting all UIDs ( For OMAP3430 only):
· Select Menu: Config-> UID Options
· Change the length of AP or BP as you want (The max length of die ID is 14 bytes), click “OK” to finish it or “Cancel” to cancel this operation.
· Additional options in pst_flash.ini file
If users want to send RQUID in the process of Flash for non-security phone, users can configure the phone’s product string by modifying the pst_flash.ini file settings. The pst_flash.ini file is installed in the RSD Lite folder.
[SendRQUID] -> -> NS Flash OMAP3430 = 1
Options of sending RQUID, the default value is ‘0’.
0 – Not send RQUID
1 – Send RQUID
· RSD Lite also support extract TI Public ID from rom code response (for OMAP343X chipset ) and log that ID into a local file “TIPubilcID.txt” which located at RSD Lite folder.
Input SPC code for each device
Steps to input SPC code from GUI of RSD Lite:
· Choose a flex file which contains SPC security code, if not, the SPC GUI will not pop up
· Press button “Start” from main GUI of RSD lite then a window pop up to let you input SPC security code for each device
· Press button “OK” of SPC GUI will use the SPC code inputted by user to unlock the device.
· Press button “ReadFromFile” of SPC GUI will use the SPC security code read out from inputted flex file to unlock the device.
· Additional options in RSDLite.ini
If users want to input SPC security code for one device on GUI, user can configure the phone’s product string into section [SPC_Needed] of RSDLite.ini which is installed in the RSD Lite folder.
[SPC_Needed]
Motorola A555=1
Options of inputting SPC security code
0 – Not pop up a window to input SPC security code
1 – Pop up a window to input SPC security code
Windows OS Details for RSD Lite
Foreign language Operating Systems:
The required 4 XP hot fix files named: Q814560, Q816843, Q822603 and Q810400 for foreign
language OS, will not be installed via RSD Lite installer.
To install foreign language XP hot fixes, please visit: http://compass.mot.com/go/153319459;
XP with Service Pack1:
For English OS only, the required 4 XP hot fix files named: Q814560, Q816843, Q822603 and
Q810400 will be installed via RSD Lite installer program. Install these hot fixes first when
prompted, and then try installing RSD Lite application. This English version of hot fixes will be
installed only once.
XP with Service Pack2:
For XP with SP2, the above named hot fix files are included and installed with SP2 by Microsoft
Corporation. Thus, users do not need to install them manually. The RSD Lite application will not
install XP hot fixes for SP2 machines.
RSD Lite program is released in English language only.
The system requires that you have to log on as an Administrator, to install the necessary drivers
for each MA type of the phone.
Re-naming of RSD Lite folder or moving to different location is not recommended. If re-named or
moved, RSD Lite program will not work.
PC/HW Requirements
Host Controller Cards
· The controller must have two type A USB ports
· The controller must be at least USB v1.1 compliant.
· The controller must NOT have a Via Technologies or Lucent Host controller.
· Microsoft’s drivers must support the controller.
· The controller ports must reside directly on the controller PCB.
· The controller’s packaging or PCB must have the “USB” compliance insignia printed on either of them.
· The controller must be USB IF compliant
· The controller card must not be the same type of host controller as the motherboard. In other words if the mother boards is a Universal Host Controller then the PCI card must be an Open Host Controller (OHCI).
PC Requirements
· Pentium III, 500MHz or faster
· 128MB of RAM
· Windows XP SP1 or higher
· Windows 2000 SP2 or higher
HW Setup
· Belkin 7 port hub F5U027 or a USB v1.1 compliant 7 port hub.
Do’s / Don’ts with RSD Lite
· Applications that are a known problem are True Sync and HotSync. They should not be active while using RSD Lite.
· RSD Lite and RSD programs can co-exist on the same PC but should not be run simultaneously.
· The security key (wibu key) is not needed to run RSD Lite program.
· Before flashing or flexing, the phone must be plugged in and completely powered-up.
RSD Lite Component Details
Drivers and Docking Stations:
· The drivers are provided as available in the driver installer at this time.
· USB support only (No Serial support).
· RSD Lite does not support communication through docking stations due to limitations of
docking stations.
· USB cables have to be directly connected to ports on the laptop.
· Device installation is simplified by pre-installing INF and driver files for Windows 2000 systems.
· If using USB hubs, daisy-chain setup is not supported.
RSD Lite Flash
· Flashing over USB and flashing the simulator cannot be performed simultaneously.
· CSV log file displays BL & RDL Download time details
RSD Lite Flex
· Support for Flexing with the new HSR format
Suspend mode after flex operation in RSD Lite:
Only users who want the phone in suspend mode after the flex operation will need set the
“AfterFlexOption” with the value 1 in RSDLite.ini file. The tool will restart the phone after the flexing operation if option for action after flex option is set up with the value 0. Therefore, if the desired behavior is restarting the phone after the flexing operation (that’s the behavior in RSD Lite 2.7 and 2.8), set the value to 0.
Debugging, Logging and Error Messages in RSD Lite
List of log files needed while reporting issues:
1) swdl.txt
2) xx_xx_xx_xx_PST_Core.log
3) FlashErrorLogxx_xx_xx_xx_xx.log
4) flexerror.txt
5) USBView Snap Shot
All error messages are logged in text files.
The firmware upgrade and multi-upgrade error messages are logged in: swdl.txt file, which is
created in RSD Lite folder. This swdl.txt file is always created and messages are logged
sequentially by date/time. User must have write access to this folder.
The flex operation error messages are logged in flexerror.txt, which is created in RSD
Lite\PhoneFileLog folder. This flexerror.txt file is created only when there is an error during
flex operation. User must have write access to this folder.
FlashErrorLog.txt file is created whenever a flash related error occurs. It is created in the RSD
Lite folder. User must have write access to this folder.
Flash break-up time can be logged to a CSV File in RSD Lite v1.7.1 Release onwards. The
details provided will contain the flashing time for each code group and size of CGs etc. This
feature is turned OFF by default. For more details, please refer User manual.
For all flash / Framework error lookup, please refer
http://compass.mot.com/go/rsdlite and type in the error number into the
Spreadsheet following the instructions provided in the spreadsheet.
Turning ON logs for Framework and Flash in RSD Lite
For debugging purposes, the logs may have to be turned ON in RSD Lite. Please delete all
the existing log files in C:\Program Files\Motorola\RSD Lite directory.
For Framework logs, please change the value in pst.ini file in C:\Program Files\Motorola\RSD
Lite directory
[CORE_LOGGING]
Level = 0x00000000 and set the core logging level value to 0xFFFFFFFF.
For Flash logs, set the values of DebugLogEnable and ErrorLogEnable to 1, in pst_flash.ini file.
USB View snapshots
Please provide the snapshot details (Example shown below for a Motorola device)
Support Limitations and known issues
· If a phone is subsidy locked, RSD Lite will ignore errors returned by the phone when flexing secure elements and continue. The phone must be manually unlocked prior to flexing to properly write secure elements.
· The FSAC timeout has been increased to 600 seconds.
· RSD Lite will use the generic flex class if the SEEM Technology information is blank.
· A Master Clear is not issued after a flex procedure.
Support Contact(s)
RSD Lite Mailing List : RSDLITE@motorola.com
Driver Mailing List : INFDRVMO@motorola.com
RSD Lite
Release Notes Section
Build Information
BUILD LABEL:
· Framework label: fw_10_35_01
· Flash label: flash_10_37_01
· Flex label: FLEX_10.28.01I_ZCH45_INT
· RSD lite label: rsd_rsdl_10_35_01
DATE: September 15, 2010
RELEASE LOCATION: http://compass.mot.com/go/rsdlite
TEST RESULT LOCATION: http://compass.mot.com/go/363348657
Released CRs
IKHDT-18
Include Everest NVIDIA pid to enable RSD Lite detection. Add appropriate flash interface string to be able to flash
IKHDT-19
Add necessary changes in PST framework to detect OMAP4430
IKHDT-25
Implement security feature for Olympus device in RSD Lite
IKHDT-37
BP flash failed on Venus2 using RSDLite4.8
IKHDT-55
RSD Lite crashes when querying test command
IKHDT-62
Provide Image File Options to Users
IKHDT-49
Support new chipset MSM7225S
IKHDT-63
Flash:Lantana flash fail with RSDLite 4.8/4.9
� EMBED MSPhotoEd.3 ���
4
RSD Lite v4.9 User Manual
Motorola Confidential Proprietary
_991124332.bin
浙公网安备 33021202002483