This week, in order to complete our assignment, we must read and understand a microcontroller datasheet. After glancing through it to get a better understanding of the role of the microcontrolle and how it can be used, some questions that I have are:
- Are all the registers utilized at the same time?
- What is the maximum amount of times a microcontroller can be programmed?
Continuing with our electronics, this week I am using my board from Electronics Design. My overall design encorporates two LEDs and a tactile switch. Through this design, when my board gets power, one LED will come on; when the button is pressed, the other LED will come on. For programming, I have found that I am more comfortable using it on the Linux side; that environment seems more user-friendly and easier to understand.
In going through the archive tutorials of steps to take in programming, I remember that you must have the Make and .C files in the same place. To test out my board, I decided to program it using the original file for the original board (before adding the button and LEDs) just to see if it would work.... And it did!
Once I knew that my board could be programmed, I decided to create my own code for what I wanted the board to do initially. I used a combination of codes for the Button and Light created by Neil for what my board will do. Here is the link to my code. These pictures caputure my board not only receiving power, but the difference in when the switch is pressed versus when it is not pressed.
These were the steps I took towards programming my board
- opening the terminal and navigating to the location of my Make and .C file
- make -f hello.embed.44.make
- sudo make -f hello.embed.44.make program-usbtiny-fuses. And this step is important because, through trial and error, I realized that for any board that has an occilator (crystal), you must set the fuses or timing and communication will be off and your board will not work
- sudo make -f hello.embed.44.make program-usbtiny. From this point it's freedom because your board should be programmed and doing what your code tells it to do.