Just an update - We found out what the issue was - the application in question assumed caches were off when it started, and re-initialized things without flushing things, which the hardware didn't like. Since this doesn't seem like a generic U-Boot issue - we are just making sure that when applications are started - they assume cache can be on or off, and set things appropriately.

Thanks for the help.