| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
by libswd internals. Will change and might not work as expected, feel free to test and feedback results :-) The goal is to have enqueued by openocd operations executed with no need for error handling (which is impossible on multiple operations enqueued and also not supported by openocd anyway) just as they were executed correctly for the first time. Error handling, retries, communication verification, etc should be done by underlying transport library (libswd in this case). swdctx->config.trunccmdqonerror=0 will result in untouched queue on error response from target (before the queue was truncated to make room for manual error handling). work in progres...
|
| |
|
|
| |
Target read functions should now work with double pointers in order to return data on flush and not produce flush on read.
|
| | |
|
| |
|
|
| |
and all sticky error flags (do we need to clear them anyway even after ABORT?).
|
| |
|
|
| |
not return data where is should, 2. calling reads with NULL pointer caused program crash.
|
| |
|
|
| |
cannot be queued up and fulshed at later time because OpenOCD use single pointers for data return from function and it is impossible to read out dynamically allocated memory this way in C.
|
| |
|
|
| |
11.04. Thanks to Przemyslaw Wegrzyn for pointing this out :-)
|
| |
|
|
| |
startup with other commands.
|
| |
|
|
| |
transport initialization and only if context is created. 2. swd_log() use vprintf as using openocd logging mechanisms caused program crash by va recurrence. 3. Fixed tcl interface to use/update loglevel configuration parameter from swdctx stored within dap.
|
| |
|
|
| |
after the DAP is created, DAP also holds the swdctx. transport_select() now only marks transport type and registers swd transport commands. Target system now consists of TAP (that is the test access port of the device), DAP (that is the debug access port of the arm system) and the TARGET+FLASH itself that allow to perform operations on the target architecture + memory. Interface and Transport connects to the TAP and allows operations on the TARGET using DAP.
|
| |
|
|
| |
registered at transport select. Available commands are 'newdap' currently pointing to jtag_newtap, 'loglevel' that can show/set/inherit loglevel for easier log analysis during development.
|
| |
|
