Hello sjr,

thanks for your question. I consulted Michael Erickson about this, and he provided the following reply:

*************************************************************
We use the same header file that this person is seeing. That is to say, the header file used by our code does define these bits in the following way:

#define RCPC_CLKCTRL_CT0_DISABLE _BIT(3)
#define RCPC_CLKCTRL_CT1_DISABLE _BIT(4)
#define RCPC_CLKCTRL_CT2_DISABLE _BIT(5)
#define RCPC_CLKCTRL_CT3_DISABLE _BIT(6)

However, we actually only use RCPC_CLKCTRL_CT1_DISABLE _BIT and RCPC_CLKCTRL_CT2_DISABLE _BIT in our code.

Therefore I think that we can reasonably assume that the definitions in the header file for xxx_CT1_xxx and xxx_CT2_xxx are correct, whereas the definitions for xxx_CT0_xxx and xxx_CT3_xxx could in fact, be wrong.

*************************************************************

Best Regards,
Andrew Wawra
Logic Product Development

Andrew,

you say BoLo/LoLo only uses timers 1 & 2? I have an email from you dated 19th Feb in which you say the Logic Loader uses timers 0 & 1 for its multitasking purposes, and you recommend we use timers 2 & 3 for our requirements.

So which is it? 0 & 1 or 1 & 2.

Regards.

Hello sjr,

Here's some more info to try and clarify the situation. It's from Bruce R., another developer at Logic. I've edited the message somewhat for clarity.

Regards,
Andrew Wawra
Logic Product Development

*********************************************************
the #defines are originally from the sharp header files for Sharp's KEV 9520 kit. Logic only uses the ones that work according to the manual.

Unfortunately their may be some erroneous ones that were never edited out. Logic was hesitant to do that because there were occasions where the header file was right but the original manuals were wrong.

in summary the #defines we use are the ones that have been tested.

*********************************************************