pib2xml.1 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114
  1. .TH pib2xml 1 "Mar 2014" "plc-utils-2.1.6" "Qualcomm Atheros Powerline Toolkit"
  2. .SH NAME
  3. pib2xml - print object driven xml editior intructions
  4. .SH SYNOPSIS
  5. .BR pib2xml
  6. .RI [ options ]
  7. .IR file
  8. .RI [ file ]
  9. .RI [ ... ]
  10. .RI [> stdout ]
  11. .SH DESCRIPTION
  12. Write XML editor instructions on stdout.
  13. This requires an object definition file that contains the size and name of data regions and members within a binary object or file.
  14. Individual data members are presented as XML instructions that can be used by program \fBpxe\fR to edit PIB files.
  15. .SH OPTIONS
  16. .TP
  17. -\fBf\fI definitions\fR
  18. The name of the object definition file that contains the size, name and description of objects within a binary file.
  19. The definition file is not modified.
  20. This option is required.
  21. There is no default file.
  22. .TP
  23. -\fBs\fI schema\fR
  24. The url for the XML schema.
  25. The default schema is \fBpiboffset.xsd\fR for the Qualcomm Atheros Powerline Toolkit verion of this program.
  26. .TP
  27. .RB - x
  28. Print an XML schema on stdout.
  29. This schema defines the elements and attributes used to define data objects and members read from input files.
  30. It can be used to validate XML files used with program \fBpxe\fR.
  31. .TP
  32. .RB - ? ,-- help
  33. Print program help summary on stdout.
  34. This option takes precedence over other options on the command line.
  35. .TP
  36. .RB - ! ,-- version
  37. Print program version information on stdout.
  38. This option takes precedence over other options on the command line.
  39. 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.
  40. .SH ARGUMENTS
  41. .TP
  42. .IR file
  43. The name of a binary file.
  44. The file must have either Thunderbolt/Lightning or Panther/Lynx format or output will be incorrect.
  45. The file is not modified by this program.
  46. Only one such file is permitted on the command line.
  47. .SH EXAMPLES
  48. The following is an example object definition file that defines a standard ethernet frame and member fields within it.
  49. The comments and descriptions shown are optional.
  50. The field lengths and field names are not.
  51. Zero-length fields denote arbitrary field groups and are used by program \fBoffset\fR to print headings.
  52. .PP
  53. # ========================================
  54. #
  55. # ----------------------------------------
  56. 0 header
  57. 6 ODA Own Destination Address
  58. 6 OSA Own Source Address
  59. 2 ET Ethertype or frame length
  60. # ========================================
  61. #
  62. # ----------------------------------------
  63. 0 body
  64. 1500 Payload
  65. # ========================================
  66. #
  67. # ----------------------------------------
  68. 0 trailer
  69. 4 CRC Cyclical Redundancy Check
  70. .PP
  71. The following command uses object definition file \fBether.txt\fR to identify and display member fields within binary file \fBabc.bin\fR as a set of xml instructions that can be used by program \fBxde\fR to edit other files.
  72. .PP
  73. # pib2xml -f ether.txt abc.bin
  74. .PP
  75. The next command writes the xml schema that defines the elements and attributes used in the edit instructions to file \fBdata.xsd\fR.
  76. This file can be used to validate xml edit instructions.
  77. .PP
  78. # pib2xml -x > data.xsd
  79. .SH SEE ALSO
  80. .BR chkpib (7),
  81. .BR chkpib2 (7),
  82. .BR getpib (7 ),
  83. .BR modpib ( 1 ),
  84. .BR pibcomp ( 1 ),
  85. .BR pibdump ( 1 ),
  86. .BR setpib ( 1 ),
  87. .BR xml2pib ( 1 )
  88. .SH CREDITS
  89. Charles Maier <cmaier@cmassoc.net>