comparison: content/hp34970a_5.rst
content/hp34970a_5.rst
- changeset 148
- 2f87039dd0b5
- parent 137
- f3070bd842cd
equal
deleted
inserted
replaced
| 147:6b6c2254dac1 | 148:2f87039dd0b5 |
|---|---|
| 126 easily. | 126 easily. |
| 127 | 127 |
| 128 I also had to use my DSLogic logic analyzer to debug a few things and get to a | 128 I also had to use my DSLogic logic analyzer to debug a few things and get to a |
| 129 point that make the front panel usable: | 129 point that make the front panel usable: |
| 130 | 130 |
| 131 .. peertube:: cc6f4327-703f-42f6-8157-03cd0a987387 | 131 .. peertube:: 74b11332-ab1f-459b-8602-2f85c887e506 |
| 132 | 132 |
| 133 In this version of the code are many remaining problems, the biggest one being | 133 In this version of the code are many remaining problems, the biggest one being |
| 134 the fact the display flickers a lot. In the code of the formware, I have a | 134 the fact the display flickers a lot. In the code of the formware, I have a |
| 135 "frame"-buffer in which the main loop draw the information to be displayed, and | 135 "frame"-buffer in which the main loop draw the information to be displayed, and |
| 136 a thread that copy this buffer to the actual display once every 30ms. And in | 136 a thread that copy this buffer to the actual display once every 30ms. And in |
| 165 and be resilient against it. | 165 and be resilient against it. |
| 166 | 166 |
| 167 But in the end, I've now reach a point where the firmware begins to be really | 167 But in the end, I've now reach a point where the firmware begins to be really |
| 168 usable: | 168 usable: |
| 169 | 169 |
| 170 .. peertube:: 172bf449-eba7-4429-8840-ab9b2d5398f8 | 170 .. peertube:: 514b7c92-d3e5-49b5-9c2d-46317dd2a3e7 |
| 171 | 171 |
| 172 | 172 |
| 173 | 173 |
| 174 Design errors | 174 Design errors |
| 175 ============= | 175 ============= |
