Flashy Clock - Yet another DEV board

[exxos]

Actually ... @Icky looking back a few posts here viewtopic.php?p=84668#p84668 you did the alt-ram driver ?

EDIT: found the PRG !

IMG_4530.JPG (57.06 KiB) Viewed 202 times

and....

IMG_4531.JPG (67.39 KiB) Viewed 200 times

IMG_4533.JPG (117.03 KiB) Viewed 192 times

Now where's my 16mhz booster....

[JezC]

Cool... I think I registered interest in one of these way back so would be great to actually get one!

[Badwolf]

Actually ... @Icky looking back a few posts here viewtopic.php?p=84668#p84668 you did the alt-ram driver ?

EDIT: found the PRG !

Oh good. You had me racking my brain as I didn't remember it!

BW

[exxos]

Was trying yesterday to give the clock running at 16mhz.. But ended up with odd issues like this..

IMG_4538.JPG (49.02 KiB) Viewed 142 times

I also think there is a missing pull-up on the 16mhz booster causing floppy issues. This was even more problematical because it seems the ZIF socket I had in my H5 for testing 1772 chips was also causing floppy issues so I should probably look for a better ZIF socket...


Next problem is the JTAG adapter which @Icky somehow lite up bright orange when I think I plugged it in wrong.. Looks like a track got a tad on the warm side..

IMG_4535.JPG (153.9 KiB) Viewed 142 times

So while I was at my girlfriends today, doing the monthly ASDA shop... I was stood there staring into space, as one does in such situations, and some something struck me.. ( no it wasn't my girlfriend throwing a tin of beans at me for not paying attention and putting it in the trolley ).. I realised I had some logic which would work fine at 8mhz but not 16mhz.. I'm not sure why that logic was there, but it was slowing down the flashyclock bus enable buffers so anyway.. we now running 16mhz !

IMG_4539.JPG (362.94 KiB) Viewed 142 times

IMG_4540.JPG (350.57 KiB) Viewed 142 times

[exxos]

First test run. Simple program which gets the RTC time & date. This will be used to set the system time as control panel won't be compatible with the RTC.

IMG_4584.JPG (53.3 KiB) Viewed 97 times

[ijor]

Next problem is the JTAG adapter which @Icky somehow lite up bright orange when I think I plugged it in wrong.. Looks like a track got a tad on the warm side..

Plugging that non-keyed JTAG connector is my worst nightmare! I always fear I am plugging it the wrong way. I keep a couple of pictures with the right orientation to be sure

[exxos]

Plugging that non-keyed JTAG connector is my worst nightmare! I always fear I am plugging it the wrong way. I keep a couple of pictures with the right orientation to be sure

Yeah I took some pictures as well now

[agranlund]

First test run. Simple program which gets the RTC time & date. This will be used to set the system time as control panel won't be compatible with the RTC.

I don't know if this helps at all, and I don't remember much of that code, but this is something I wrote for myself when I installed an incompatible RTC in my ST:
https://github.com/agranlund/rtc


core.s is the generic and hardware agnostic code.
Updates the Gemdos time at startup and hooks xbios get/set time functions. Stuff like control panel and other things will then work.

dallas.s is for the specific rtc I used and will not be of use for you other than perhaps as an example.
but it seems I made a "template.s" to use as a template for when making a driver for some other rtc.

[exxos]

I don't know if this helps at all, and I don't remember much of that code, but this is something I wrote for myself when I installed an incompatible RTC in my ST:
https://github.com/agranlund/rtc

Yeah I think something is "broken" in TOS and needs a patch to work properly.. that seems to be the conclusion here..
viewtopic.php?p=139580#p139580

Its impossible to set the year.

I half recall @Icky might have been doing some related work in TOS a long time ago.. But im using the DS12885, same as in the falcon RTC. Maybe something in TOS is already patched to take care of this.. but ive zero idea how to create xbios hooks anyway.

EDIT:

Your code sort of looks patchable as it lists routines for your RTC chip, but would be "simple" to patch in my RTC read code in there.. beyond that.. no idea.. I suppose it depends if it will compile with devpac as well ?

[agranlund]

Your code sort of looks patchable as it lists routines for your RTC chip, but would be "simple" to patch in my RTC read code in there.. beyond that.. no idea.. I suppose it depends if it will compile with devpac as well ?

I recall scratching my head about that and in the end needed to have it first update the Gemdos time and then hook the xbios get/set for the stuff to work and for gemdos and xbios to both agree about what time it is. or something like that..

Yep, it should be fairly easy to slot in only what is specific for some other chip in a copy of template.s
Or at least that was the idea.

And I believe I built that stuff with Devpac3.

For the dallas program you simply build dallas.s as it includes core.s.
It should be the same for template.s.