From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" To: "'Jonathan Larmour'" Cc: "'eCos Disuss'" Subject: RE: [ECOS] program doesn't work with new redboot Date: Mon, 13 Aug 2001 14:10:00 -0000 Message-id: <000701c1243c$6483c700$090110ac@TRENT> References: <3B783836.848713EF@redhat.com> X-SW-Source: 2001-08/msg00429.html Sorry, wrong terminology! :) It's not the timer I'm worried about. If the CL-PS6700 does not run at a constant 18.432MHz, it will not work properly. The cycle timing will be off and I won't be able to communicate with the PC-card. So, with this new information, is it possible that Redboot's clock rate could interfere with the eCos program? -----Original Message----- From: jlarmour@cambridge.redhat.com [ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour Sent: Monday, August 13, 2001 2:28 PM To: Trenton D. Adams Cc: 'eCos Disuss' Subject: Re: [ECOS] program doesn't work with new redboot "Trenton D. Adams" wrote: > > What about the clock speed of the processor? Oh you meant *eCos* configuration options when you said "compilation options". I thought you meant the compile line options. In that case, "yes" :-). > Default settings for the > EDB7111 is 73.728MHz. So, I assume that redboot must be set to this > since the Redboot user guide seems to use mostly default values. Is > this likely to cause a problem if I need my eCos program to run at > 18.432MHz? But, I would think that since eCos is the last system to > start up, the CPU should be set to 18.432MHz instead of what redboot > wanted it to be. I don't think RedBoot uses the timer for anything, so porbably okay. Jifl -- Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062 Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine