【導讀】程序里設置斷點或以一種不干擾的方式來觀察運行情況，本章介紹了可用于下載，運行和調試嵌入式軟件是各種技術。形狀和大小的芯片插座，可以用來為各種存儲芯片編程。在一個理想的開發(fā)條件下，設備編程器應該和主機接在同一個網絡上?？蓤?zhí)行二進制映像文件就很容易傳給它來對ROM芯片編程。大小和你所用的芯片型號來定。應該在插入芯片之前關掉電源，插入之后在打開。一旦加電，處理器就開始從ROM里取出代碼并執(zhí)行。不過，要注意到每一種處。理器對第一條指令的位置都有自己的要求。須保證ROM里你的二進制映像格式要遵從目標處理器的復位要求。的芯ROM程序是不是滿足了處理器的基本要求。以對這個快閃存儲器編程的功能?？趤盹@示正在運行的程序的源代碼、寄存器內容和其他相關信息。GDB前端和調試監(jiān)控器之間的通信專門被設計來通過串行連接進行字節(jié)傳輸。Ar電路板在交付的時候在快閃存儲器里包含了一個免費的調試系統(tǒng)。的RAM里并運行，你可以用tload工具來完成這一任務。

　　

【正文】 h μVision2. The source files for theTRAFFIC project will be shown in theProject Window – Files page. The RTX51 Tiny RealTime OS is selected under Options for Target. Build the TRAFFIC program with Project Build or the toolbar button. Run the TRAFFIC Program You can test TRAFFIC with theμVision2 simulator. The watch variables shown on the rightallow you to view port status that drivesthe lights. The push_keysignal functionsimulates thepedestrianpush key thatswitches thelight system towalk functionis called withthe Push forUse Debug – Function Editor to open . This file is specified the Push forWalk toolbarbutton. under Options for Target – Debug – Initialization File and defines thesignal function push_key, the port initialization and the toolbar button. Note: the VTREG symbol Clock is literalized with a back quote (`),since there is a C function named clock in the to “Literal Symbols” on page 121 for more information. Now run the TRAFFIC application. Enable View – Periodic WindowUpdate to view the lights in the watch window during program execution. The Serial Window 1 displays the printf output and allows you to enterthe traffic light controller mands described in the table above. Set the clocktime outside ofthe start/endtime intervalto flash theyellow light. RTX Kernel Aware Debugging A RTX application can be tested with the same methods and mands asstandard 8051 applications. When you select an Operating System underOptions for Target – Target, μVision2 enables additional debugging features:a dialog lists the operating system status and with the _TaskRunning_ debugfunction you may stop program execution when a specific task is active. The following section exemplifies RTX debugging with the TRAFFIC example. Stop program execution, reset the CPU and kill all breakpoints. An RTX51 application can be tested in the same way as standardapplications. You may open source files, set break points and single stepthrough the code. The TRAFFIC application starts with task 0 init. μVision2 is pletely kernel aware. You may display the task statuswith the menu mand Peripherals – RTX Tiny Tasklist. The dialog RTX51 Tiny Tasklist gives you the following information: 頭 描述 TID task_id used in the definition of the task function. Task Name name of the task function. State task state of the function。 explained in detail in the next table. Wait for event the task is waiting for。 the following events are possible (also in bination): Event Timeout: the task Timer is set to the duration is specified with the os_wait function call. After the Timer decrements to zero, the task goes into Ready state. Interval: the time interval specified with os_wait is added to the task Timer value. After the Timer decrements to zero, the task goes into Ready state. Signal: the os_wait function was called with K_SIG and the task waits for Sig = 1. Sig status of the Signal bit that is assigned to this task. Timer value of the Timer that is assigned to this task. The Timer value decrements with every RTX system timer tick. If the Timer bees zero and the task is waiting for Timeout or Interval the task goes into Ready state. Stack value of the stack pointer (SP) that is used when this task is Running. RTX51 Tiny contains an efficient stack management that is explained in the RTX51 Tiny User’sGuide, Chapter 5: RTX51 Tiny, Stack Management. This manual provides detailed information about the Stack value. S 狀態(tài) 描述 Deleted Tasks that are not started are in the Deleted state. Ready Tasks that are waiting for execution are in the Ready state. After the currently Running task has finished processing, RTX starts the next task that is in the Ready state. Running The task currently being executed is in the Running state. Only one task is in the Running state at a time. Timeout Tasks that were interrupted by a roundrobin timeout are in the Timeout state. This state is equivalent to Ready。 however, a roundrobin task switch is marked due to internal operating procedures. Waiting Tasks that are waiting for an event are in the Waiting state. If the event occurs which the task is waiting for, this task then enters the Ready state. The Debug – Breakpoints… dialog allows you to define breakpoints that stopthe program execution only when the task specified in the _TaskRunning_debug function argument is Running. Refer to “Predefined Functions” on page134 for a detailed description of the _TaskRunning_ debug function. The breakpoint at the function signalon stops execution only if lights is the current Running task.