comparison doc/Loadtools-usage @ 586:f3af56eac3f4

doc/Loadtools-usage: -P option instead of -n
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 03 Feb 2020 07:51:11 +0000
parents a97d96e0fc5c
children 7674abe34c25
comparison
equal deleted inserted replaced
585:d3e2b23ebf1d 586:f3af56eac3f4
227 In this mode the jump command to start executing the loaded image is 227 In this mode the jump command to start executing the loaded image is
228 skipped and the target is left in loadagent, allowing the developer to 228 skipped and the target is left in loadagent, allowing the developer to
229 connect via JTAG, halt the ARM7 core, set whatever breakpoints or 229 connect via JTAG, halt the ARM7 core, set whatever breakpoints or
230 watchpoints are needed and resume at the image start address. 230 watchpoints are needed and resume at the image start address.
231 231
232 -n 232 -P <boot control name>
233 233
234 This option does anything only when loadtools have been compiled to run 234 This option is common for all utilities in the loadtools suite; it
235 on GTA0x AP (see the Loadtools-on-GTA0x article). If you've compiled 235 tells the tools to perform target boot control as described in the
236 loadtools with the -DGTA0x_AP_BUILD option, it has an effect of making 236 Target-boot-control article.
237 each tool automatically toggle the modem power control upon startup,
238 removing the need for manual sequencing of the Calypso boot process.
239 This -n option suppresses that action, making the AP build behave like
240 the standard build in this regard.
241 237
242 -r baud (fc-loadtool) 238 -r baud (fc-loadtool)
243 239
244 This option is specific to fc-loadtool. It causes the tool to skip its 240 This option is specific to fc-loadtool. It causes the tool to skip its
245 normal steps of feeding loadagent and possibly compalstage to the target 241 normal steps of feeding loadagent and possibly compalstage to the target