Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Just build a small project on a breadboard. Write a small program to light a led on each of the outputs. This can be a simple way to test the outputs... The ADC and other functionality will need a specialised board.
**broken link removed**
Try to see the UNI-DS2 board. It's quite versatile.
Build yourself a simple test jig with input switches and output LEDs for all of the pins on the chip. Then write a simple test program that takes inputs and sends the data to the outputs. For example, using 10K resistors pulling all of port A high with switches taking the input to ground when pressed and LEDs with 330 ohm resistors to ground, then IF RA.0 = 0 THEN RB.0 = 1 ELSE RB.0 = 0: then continue with RA.1 and so forth. It's a simple process.
OF COURSE the only other natural thing to do is drop the micro into your project and see if it works! If it doesn't then the troubleshooting begins. I would build a test jig as mentioned above just to verify that the problem wasn't the chip. Also if it didn't work in your project you could always put a second micro in your project and see if it works.
If you are new to working with micros then the test jig is just the thing to learn how to work with these great little machines.
Testing the microcontroller involves several steps.
1- Find out your components are working. Chances are if they are new, they are working. Assume they are working. If your luck is in a low tyde, maybe you have a faulty component. If you are using scrap, you must test it in a known good circuit, maybe that component defect was the cause of scraping.
2- Since design, one should have in mind how to test the microcontroller board. I usually include some access to the bus ports designed originaly. It is just some terminations in a connector that maybe or not used in the final design.
3- Have some LEDs with BUFFERS mounted. LEDs consume 20mA, this exceeds the fan out current of most microcontrollers. You must use a buffer to connect the LED with some RESISTORS in series with it. The calculation is simple and you should have your VCC(5v) subtracted 0.7 (LED drop) divided by current. DONT EVER CONNECT LEDs DIRECT TO THE PINS. ULN 2003 are simple and cheap for this task.
4- Microcontrollers have hardware and software. These must be both working at the same time. Using more LEDs will help you track initializations and others. You can use some sort of simulators / emulators to think about some code that works for you. Get Keil compiler to help you. There is a limited size free compiler with powerfull graphical emulation / debugging utility.
Another approach would be using a simulator. there is a software called Proteus, This software could simulate some MCUs as well as some basic analog circuits.
you can read about it more here :
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
