target_type struct

Name of this type of target. Do @b not access this field directly, use target_type_name() instead.

The implementation is responsible for polling the target such that target->state reflects the state correctly. Otherwise the following would fail, as there will not be any "poll" invoked between the "reset run" and "halt". reset run; halt.

Target architecture for GDB. The string returned by this function will not be automatically freed; if dynamic allocation is used for this value, it must be managed by the target, ideally by caching the result for subsequent calls.

Target register access for GDB. Do @b not call this function directly, use target_get_gdb_reg_list() instead. Danger! this function will succeed even if the target is running and return a register list with dummy values. The reason is that GDB connection will fail without a valid register list, however it is after GDB is connected that monitor commands can be run to properly initialize the target.

Same as get_gdb_reg_list, but doesn't read the register values.

Target memory read callback. Do @b not call this function directly, use target_read_memory() instead.

Target memory write callback. Do @b not call this function directly, use target_write_memory() instead.

Target algorithm support. Do @b not call this method directly, use target_run_algorithm() instead.

This method is used to perform target setup that requires JTAG access. This may be called multiple times. It is called after the scan chain is initially validated, or later after the target is enabled by a JRC. It may also be called during some parts of the reset sequence. For one-time initialization tasks, use target_was_examined() and target_set_examined(). For example, probe the hardware before setting up chip-specific state, and then set that flag so you don't do that again.

Free all the resources allocated by the target. WARNING: deinit_target is called unconditionally regardless the target has ever been examined/initialised or not. If a problem has prevented establishing JTAG/SWD/... communication or if the target was created with -defer-examine flag and has never been examined then it is not possible to communicate with the target. If you need to talk to the target during deinit, first check if target_was_examined()!.