I'm using OpenOCD and a Flyswatter to debug some new code that is
based on the u-boot-next tree.  The board is a Beagle C4.  The problem
that I am seeing is that I can not access memory from the telnet
sesson to OpenOCD or from an attached gdb session.  I believe the
problem is that in the -next u-boot tree the mmu is enabled and I
think I have seen mention on this list of this not being supported.
The mapping is simple one-to-one physical-to-virtual.  I believe it
has been added to get page level control of caching so i-cache and
d-cache commands can be enabled for arm.

Is there anything I can do to get this to work?  I believe that having
the mmu on for arm in u-boot will be the norm soon so being able to
deal with this in OpenOCD would be nice.

Thanks
John
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to