Does this mean that there is something wrong with the Intel provided ESRAM driver in the BSP? Dealing with the mapping and physical addresses is the drivers job as far as I know.
I am following "Intel® Quark™ Software Developer's Manual for Linux" documentation that describes the esram driver. I am using "intel_qrk_esram_map_range()" function (BSP 1.0.1) that takes a virtual address range. I am not playing with the physical addresses.
Thanks,
-Ehsan