I remember reading about the Dallas RTC (probably on the old "forum that was")... can you give me more info? I only have 1571 and uIEC so I don't have any RTC capability, and would like to add that feature to my C128 by some method (like that empty [EP]ROM socket).
Here is some documentation and a usage example (it is designed with a microcontroller in mind, but I found it useful anyway).
The Ace needs not SuperCPU - only for apps written for it or in settings to set 16-bit mode. RAM Expansion is req'd 'cause system really can't to swap everything to disk, it needs to work with data and handle sys routines. OverLook is written to handle many tabs in one window to minimize graphic requirements, but is not applicable in old look, my Qs to users are simple - use old look (faster release, but many functions never available) or new look (release later, support of all fns - maybe not in first release, but without changes later). I need feedback.
Commodore 64 was great, Commodore 128 is bigger, better, faster and more powerful... Commodore 65 was almost here, but C256 is coming and it will be earthquake...
[...] my Qs to users are simple - use old look (faster release, but many functions never available) or new look (release later, support of all fns - maybe not in first release, but without changes later). I need feedback.
I'd say: go for the new look!
In my experience developing software while knowing that some functionalities are outdated and that they very likely should be rewritten in the future only to release it earlier is a bad decision in the long run.
Hi Miro, I've seen on your website that you still plan to support Dallas Smartwatch (DS1216E) as a solution for RTC: have you already done some work for it?
I own one (bought new from DigiKey), I plugged it into the internal function rom socket U36 and wrote some (ugly) assembly code to support reading and setting time, but It never worked; I don't know if I'm doing something wrong (which could certainly be the case due to my limited skill with 8502 assembler) or if the IC just doesn't work.
I can think of two sources of trouble there—one each hard- and software. In hardware, those things have an internal battery. After 25 years+ they are no good any more. Fixable? Derned if I know. In software, AFAIK the function ROM socket doesn’t have a Read/Write signal connected. Makes it tricky to write to it. If anyone out there can say I am mistaken in that latter point I would appreciate a correction.
The world’s only gsteemso
Agitator-in-chief for the Seattle Retro-Computing Society
You are correct (at least 1 point) because you can look at the C128 PRG schematics and the socket definitely lacks read/write (because it was designed for [EP]ROM). I was thinking there was a thread on the old forum, or perhaps an article somewhere on the web (Commodore Hacking?) that described connecting the read/write line to the RTC. Actually that socket has been used for a lot of non-ROM purposes, so I could be thinking of another project.
I always assumed you connected a small battery to the chip, like the one used to hold BIOS settings on a PC (which many people call CMOS RAM). But the way you talk, gsteemso, the battery was actually inside the chip? Wow, that's amazing... I wouldn't think they could build a battery big enough to fit inside DIP chip. Assuming that is correct, then it would be a SERIOUS hardware problem to solve.
Thanks for the info, cthulhu! The example was quite confusing to me... mainly the schematic. Probably because I am not familiar with the microcontroller they used. More importantly, I did not see where an external battery was connected...
The application notes (documentation) also states it uses a lithium battery to maintain timekeeping and preserve RAM (in those chips which have RAM)... for model DS1315 it says an EXTERNAL battery is used to maintain time keeping and SRAM. It also says the DS1216 contains an INTERNAL battery (and has SRAM controller, but no actual RAM). It also says the DS124X series consists of a DS1216+RAM... in other words, INTERNAL battery.
So, to make a long story short, if you can't get a DS1216 or DS124X to work it may be a defective battery like gsteemso says... in which case you would need to use a DS1315 with a fresh external battery... but it lacks NV SRAM.
Last Edit: Oct 26, 2014 5:17:29 GMT by hydrophilic: More details...
I don't think the internal battary could be the culprit here: its purpouse should be to keep the clock running when power is off, what I'm experiencing is that I'm not abale to operate the clock at all. I mean, after setting the correct time I should be able to subsequently read incrementing time values, but I'm not. By the way, this is the code for a small library to set and read time from the SmartWatch:
Writing the device seems like it would never give an error... if you use known good code to write the device, but reading (with known good code) fails, then it seems the device is defective. A dead internal battery like mentioned by somebody else (gsteemso?) sounds like the best culprit. Of course, I don't have a Dallas RTC to test... so I may be COMPLETELY wrong, but I hope you take this as constructive feedback (admittedly hypothetical).
I will comment, regardless. (you broke the "don't ask, don't tell Rule" )
I don't know if it can be fixed, but the editor for this forum FAILs when trying to assign a link to text containing a quote (like the link above). I only got it to work after "manual" hacking of this post.
Really sad the Internet/HTML has been around for about 20 years now, but things still FAIL with basic operations like 'link'...
Understandable for us vintage hackers with virtually no budge and an 8-bit CPU... totally PATHETIC for multi-million dollar companies developing for 64-bit CPUs!!!!!!!!!!!!!!!!
Last Edit: Dec 13, 2014 8:55:27 GMT by hydrophilic: Sad :(