-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO
60 lines (44 loc) · 2.54 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
hostware: Allow setting measurement intervals on command line.
hostware: Allow giving commands on command line.
hostware: Ignore tty input after receiving an <esc>. Idea: Ignore
stupid escape sequences.
hostware: For time series data, when receiving a value table, use
the receive time and the total_duration to generate proper
time stamps for the output file instead of just numbering
the value table elements.
hostware: At least for time series value tables, link against libR.so
and directly let R plot statistics.
firmware: Put EEPROM parameter block to a different place for each
personality, so that changing the personality code does not
require changing the parameters in EEPROM. Would only make
sense if avrdude could program the flash without touching
the EEPROM - which it cannot (or the ATmega cannot).
firmware: Device Signature
hostware: Examine whether the checksum code can be made more simple
by working with pure functions of the prototype
uint16_t crc16_update(uint16_t crc, uint8_t byte)
firmware: Use <util/setbaud.h> for calculating baud rate?
firmware: Examine how doxygen copes with the new multiple parallel
definitions of the same function/variable in different
source files.
Answer: Badly. It just picks one.
firmware: Examine whether e.g. the adc-int and adc-ext histogram
definitions (which differ only in table size) can be unified
into a common source file.
firmware: Generate build-time configuration information summaries on
the actual constants, clock frequencies etc. actually used
in the build. Idea: Put numerical values into const data
sections named something like ".configinfo.uart_baudrate",
and then extract all ".configinfo.*" sections at build time
to make them into config info reports (and avoid linking
these sections into the actual firmware images).
hostware: When reading params from EEProm, set local measurement timer
settings accordingly.
hostware: Print both firmware and hostware build revisions into
packet dump files.
hostware: Mark incomplete last line in exported time series files.
hostware: Why can't we query/set EEPROM during measurement? Querying
EEPROM could set hostware status to what the FW is running
on, and setting EEPROM could write a calculated starting
time into EEPROM if the measurement was started by pressing
a button instead of by RS232 command.