• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 4 answers
  • Subscribers 98 subscribers
  • Views 1925 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM572x RAM Disc file system

Ilya Kravchuk
Expert 1520 points
Other Parts Discussed in Thread: AM5728

I want to boot linux kernel with simple filesystem in DDR on my customboard, based on Sitara AM5728.
I've build linux kernel uImage with simple init filesystem, downloaded from this topic. 
Then I downloaded u-boot, kernel and dtb file via ymodem to DDR and change "fdtfile" variable in u-boot environment.
But when I'm trying to boot kernel by  "bootm" command, following error appears:



When I'm trying too boot kernel, without init filesystem configuration, it works.

In connection with, I've got a two questions:

1. What am I supose to do, to solve this problem?
2. Did I correctly understand, that, when I configure the kernel and change init ram filesystem path via menuconfig, filesystem includes in uImage after building and I don't need to download a filesystem in DDR: only kernel and dtb file?

  • 0
    TI__Guru**** 393215 points
    Hi,

    The software team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    TI__Guru 55345 points

    Hello Ilya,

    1. Please check if zImage or uImage is defined as bootfile, seems you are passing the kernel in zImage format to bootm command.
    2. Yes, the kernel contains ramfs if you configure and build it in the way you have described.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    Expert 1520 points

    It's ok, now kernel is booting with following bootargs: setenv bootargs console=ttyO2,115200n8

    But it hangs on this moment

    Did I correctly understand, that problem is in FS initialization?

  • 0
    Expert 1520 points

    I want to boot linux kernel with simple filesystem in DDR on my customboard, based on Sitara AM5728.
    I've create initrd from filesystem, which is attached here, as it described at this link. But I didn't find this notes in .config:

    CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=1
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024


    And when I'm trying to boot with following bootargs: setenv bootargs mem=32M console=ttyO2,115200n8 root=/dev/ram0 rw. The following error appears:


    What am I supposed to do to fix this problem?
    And as I understand this fs, is intended for initfs creation. The filesystem, included in SDK is too large, where I can get another empty tiny filesystem?

  • 0 in reply to Ilya Kravchuk
    TI__Guru 55345 points

    Have you tried with the <Processor SDK>/filesystem/arago-base-tisdk-image-am57xx-evm.tar.gz filesystem.

  • 0 in reply to Kemal R. Shakir
    Expert 1520 points
    Thank you for fast reply.
    In this fs already exists file, named "Init".

    Therefore, I've got two questions:
    1. Can I create initrd of this fs, or, firstly, I should remove this Init file?
    2. If I want to use this fs how initfs, does it normal, that I haven't got following in .config:
    CONFIG_BLK_DEV_RAM=y
    CONFIG_BLK_DEV_RAM_COUNT=1
    CONFIG_BLK_DEV_RAM_SIZE=8192
    CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
  • 0 in reply to Ilya Kravchuk
    TI__Guru 55345 points

    1.

    When using initrd, the system typically boots as follows:

1) the boot loader loads the kernel and the initial RAM disk
2) the kernel converts initrd into a "normal" RAM disk and
frees the memory used by initrd
3) if the root device is not /dev/ram0, the old (deprecated)
change_root procedure is followed. see the "Obsolete root change
mechanism" section below.
4) root device is mounted. if it is /dev/ram0, the initrd image is
then mounted as root
5) /sbin/init is executed (this can be any valid executable, including
shell scripts; it is run with uid 0 and can do basically everything
init can do).
6) init mounts the "real" root file system
7) init places the root file system at the root directory using the
pivot_root system call
8) init execs the /sbin/init on the new root filesystem, performing
the usual boot sequence
9) the initrd file system is removed

    <Processor SDK>/board-support/linux-<version>/Documentation/initrd.txt

    2. You should run make menuconfig to enable these options if they are not present in the .config.
    processors.wiki.ti.com/.../Sitara_Linux_Training:_Linux_Host_Configuration

  • 0 in reply to Kemal R. Shakir
    Expert 1520 points

    There is no same fields

  • 0 in reply to Ilya Kravchuk
    TI__Guru 55345 points

    Check the General setup section.