Difference between revisions of "Default Configuration Customization"
| (7 intermediate revisions by 2 users not shown) | |||
| Line 16: | Line 16: | ||
In order to create a custom version of the Default Configuration you need to do the following: | In order to create a custom version of the Default Configuration you need to do the following: | ||
# change with binary-editor the configuration values in the config.bin file | # change with binary-editor the configuration values in the '''config.bin''' file | ||
# run the web2cob command (batch file available in the package) to generate the file xxxxapp.cob | # run the web2cob command (batch file available in the package) to generate the file '''xxxxapp.cob''' | ||
# copy the config.bin and the xxxxapp.cob file in the update-rescue folder | # copy the config.bin and the xxxxapp.cob file in the update-rescue folder | ||
# run the load_win command (batch file available in the package) to generate the compound.bin file | # run the load_win command (batch file gen.bat available in the package) to generate the '''compound.bin''' file | ||
NOTE: the configuration parameters mapping can be found in the Technical Documention of the Firmware | NOTE: the configuration parameters mapping can be found in the Technical Documention of the Firmware | ||
| Line 32: | Line 32: | ||
These 2 files are merged in a new config.bin file in folder "update_rescue". | These 2 files are merged in a new config.bin file in folder "update_rescue". | ||
In order to create a custom version of the Default Configuration you need to do the following: | In order to create a custom version of the Default Configuration you need to do the following: | ||
# change with binary-editor the configuration values in the config.bin file (1 | # change with binary-editor the configuration values in the '''config.bin''' file (1) | ||
# run the web2cob command (batch file abclapp.bat available in the package) to generate the file '''abclapp.cob''' | |||
# run the web2cob command (batch file abclapp.bat available in the package) to generate the file abclapp.cob | # change with binary-editor the configuration values in the '''appconfig.bin''' file (2) | ||
# run the tokenizer and web2cob commands (batch file applctns.bat available in the package) to generate the file applications.cob | # run the tokenizer and web2cob commands (batch file applctns.bat available in the package) to generate the file '''applications.cob''' | ||
# merge the two configuration files into one (e.g. use "cat" from command-line: cat config.bin appconfig.bin > config.bin) | # merge the two configuration files into one (e.g. use "cat" from command-line: cat config.bin appconfig.bin > config.bin) | ||
# copy the config.bin, abclapp.cob and the applications.cob file in the update-rescue folder | # copy the config.bin, abclapp.cob and the applications.cob file in the update-rescue folder | ||
# run the load_win command (batch file gen.bat available in the package) to generate the compound.bin file | # run the load_win command (batch file gen.bat available in the package) to generate the '''compound.bin''' file | ||
NOTE (1): the configuration parameters mapping can be found in the Technical Documention of the Firmware | NOTE (1): the configuration parameters mapping can be found in the Technical Documention of the Firmware | ||
NOTE (2): the configuration parameters mapping can be found in the EEPROM layout Documention in the same folder | NOTE (2): the configuration parameters mapping can be found in the EEPROM layout Documention in the same folder | ||
'''IMPORTANT: Do not forget to apply "Factory Defaults" after uploading the new binaries onto the device.''' | |||
Latest revision as of 14:13, 17 November 2011
Default Configuration Customization
How to customize the default configuration settings of your Barix Audio product.
WARNING: The following tips are intended only for expert users of Barix products as they may cause misconfiguration of the devices.
Standard Firmware Package
The configuration information are contained in one file
► config.bin located in folder "webuidevkit/xxxxapp" where xxxx depends on the SW package.
The same file is copied also in folder "update_rescue".
In order to create a custom version of the Default Configuration you need to do the following:
- change with binary-editor the configuration values in the config.bin file
- run the web2cob command (batch file available in the package) to generate the file xxxxapp.cob
- copy the config.bin and the xxxxapp.cob file in the update-rescue folder
- run the load_win command (batch file gen.bat available in the package) to generate the compound.bin file
NOTE: the configuration parameters mapping can be found in the Technical Documention of the Firmware
ABCL Firmware/Application Package
The configuration information are contained in two different files
► config.bin located in folder "webuidevkit/abclapp" for the common abcl settings
► appconfig.bin located in folder "bcldevkit" for the application specific settings
These 2 files are merged in a new config.bin file in folder "update_rescue".
In order to create a custom version of the Default Configuration you need to do the following:
- change with binary-editor the configuration values in the config.bin file (1)
- run the web2cob command (batch file abclapp.bat available in the package) to generate the file abclapp.cob
- change with binary-editor the configuration values in the appconfig.bin file (2)
- run the tokenizer and web2cob commands (batch file applctns.bat available in the package) to generate the file applications.cob
- merge the two configuration files into one (e.g. use "cat" from command-line: cat config.bin appconfig.bin > config.bin)
- copy the config.bin, abclapp.cob and the applications.cob file in the update-rescue folder
- run the load_win command (batch file gen.bat available in the package) to generate the compound.bin file
NOTE (1): the configuration parameters mapping can be found in the Technical Documention of the Firmware
NOTE (2): the configuration parameters mapping can be found in the EEPROM layout Documention in the same folder
IMPORTANT: Do not forget to apply "Factory Defaults" after uploading the new binaries onto the device.
