config2cfg.1 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. .TH config2cfg 1 "Mar 2014" "plc-utils-2.1.6" "Qualcomm Atheros Powerline Toolkit"
  2. .SH NAME
  3. config2cfg \- Atheros Configuration File Converter
  4. .SH SYNOPSIS
  5. \fBconfig2cfg\fR [\fBoptions\fR] \fBfile\fR [\fBfile\fR] [\fB...\fR]
  6. .SH DESCRIPTION
  7. The \fBconfig2cfg\fR program converts an SDRAM configuration file used by the Windows Device Manager to the configuration file format used by the Qualcomm Atheros Powerline Toolkit.
  8. .P
  9. This program is part of the Qualcomm Atheros Powerline Toolkit.
  10. See the \fBAMP\fR man page for an overview and installation instructions.
  11. .SH OPTIONS
  12. There are no options.
  13. .SH EXPLANATION
  14. The Windows Device Manager format consists of 64 ASCII hexadecomal characters.
  15. Files usually have a \fB.config\fR extension.
  16. File size is at least 64 characters.
  17. Excess characters are ignored in input.
  18. This means that files can be modified using any text editor and there is no way to detect modification.
  19. From a programmin standpoint, ASCII-to-binary convertion and checksum computation is required on input and binary-to-ASCII conversion iw required on output.
  20. .PP
  21. The Atheros Powerline Toolkit format consists of 32 binary bytes plus a 4 byte (32 bit) checksum.
  22. Files usually have a \fB.cfg\fR extension.
  23. File size is always 36 characters.
  24. The files can be edited using any hex editor but a new checksum must be computed and inserted after any change.
  25. No conversion or computation is required on input or output.
  26. Input is ready for direct insertion into a VS_SET_SDRAM message.
  27. .PP
  28. Programs \fBint6k\fR and \fBint6kf\fR expect this latter format and so you can use this program determine if a given file has the proper format.
  29. .SH OPTIONS
  30. .TP
  31. \fIfile\fR
  32. The filename of a Windows Device Manager SDRAM configuration file.
  33. The file is re-written such that the filename is preserved but the contents are not.
  34. Windows Device Manager SDRAM configuration files usually have a \fB.config\fR extension but the program makes no assumption based on filename and does not enforce any filename conventions.
  35. .TP
  36. \fB\-q\fR
  37. Suppresses printing of progress messages.
  38. There are no progress messages in this version.
  39. .TP
  40. \fB\-v\fR
  41. Print additional information.
  42. There is no additional information printed in this version.
  43. .TP
  44. -\fB?\fR, --\fBhelp\fR
  45. Print program help summary on stdout.
  46. This option takes precedence over other options on the command line.
  47. .TP
  48. -\fB!\fR, --\fBversion\fR
  49. Print program version information on stdout.
  50. This option takes precedence over other options on the command line.
  51. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of the Linux Toolkit you are using.
  52. .SH EXAMPLES
  53. The following example reads file abc.cfg and validates it.
  54. The message shown indicates that the configuration file is the correct size and has a checksums and there are no read errors.
  55. .P
  56. > chkcfg abc.cfg
  57. chkcfg: abc.cfg looks good
  58. .P
  59. The following example reads three files in succession and reports on each one.
  60. You can suppress good news with the \fB-q\fR option.
  61. .P
  62. # chkcfg abc.cfg def.cfg ghi.cfg
  63. chkcfg: abc.cfg looks good
  64. chkcfg: def.cfg is corrupt
  65. chkcfg: ghi.cfg looks good
  66. .P
  67. The following example displays the SDRAM configuration values in all files having names that match the wildcard pattern \fBsdram*.cfg\fR.
  68. We can confirm that the values inside are correct for their filenames.
  69. Program output could have been sent to a file and saved for later reference.
  70. .P
  71. # chknvm -qv sdram*.cfg
  72. ------- sdram32.cfg -------
  73. SIZE=0x02000000 (32mb)
  74. CONF=0x00143188
  75. TIM0=0x01E1D491
  76. TIM1=0x000883D6
  77. CNTRL=0x00003089
  78. REF=0x00000366
  79. CLOCK=0x00000001
  80. ------- sdram16.cfg -------
  81. SIZE=0x01000000 (16mb)
  82. CONF=0x00142F68
  83. TIM0=0x0115124E
  84. TIM1=0x000883D6
  85. CNTRL=0x00003089
  86. REF=0x00000493
  87. CLOCK=0x00000001
  88. .SH DISCLAIMER
  89. The SDRAM file structure and content is proprietary to Qualcomm Atheros, Ocala FL USA.
  90. Consequently, public information is not available.
  91. Qualcomm Atheros reserves the right to change the file structure or content in future firmware releases without any obligation to notify or compensate users of this program.
  92. .SH SEE ALSO
  93. .BR int6k ( 1 ),
  94. .BR int6kf ( 1 ),
  95. .BR modpib ( 1 ),
  96. .BR chknvm ( 1 ),
  97. .BR chkpib ( 1 )
  98. .SH CREDITS
  99. Charles Maier <cmaier@qca.qualcomm.com>