An Implementation of JTAG API to Perform Dynamic Program Analysis for Embedded Systems


KIPS Transactions on Computer and Communication Systems, Vol. 3, No. 2, pp. 31-42, Feb. 2014
10.3745/KTCCS.2014.3.2.31,   PDF Download:

Abstract

Debugger systems are necessary to apply dynamic program analysis when evaluating security properties of embedded system software. It may be possible to make the use of software-based debugger and/or DBI framework if target devices support general purpose operating systems, however, constraints on applicability as well as environmental transparency might be incurred thereby hindering overall analyzability. Analysis with JTAG (IEEE 1149.1) debugging devices can overcome these difficulties in that no change would be involved in terms of internal software environment. In that sense, JTAG API can facilitate to practically perform dynamic program analysis for evaluating security properties of target device software. In this paper, we introduce an implementation of JTAG API to enable analysis of ARM core based embedded systems. The API function set includes the categories of debugger and target device controls: debugging environment and operation. To verify API applicability, we also provide example analysis tool implementations: our JTAG API could be used to build kernel function fuzzing and live memory forensics modules.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
H. C. Kim and I. H. Park, "An Implementation of JTAG API to Perform Dynamic Program Analysis for Embedded Systems," KIPS Transactions on Computer and Communication Systems, vol. 3, no. 2, pp. 31-42, 2014. DOI: 10.3745/KTCCS.2014.3.2.31.

[ACM Style]
Hyung Chan Kim and Il Hwan Park. 2014. An Implementation of JTAG API to Perform Dynamic Program Analysis for Embedded Systems. KIPS Transactions on Computer and Communication Systems, 3, 2, (2014), 31-42. DOI: 10.3745/KTCCS.2014.3.2.31.