Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for RTC in M2M: Firmware #30

Open
sy2002 opened this issue Nov 2, 2023 · 1 comment
Open

Add support for RTC in M2M: Firmware #30

sy2002 opened this issue Nov 2, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@sy2002
Copy link
Owner

sy2002 commented Nov 2, 2023

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.

@sy2002 sy2002 added the enhancement New feature or request label Nov 2, 2023
@sy2002 sy2002 self-assigned this Nov 2, 2023
@MJoergen
Copy link
Collaborator

MJoergen commented Nov 2, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants