This patch fixes the exceptions cases with respect to
python3.
Change-Id: I3b1264c0bb6a32e7e6ebb588dc6cd5fb43f357b2
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
(cherry picked from commit 1b1930dfa1)
Update pack_v2 script to flash bootconfig only for non-apps
image.
Change-Id: Iebc8f742b2e04f5950dfbce044f55b7f644c9846
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
(cherry picked from commit 3717bbac92)
This patch adds support in the pack_v2 script to limit
the wifi firmwares which packed into the single images
based on the profiles.
Add corresponding profile entry under each RDP
config in config.xml to restrict wifi fw images
packed into the single image.
Eg:
<profiles>256</profiles>
<profiles>512</profiles>
<profiles>512,256</profiles>
Note: No need add default profile in profiles tag.
Change-Id: I06667ec7ba31a2bbcb742fbd5319f0e30be193fc
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch adds support to flash the bootconfig based on the
RDPs.
1. To flash bootconfig based on Multi-RDP add entry like
below in all flash partition xmls
for non-mmc flash partition:
<img_name type="string" bootconfig_type="1">file1_name</img_name>
<img_name type="string" bootconfig_type="2">file2_name</img_name>
<img_name type="string" bootconfig_type="3">file3_name</img_name>
for mmc flash partition:
bootconfig_type_max="2"
filename_img1="file1_name"
filename_img2="file2_name"
and specify which bootconfig to flash on each RDP by adding
entry like below, in config xml under each RDP nodes.
<bootconfig_type>1</bootconfig_type>
2. for single bootconfig case, there is no change.
just add single entry like below in all flash partition xmls
<img_name type="string">file_name</img_name>
Change-Id: Id68c4f6f6c4cced493ac5130378897711e8cb9e4
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch updates the image_type condition check
for 0:WIFIFW since emmc-partition.xml each partition
information is parsed in single xml tag but for other
partition.xml files each partition information is
mentioned in multiple xml tags
For Example
ipq5332/flash_partition/tiny-nor-partition.xml
<partition>
<name length="16" type="string">0:WIFIFW</name>
<size_kb length="4">5500</size_kb>
<pad_kb length="2">0</pad_kb>
<which_flash length="2">0</which_flash>
<attr>0xFF</attr>
<attr>0xFF</attr>
<attr>0x00</attr>
<attr>0xFF</attr>
<img_name image_type="hlos" optional="true" type="string"
wififw_type="1">wifi_fw_ipq5332_qcn6432_squashfs.img </img_name>
</partition>
ipq5332/flash_partition/emmc-partition.xml
<partition
label="0:WIFIFW"
size_in_kb="12288"
type="888d8069-8d27-40a8-95a9-6006e1ce9b3b"
bootable="false"
readonly="false"
image_type = "hlos"
optional="true"
filename="wifi_fw_ipq5332_qcn9224_v2_single_dualmac_squashfs.img"
/>
Change-Id: I1b5835b0835f2c05958924ad6ce5f403e934aac4
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
tiny-nor was using ubi volume name "wifi_fw" instead
of partition name "0:WIFIFW". This change fixes the same.
Change-Id: I55dc83a2cc40178ffffdfa25fe20a739f21040ad
Signed-off-by: Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>
This patch resolves the wififw section name mis-match for
the nor flash types.
In image info, wififw-SHA-HASH is used, whereas in the scripts
wifi_fw_ipq5332_qcn6432-SHA-HASH is used. It occur on nor-only build.
For nand/nor+nand, wifi usually in the ubi volume. Incase of
emmc, it is properly taken care.
So, handled all nor-only cases (including tiny-nor) as
similar as emmc case.
Change-Id: I3741a8255da487ad0546d9706933d19f1b1a3a93
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch updates the pack & pack-v2 scripts with python3
compatible support
Change-Id: I2bf9a1cb2dedbdae94355aed4078d9f792fc7ba9
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
For 'tiny-nor' flash type, new configuration is added.
Update the script to read the new parameter.
Change-Id: I0d0e3e5332dfe6476da735d0defb4b43754f02ee
Signed-off-by: Rajkumar Ayyasamy <quic_arajkuma@quicinc.com>
Signed-off-by: Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>
This patch adds the NAND 64M flash support and adds
the new param --flash_size to denote the flash size
Change-Id: I101cf75d2f1d177475052b8f90cb0cdf30731a20
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
If flash image type is emmc, switch the flash
type to emmc from nor in norplusemmc board using
the flupdate commands. Once the image is flashed
switch back the flash type to nor using the same
flupdate commands.
This change is to support the below Change-Id
Ib328cc1fea0b37f27e6479d55fce08365fbfcf69
Change-Id: Ia5f75923d7bdfd313a986826f1ac2f7f571c414a
Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
This patch provides the fix for emmc apps image generation.
The partition variable value has to be marked as null
for the partitions to be skipped in apps image generation.
Change-Id: I0067c527f0de38eb513e27fadfeee2accb69f3d3
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
This patch adds the additional conditional check to filter
out wififw images for nor flash type
Change-Id: Iba078721fbfc5ed4cd3bd74689e9ba6352a69130
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
This patch update the mibib_reload sequence by checking 0:MIBIB in
all partitions info instead of using a specific partition index
and this change has some code cleanup
Change-Id: I09b3be3be7a5bfae7dc5ddc5c2ae54f6b06a7333
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
This patch updates the following things.
1. Simplified the wififw pack script logic
2. Added the multi fw version support with simple changes
i. To add RDP specific fw img, mention the corresponding fw
name under each RDP entry in config.xml like below.
<wififw_name>file-name</wififw_name>
ii. When we migrate to new fw version for a specfic chipset,
add the following entry in the config.xml.
<data type="VERSION_PARAMETER">
<version_check>chip-set-number</version_check>
<default_version>base-fw-version</default_version>
</data>
Note: Also, make sure that all the fw names mentioned in the
config.xml are in the base verison.
iii. Once migration is done, remove the entries added in (ii).
and rename the new version fw names in the config.xml as
mentioned in the (i).
Change-Id: I296dab47e9ff321a1ed44130df8fc5cdd8a5bfa5
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
added boot type based nand or emmc flash selection.
So machid based flash selection becomes obsolete.
Change-Id: I96fa43d31d23397fa249e02f62b905d6e4e67770
Signed-off-by: Rajkumar Ayyasamy <quic_arajkuma@quicinc.com>
xtract_n_flash $imgaddr $filename $partname
The above cmd can be used instead of below set of cmds
imxtract $imgaddr $filename
erase <offset> <size>
write <fileaddr> <offset> <filesize>
This patch also removes padding as it will be taken
care by the flash cmd itself
Change-Id: Id55d844103a97a6a621545e4d62d3da408ffa61c
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
Signed-off-by: Rajkumar Ayyasamy <quic_arajkuma@quicinc.com>
Reverted the changes till the below commit
d84c9f230d ("tools: pack: add new option to select fw based on
machid")
Change-Id: I0578dd5014fbd1d4669065e0bff566c9fc899811
Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
Add the snapshot as of below commit from win.coretech.1.0 branch
9e40b52661 ("tools: pack: Update pack script for IPQ9574")
Change-Id: Iebafae7f827a5ae8bb0b48ca9c899f2672f65fb3
Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
