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.

AM623: Filesystem cannot boot up

Part Number: AM623
Other Parts Discussed in Thread: TSC2007

Hi,

SDK:08.03.00.19

Customer has disabled the gpu according to the instructions below figure, but the file system cannot boot up at present. How can the file system be modified to adapt to 6231?

The error as follows:

[ 14.803125] max_p2p_conn = 8, max_sta_conn = 8 Starting Load/Save RF Kill Switch Status...

[ 14.849629] wlan: version = SD8987---16.92.10.p208-MXM5X16210-GPL-(FP92)

[ 14.859212] wlan: Driver loaded successfully

[ OK ] Started Load/Save RF Kill Switch Status.

[ *** ] A start job is running for udev Wai…ice Initialization (30s / 3min 2s)

  • Hi Nancy,

    Is this on custom board or AM62x SK? What interface is it booting from?

    Please attach the full console boot log.

  • Hi,

    It's custom board, and boots from SD card.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    -Boot SPL 2021.01 (Jan 10 2023 - 10:47:53 +0800)
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.1--w2022.07-am62x (Terrifi')
    am625_init: board_init_f done(counter=1)
    SPL initial stack usage: 13768 bytes
    i2c_write: error waiting for data ACK (status=0x116)
    i2c_write: error waiting for data ACK (status=0x116)
    Auth Success!
    normal mode
    am625_init: spl_boot_device: devstat = 0x1843 bootmedia = 0x9 bootindex = 0
    Trying to boot from MMC1
    am625_init: spl_boot_device: devstat = 0x1843 bootmedia = 0x9 bootindex = 0
    Loading Environment from MMC... MMC: block number 0x3500 exceeds max(0x2000)
    *** Warning - !read failed, using default environment
    am625_init: spl_boot_device: devstat = 0x1843 bootmedia = 0x9 bootindex = 0
    am625_init: spl_boot_device: devstat = 0x1843 bootmedia = 0x9 bootindex = 0
    init_env from device 9 not supported!
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.5(release):v0.6-6-gd489c56
    NOTICE: BL31: Built : 10:44:15, Jan 10 2023
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Hi Nancy,

    The log shows pruss init failure. Please disable pruss node in the kernel device tree to see if it solves the issue.

  • Hi,

    After removing the pruss, it shows [ *** ] A start job is running for udev Wai…nitialization (1min 35s / 3min 2s) After the countdown ends, the login interface can be started, but the desktop is not displayed, and the watchdog also reports an error. As follows, how to modify to display the desktop without gpu.

    [ 9.182085] Goodix-TS 3-0014: supply AVDD28 not found, using dummy regulator
    [ 9.265983] Goodix-TS 3-0014: supply VDDIO not found, using dummy regulator
    [ 9.469933] Goodix-TS 3-0014: i2c test failed attempt 1: -121
    [ 9.530012] Goodix-TS 3-0014: i2c test failed attempt 2: -121
    [ 9.600765] saul-crypto bus@f0000:crypto@40900000: invalid resource
    [ 9.609650] Goodix-TS 3-0014: I2C communication failure: -121
    [ 9.647658] Goodix-TS: probe of 3-0014 failed with error -121
    [ 9.666082] saul-crypto: probe of bus@f0000:crypto@40900000 failed with error -22
    [ 9.788470] Internal error: synchronous external abort: 96000010 [#1] PREEMPT SMP
    [ 9.795958] Modules linked in: rti_wdt(+) sa2ul sha512_generic authenc j721e_csi2rx(+) videobuf2_dma_contig cdns_dphy videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_es8328_i2c snd_soc_es8328 tsc2007 goodix rtc_pcf8563 m_can_platform m_can can_dev sch_fq_codel cryptodev(O) ipv6
    [ 9.821355] CPU: 0 PID: 183 Comm: systemd-udevd Tainted: G O 5.10.87 #1
    [ 9.829253] Hardware name: Forlinx AM62xx (DT)
    [ 9.833688] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
    [ 9.839692] pc : rti_wdt_probe+0x1c4/0x50c [rti_wdt]
    [ 9.844646] lr : rti_wdt_probe+0x1b4/0x50c [rti_wdt]
    [ 9.849596] sp : ffff800012aaf910
    [ 9.852901] x29: ffff800012aaf910 x28: ffff00001dd46800
    [ 9.858204] x27: ffff8000100f34b0 x26: 0000000000000003
    [ 9.863505] x25: ffff8000112f76e8 x24: ffff00000c74ef20
    [ 9.868806] x23: ffff00000c74ee90 x22: ffff00001e47d800
    [ 9.874108] x21: 0000000000000000 x20: ffff00001e47d810
    [ 9.879409] x19: ffff00000c74ee80 x18: 0140000000000000
    [ 9.884710] x17: 0000000000000000 x16: 0000000000000000
    [ 9.890011] x15: ffff800011380000 x14: 000000000e020000
    [ 9.895312] x13: 000000000000029f x12: ffff00003fff0008
    [ 9.900615] x11: ffff8000123d0000 x10: ffff00000fed18c0
    [ 9.905915] x9 : 00007ffffbc60000 x8 : ffff80000fffffff
    [ 9.911216] x7 : 0000000000000020 x6 : ffff8000123bffff
    [ 9.916516] x5 : ffff80001123448c x4 : ffff00001e47da10
    [ 9.921817] x3 : ffff00000185e300 x2 : 0000000000000000
    [ 9.927118] x1 : ffff000001baa800 x0 : ffff8000123b0090
    [ 9.932420] Call trace:
    [ 9.934863] rti_wdt_probe+0x1c4/0x50c [rti_wdt]
    [ 9.939475] platform_drv_probe+0x54/0xa8
    [ 9.943473] really_probe+0xec/0x3e0
    [ 9.947039] driver_probe_device+0x58/0xb8
    [ 9.951125] device_driver_attach+0x74/0x80
    [ 9.955296] __driver_attach+0x58/0xe0
    [ 9.959037] bus_for_each_dev+0x70/0xc0
    [ 9.962861] driver_attach+0x24/0x30
    [ 9.966427] bus_add_driver+0x14c/0x1f0
    [ 9.970251] driver_register+0x64/0x120
    [ 9.974077] __platform_driver_register+0x48/0x58
    [ 9.978771] rti_wdt_driver_init+0x24/0x10000 [rti_wdt]
    [ 9.983985] do_one_initcall+0x54/0x1b8
    [ 9.987816] do_init_module+0x54/0x208
    [ 9.991555] load_module+0x1f28/0x24c8
    [ 9.995293] __do_sys_finit_module+0xb8/0xf8
    [ 9.999551] __arm64_sys_finit_module+0x20/0x30
    [ 10.004073] el0_svc_common.constprop.0+0x78/0x1c8
    [ 10.008851] do_el0_svc+0x24/0x90
    [ 10.012159] el0_svc+0x14/0x20
    [ 10.015204] el0_sync_handler+0xb0/0xb8
    [ 10.019028] el0_sync+0x180/0x1c0
    [ 10.022341] Code: f9000260 b140041f 54000fc8 91024000 (b9400000)
    [ 10.028422] ---[ end trace 8a5bed03ba7c953b ]---
    [ 10.462820] k3-m4-rproc 5000000.m4fss: assigned reserved memory node m4f-dma-memory@a4000000
    [ 10.581115] k3-m4-rproc 5000000.m4fss: configured M4 for remoteproc mode
    [ 10.623248] k3-m4-rproc 5000000.m4fss: local reset is deasserted for device
    [ 10.708157] remoteproc remoteproc0: 5000000.m4fss is available

  • Hi Nancy,

    [ 9.600765] saul-crypto bus@f0000:crypto@40900000: invalid resource
    [ 9.609650] Goodix-TS 3-0014: I2C communication failure: -121
    [ 9.647658] Goodix-TS: probe of 3-0014 failed with error -121
    [ 9.666082] saul-crypto: probe of bus@f0000:crypto@40900000 failed with error -22

    Does the customer enables crypto in device tree? I don't see such saul-crypto errors on the EVM.

    To bring up Linux on a custom board, please ask the customer to follow the process linked below, and use k3-am625-skeleton.dts provided in the SDK kernel, instead of k3-am625-sk.dts.

    https://dev.ti.com/tirex/explore/node?node=A__AAH6hGIXbUwhj18pp-affA__linux_academy_am62x__XaWts8R__LATEST