ACA500plus + RTC module issue

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Please understand that you need to create an account to be able to post, guest posting was disabled as an anti spam measure.

  • My setup includes ACA500+rtc (also X-Surf-500).

    This is my custom setup for OS3.2.1.

    Q

    The RTC is functioning with some issues.

    Every time it powers is cycled, it sets the date to 2020, and the time is no longer right. (Month and day are corrects).

    The CR1220 battery is new and charged.

    Any suggestions would be appreciated.


    Thanks.

  • Okay, okay,

    this isn't an operating system issue because:


    1) I turn everything on.

    2) I set the time and date through the WB preferences.

    3) Reset + mouse button pressed.

    4) Jens's "BIOS" boots up. The time is still correct.

    5) I boot OS3.2.1. The time is correct.

    6) Another soft reset with the mouse button pressed. The time and date are still correct. The WB will say the same thing.

    7) Power off.

    7+1) Just 10 seconds.

    9) I turn it on again.

    10) The BIOS shows the incorrect time and date


    Day and month are right. Year is 2020. I'm 6 years younger. :-)
    Time is a few minutes earlier than the actual one.


    My configuration includes an internal memory expansion with RTC (without battery).

    Removing it doesn't change anything.


    ACA500p ROM: v0.150

  • Now we have battery on the trapdoor's RTC.


    We have two profiles:

    One with the RTC on the ACA500plus and one with the RTC on the trapdoor.

    This is the result:

    Seems to something does not work proprly on RTC of ACA500plus..

  • What about your global settings? Is that set still to "auto-detect"? If so, that (somewhat non-working) auto-detect routine might cause the time to be altered.


    Jens

  • Hi Jens,

    Thanks for your reply.

    For practical purposes, the global RTC settings don't solve the problem.

    I recently set the RTC to ACA600+ in both the global settings and in profile 2 (which, by the way, I'd already tried with several variations).

    It didn't solve the problem.

  • An update. The RTC module moved to the aca1260 works perfectly.

    Obviously, the aca1260 is mounted on the ACA500plus.

    At this point, it seems pointless to keep the 512MB internal expansion card inserted.

    Have a nice weekend.


    P.S.

    Is there anyone in the forum who has tried the rtc module on aca500plus with success?

  • At this point, it seems pointless to keep the 512MB internal expansion card inserted.

    I guess you mean the trapdoor memory expansion of 512k?


    You obviously have an ECS Agnus, so it makes a lot of sense to leave that trapdoor expansion installed. Reason is that the ACA500plus can turn that into chip ram if you select it in the expert menu, or if you select the "full config" with F1 from a cold start. Didn't you notice that you have more chip ram with the ACA500plus? This is only possible with a trapdoor memory expansion installed.


    Jens

  • I use the RTC on my trapdoor expansion (ACA500+ and ACA1234 otherwise), but despite having a 2MB Chip RAM expansion (and thus not needing the trapdoor memory for chip ram, which is a great feature) I find having the trapdoor ram handy for when I want to use stealth mode and the program is looking to have some "fast ram" installed. In other words, it helps with compatibility sometimes.

  • Even in stealth mode, what you get as "trapdoor memory" is really on the ACA500plus. One of my goals in development was to make the trapdoor memory expansion either completely unnecessary (as it might have been destroyed beyond repair with a leaked battery), or so make good use of it by turning it into chip ram.


    If you need memory in the $c0.0000 space, the ACA500plus provides that, and emulates cycle-exact timing if running at 7MHz CPU speed. So even though it's physically "real fastmem", it behaves like "ranger mem" with all the wait states that the chipset adds.


    Jens

  • I guess you mean the trapdoor memory expansion of 512k?

    Yes.

    Didn't you notice that you have more chip ram with the ACA500plus?

    Of course!

    I was fooled by the fact that in F10 - Expert options I can set "$C0/Trapdoor RAM: Disabled" and still have all the chip RAM available.
    So does the "1M Chip RAM expansion: On" setting overwrite the previous setting?
    I apologize for the question, which is certainly completely irrelevant.

  • So does the "1M Chip RAM expansion: On" setting overwrite the previous setting?

    That's a multi-level answer: Everytime you switch on the 1M chip ram expansion, the actual physical trapdoor memory expansion is converted to chip ram. However, many titles still want to access memory at $c0.0000 (the trapdoor area), and the ACA500plus provides that if selected. It even emulates the real ranger-mem speed if 7MHz mode is selected - slowing down if you activate more bit planes. So you can really have both, although seemingly-physically impossible.


    And no, I don't think the question is irrelevant. It shows that you have enough knowledge about the A500 to ask this question in the first place. And of course I'm happy to show off the depth of development that went into the ACA500plus :-)


    Jens

  • Everytime you switch on the 1M chip ram expansion, the actual physical trapdoor memory expansion is converted to chip ram.

    Ok, ok.

    If I understand correctly, with this option enabled, the memory segment $C00000-$D7FFFF is magically remapped to $080000-$0FFFFF.

    Right?


    However, many titles still want to access memory at $c0.0000 (the trapdoor area), and the ACA500plus provides that if selected. It even emulates the real ranger-mem speed if 7MHz mode is selected - slowing down if you activate more bit planes. So you can really have both, although seemingly-physically impossible.

    I deduce that keeping "$C0/Trapdoor RAM: Enabled" and "1M Chip RAM expansion: On" enabled at the same time if 7Mhz mode is not enabled doesn't make much sense...


    For old titles(7MHz mode selected)

    "$C0/Trapdoor RAM: Enabled"

    "1M Chip RAM expansion: Off" -> don't care


    For brand new :-) A500+A500P+ACA2060:

    "$C0/Trapdoor RAM: Disabled" -> don't care

    "1M Chip RAM expansion: On"


    And no, I don't think the question is irrelevant. It shows that you have enough knowledge about the A500 to ask this question in the first place.

    Yes, yes! In my dreams! :-)

  • If I understand correctly, with this option enabled, the memory segment $C00000-$D7FFFF is magically remapped to $080000-$0FFFFF.

    Right?

    It's a tiny MMU in external hardware, yes.


    Even without trapdoor memory installed…

    In that case, the ACA500plus can provide $c0.0000 trapdoor memory, but it can't provide chip ram, as it does not have full access to the chip bus.


    Jens