From:	owner-rtems-l@lists1.slac.stanford.edu on behalf of Till Straumann 
[strauman@slac.stanford.edu]
Sent:	Thursday, February 03, 2011 3:21 PM
To:	rtems-l
Subject:	rtems-4.9.4_p1 for uC5282 (only) released

I created a new patchlevel release of RTEMS 4.9.4 which adds run-time support 
for 80MHz versions of the uC5282 board.

Since no other boards or architectures are affected I built rtems_p1 for 
uC5282 only.

The ssrlApps package is unchanged at patchlevel ssrlApps_p3.

On any 80Mhz board you *have*to* program the bootloader with the image from

<top>/m68k-rtems/uC5282/img/netboot.flashimg.bin

and boot

<top>/m68k-rtems/uC5282/bin/rtems.ralf

with <top> being:

/afs/slac/package/rtems/4.9.4/target/rtems_p1/ssrlApps_p3/

Previous versions do not work on a 80MHz unit. The new version is 64MHz 
compatible.

-- Till

PS: Here a little more detail about the fix:

The BSP now determines the clock speed according to the following
rules:

a) if the uCbootloader env variable SYS_CLOCK_SPEED is set and can
    be converted w/o errors into a decimal number then that setting
    is used (in Hz).

b) if a) didn't produce any results (or the value is zero)
    then check if the linker-provided _CPUClockSpeed symbol is
    non-zero and use it's value for the clock speed.
    The default linker value has been changed from
    64000000 to 0.

c) if neither a) nor b) produce a non-zero clock speed then use
    the linker-provided symbol _PLLRefClockSpeed which defaults
    to 8000000 and work backwards from this reference clock and
    the multiplier/divider settings in the CLOCK_SYNCR register
    to calculate the clock speed.

Currently, neither a) nor b) are set, so c) delivers the clock speed and that 
works fine on my 64MHz board here and also on
eioc-b034-pad01 (a 80MHz unit). I recommend to *not* set SYS_CLOCK_SPEED nor 
use a non-zero linker-provided value unless you have to (e.g., because you run 
into a board with a ref.clock different from 8MHz).