- 您現(xiàn)在的位置：買賣IC網(wǎng) > PDF目錄381164 > UDI_SPEC LOW POWER FIRE LIGHTER CIRCUIT PDF資料下載
參數(shù)資料
| 型號(hào)： | UDI_SPEC |
| 英文描述： | LOW POWER FIRE LIGHTER CIRCUIT |
| 中文描述： | 通用調(diào)試接口（UDI）規(guī)范。版本1.4 |
| 文件頁(yè)數(shù)： | 22/205頁(yè) |
| 文件大?。?/td> | 364K |
| 代理商： | UDI_SPEC |
第1頁(yè)第2頁(yè)第3頁(yè)第4頁(yè)第5頁(yè)第6頁(yè)第7頁(yè)第8頁(yè)第9頁(yè)第10頁(yè)第11頁(yè)第12頁(yè)第13頁(yè)第14頁(yè)第15頁(yè)第16頁(yè)第17頁(yè)第18頁(yè)第19頁(yè)第20頁(yè)第21頁(yè)當(dāng)前第22頁(yè)第23頁(yè)第24頁(yè)第25頁(yè)第26頁(yè)第27頁(yè)第28頁(yè)第29頁(yè)第30頁(yè)第31頁(yè)第32頁(yè)第33頁(yè)第34頁(yè)第35頁(yè)第36頁(yè)第37頁(yè)第38頁(yè)第39頁(yè)第40頁(yè)第41頁(yè)第42頁(yè)第43頁(yè)第44頁(yè)第45頁(yè)第46頁(yè)第47頁(yè)第48頁(yè)第49頁(yè)第50頁(yè)第51頁(yè)第52頁(yè)第53頁(yè)第54頁(yè)第55頁(yè)第56頁(yè)第57頁(yè)第58頁(yè)第59頁(yè)第60頁(yè)第61頁(yè)第62頁(yè)第63頁(yè)第64頁(yè)第65頁(yè)第66頁(yè)第67頁(yè)第68頁(yè)第69頁(yè)第70頁(yè)第71頁(yè)第72頁(yè)第73頁(yè)第74頁(yè)第75頁(yè)第76頁(yè)第77頁(yè)第78頁(yè)第79頁(yè)第80頁(yè)第81頁(yè)第82頁(yè)第83頁(yè)第84頁(yè)第85頁(yè)第86頁(yè)第87頁(yè)第88頁(yè)第89頁(yè)第90頁(yè)第91頁(yè)第92頁(yè)第93頁(yè)第94頁(yè)第95頁(yè)第96頁(yè)第97頁(yè)第98頁(yè)第99頁(yè)第100頁(yè)第101頁(yè)第102頁(yè)第103頁(yè)第104頁(yè)第105頁(yè)第106頁(yè)第107頁(yè)第108頁(yè)第109頁(yè)第110頁(yè)第111頁(yè)第112頁(yè)第113頁(yè)第114頁(yè)第115頁(yè)第116頁(yè)第117頁(yè)第118頁(yè)第119頁(yè)第120頁(yè)第121頁(yè)第122頁(yè)第123頁(yè)第124頁(yè)第125頁(yè)第126頁(yè)第127頁(yè)第128頁(yè)第129頁(yè)第130頁(yè)第131頁(yè)第132頁(yè)第133頁(yè)第134頁(yè)第135頁(yè)第136頁(yè)第137頁(yè)第138頁(yè)第139頁(yè)第140頁(yè)第141頁(yè)第142頁(yè)第143頁(yè)第144頁(yè)第145頁(yè)第146頁(yè)第147頁(yè)第148頁(yè)第149頁(yè)第150頁(yè)第151頁(yè)第152頁(yè)第153頁(yè)第154頁(yè)第155頁(yè)第156頁(yè)第157頁(yè)第158頁(yè)第159頁(yè)第160頁(yè)第161頁(yè)第162頁(yè)第163頁(yè)第164頁(yè)第165頁(yè)第166頁(yè)第167頁(yè)第168頁(yè)第169頁(yè)第170頁(yè)第171頁(yè)第172頁(yè)第173頁(yè)第174頁(yè)第175頁(yè)第176頁(yè)第177頁(yè)第178頁(yè)第179頁(yè)第180頁(yè)第181頁(yè)第182頁(yè)第183頁(yè)第184頁(yè)第185頁(yè)第186頁(yè)第187頁(yè)第188頁(yè)第189頁(yè)第190頁(yè)第191頁(yè)第192頁(yè)第193頁(yè)第194頁(yè)第195頁(yè)第196頁(yè)第197頁(yè)第198頁(yè)第199頁(yè)第200頁(yè)第201頁(yè)第202頁(yè)第203頁(yè)第204頁(yè)第205頁(yè)
UDI Services Overview
2-4
Universal Debugger Interface Specification
When a DFE starts up a new connection, it should always call
UDICreateProcess
. TIPs that support only raw machine debugging (type 0
TIPs) return a process ID (PId) of
UDIProcessProcessor
. TIPs that support
only program debugging (type 1 TIPs) must return a different PId. TIPs that
differentiate between program and machine resources (type 2 TIPs) should also
return a PId other than
UDIProcessProcessor
. TIPs that return process
UDIProcessProcessor
in response to a
UDICreate
call can still support OS
services. Note, also, that
UDICreateProcess
has the side effect of setting the
current process as the one created.
In most cases, the DFE downloads the program to be debugged. In all cases,
the program to be debugged is downloaded into a process space compatible
with the TIP. If the current process is
UDIProcessProcessor
, the DFE simply
sets the PC to the downloaded program's entry point and is ready to execute.
(A
UDIInitializeProcess
when the process is
UDIProcessProcessor
performs
a target reset).
If the current process is not
UDIProcessProcessor
, then the DFE should call
UDIInitializeProcess
. The TIP initializes the process so that the next
instruction to be executed is the first instruction in the process (i.e., the entry
point). The TIP determines what happens to any other
UDIInitializeProcess
parameters.
DFEs that debug programs rather than the raw machine can now inspect the
PC (using UDI PC space). If the PC is not at the entry point of the program,
the DFE sets a breakpoint at the entry point and executes up to it. Otherwise,
stepping the TIP may result in executing one or more instructions that the DFE
did not download, and this may confuse the DFE.
As stated earlier,
UDICreateProcess
also allows multi–tasking TIPs to create
a new process context. For TIPs that allow multiple processes, but do not allow
run–time creation of processes, this call would still be used to determine
whether a process can be debugged. A process is executed in the context of an
operating environment. When
UDIInitializeProcess
is called, command line
arguments for the process are passed. The TIP determines what to do with the
command line arguments.
Because
UDIStep
may possibly exclude calls to other functions and/or traps,
stepping may take a significant amount of time. As a result,
UDIStep
, like
UDIExecute
, returns as soon as stepping has begun. Both
UDIStep
and
UDIExecute
stop when a breakpoint is hit, when the TIP can no longer
continue executing the process, or when
UDIStop
is called.
相關(guān)PDF資料 |
PDF描述 |
|---|---|
| UDK2547B | Current limited over-voltage protected quad digital termination |
| UDK2549B | Dual current limited over-voltage protected digital termination |
| UDK2549EB | Home appliance control circuit |
| UDK2559B-T | PROTECTED QUAD POWER DRIVER |
| UDK2559EB-T | PROTECTED QUAD POWER DRIVER |
相關(guān)代理商/技術(shù)參數(shù) |
參數(shù)描述 |
|---|---|
| UDK2008 | 制造商:未知廠家 制造商全稱:未知廠家 功能描述:U盤主控 |
| UDK2008A | 制造商:未知廠家 制造商全稱:未知廠家 功能描述:U盤主控 |
| UDK2547 | 制造商:ALLEGRO 制造商全稱:Allegro MicroSystems 功能描述:PROTECTED QUAD POWER DRIVERS |
| UDK2547B | 制造商:未知廠家 制造商全稱:未知廠家 功能描述:Quad Peripheral Driver |
| UDK2547EB | 制造商:ALLEGRO 制造商全稱:Allegro MicroSystems 功能描述:PROTECTED QUAD POWER DRIVERS |
發(fā)布緊急采購(gòu)，3分鐘左右您將得到回復(fù)。