Hi,
1) Yes, you could use the ">" output redirection at your EBlink invocation. This is more a OS feature to be honest.
If you need to read a particular memory location and write this to file, use the verbose level 0, this will omit all the info text and will give you only the memory value(s).
Remember, the output is an hex array (memory dump) of bytes because you can read any length of memory. So if you need to read an unsigned 32 you have to rebuild it by endianness your self.
P.s. If you used the EBlink installer then you can invoke EBlink in any directory. Just open a terminal in the directory where your file should be written and use the above command.
2) Depends what you mean with terminal application. You can from CLI:
- start/stop/reset the core
- read memory locations even from running target without stopping it
- write flash locations even from running target without stopping it
1) Yes, you could use the ">" output redirection at your EBlink invocation. This is more a OS feature to be honest.
If you need to read a particular memory location and write this to file, use the verbose level 0, this will omit all the info text and will give you only the memory value(s).
Code:
EBlink -v0 -Istlink -Sauto -Fread=4@0x8000004 > outfile.txtRemember, the output is an hex array (memory dump) of bytes because you can read any length of memory. So if you need to read an unsigned 32 you have to rebuild it by endianness your self.
P.s. If you used the EBlink installer then you can invoke EBlink in any directory. Just open a terminal in the directory where your file should be written and use the above command.
2) Depends what you mean with terminal application. You can from CLI:
- start/stop/reset the core
- read memory locations even from running target without stopping it
- write flash locations even from running target without stopping it