timer problem on RouterBOARD 230r3 (CPU revision B1)

Hi there,

i’ve got a strange problem with a new rb230. When routeros has started CPU frequency is at 100Mhz:

[admin@904G] > /system resource print
uptime: 11m9s
version: “3.20”
free-memory: 117672kB
total-memory: 127072kB
model: “RouterBOARD 230”
cpu: “Geode”
cpu-count: 1
cpu-frequency: 100MHz
cpu-load: 4
free-hdd-space: 84474kB
total-hdd-space: 121215kB
write-sect-since-reboot: 376
write-sect-total: 376
architecture-name: “x86”
board-name: “x86”
[admin@904G] >

After trying without success to put the correct cpu frequency in my rb, i’ve seen this strange error after bios POST:

RouterBIOS-200 v1.3.8 MikroTik ™ 2003-2005

RouterBOARD 230r3 (CPU revision B1)
CPU frequency: 266 MHz
Memory size: 128 MB

Press any key within 1 second to enter setup..
timer not ready after 4294ms (clock speed 243.47%)!

Booting IDE…

If you want more information there is the output of the command:

[admin@904G] > /system routerboard print
routerboard: yes
model: “230r3”
serial-number: “034B01DEC554”
current-firmware: “1.3.8 (Dec/11/2007 16:39:15)”
upgrade-firmware: “1.3.8 (Dec/11/2007 16:39:15)”
[admin@904G] >

[admin@904G] > /system routerboard bios print
baud-rate: 9600
debug-level: low
boot-delay: 1s
enter-setup-on: any-key
beep-on-boot: yes
boot-device: ide-only
etherboot-timeout: 1m
vga-to-serial: yes
memory-settings: optimal
memory-test: no
cpu-mode: power-save
pci-backoff: enabled
[admin@904G] >


Thank you, regards.

when and where did you brought this board?
Looks like a hardware problem, you can try to RMA if you still have warranty for it.

Hi there,it seems it’s RTC problem. Check RTC battery is there 3V on battery holder + pole. Else check JP3 and Y1/Y5

Thank’s for reply to all:

udis: i’ve bought two directly from you, 2 weeks ago. One go right the other has got this problem.
aaa: i’ll check asap.

Best Regards.

Here you have the output of the console with bios debug level set to high.

If you can please read it,

Thank you very much,

Nice Regards.
rb230.pdf (37 KB)

it looks more like hardware problem, please contact RMA.