Re: Need help with BeagleBoard rev. C4

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi!

From: Stefan Hertenberger <Stefan@Hertenberger.bayern>
Date: Thu, 13 Oct 2016 21:34:14 +0200

> the system starts but fails with
> 
> ...
> omapmputmr0 at obio2 addr 0x49032000-0x490320ff intr 38: OMAP MPU Timer
> #2 
> omapmputmr1 at obio2 addr 0x49034000-0x490340ff intr 39: OMAP MPU
> Timer #3 
> omapmputmr2 at obio2 addr 0x49036000-0x490360ff intr 40: OMAP MPU Timer
> #4 
> clock: hz=100 stathz=64 data_abort_handler: data_aborts fsr=0x1808
> far=0xe103401c 
> Fatal kernel mode data abort: 'External Non-Linefetch Abort (S)'
> trapframe: 0x80afbeb0 FSR=00001808, FAR=e103401c, spsr=20000153
> r0 =00000000, r1 =e1034000, r2 =0000001c, r3 =00000000
> r4 =8080ff5c, r5 =80acd1b8, r6 =8077ad04, r7 =00000000
> r8 =8030e880, r9 =8ef17ed0, r10=87ffc01b, r11=80afbf2c
> r12=80afbed0, ssp=80afbf00, slr=80306078, pc =8030e880
> 
> Stopped in pid 0.1 (system) at  netbsd:generic_bs_w_4:  str     r3,
> [r1, r2]
> db> bt
> 0x80afbf2c: netbsd:cpu_initclocks+0xc
> 0x80afbf94: netbsd:initclocks+0x48
> 0x80afbfec: netbsd:main+0x238
> 0x80afbffc: netbsd:kernel_text+0x50
> db>
> 
> Is u-boot the cause? any ideas are welcome.
> 
> the board seems to work because i can boot an old angstrom linux image
> and with the old u-boot, from 2009 even NetBSD was able to boot.

I think, Yes!
In my memory, I saw in my OVERO and recent u-boot.  Recent u-boot does
not enable the clock of the timer you do not want to use.
Can you try on u-boot's prompt?

  md 48005000 1
  md 48005010 1

I would expect that any of the bits 3, 4 and 5 is not the 1.
Please write back to them to 1.

  mw 48005000 <former value | 38>
  mw 48005010 <letter value | 38>

And try boot NetBSD.


Or, if you still have the old u-boot

  md.w 480021be 2

The values of the result, which also I think that it is "11c 11c".
if yes,

  mw.w 480021be 110
  mw.w 480021c0 110

And try to boot NetBSD.

Thanks,
--
kiyohara