Order ID:89JHGSJE83839 | Style:APA/MLA/Harvard/Chicago | Pages:5-10 |
Instructions:
Embedded Systems Design Lab Report Essay Assignment
Lab/Homework #3
I wanted to give you some experience in programming timers and interrupts, and using assembly language to do so. This is a topic which would be much better served with a more advance processor, such as a Raspberry Pi or such. This was in fact my intent, but because of the current university shutdown situation, we will work with what we have, though I understand this approach will be a bit inferior.
It is very important in studying embedded systems to understand how to use timers and interrupts. These can be programmed using the simple Arduino C programming language, but can be made much more efficient (both in speed and in memory usage) using assembly language. In addition, you can build functions that you do not even have available in Arduino C.
As I am aware that most of you have not programmed in assembly language before, note that these are all fairly low level exercises, built for hobbyists. But they will nonetheless be quite instructive and useful for us to investigate.
I found five different websites that I wish for you to study, program onto your Arduino, and then to build and run them as much as possible with the components you have available.
The five webpages are :
1). https://medium.com/jungletronics/meeting-assembly-…
2). https://microcontrollerslab.com/use-arduino-interr…
3). https://gist.github.com/mhitza/8a4608f4dfdec20d387…
4). https://ucexperiment.wordpress.com/2016/03/04/ardu…
5). https://e-radionica.com/en/blog/low-level-arduino-…
(Note also that I did not write any of these exercises, but rather borrowed them from the given webpages).
A few of these will require you to download a demo version of a software platform named AVR in order to write assembly code for the Arduino. The instructions for doing so are included on the webpages.
Simply follow the given instructions in each of these webpages. Note that they are pretty much step by step, and fairly simple.
Deliverables: Turn in evidence to demonstrate that you have completed each of these tasks. This could include code, screenshots, and especially short videos of the tasks running. You should also include any comments you feel may serve your report well.
Note that I am not expecting a full project report as you did for the two class projects. Think more at the level you would do for a standard lab class. My expectations are, however, that it should still stand as a reasonable and organized lab report, not as a jumbled collection of photos, data, and a few smatterings of statements.
You will turn these in following our established protocol.
RUBRIC |
||||||
Excellent Quality 95-100%
|
Introduction
45-41 points The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned. |
Literature Support 91-84 points The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned. |
Methodology 58-53 points Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met. |
|||
Average Score 50-85% |
40-38 points More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided. |
83-76 points Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration. |
52-49 points Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met. |
|||
Poor Quality 0-45% |
37-1 points The background and/or significance are missing. No search history information is provided. |
75-1 points Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration. |
48-1 points There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met |
|||
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow
Embedded Systems Design Lab Report Essay Assignment |
Embedded Systems Design Lab Report Essay Assignment