On Sun, 22 Aug 2004 19:36:53 -0400, Herbert Graf wrote:
> Hmm, I did try the simulator, it shows:
>
> start time:     clocks=422              seconds=8.44E-6 stop time:
> clocks=443              seconds=8.86E-6
>
> That equates to: 2.38MHz
>
> That would seem to match with what the assembly shows, so I
> definately have SOMETHING wrong with the dev kit, grr...
>
> Thanks for the suggestion. TTYL

Herbert,

Check the eZ80 datasheet -- I seem to recall that the internal flash
has is quite slow and uses a bunch of wait states. Also make sure they
are not using RAM with wait states. The external bus cycles at 50 MHz
are pretty short and take some darn fast (and expensive) memories to
run with few or no wait states.

I ran into this same kind of problem with the Rabbit CPUs when they
came out with their 44MHz R3000 chip. It only ran marginally faster
than a 22MHz R2000 CPU. The cause was adding wait states because they
used Flash that couldn't run with 0 wait states.

Matt Pobursky
Maximum Performance Systems

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body