Error: Could Not Calibrate SDARM

Hi Stephen,

Thanks for your help but I already read all related topics.

The problem is that when I use a Altera or Intel (Arria 10 ) as a target in configuration I do not have any access to memory and during the debug the error is printed but if I use FVP(Fast Model) and choose the Cortex9 as a target then I the boot file is loaded:

"+loadfile u-boot-socfpga/u-boot
Loaded section .text: S:0x01000040 ~ S:0x010003E7 (size 0x3A8)
Loaded section .efi_runtime: S:0x010003E8 ~ S:0x01000EE7 (size 0xB00)
Loaded section .text_rest: S:0x01000F00 ~ S:0x0103028D (size 0x2F38E)
Loaded section .rodata: S:0x01030290 ~ S:0x0103E013 (size 0xDD84)
Loaded section .hash: S:0x0103E014 ~ S:0x0103E02B (size 0x18)
Loaded section .data: S:0x0103E030 ~ S:0x01040FEF (size 0x2FC0)
Loaded section .got.plt: S:0x01040FF0 ~ S:0x01040FFB (size 0xC)
Loaded section .u_boot_list: S:0x01040FFC ~ S:0x0104246B (size 0x1470)
Loaded section .efi_runtime_rel: S:0x0104246C ~ S:0x0104253B (size 0xD0)
Loaded section .rel.dyn: S:0x0104253C ~ S:0x0104BE93 (size 0x9958)
Loaded section .dynsym: S:0x0104BE94 ~ S:0x0104BEC3 (size 0x30)
Loaded section .dynstr: S:0x0104BEC4 ~ S:0x0104BEC4 (size 0x1)
Loaded section .dynamic: S:0x0104BEC8 ~ S:0x0104BF57 (size 0x90)
Loaded section .gnu.hash: S:0x0104BF58 ~ S:0x0104BF6F (size 0x18)
Loaded section .dynamic: S:0x0104BEC8 ~ S:0x0104BF57 (size 0x90)
Entry point S:0x01000040
+set $PC = 0x01000040
+wait 10s"

also I have access to the memory and I can read the data:

I could not found any answer in this situation an I could not find what is the exactly different between these two type of target, on the other hand I am not sure which I can use this target ? Do you have more information these target or extra document.

Regards

Fatima

Thanks for quick answer.

I already did unfortunately when I debug as Arria 10 target (Altera or Intel) I did not have an access to write but via FVP it is possible.

Indeed the MMU is enable

when I try with Arria10 debug target ;

memory fill 0x01000040 0x01000100 1 0x0 

*****************************************************************************
Target Message: Memory access caused precise abort.
Debug Precise Abort Registers : DFSR = 0x00000805, DFAR = 0x01000100
ERROR(TAD100-NAL18):
! Memory fill failed at address S:0x01000040, filling 193 8 bit values
! Bus error on memory operation.
Target Message: Memory access caused precise abort.
Debug Precise Abort Registers : DFSR = 0x00000005, DFAR = 0x01000040
Target Message: Memory access caused precise abort.
Debug Precise Abort Registers : DFSR = 0x00000005, DFAR = 0x01000040

*********************************************************************************

with FVP:

memory fill 0x01000040 0x01000100 1 0x0  => 

Thanks for confirming the area of memory at S:0x01000040 is not writable.  That explains why the Debugger is unable to download U-Boot to that address.

The differences you see between the behaviour of the Cortex-A9 FVP model and the Arria 10 hardware are to be expected.  The FVP is a model of an example Cortex-A9-based system.  It accurately models the behaviour of the Cortex-A9 processor core, but its memory system and peripherals are not the same as the ones on the Arria 10.

I'm afraid that you will have to investigate why that area of memory is not writable on the Arria 10 yourself.  If the MMU is enabled, try using the Debugger's MMU/MPU view to see which areas are accessible.  You could also try temporarily turning the MMU off.  If that doesn't work, then try looking elsewhere for information about how the RAM/ROM/SDRAM remapping is controlled.

Hope this helps

Stephen

Thanks a lot Stephen for helpful comments and I appreciate you taking the time to find out the solution.

Thanks a lot Stephen  for helpful comments and I appreciate you taking the time to find out the solution.

Thank you Ronan for giving me this information.