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.

AM62A7-Q1: In MCU+SDK falcon mode, the kernel failed to boot.

Part Number: AM62A7-Q1

Tool/software:

Hi,

When using MCU+SDK Falcon mode, we encountered the following problems when starting to kernel stage:

[    2.635963] /dev/root: Can't open blockdev
[    2.640098] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    2.647581] Please append a correct "root=" boot option; here are the available partitions:
[    2.655962] b300        30539776 mmcblk0
[    2.655969]  driver: mmcblk
[    2.662793]   b301          131072 mmcblk0p1 3f4cc94b-01
[    2.662801]
[    2.669621]   b302        10485760 mmcblk0p2 3f4cc94b-02
[    2.669628]
[    2.676436]   b303        10485760 mmcblk0p3 3f4cc94b-03
[    2.676442]
[    2.683236]   b304         4194304 mmcblk0p4 3f4cc94b-04
[    2.683241]
[    2.690047] b320           32640 mmcblk0boot0
[    2.690052]  (driver?)
[    2.696846] b340           32640 mmcblk0boot1
[    2.696851]  (driver?)
[    2.703645] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    2.711901] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.80-ti-g2e423244f8c0 #1
[    2.719290] Hardware name: Texas Instruments AM62A7 SK (DT)
[    2.724854] Call trace:
[    2.727294]  dump_backtrace.part.0+0xdc/0xf0
[    2.731570]  show_stack+0x18/0x30
[    2.734882]  dump_stack_lvl+0x68/0x84
[    2.738544]  dump_stack+0x18/0x34
[    2.741856]  panic+0x188/0x348
[    2.744908]  mount_block_root+0x188/0x23c
[    2.748916]  mount_root+0x208/0x248
[    2.752399]  prepare_namespace+0x130/0x170
[    2.756490]  kernel_init_freeable+0x258/0x284
[    2.760841]  kernel_init+0x24/0x130
[    2.764328]  ret_from_fork+0x10/0x20
[    2.767902] SMP: stopping secondary CPUs
[    2.771820] Kernel Offset: 0x80000 from 0xffff800008000000
[    2.777296] PHYS_OFFSET: 0x80000000
[    2.780778] CPU features: 0x00000,00900084,0000420b
[    2.785649] Memory Limit: none
[    2.788702] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

We tried to add the following code to the device tree, but it didn't work.

bootargs="...... root=/dev/mmcblk0p2 ......"

How to solve this problem?

In falcon, Image and k3-am62a7-sk.dtb of board-support/ prebuild-images are used. I would like to know the difference between these two files and normal kernel files.

How do I generate the kernel files used in falcon?

  • Hello,

    Could you share the full bootargs statement?
    The location of filesystem is unknown. I hope you have the filesystem in SD card and you can boot the board using SD card boot mode.

    Image and k3-am62a7-sk.dtb of board-support/ prebuild-images are used.

    These are the default images and the bootargs changes you have made in the dts file will not be reflected in these images. Hence, after building linux kernel, you will have to use the images from:
    /board-support/ti-linux-kernel-6.1.80+gitAUTOINC+2e423244f8-ti/arch/arm64/boot/Image
    /board-support/ti-linux-kernel-6.1.80+gitAUTOINC+2e423244f8-ti/arch/arm64/boot/dts/ti/k3-am62a7-sk.dtb

    How do I generate the kernel files used in falcon?

    To build the linux kernel, you can run make linux command from SDK directory, using the top-level makefile.

    Regards,
    Aparna

  • Hi,

    When we used the Image and DTB compiled by ourselves, falcon could not boot normally, but the Image and dtb of board-support/ prebuild-images could actually boot to the kernel normally. We would like to know if there are any special configurations for Image and dtb of board-support/ prebuild-images?

    Regards,

    Gangqiang

  • Hi,

    Today we checked the problem and found that using Image compiled by ourselves and dtb of board-support/prebuild-images can boot to the kernel normally. Is there anything that needs to be configured in dtb?

    Regards,
    Gangqiang

  • Hi,

    Good to know that you can boot properly until Linux.

    There is nothing that needs to be configured in dtb for falcon boot mode other than setting the bootargs to point to the filesystem location.

    Regards,
    Aparna

  • Hi,

    Thanks to your support, we solved our problem.We have a configuration problem with our device tree.
    Regards,
    Gangqiang