tonvm.1 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. .TH tonvm 1 "Mar 2014" "plc-utils-2.1.6" "Qualcomm Atheros Powerline Toolkit"
  2. .SH NAME
  3. tonvm - Prepend Lightning/Thunderbolt NVM Image header
  4. .SH SYNOPSIS
  5. .BR tonvm
  6. .RI [ options ]
  7. .IR file
  8. .RI [ file ]
  9. .RI [ ... ]
  10. .SH DESCRIPTION
  11. This tool is used to prepend a NVM header to an image file that can be used by \fBThunderbolt\fR and \fRLightning\fR\ ICs.
  12. The tool makes no attempt to check any internal information other than firmware header checksums, image lengths and image checksums.
  13. .PP
  14. This program handles \fBThunderbolt\fR and \fBLightning\fR chipsets only.
  15. .PP
  16. This program is part of the Qualcomm Atheros Powerline Toolkit.
  17. .SH OPTIONS
  18. .TP
  19. .RB - E
  20. Entry Point address for image. This is the address in SDRAM where execution will start. This value is used by the bootloader during start-up.
  21. .TP
  22. .RB - F
  23. Address in flash where the image should be stored. This is the address in flash (NVM) that the image will be stored at. This value is read and used by the runtime firmware when writing the flash memory.
  24. .TP
  25. .RB - M
  26. Module ID of the image. This value specifies the type of module that this header will be used for. ( 0=softloader,1=firmware,2=pib,3=custom module)
  27. .TP
  28. .RB - m
  29. Sub-Module ID of the image. This value specifies the type of sub-module that this header will be used for. ( used only for custom modules)
  30. .TP
  31. .RB - S
  32. Address in SDRAM where the image should be stored.
  33. .TP
  34. .RB - T
  35. Image type
  36. .TP
  37. .RB - I
  38. Ignore mask
  39. .TP
  40. .RB - ? ,-- help
  41. Print program help summary on stdout.
  42. This option takes precedence over other options on the command line.
  43. .TP
  44. .BR - ! ,-- version
  45. Print program version information on stdout.
  46. This option takes precedence over other options on the command line.
  47. 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.
  48. .SH ARGUMENTS
  49. .TP
  50. .IR file
  51. The name of the image file that should be used to prepend the header.
  52. By convention, Atheros Image files have a \fB.nvm\fR file extension but this program does not enforce this convention.
  53. .SH DISCLAIMER
  54. Qualcomm Atheros firmware file structure and content is proprietary to Qualcomm Atheros, Ocala FL USA.
  55. Consequently, public information is not available.
  56. Qualcomm Atheros reserves the right to change firmware file structure or content or change the name or behavior of any program that inspects or changes firmware files, in future software releases without any obligation to notify or compensate users of such programs.
  57. .SH EXAMPLES
  58. This example reads file abc.nvm and uses it to prepend a header. The entry address is set to 0x00000AFC and the flash address is set to 0x78
  59. .PP
  60. # tonvm -E 0x00000AFC -F 0x00000078 abc.nvm
  61. .SH SEE ALSO
  62. .BR chknvm ( 1 ),
  63. .BR chkpib ( 1 ),
  64. .BR chkpib1 ( 1 ),
  65. .BR chkpib2 ( 1 ),
  66. .BR int6ktest (7),
  67. .BR nvmmerge ( 1 ),
  68. .BR nvmsplit ( 1 ),
  69. .BR plctest ( 7)
  70. .SH CREDITS
  71. Charles Maier <cmaier@qca.qualcomm.com>