Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Jul 2013 22:51:31 -0700
From:      Rui Paulo <rpaulo@felyko.com>
To:        "freebsd-arm@freebsd.org" <arm@freebsd.org>
Subject:   Re: External Non-Linefetch Abort (S)
Message-ID:  <FF70D0AA-FAFD-4EA5-9D3C-331D4C5EF1A1@felyko.com>
In-Reply-To: <3C6B0B0D-3F16-44A5-8DF2-A79CBD0D02D3@felyko.com>
References:  <3C6B0B0D-3F16-44A5-8DF2-A79CBD0D02D3@felyko.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Jul 2013, at 20:33, Rui Paulo <rpaulo@felyko.com> wrote:

> On the BeagleBone, I'm trying to access this address 0x4a300000. I =
know there is a device there (the PRUSS) and I should be able to access =
it, but instead I get this data abort trap:
>=20
> Fatal kernel mode data abort: 'External Non-Linefetch Abort (S)'
> trapframe: 0xc08c5c84
> FSR=3D00001008, FAR=3Dd4a5c000, spsr=3D60000093
> r0 =3D00000000, r1 =3Dd4a5c000, r2 =3D00000000, r3 =3Dc062a908
> r4 =3D00000000, r5 =3Dc08c5ce4, r6 =3Dc1825500, r7 =3Dc18eb700
> r8 =3Dffffffff, r9 =3Dc1825d80, r10=3Dc1825500, r11=3Dc05511e0
> r12=3D00000015, ssp=3Dc08c5cd0, slr=3Dc052f1b0, pc =3Dc050bf78
>=20
> [ thread pid 0 tid 100000 ]
> Stopped at      generic_bs_r_4: ldr     r0, [r1, r2]
>=20
> It looks like 0xd4a5c000 is the virtual address that points to =
0x4a300000 (I checked with vtophys()).
>=20
> Does anyone know what this problem could be? I made sure the clock for =
this device are running.


Nevermind, I missed one PRCM bit...

--
Rui Paulo




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF70D0AA-FAFD-4EA5-9D3C-331D4C5EF1A1>