Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Lecture Slides on Debug Techniques for SW Systems | ECE 473, Assignments of Microprocessors

Oregon State University (OSU)Microprocessors
Prof. R. Traylor

Material Type: Assignment; Professor: Traylor; Class: MICROPROCESSOR SYSTEM DESIGN; Subject: Electrical & Computer Engineer; University: Oregon State University; Term: Unknown 1989;

Typology: Assignments

Pre 2010

Uploaded on 08/30/2009

koofers-user-463
koofers-user-463 🇺🇸

10 documents

1 / 9

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Debug Techinques for HW/SW Systems
What's broken, the HW or the SW?
Some basic thoughts:
-assume that its broken
-its not working correctly until proven by repeated experiments
-never quite trust that it works correctly
-assume that a few small bugs may still exist
-failure to find bugs usually stems from wrong assumptions
-when debugging, prove each assumption correct
-don't grasp at straws or take shots in the dart
-engineering is not gambling
A debugging world view:
a zeitgeist of suspicion,
tempered by trust in the laws of physics,
curiosity dulled only by the determination to stay focused on a single problem,
and a zealot's regard for the scientific method.
(Jack Gansle)
pf3
pf4
pf5
pf8
pf9

Partial preview of the text

Download Lecture Slides on Debug Techniques for SW Systems | ECE 473 and more Assignments Microprocessors in PDF only on Docsity!

Debug Techinques for HW/SW Systems

What's broken, the HW or the SW?

Some basic thoughts:

  • assume that its broken -its not working correctly until proven by repeated experiments
  • never quite trust that it works correctly -assume that a few small bugs may still exist
  • failure to find bugs usually stems from wrong assumptions -when debugging, prove each assumption correct -don't grasp at straws or take shots in the dart -engineering is not gambling A debugging world view: a zeitgeist of suspicion, tempered by trust in the laws of physics, curiosity dulled only by the determination to stay focused on a single problem, and a zealot's regard for the scientific method. ( Jack Gansle )

Debug Techinques for HW/SW Systems

What's broken, the HW or the SW?

A debugging methodology: (adoped with changes from: Gansel, The Art of Designing Embedded Systems) -make the bug repeatable -observe the behavior, getting information to isolate the apparent bug -create a suspect list (remain rational in this step) -generate a hypothesis to pinpoint the bug -create an experiment to test the hypothesis -fix the bug -test the fix and then everything else You must have good controlability and obserability into the system.

  • probe with instruments to stimulate and observe the hardware
  • instrument the software to cause and observe software behavior -this means to both inject stimulus and to observe results -keep notes of your observations Hardware instruments -multimeter, oscilloscope, signal generator Software instruments -LEDs, “printf”, toggle a port pin, watch a timer

Debug Techinques for HW/SW Systems

Bugs that mysteriously go away will mysteriously reappear!

- Find the problem, or your customer will. Random probing will often give some hints as to what is broken. Just as often you will find weird things that are completely normal and think them to be bugs.

  • Avoid rabbit trails. Stick to your hypothesis. -Make sure the power is on. -Was the board basically functional? Run a sanity test. -Did you compile the right source file? -“When things are acting funny, measure the amount of funny”. (Bob Pease) -Are any parts warm or hot to the touch? Should they be? -The best troubleshooting tool is between your ears.

Thoughts worth considering...

Debug Techinques for HW/SW Systems

What's broken, the HW or the SW?

If possible, with both new hardware and new software....... -build a little hardware, -write a little software, -test at each step The sure path to frustration is to build all the hardware, write all the software and expect the whole mess to come up and work as expected.

ATMega128 I/O Ports

Building/Testing Lab 2

Next, try testing to make sure the segments are connected correctly and that the digits are enabled correctly. int main(){ DDRA = 0xFF; //set port A to all outputs DDRB = 0xF0; //set port bits 47 B as outputs DDRD = 0x00; //set port D all inputs PORTD = 0xFF; //set port D all pullups PORTA = 0x00; //set port A to all zeros while(1){ PORTB = ~PIND; //push button selects segment } //while } //main

ATMega128 I/O Ports

Building/Testing Lab 2

Next, try walking through the segments and digits separately. uint16_t i; //big counter uint8_t k, j; //small counters while(1){ k++; j = (k % 5); //j varies from 0 to 4 PORTB = (j << 4); //walk through the digits PORTA = ~0x01; for (i=0; i<100000; i++){} //A PORTA = ~0x02; for (i=0; i<100000; i++){} //B PORTA = ~0x04; for (i=0; i<100000; i++){} PORTA = ~0x08; for (i=0; i<100000; i++){} PORTA = ~0x10; for (i=0; i<100000; i++){} PORTA = ~0x20; for (i=0; i<100000; i++){} PORTA = ~0x40; for (i=0; i<100000; i++){} //G PORTA = ~0x80; for (i=0; i<100000; i++){} //colon } //while