Talk:Digital Systems: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
* The labs made the material a lot easier to understand -- doing more at the start on early material would be helpful. | * The labs made the material a lot easier to understand -- doing more at the start on early material would be helpful. | ||
* I like having very open practicals, but more (maybe still optional) direction for projects seems useful. | * I like having very open practicals, but more (maybe still optional) direction for projects seems useful. | ||
* Small critique but the | * Small critique but the hypothetical users, programmers and personified processes in this course probably shouldn't be imagined as he/him by default. | ||
* A very interesting and well taught course. | * A very interesting and well taught course. | ||
* Some of the tutorial sheet questions were on | * Some of the tutorial sheet questions were on something I had never seen or heard about before, wasn't in the notes and didn't have an answer online. [I] felt like there were too many questions for which I was completely guessing / interpreting someone's poorly written stack overflow answer. | ||
==Previous years== | ==Previous years== | ||
* [[/2019|Comments from 2019]] | * [[/2019|Comments from 2019]] | ||
Revision as of 11:20, 7 March 2022
Comments from 2022
Something you'd like more of
- Assembly language code examples of things written in high level language. Also pictures.
- More on how handlers and buffers and interrupts are actually coded.
- More on C (e.g. pointers?)
- Explanation for each ARM instruction keyword, instead of only showing examples, as it is slightly confusing, e.g. the
lsrsandadrs. - More demos during lectures? With explanation of how we could create our own on the website.
- More time taken with introduction to C and/or a more gradual walk through initial practicals.
- Possibly could improve explanation of some of the micro:bit interface dealing with GPIO for buttons, etc., and using/coding interrupts.
- I would have liked larger overviews of how each topic works before getting into more specific examples.
- More detail about setting interrupt flags and how to find the documentation for them would be nice.
- More time could be spent on the special registers and their abbreviations (e.g.,
pc= program counter).
Something you could do with less of
- Less time could be spent on very specific features of the processor (some problem sheet questions seem to expect us to have learnt the 400 page manual).
Something that could be done better
- Some problem sheet questions weren't linked very clearly with the notes, so it was hard to figure them out.
- Operating systems could be taught better.
General comments
- The notes provided are very useful.
- The labs made the material a lot easier to understand – doing more at the start on early material would be helpful.
- I like having very open practicals, but more (maybe still optional) direction for projects seems useful.
- Small critique but the hypothetical users, programmers and personified processes in this course probably shouldn't be imagined as he/him by default.
- A very interesting and well taught course.
- Some of the tutorial sheet questions were on something I had never seen or heard about before, wasn't in the notes and didn't have an answer online. [I] felt like there were too many questions for which I was completely guessing / interpreting someone's poorly written stack overflow answer.