Closed GoogleCodeExporter closed 9 years ago
Can we get more information on this bug? what kind of environment do you have?
Original comment by albe...@google.com
on 10 May 2012 at 6:21
Unaligned access support is a requirement for the ARM version.
Have you initialized your cortex-a8 correctly to enable unaligned accesses? set
U=1 and A=0 in CP15?
The reason why you dont get the exception on pandaboard is exactly this, it is
initialized properly and unaligned accesses are handled correctly by the system.
What version of RVDS are you using?
Original comment by attilan...@google.com
on 11 May 2012 at 5:51
Unaligned access support is a requirement for the ARM version.
Have you initialized your cortex-a8 correctly to enable unaligned accesses? set
U=1 and A=0 in CP15?
The reason why you dont get the exception on pandaboard is exactly this, it is
initialized properly and unaligned accesses are handled correctly by the system.
What version of RVDS are you using?
Original comment by attilan...@google.com
on 11 May 2012 at 5:51
[deleted comment]
By default A=0 in cortex-a8 CP15 c1 control register.
But i am not finding U bit in CP15 c1 control register
I am using Metrowerks codewarrior IDE 5.7.0 compiler and RVDEBUG V3.0 service
pack 1
simulator.
Original comment by satish...@gmail.com
on 18 May 2012 at 4:20
My mistake, U bit is not anymore in Cortex.
"The MMU controls what type of memory the CPU sees at a particular address.
There are three memory types: Normal, Device, and Strongly-Ordered. Only
Normal memory supports unaligned accesses. So, in order to have unaligned
accesses work on the Cortex-A8/9, the memory being accessed needs to be marked
as Normal and the CP15 A bit must be 0."
I think there are RVDS examples of setting up MMU.
Original comment by attilan...@google.com
on 18 May 2012 at 5:31
can you suggest any example ?
Original comment by satish...@gmail.com
on 18 May 2012 at 6:53
the example i had in mind is actually in the ARM Profiler...xvid
Original comment by attilan...@google.com
on 18 May 2012 at 7:11
Original comment by attilan...@google.com
on 30 May 2012 at 6:06
Please re-open if the ARM configuration you have does not work.
thanks
Original comment by albe...@google.com
on 28 Mar 2013 at 10:17
Original issue reported on code.google.com by
satish...@gmail.com
on 4 May 2012 at 4:27