Gregory Haerr

> What do you think? As far as interfacing with your RTC, why not? :) It seems the main purpose would be for setting/getting date and time, rather than hardware...

Hello @tyama501, Thank you for the FAT bug report, I didn't realize FAT uses localtime on disk! Apart from that, I had thought we had worked out the ability to...

> Yes, the localtime in RTC works well other than FAT problem. Are you using the ELKS TZ= environment variable to properly convert from/to UTC and localtime? There is a...

> But I have set TZ in profile as JST-9 before and it is working well with date, clock -w, clock -s without -u. Ok, I will produce a PR...

> As far as I can tell, the BIOS/CMOS way of accessing the RTC registers is by doing a simple out(fixed address, register number), then reading or writing to that...

Hello @tyama501, > I think expecting UTC time to set is not user-friendly... Agreed. Looking at elkscmd/sh_utils/date.c, the date is not corrected for localtime in utc_mktime() function. Can you try...

> In the meantime, I've added the INP and OUT keywords/tokens to basic, which aren't part of the Sinclair spec, but rather more like QBasic did. I'll open a PR...

> Also, the 32kHz crystal doesn't always start, which is kind of strange. It's not the RST line of the chip, it might be the supply rail of the chip....

> I would like to have PEEK/POKE command to debug codes from background/other screen. What sort of things would you debug? I assume you'd want to use the proposed extension...

Hello @cocus, Was this the only error and did the build complete, or are there still more similar issues? ELKS is running an older commit of the toolchain, perhaps with...