pibdump.1 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. .TH pibdump 1 "Mar 2014" "plc-utils-2.1.6" "Qualcomm Atheros Powerline Toolkit"
  2. .SH NAME
  3. pibdump - Qualcomm Atheros Parameter Information Block Dump Utility
  4. .SH SYNOPSIS
  5. .BR pibdump
  6. .RI [ options ]
  7. .IR file
  8. .RI [> stdout ]
  9. .SH DESCRIPTION
  10. Read a Qualcomm Atheros powerline parameter information block (PIB) file and print an object driven dump on stdout.
  11. This program replaces program \fBodd\fR because it distinguishes between legacy and current PIB file formats.
  12. .PP
  13. An object driven dump requires an object definition file that lists the size and name of data objects (ie; integers, arrays or structures) within the parameter file.
  14. Individual data members are presented as smaller, individual data dumps within a larger, overall data dump.
  15. .SH OPTIONS
  16. .TP
  17. -\fBf\fI file\fR
  18. The object definition file that lists the size, name and description of individual individual objects in order of occurance.
  19. If this option is omitted then object definitions are read from stdin.
  20. The object definition file is not modified by this program.
  21. .TP
  22. .RB - ? ,-- help
  23. Print program help summary on stdout.
  24. This option takes precedence over other options on the command line.
  25. .TP
  26. .RB - ! ,-- version
  27. Print program version information on stdout.
  28. This option takes precedence over other options on the command line.
  29. 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.
  30. .SH ARGUMENTS
  31. .TP
  32. .IR file
  33. The name of a binary file.
  34. The file must have either Thunderbolt/Lightning or Panther/Lynx format or output will be incorrect.
  35. The file is not modified by this program.
  36. Only one such file is permitted on the command line.
  37. .SH EXAMPLES
  38. The following is an example object definition file for an Ethernet frame.
  39. Frame fields, like \fBODA\fR, \fBOSA\fR and \fBETHTYPE\fR, are defined by \fIlength\fR in order of their appears in the frame.
  40. Array subscripts following object names are optional but, if present, become part of the object name.
  41. Fields having no \fIlength\fR are headers and will be ignored.
  42. Comments and blank lines are also ignored.
  43. .PP
  44. # ========================================
  45. #
  46. # ----------------------------------------
  47. 0 header
  48. 6 ODA[6] Own Destination Address
  49. 6 OSA[6] Own Source Address
  50. 2 ETHTYPE Ethertype or frame length
  51. # ========================================
  52. #
  53. # ----------------------------------------
  54. 0 body
  55. 1500 Payload[1500]
  56. # ========================================
  57. #
  58. # ----------------------------------------
  59. 0 trailer
  60. 4 CRC Cyclical Redundancy Check
  61. .PP
  62. The following command uses object definition file \fBether.txt\fR to identify and display member fields within binary file \fBabc.bin\fR in hexadecimal dump format.
  63. .PP
  64. # pibdump -f ether.txt abc.bin
  65. .SH SEE ALSO
  66. .BR chkpib (7),
  67. .BR chkpib2 (7),
  68. .BR getpib (7 ),
  69. .BR modpib ( 1 ),
  70. .BR pib2xml ( 1 ),
  71. .BR pibcomp ( 1 ),
  72. .BR setpib ( 1 ),
  73. .BR xml2pib ( 1 )
  74. .SH CREDITS
  75. Charles Maier <cmaier@qca.qualcomm.com>