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.

Linux/AM5726: Kernel boot hangs

Part Number: AM5726
Other Parts Discussed in Thread: AM5728,

Tool/software: Linux

Hi,

I have created SD card with SDK 4.02.00.09 and try booting our own board. Kernel hangs with the below log:

*
*
*
[ OK ] Started Rebuild Hardware Database.
Starting udev Coldplug all Devices...
[ OK ] Reached target System Time Synchronized.
[ OK ] Started udev Coldplug all Devices.
[ 9.971057] omap-rproc 58820000.ipu: assigned reserved memory node ipu1_cma@9d000000
[ 9.994145] remoteproc remoteproc0: 58820000.ipu is available
[ 10.037405] omap-rproc 55020000.ipu: assigned reserved memory node ipu2_cma@95800000
[ 10.084029] remoteproc remoteproc1: 55020000.ipu is available
[ 10.108608] omap-rproc 40800000.dsp: assigned reserved memory node dsp1_cma@99000000
[ 10.156884] remoteproc remoteproc2: 40800000.dsp is available
[ 10.160544] omap-rproc 41000000.dsp: assigned reserved memory node dsp2_cma@9f000000
[ 10.160661] remoteproc remoteproc3: 41000000.dsp is available
[ 10.279929] rtc-ds1307: probe of 2-006f failed with error -5
[ 10.342865] palmas-rtc 48070000.i2c:tps659038@58:tps659038_rtc: rtc core: registered 48070000.i2c:tps659 as rtc1
[ 10.388304] omap-des 480a5000.des: OMAP DES hw accel rev: 2.2
[ 10.415373] omap-des 480a5000.des: will run requests pump with realtime priority
[ 10.475174] systemd[1]: Found device /dev/ttyS2.
[ OK ] Found device /dev/ttyS2.
[ OK ] Started Opkg first boot configure.
[ 10.633963] remoteproc remoteproc0: powering up 58820000.ipu
[ 10.640051] remoteproc remoteproc0: Booting fw image dra7-ipu1-fw.xem4, size 4687356
[ 10.648659] omap-iommu 58882000.mmu: 58882000.mmu: version 2.1
[ 10.656264] remoteproc remoteproc1: powering up 55020000.ipu
[ 10.662005] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3738980
[ 10.673731] omap-iommu 55082000.mmu: 55082000.mmu: version 2.1


the main difference with the EVM is that we use AM5726 not AM5728
What may be the problem ? Is it because of powering up ipu?

Thanks and best regards
Ferhat

  • Hi Ferhat,

    I'm not seeing a crash on the log but the main difference between AM5728 and AM5726 is that AM5726 has no graphics acceleration and HDMI port and you are using SW for AM5728 it could be a reason for causing stuck if there is some attempt for call systems which not present.
    I suggest you to revise the device tree and kernel config file and comment all initializations related to graphics and HDMI. The rebuild kernel, modules and device tree and make a SD again.

    BR
    Tsvetolin Shulev
  • Hi Shulev,

    I have rebuilt the kernel without graphics and HDMI but nothing changes. I find a below tread in e2e forum which is similar to my problem:

    e2e.ti.com/.../2306489

    May this stuck problem caused by remoteproc while loading firmwares? How can I disable these processes to understand which one is the main reason?

    Note: When I renamed /lib/modules (no module install attempt) the board brings up and come to login screen.

    Regards
  • Ferhat,

    Let's focus on the case with renamed /lib/modules folder and successfully login. It seems that one of the modules cause stuck of the system.
    I suggest you to experiment which module causing the issue.

    BR
    Tsvetolin Shulev