This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TIDEP-01002: DRA711 custom board: VisionSDK earlyboot kernel panic

Part Number: TIDEP-01002
Other Parts Discussed in Thread: DRA71

hi all experts,

Our custom board soc is dra711, we had run visionSdk earlyboot on J6entry EVM board (TIDEP-01002) successly. Now our custom board can run very well when not run visionSDK.

The most different between custom board and J6entry EVM board is DDR3 memory size. Our DDR3 size is 512M. so i modify the  build/tda2ex/mem_segment_definition_linux.xs

in visionSDK, as following:

The address segment as following:

0537.mem_segment_definition_linux.zip

MEMORY CONFIGURATION

 

         name            origin    length      used     unused   attr    fill

----------------------  --------  ---------  --------  --------  ----  --------

  L2_ROM                00000000   00004000  00000184  00003e7c  RWIX

  L2_RAM                20000000   00010000  00000000  00010000  RWIX

  OCMC_RAM1             40300000   00080000  00000000  00080000  RWIX

  OCMC_RAM2             40400000   00100000  00000000  00100000  RWIX

  OCMC_RAM3             40500000   00100000  00000000  00100000  RWIX

  DSP1_L2_SRAM          40800000   00048000  00000000  00048000  RWIX

  NDK_MEM               84000000   00200000  00000000  00200000  RWIX

  SR1_BUFF_ECC_ASIL_MEM 84200000   00001000  00000000  00001000  RWIX

  SR1_BUFF_ECC_QM_MEM   84201000   00001000  00000000  00001000  RWIX

  SR1_BUFF_NON_ECC_ASIL 84202000   00001000  00000000  00001000  RWIX

  SR1_FRAME_BUFFER_MEM  84203000   07a00000  00000000  07a00000  RWIX

 IPU2_CODE_MEM         8c000000   00800000  001979f7  00668609  RWIX       

  IPU2_DATA_MEM         8c800000   01400000  00558198  00ea7e68  RWIX     

  IPU1_0_CODE_MEM       91000000   00800000  00000000  00800000  RWIX   

  IPU1_0_DATA_MEM       91800000   01400000  00000000  01400000  RWIX

  DSP1_CODE_MEM         92c00000   00200000  00000000  00200000  RWIX     

  DSP1_DATA_MEM         92e00000   00200000  00000000  00200000  RWIX

  SR2_MEM               93000000   04000000  00000000  04000000  RWIX

  FALLBACK_CLUSTER_PNG_ 97000000   01000000  00000000  01000000  RWIX   

  VSDK_RESOURCE_ARRAY_M 98000000   02000000  00000000  02000000  RWIX

  SR0                   9fc00000   00100000  00100000  00000000  RWIX

  REMOTE_LOG_MEM        9fd00000   00040000  000278a0  00018760  RWIX

  LINK_STATS_MEM        9fd40000   00080000  00024df4  0005b20c  RWIX

  SYSTEM_IPC_SHM_MEM    9fdc0000   00080000  00062100  0001df00  RWIX

  HDVPSS_DESC_MEM       9fe40000   00100000  0001b6c0  000e4940  RWIX

  TRACE_BUF             9ff40000   00060000  00008000  00058000  RWIX

  EXC_DATA              9ffa0000   00010000  00000000  00010000  RWIX

  PM_DATA               9ffb0000   00080000  00000000  00080000  RWIX

 

 

SEGMENT ALLOCATION MAP

i already modify the uboot relate definition in  board/ti/dra7xx/lateattach.c of uboot, and i also modify the dts file of kernel.

now my problem is kernel panic when booting, log as following:

U-Boot SPL 2018.01-00436-g9ac3dc8-dirty (Apr 01 2020 - 12:59:16)
DRA722-GP ES2.1
[TICK 00020] spl_board_init: i2c begin
[TICK 00025] spl_board_init: i2c end
[TICK 00028] Trying to boot from MMC1
no pinctrl state for default mode
i2c_write: error waiting for addr ACK (status=0x116)
tps65903x: could not set LDO1 voltage.
[TICK 00043] spl_mmc_find_device: mmc_initialize cost 11
[TICK 00271] spl_mmc_find_device: mmc_initialize cost 0
loading remote core IPU2 successful
[TICK 00315] spl_mmc_find_device: mmc_initialize cost 0
[TICK 00319] spl_mmc_load_image: mmc_init cost 0
[TICK 00348] spl_mmc_do_fs_boot: load u-boot.img err 0 cost 24
===LCD GPIO SETED====
[TICK 00355] spl_mmc_find_device: mmc_initialize cost 0
SPL Load: png_res.data, size = 1527576 in phyaddr: 0x97000000
Jumping to U-Boot
loaded - jumping to U-Boot...
[TICK 00440] image entry point: 0x80800000
[TICK 00443] uboot init
[TICK 00534] serial cost 83
[TICK 00539] DRAM:  ram size gd->ram_size:536870912
512 MiB
[TICK 00555] begin init r
[TICK 00578] initr_dm cost 11
MMC:   OMAP SD/MMC: 0
MMC Device 1 not found
*** Warning - No MMC card found, using default environment

run cmd: run findfdt; run envboot; run mmcboot;
[TICK 00666] do_mmc_dev: init_mmc_device cost 65
SD/MMC found on device 0
** Unable to read file boot.scr **
235 bytes read in 1 ms (229.5 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc0 ...
[TICK 00816] do_mmc_dev: init_mmc_device cost 64
SD/MMC found on device 0
4247096 bytes read in 188 ms (21.5 MiB/s)
88460 bytes read in 11 ms (7.7 MiB/s)
[TICK 01098] ## Flattened Device Tree blob at 88000000
[TICK 01105] Starting kernel ...
when i relace the dra71-dcard.dtb with not earlyboot DTB, kernel can go more far.
so i guess, something wrong in my DTS config. DTS as following:
can anyone help me figure out the problem?
best regards!
  • Hi Fanok,

    I see U-Boot SPL 2018.01-00436-g9ac3dc8-dirty

    Does it mean early boot and late-attach are ported to different u-boot and kernel?

    Can you confirm, memory map and dts file memory reservations are matching?

    and also , some #defines in lateattach.c for firmware loading are not in conflict with any other reserved memory?

    Thanks

    RamPrasad