Forums - Did "Appending tunable data sets to firmware binary" work?

2 posts / 0 new
Last post
Did "Appending tunable data sets to firmware binary" work?
douglas.turnbow
Join Date: 26 Nov 14
Posts: 11
Posted: Wed, 2015-03-25 11:45

I just went through section 6.4.3 "Appending tunable data sets to firmware binary" of 80-Y9106-6_A_I-WSR3_3_2_Hosted_Release_Notes_non-NDA.pdf.  

A few things look questionable to me.  I'm just wondering if it "worked" or not.  

1. There is a status message "cannot stat 'rodset.bin'.  Is this a problem?

2. The original flashotp*.bin file is 139k bytes, but the flashtop*.bin.new file is only 684 bytes. (file name changed from otp to top and the size changed to something smaller).  Is this a problem?

3. The raw_flashimage*.bin file and raw_flashimage*.bin.new files are the same size.  Should they be?

Here's the contents of the terminal interaction:

[developer@localhost htmltoflash]$ ./flash_readonly_dset_update.sh raw_flashimage_AR400X_REV4_IOT_SP144_hosted_dualband.bin flashtop_AR400X_REV4_IOT_SP144_hosted_dualband.bin ../tunable_dset/sp144_4bitflash rodset.bin
TOOLDIR=.
TUNABLE DIR : ../tunable_dset/sp144_4bitflash RODSETIMAGE Name: rodset.bin
./htmltoflash.sh File "filelist" not found. Skipping HTML files
stat: cannot stat `rodset.bin': No such file or directory
Size of rodset.bin after HTML appending is :
Appending dset ID 0xa02 with data from ../tunable_dset/sp144_4bitflash/dset_tunable_1.bin to rodset.bin
Appending dset ID 0xa03 with data from ../tunable_dset/sp144_4bitflash/dset_tunable_2.bin to rodset.bin
Appending dset ID 0xa04 with data from ../tunable_dset/sp144_4bitflash/dset_tunable_3.bin to rodset.bin
stat: cannot stat `flashtop_AR400X_REV4_IOT_SP144_hosted_dualband.bin': No such file or directory
New binary created: flashtop_AR400X_REV4_IOT_SP144_hosted_dualband.bin.new
Generated FLASHOTP image with RODSET
Generated RAW FLASH image with RODSET
Creating image: ota_raw_flashimage_AR400X_REV4_IOT_SP144_hosted_dualband.bin.new
Generated OTA RAW FLASH image with RODSET
[developer@localhost htmltoflash]$ ls -l
total 960
-rwxr-xr-x 1 developer developer   2022 2015-03-23 09:46 create_rodset.sh
-rwxr-xr-x 1 developer developer   3495 2015-03-23 09:46 dset_insert.sh
-rwxr-xr-x 1 developer developer 139664 2015-03-23 09:46 flashotp_AR400X_REV4_IOT_SP144_hosted_dualband.bin
-rwxr-xr-x 1 developer developer   3080 2015-03-23 09:46 flash_readonly_dset_update.sh
-rw-rw-r-- 1 developer developer    684 2015-03-25 14:10 flashtop_AR400X_REV4_IOT_SP144_hosted_dualband.bin.new
-rwxr-xr-x 1 developer developer   2349 2015-03-23 09:46 htmltoflash.sh
-rwxr-xr-x 1 developer developer   7138 2015-03-23 09:46 makeimg.sh
-rwxr-xr-x 1 developer developer   6157 2015-03-23 09:46 makeseg.sh
-rwxr-xr-x 1 developer developer    948 2015-03-23 09:46 mkrodset.sh
-rw-rw-r-- 1 developer developer 262144 2015-03-25 14:10 ota_raw_flashimage_AR400X_REV4_IOT_SP144_hosted_dualband.bin.new
-rwxr-xr-x 1 developer developer   1848 2015-03-23 09:46 ota.sh
-rwxr-xr-x 1 developer developer 262144 2015-03-23 09:46 raw_flashimage_AR400X_REV4_IOT_SP144_hosted_dualband.bin
-rw-rw-r-- 1 developer developer 262144 2015-03-25 14:10 raw_flashimage_AR400X_REV4_IOT_SP144_hosted_dualband.bin.new
-rwxr-xr-x 1 developer developer   2074 2015-03-23 09:46 readme.txt
-rw-rw-r-- 1 developer developer    636 2015-03-25 14:10 rodset.bin
  • Up0
  • Down0
manjulak Moderator
Join Date: 5 Dec 14
Posts: 33
Posted: Wed, 2015-05-13 14:03

1. "cannot stat 'rodset.bin' is not a problem. It is created by the script and contains all the tunable binary information. This file is not used elsewhere.
2. You should not see "stat: cannot stat `flashtop_AR400X_REV4_IOT_SP144_hosted_dualband.bin': No such file or directory". Make sure you copied flashotp_AR400X_REV4_IOT_SP144_hosted_dualband.bin from target/bin to tool/htmltoflash folder. flashotp*.bin.new file will be closer in size to original flashotp*.bin file.
3. The raw_flashimage*.bin file and raw_flashimage*.bin.new files will be same size.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.