[Coco] Disto 4-in-1 clock2 with CocoSDC

[Bob Devries]

Hi Robert,

I also notice that there's no entry in the makefile to actually *build* 
the clock2_disto4 module. The makefile has an entry for two software 
clocks (50 and 60Hz), the cloud9 and the BNB clock2 modules.

I notice that the other clock2 entries have something like -DCLOUD9=1 or 
-DBNB=1. However, I can't see where this is used. Should I set the 
clock2_disto4 to -DDISTO or -DDISTO4.

And yet, it appears that there is a clock2 module in the 
NITROS9/6309L2/CLOCKS directory on the created disk image. That image 
doesn't read the clock since I suspect that the default clock2 module is 
the 60Hz software clock.

You would be forgiven if you think I'm floundering here. :)

Regards, Bob Devries
Dalby, QLD, Australia


On 21/01/2015 2:11 PM, Robert Gault wrote:
> Bob Devries wrote:
>> Hi Robert,
>>
>> I have had a look at the source of clock2_disto4.asm and found that it
>> is indeed
>> set up to be slot-ready, but it needs to have MPIFlag set to the slot
>> number
>> (1-4). Now I'm left wondering where this is set? I have the idea that
>> it should
>> be in one of the rules.mak? Would that be correct?
>>
>> Regards, Bob Devries
>> Dalby, QLD, Australia
>>
>>
>
> Look at the level2/coco3/modules/makefile for example and you will see
>
> CLOCKSMART      = -DRTCSmart=1 -DMPIFlag=1
>
> None of the other clock2 files have the flag set and you would need to
> adjust the makefile to suit your preferences.
>
> MPIFlag does seem to be used to indicate the slot holding the RTC. That
> would save code but a search routine would be better since you would not
> need to recompile if the clock were moved from a default slot#.
>
> Note that clock2_smart.asm does not use MPIFlag even though the makefile
> does but always searches through all four slots looking for the RTC.
>
> Robert
>
>