• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 600 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.

TI816x RAM Restriction

Tom Schneider
Prodigy 60 points

Hello,

 

I am seeing a RAM restriction at 768 MB (with a 2GB stick installed).  Here are my boot settings:

bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw mem=1000M earlyprink vram=10M ti816xfb.vram=0:16M,1:16M,2:6M;

bootcmd=mmc init;fatload mmc 0 0x80300000 uImage;bootm 0x080300000;

 

Then during boot this happens....

 

Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw mem=1000M earlyprink vram=10M ti816xfb.vram=0:16M,1:16M,2:6M;

PID hash table entries: 4096 (order: 2, 16384 bytes)

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

Memory: 768MB = 768MB total

Memory: 775244k/775244k available, 11188k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)

    vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)

    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)

    modules : 0xbf000000 - 0xc0000000   (  16 MB)

      .init : 0xc0008000 - 0xc0031000   ( 164 kB)

      .text : 0xc0031000 - 0xc03c9000   (3680 kB)

      .data : 0xc03ca000 - 0xc03f0280   ( 153 kB)

 

Is any one else seeing this issue? I assume that it is something that I am doing wrong while compiling the kernel; however, I haven't been able to track it down. Any advice? Thanks for your time.

 

Regards,

Tom

  • 0
    TI__Expert 4245 points

    Hi Tom,

    Tom Schneider said:

    I am seeing a RAM restriction at 768 MB (with a 2GB stick installed).  Here are my boot settings:

    bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw mem=1000M earlyprink vram=10M ti816xfb.vram=0:16M,1:16M,2:6M;

    bootcmd=mmc init;fatload mmc 0 0x80300000 uImage;bootm 0x080300000;

    I'm not sure I understood why mem=1000M. From a memory map perspective, please take a look at the FAQ at http://processors.wiki.ti.com/index.php/EZ_SDK_FAQ. You will need to pass mem=166M to linux. If you need additional memory beyond the memory reserved for DSP, CMEM, SR1 etc, then you can add to the linux memory on top of this. The PSP documentation should contain more information on how to configure linux for memory beyond the reserved memory.

    --Sid

     

  • 0 in reply to Siddharth Heroor
    Prodigy 60 points

    Siddharth,

    Thanks for the quick response. That helps alot actually. Also, I have been using your work from the arago-project. Thanks for being so active! It has helped me out.

    I also had a question about the newer kernels. I am seeing busybox errors when I try to update to 2.6.37. The errors appear right after I get to run level 5 (I never actually get to the login prompt). Here are my new bootargs:

    bootcmd=mmc init;fatload mmc 0 0x80300000 uImage;fatload mmc 0 0x81000000 rmdisk.gz;bootm 0x80300000;
    bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootwait mem=166M initrd=0x81000000,50M;

    Where rmdisk.gz is the arago-base-image ramdisk file.

    And here are the errors I am seeing:

    Bad inittab entry at line 5
    can't open /dev/si: No such file or directory
    can't open /dev/~~: No such file or directory
    can't open /dev/l0: No such file or directory
    can't open /dev/l1: No such file or directory
    can't open /dev/l2: No such file or directory
    can't open /dev/l3: No such file or directory
    can't open /dev/l4: No such file or directory
    can't open /dev/l5: No such file or directory
    can't open /dev/l6: No such file or directory
    can't open /dev/z6: No such file or directory
    can't open /dev/S: No such file or directory
    can't open /dev/1: No such file or directory
    process '/sbin/sulogin' (pid 54) exited. Scheduling for restart.
    process '/sbin/getty 115200 ttyS2' (pid 55) exited. Scheduling for restart.
    process '/sbin/getty 38400 tty1' (pid 56) exited. Scheduling for restart.

    Do you have any advice or thoughts on this?

    Once again, thanks for your time. I appreciate it.

    Regards,

    Tom Schneider

  • 0 in reply to Tom Schneider
    TI__Expert 4245 points

    Hi Tom,

    Tom Schneider said:
    process '/sbin/getty 115200 ttyS2' (pid 55) exited. Scheduling for restart.

    With the new 2.6.37 kernel, the TTY has changed from ttyS2 to ttyO2. I noticed that you have updated your bootargs for this, but from the errors, it looks like inittab is still picking ttyS2. If you are picking up from the Arago mainline, this requires a change in the conf/machine/include/ti816x.inc file. I had submitted patches for this last week.

    I haven't tried using ramdisk myself, but one thing that you could check is that the filesystem is created with root permissions instead of user level permissions, especially for /dev/ /usr and /etc. I have verified that the arago-base-image works fine from NFS though.

    --Sid

  • 0 in reply to Siddharth Heroor
    Prodigy 60 points

    Hi Siddarth,

    Thanks for all the help. Making the change to ti816x.inc fixes the problem. I have confirmed that the RAM and SD boot both work. Have a great day!

    Regards,

    Tom