You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kind of interface (with the QNICE) should we agree on? I'm thinking about reserving a page in sys_info, where basically the entire register map of the RTC is mirrored. In other words, setting page to C_SYS_RTC, and then reading from 0x7001 to 0x7007 would give the current date/time.
However, this exposes the register map of the particular device, and therefore the firmware must know and distinguish between the different types.
The other option is to have this logic entirely within the VHDL code. Then we would instead just present to the firmware a generic date/time value, e.g. a 32-bit value "seconds since 1970" like in Unix.
As soon as we support the RTC in hardware (#29) then we can start tackling it in the firmware.
One obvious idea what the firmware can do with an RTC is:
Files on the SD card (FAT32) that are written to/changed, for example disk images, can showing the updated date/time in future.
Maybe there are even more ideas.
The firmware part is not a low hanging fruit for the R4/R5 surge.
The text was updated successfully, but these errors were encountered: