1. set FEATURE_EFS_ENABLE_FACTORY_IMAGE_SECURITY_HOLE, and download whole image and qcn file.
2. switch the device to the mass storage (download) mode, use "sudo fdisk" to find the right partition of MODEM_ST1 and MODEM_ST2, add dump it. for example:
sudo dd if=/dev/sdb10 of=./st1.bin
sudo dd if=/dev/sdb11 of=./st2.bin
3.creat a dummy file.
dd if=/dev/zero of=./dummy.bin count=1 bs=3145728
4.modify the rawprogram0.xml
+++++<program file_sector_offset="0" filename="dummy.bin" label="BACKUP" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x50ad000" start_sector="165224" />
--------<program file_sector_offset="0" filename="" label="BACKUP" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x50ad000" start_sector="165224" />
+++++<program file_sector_offset="0" filename="st1.bin" label="MODEM_ST1" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x53ad000" start_sector="171368" />
------<program file_sector_offset="0" filename="" label="MODEM_ST1" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x53ad000" start_sector="171368" />
++++<program file_sector_offset="0" filename="st2.bin" label="MODEM_ST2" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x56ad000" start_sector="177512" />
-------<program file_sector_offset="0" filename="" label="MODEM_ST2" num_partition_sectors="6144" physical_partition_number="0" size_in_KB="3072.0" sparse="false" start_byte_hex="0x56ad000" start_sector="177512" />
5. download the st1.bin and st2.bin with xml.
Showing posts with label NV. Show all posts
Showing posts with label NV. Show all posts
2/01/2013
6/22/2012
HSUSB related NV items in qualcomm chipset
NV Items defined by HS-USB
High Speed USB Current Composition
a.. Number: 04526
b.. Area: System
c.. Description: USB Composition value
HS USB Remote Wakeup Delay
a.. Number: 04918
b.. Area: System
c.. Description:
a.. Indicates the number of milliseconds to wait before performing explicit remote wakeup when in suspend mode. When set to 0, the device doesn't perform explicit remote wakeup.
b.. Default (inactive) is 0.
c.. Set to 3000 before running USBCV.
HS USB Use PMIC OTG comparators
a.. Number: 06235
b.. Area: System
c.. Description:
a.. Indicates whether to use PMIC comparators in LCU.
b.. Default (inactive) is FALSE.
HS USB Number of SDCC LUNS
a.. Number: 06239
b.. Area: System
c.. Description:
a.. Indicates the number of SDCC/MMC LUNs that are enabled. The actual number of MS LUNS will be the maximum of this value and the actual number of SDCC controllers defined by the target.
b.. Default (inactive) is 1.
Host Mode Enabled
a.. Number: 06259
b.. Area: System
c.. Description:
a.. 0x01 means host mode is enabled. 0x00 means host mode is disabled.
b.. Default (inactive) is 0x00.
HS USB Use Diag on Legacy Port
a.. Number: 05044
b.. Area: System
c.. Description:
a.. Indicates whether DIAG should run over HS-USB or (if available) FS-USB (legacy). If full-speed device support is disabled in the target, this NV item is not being used.
b.. Default (inactive) is FALSE.
HS-USB disable sleep voting
a.. Number: 06327
b.. Area: System
c.. Description
a.. Indicates whether to disable voting for sleep when entering LPM after the USB bus is suspended.
b.. This NV item does not affect sleep voting when the USB port is disconnected. Sleep voting is always enabled in this case.
a.. 1 - Disable sleep voting during USB bus suspend state.
b.. 0 - Sleep voting is enabled during USB bus suspend state (default).
Set HS USB performance
a.. Name: NV_HS_USB_PERFORMANCE_SETTING_I
b.. Number: 6841
c.. Area: System
d.. Description:
a.. Determine HS USB performance
a.. LOW = 0 - minimum speed : CPU MIPS will be voted with 0 for NPA. This is only for a testing purpose because it does not guarantee the 4 MHz minimum PCLK requirement for HS USB link HW.
b.. MID = 1 - medium speed
c.. HIGH = 2 - maximum speed
Disable LPM
a.. Number: 6843
b.. Area: System
c.. Description:
a.. Indicates whether phone will enter LPM (low power mode)or not
a.. 0 - LPM is enabled
b.. 1 - LPM is disabled.
a.. By default LPM is enabled.
b.. Note - Disabling LPM also disables HS-USB sleep voting.
PHY Configuration
a.. Number: 06872
b.. Area: System
c.. Description:
a.. change the PHY configuration parameters
a.. pre_emphasis_enable - enable/disable pre-emphasis configure.
b.. pre_emphasis_value - the value for pre-emphasis.
c.. amplitude_adjustment_enable - enable/disable amplitude adjustment.
d.. amplitude_adjustment_value - the value for amplitude adjustment.
External NV Items useful to HS-USB
USB Charging NV Disable Value
a.. Number: 02822
b.. Area: Factory
c.. Description:
a.. Indicates to PMIC charging software whether to use USB charging. When set to 0, USB charging is enabled. When set to 1, USB charging is disabled.
b.. Default (inactive) is handled as charging disabled.
RMNet Autoconnect
a.. Number: 03534
b.. Area: Data
c.. Description:
a.. Indicates whether RMNet will automatically start the data call after the USB ECM connection is established.
a.. FALSE - Don't use RMNet autoconnect.
b.. TRUE - Use RMNet autoconnect.
a.. Default (inactive) is FALSE.
UIM First Instruction Class
a.. Number: 00896
b.. Area: GSM
c.. Description:
a.. Indicates whether to use UICC:
a.. 0-1 Don't use UICC
b.. 2 Use UICC without ISO Reset line high workaround
c.. 3 Use UICC with ISO Reset line high workaround
a.. Default (inactive) is 2.
Application Power Disable
a.. Number: 04201
b.. Area: Debug
c.. Description:
a.. Indicates whether to disable power on application processor (apps power collapse). Prerequisite to TCXO shutdown.
a.. FALSE - Use apps power collapse.
b.. TRUE - Don't use apps power collapse.
DCVS Application NV
a.. Number: 04393
b.. Area: System
c.. Description:
a.. Indicates whether to disable CPU clock control.
a.. type = 0 - Disable DCVS.
b.. type = 1 - Enable DCVS.
Enable reset logging
a.. Number: 04399
b.. Area: Debug
c.. Description:
a.. Indicates whether Phone will go to download mode after reset
a.. type = 0 - Disable the move to sw dload..
b.. type = 1 - Enable the move to sw dload.
High Speed USB Current Composition
a.. Number: 04526
b.. Area: System
c.. Description: USB Composition value
HS USB Remote Wakeup Delay
a.. Number: 04918
b.. Area: System
c.. Description:
a.. Indicates the number of milliseconds to wait before performing explicit remote wakeup when in suspend mode. When set to 0, the device doesn't perform explicit remote wakeup.
b.. Default (inactive) is 0.
c.. Set to 3000 before running USBCV.
HS USB Use PMIC OTG comparators
a.. Number: 06235
b.. Area: System
c.. Description:
a.. Indicates whether to use PMIC comparators in LCU.
b.. Default (inactive) is FALSE.
HS USB Number of SDCC LUNS
a.. Number: 06239
b.. Area: System
c.. Description:
a.. Indicates the number of SDCC/MMC LUNs that are enabled. The actual number of MS LUNS will be the maximum of this value and the actual number of SDCC controllers defined by the target.
b.. Default (inactive) is 1.
Host Mode Enabled
a.. Number: 06259
b.. Area: System
c.. Description:
a.. 0x01 means host mode is enabled. 0x00 means host mode is disabled.
b.. Default (inactive) is 0x00.
HS USB Use Diag on Legacy Port
a.. Number: 05044
b.. Area: System
c.. Description:
a.. Indicates whether DIAG should run over HS-USB or (if available) FS-USB (legacy). If full-speed device support is disabled in the target, this NV item is not being used.
b.. Default (inactive) is FALSE.
HS-USB disable sleep voting
a.. Number: 06327
b.. Area: System
c.. Description
a.. Indicates whether to disable voting for sleep when entering LPM after the USB bus is suspended.
b.. This NV item does not affect sleep voting when the USB port is disconnected. Sleep voting is always enabled in this case.
a.. 1 - Disable sleep voting during USB bus suspend state.
b.. 0 - Sleep voting is enabled during USB bus suspend state (default).
Set HS USB performance
a.. Name: NV_HS_USB_PERFORMANCE_SETTING_I
b.. Number: 6841
c.. Area: System
d.. Description:
a.. Determine HS USB performance
a.. LOW = 0 - minimum speed : CPU MIPS will be voted with 0 for NPA. This is only for a testing purpose because it does not guarantee the 4 MHz minimum PCLK requirement for HS USB link HW.
b.. MID = 1 - medium speed
c.. HIGH = 2 - maximum speed
Disable LPM
a.. Number: 6843
b.. Area: System
c.. Description:
a.. Indicates whether phone will enter LPM (low power mode)or not
a.. 0 - LPM is enabled
b.. 1 - LPM is disabled.
a.. By default LPM is enabled.
b.. Note - Disabling LPM also disables HS-USB sleep voting.
PHY Configuration
a.. Number: 06872
b.. Area: System
c.. Description:
a.. change the PHY configuration parameters
a.. pre_emphasis_enable - enable/disable pre-emphasis configure.
b.. pre_emphasis_value - the value for pre-emphasis.
c.. amplitude_adjustment_enable - enable/disable amplitude adjustment.
d.. amplitude_adjustment_value - the value for amplitude adjustment.
External NV Items useful to HS-USB
USB Charging NV Disable Value
a.. Number: 02822
b.. Area: Factory
c.. Description:
a.. Indicates to PMIC charging software whether to use USB charging. When set to 0, USB charging is enabled. When set to 1, USB charging is disabled.
b.. Default (inactive) is handled as charging disabled.
RMNet Autoconnect
a.. Number: 03534
b.. Area: Data
c.. Description:
a.. Indicates whether RMNet will automatically start the data call after the USB ECM connection is established.
a.. FALSE - Don't use RMNet autoconnect.
b.. TRUE - Use RMNet autoconnect.
a.. Default (inactive) is FALSE.
UIM First Instruction Class
a.. Number: 00896
b.. Area: GSM
c.. Description:
a.. Indicates whether to use UICC:
a.. 0-1 Don't use UICC
b.. 2 Use UICC without ISO Reset line high workaround
c.. 3 Use UICC with ISO Reset line high workaround
a.. Default (inactive) is 2.
Application Power Disable
a.. Number: 04201
b.. Area: Debug
c.. Description:
a.. Indicates whether to disable power on application processor (apps power collapse). Prerequisite to TCXO shutdown.
a.. FALSE - Use apps power collapse.
b.. TRUE - Don't use apps power collapse.
DCVS Application NV
a.. Number: 04393
b.. Area: System
c.. Description:
a.. Indicates whether to disable CPU clock control.
a.. type = 0 - Disable DCVS.
b.. type = 1 - Enable DCVS.
Enable reset logging
a.. Number: 04399
b.. Area: Debug
c.. Description:
a.. Indicates whether Phone will go to download mode after reset
a.. type = 0 - Disable the move to sw dload..
b.. type = 1 - Enable the move to sw dload.
6/01/2012
CPU Dynamics versus DCVS Service for MSM7630/8655 and NV 4393 in the MSM7x30
The term CPU Dynamics is introduced in the MSM7630 software with NPA environment. It is also applicable to the MSM8655 and SCMM based products.
It is synonymous to Application Processor DCVS service that is present on non-Android based products of MSM7K and MSM8K. When running Android software, only the modem processor runs CPU Dynamics; the applications processor will continue to use CPUFreq. On non-Android HLOS, both modem and applications processsors may both use CPU Dynamics.
One reason why CPU Dynamics is coined is that term DCVS is used quite loosely and can be ambiguous at times.
DCVS can refer to:
(1) Specific algorithm based service, which wakes up periodically to check for CPU utilization and adjust the CPU speed either upward or downward based on the criteria set by the algorithm.
(2) Frequency and voltage switching mechanism on the AMSS (Modem Processor side). This is traditionally done on demand basis. Each application knows how much CPU or Bus speed it needs and make request using clock regime API (s) to make a minimum level request. No period service that checks for CPU utilization gets involved.
CPU Dynamics refers to the service outlined in (1).
Along with the change in the clock and voltage switching software for the chipsets mentioned above, method to disable Apps DCVS service has changed.
The service requires following parameters:
1. Algorithm used - Enabled, Disabled, Others...
2. Sampling period -- How often to wake up to check for CPU utilization
3. N_lower -- Number of consecutive periods that CPU utilization stays lower than threshold before freq is taken to the lower level
4. N_raise -- Number of consecutive periods that CPU utilization stays above threshold before freq is taken to the higher level
The NV 4393 which was used to specify following values and to enable the service are no longer used on MSM7630/8655. The plan is to not use it in the future products.
The new way to enable/disable CPU Dynamics is by using NV files in EFS for the processor.
To disable CPU Dynamics (Apps DCVS service),
enter "Disabled" to /nv/item_files/CoreCPU/CoreAll/Startup/Algorithm.txt (for all cores for multi-core Apps CPU)
(for single core Apps CPU, this is valid as well)
enter "Disabled" to /nv/item_files/CoreCPU/Core0/Statrup/Algorith.txt (for the first core of multi-core Apps CPU)
enter "Disabled" to /nv/item_files/CoreCPU/Core1/Statrup/Algorith.txt (for the second core of multi-core Apps CPU)
To enable CPU Dynamics, enter "Classic" for algorithm used on 7x00, 7x25, 7x27, 8x50 software.
To change the sampling period,
change /nv/item_files/CoreCpu/Default/Monitor/SamplePeriod.uint file with the desired sampling period in milli-seconds.
Different values can be entered on individual core for multi-core Apps processor.
If the Modem processor supports CPU Dynamics for the build, the NV file listed above can be used to control it.
Demand based modem processor clock and voltage switching still uses NV 3519 as it was in other products.
It is synonymous to Application Processor DCVS service that is present on non-Android based products of MSM7K and MSM8K. When running Android software, only the modem processor runs CPU Dynamics; the applications processor will continue to use CPUFreq. On non-Android HLOS, both modem and applications processsors may both use CPU Dynamics.
One reason why CPU Dynamics is coined is that term DCVS is used quite loosely and can be ambiguous at times.
DCVS can refer to:
(1) Specific algorithm based service, which wakes up periodically to check for CPU utilization and adjust the CPU speed either upward or downward based on the criteria set by the algorithm.
(2) Frequency and voltage switching mechanism on the AMSS (Modem Processor side). This is traditionally done on demand basis. Each application knows how much CPU or Bus speed it needs and make request using clock regime API (s) to make a minimum level request. No period service that checks for CPU utilization gets involved.
CPU Dynamics refers to the service outlined in (1).
Along with the change in the clock and voltage switching software for the chipsets mentioned above, method to disable Apps DCVS service has changed.
The service requires following parameters:
1. Algorithm used - Enabled, Disabled, Others...
2. Sampling period -- How often to wake up to check for CPU utilization
3. N_lower -- Number of consecutive periods that CPU utilization stays lower than threshold before freq is taken to the lower level
4. N_raise -- Number of consecutive periods that CPU utilization stays above threshold before freq is taken to the higher level
The NV 4393 which was used to specify following values and to enable the service are no longer used on MSM7630/8655. The plan is to not use it in the future products.
The new way to enable/disable CPU Dynamics is by using NV files in EFS for the processor.
To disable CPU Dynamics (Apps DCVS service),
enter "Disabled" to /nv/item_files/CoreCPU/CoreAll/Startup/Algorithm.txt (for all cores for multi-core Apps CPU)
(for single core Apps CPU, this is valid as well)
enter "Disabled" to /nv/item_files/CoreCPU/Core0/Statrup/Algorith.txt (for the first core of multi-core Apps CPU)
enter "Disabled" to /nv/item_files/CoreCPU/Core1/Statrup/Algorith.txt (for the second core of multi-core Apps CPU)
To enable CPU Dynamics, enter "Classic" for algorithm used on 7x00, 7x25, 7x27, 8x50 software.
To change the sampling period,
change /nv/item_files/CoreCpu/Default/Monitor/SamplePeriod.uint file with the desired sampling period in milli-seconds.
Different values can be entered on individual core for multi-core Apps processor.
If the Modem processor supports CPU Dynamics for the build, the NV file listed above can be used to control it.
Demand based modem processor clock and voltage switching still uses NV 3519 as it was in other products.
Subscribe to:
Posts (Atom)