I tech features Juliette

We use cookies to personalise content and ads, to provide social media features and to analyse traffic. We share info about use of our site with social media, ads and analytics partners. By continuing to browse you are agreeing to use of cookies. See details or close this message.

Page

100%

Specifications	I tech features Juliette
Business section

debug designfebruary 2003 RReeppoorrttss ooff tthhee ddeemmiissee ooff tthhee 88bbiitt mmiiccrrooccoonnttrroolllleerr hhaavve

Specifications	I tech features Juliette
Suggested Link Details/Purchase
Content	debug designfebruary 2003 RReeppoorrttss ooff tthhee ddeemmiissee ooff tthhee 88bbiitt mmiiccrrooccoonnttrroolllleerr hhaavvee bbeeeenn ggrreeaattllyy eexxaaggggeerraatteedd DEBUGGING MIX-UP? 25epd T he industry standard 8052 microcon- troller today includes timers, counters, a UART, and on-chip RAM and ROM. Semiconductor manufacturers have integrat- ed ultra-high precision analogue I/O peripher- als like 12- to 24bit ADCs and precision DACs on chip, offering a fully integrated system-on- chip solution. This level of integration presents new challenges in terms of debugging the embedded software and hardware system. Debugging issues Embedded system designers can make extensive use of modern microcontroller- based code simulators, to prove functionality of a great portion of code before running on a real hardware platform. These simulators can accept assembled microcontroller code and allow the user to single step through the code execution in a Windows-based environment. A ‘burn and learn’ approach can be adopted on OTP or EPROM-based microcontrollers. PC- assembled code is programmed onto the ROM-based microcontroller via a device pro- grammer. External port pins can be used to drive LEDs on/off when the code gets to certain points in its execution. External interrupt inputs can be used to trigger specific debug events dumping internal register contents via the UART to an PC or dumb serial port terminal to confirm microcontroller core status. As manufacturers integrate more peripheral functions into microcontrollers, the resulting small, large pin-count package makes the socket based approach impractical. These constraints have led to the devel- opment of an on-chip (software) debug monitor strategy. A debug-monitor is pro- grammed onto the device with the user’s run- time code. The on-chip debug monitor typically communicates with a host PC’s, Windows- based debug monitor via a serial link. This strategy is called intrusive debug, because the on-chip debug monitor uses on- chip resources like the serial port for commu- nication. The debug monitor sets break points in software by replacing the code instruction at a break point location by a jump instruction directly to the debug monitor code. Because the monitor must modify (or reprogram) the code memory to set a break point, it is not a strategy that can be used in EPROM or OTP devices. Some on-chip monitors will be interrupt-driven; this means that designers may not be able to set debug break points within interrupt service routines in their own code. In-circuit emulators provide a debug option where an emulation pod electrically replicates the functionality of the microcontroller. The functionality of the real device can be emulated from a PC-based debug front-end. Many modern emulators have additional RAM to trace real-time code execution. Given Today, many different 8bit architectures proliferate, and predications of the demise of the 8bit microcontroller are greatly exaggerated
Navigation	Previous Page / Next Page
Suggested Link Details/Purchase

Following Datasheets	143431680AN204 (10 pages) 145-1 (12 pages) 146531367AN592 (1 pages) 147153369ADA4302_4_pbrief_FINAL_12_23 (2 pages) 14_8shd_substances_in_articles_en (12 pages) 14_bshd_lipkova_guidance_en (11 pages) 14_jss_how_support_members_d1_lrws_20120203_en_1 (16 pages) 1508_2 (4 pages) 150829806transformer_vs_amp_CN (7 pages) 1509_1 (9 pages)
Check in e-portals	World-H-News Products Extensions Partners Automation Jet Parts
Sitemap Folder	group1 group2 group3 group4 group5 group6 group7 group8 group9 group10 group11 group12 group13 group14 group15 group16 group17 group18 group19 group20 group21 group22 group23 group24 group25 group26 group27 group28 group29 group30 group31 group32 group33 group34 group35 group36 group37 group38 group39 group40 group41 group42 group43 group44 group45 group46 group47 group48 group49 group50 group51 group52 group53 group54 group55 group56 group57 group58 group59 group60 group61 group62 group63 group64 group65 group66 group67 group68 group69 group70 group71 group72 group73 group74 group75 group76 group77 group78 group79 group80 group81 group82 group83 group84 group85 group86 group87 group88 group89 group90 group91 group92 group93 group94 group95 group96 group97 group98 group99 group100 Prewious Folder Next Folder