Segger J-Link User Manual page 77

3.2.1.14 fwrite (fwr)
On emulators which support file I/O this command writes a specific file. Currently,
only Flasher models support file I/O.
NumBytes is limited to 512 bytes at once. This means, if you want to write e.g. 1024
bytes, you have to send the command twice, using an appropriate offset when send-
ing it the second time. Offset applies to both destination and source file.
Syntax
fwrite <EmuFile> <HostFile> [<Offset> [<NumBytes>]]
Parameter
EmuFile
HostFile
Offset
NumBytes
Example
fwrite Flasher.dat C:\Project\Flasher.dat
3.2.1.15 go (g)
Starts the CPU. In order to avoid setting breakpoints it allows to define a maximum
number of instructions which can be simulated/emulated. This is particulary useful
when the program is located in flash and flash breakpoints are used. Simulating
instructions avoids to reprogram the flash and speeds up (single) stepping.
Syntax
go [<NumSteps> [<Flags>]]
Parameter
NumSteps
Flags
Example
go //Simply starts the CPU
go 20, 1
3.2.1.16 halt (h)
Halts the CPU Core. If successful, shows the current CPU registers.
Syntax
halt
3.2.1.17 hwinfo
This command can be used to get information about the power consumption of the
target (if the target is powered via J-Link). It also gives the information if an over-
current happened.
Syntax
hwinfo
J-Link / J-Trace (UM08001)
File name to write to.
Source file on the host
Specifies the offset in the file, at which data writing is started.
Maximum number of bytes to write.
Maximum number of instructions allowed to be simulated. Instruc-
tion simulation stops whenever a breakpointed instruction is hit, an
instruction which cannot be simulated/emulated is hit or when Num-
Steps is reached.
0: Do not start the CPU if a BP is in range of NumSteps
1: Overstep BPs
Meaning
Meaning
© 2004-2017 SEGGER Microcontroller GmbH & Co. KG
77