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.

use x-load-1.4.2 load the kernel directly, but found the total memory is 16M

hi~

i revise the x-load-1.4.2 and the kernel ,so that i can ship the u-boot,and use the x-load to load kernel to 0x80008000 

then start the kernel at 0x80008000 ,it can boot successfully ,but the memory the kernel  detect only 16M, while the real SDRAM in beagleboard C4 is 128M+128M=256M ,how can i fix it?   

  • Hello,

    Could you give some details about how you detect memory size in the Kernel or you observe the booting log? If it is true could you attach a text file with the whole booting log? Also as I see you are using very old x-loader version 1.4.2 and I can not see any information about the u-boot and Kernel versions and where from they are downloaded.

    BR

    Tsvetolin Shulev

  • thinks!

           i tried the new x-loader version 1.51

    https://gitorious.org/x-loader/x-loader/source/ce2dc2f1edf152d681c732f378e2bd464d78050f:

    nothing changed,i skip the u-boot ,and the linux kernel is 2.6.29 .here is the booting log

    Texas Instruments X-Loader 1.5.1 (Mar 28 2014 - 16:16:24)
    Beagle Rev C4
    Loading Image from nand
    Linux version 2.6.29 (root@csq-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #51 Wed Mar 26 14:58:00 CST 2014
    CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387d
    CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    Machine: OMAP3 Beagle Board
    Warning: bad configuration page, trying to continue
    Memory policy: ECC disabled, Data cache writeback
    OMAP3430 ES3.1
    SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
    Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
    Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext2 rootwait lpj=1236992
    Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz
    GPMC revision 5.0
    IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
    Total of 96 interrupts on 1 active controller
    OMAP34xx GPIO hardware version 2.5
    PID hash table entries: 64 (order: 6, 256 bytes)
    OMAP clockevent source: GPTIMER12 at 32768 Hz
    Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
    Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Memory: 16MB = 16MB total
    Memory: 15032KB available (968K code, 128K data, 60K init)
    Calibrating delay loop (skipped) preset value.. 316.17 BogoMIPS (lpj=1236992)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    regulator: core version 0.5
    Found NAND on CS0
    Registering NAND on CS0
    OMAP DMA hardware revision 4.0
    bio: create slab <bio-0> at 0
    i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
    twl4030: PIH (irq 7) chaining IRQs 368..375
    twl4030: power (irq 373) chaining IRQs 376..383
    twl4030: gpio (irq 368) chaining IRQs 384..401
    regulator: VMMC1: 1850 <--> 3150 mV normal standby
    regulator: VDAC: 1800 mV normal standby
    regulator: VPLL2: 1800 mV normal standby
    regulator: VMMC2: 2800 <--> 3150 mV normal standby
    regulator: VSIM: 1800 <--> 3000 mV normal standby
    i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
    i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
    msgmni has been set to 29
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Switched to NOHz mode on CPU #0
    serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
    serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
    serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
    console [ttyS2] enabled
    i2c /dev entries driver
    mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
    mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
    ThumbEE CPU extension supported.
    Disabling unused clock "sr2_fck"
    Disabling unused clock "sr1_fck"
    Disabling unused clock "mcbsp_fck"
    Disabling unused clock "mcbsp_fck"
    Disabling unused clock "mcbsp_fck"
    Disabling unused clock "mcbsp_ick"
    Disabling unused clock "mcbsp_ick"
    Disabling unused clock "mcbsp_ick"
    Disabling unused clock "gpt2_ick"
    Disabling unused clock "gpt3_ick"
    Disabling unused clock "gpt4_ick"
    Disabling unused clock "gpt5_ick"
    Disabling unused clock "gpt6_ick"
    Disabling unused clock "gpt7_ick"
    Disabling unused clock "gpt8_ick"
    Disabling unused clock "gpt9_ick"
    Disabling unused clock "wdt3_ick"
    Disabling unused clock "wdt3_fck"
    Disabling unused clock "gpio2_dbck"
    Disabling unused clock "gpio3_dbck"
    Disabling unused clock "gpio4_dbck"
    Disabling unused clock "gpio5_dbck"
    Disabling unused clock "gpio6_dbck"
    Disabling unused clock "gpt9_fck"
    Disabling unused clock "gpt8_fck"
    Disabling unused clock "gpt7_fck"
    Disabling unused clock "gpt6_fck"
    Disabling unused clock "gpt5_fck"
    Disabling unused clock "gpt4_fck"
    Disabling unused clock "gpt3_fck"
    Disabling unused clock "gpt2_fck"
    Disabling unused clock "gpt1_ick"
    Disabling unused clock "wdt1_ick"
    Disabling unused clock "wdt2_ick"
    Disabling unused clock "wdt2_fck"
    Disabling unused clock "gpio1_dbck"
    Disabling unused clock "gpt1_fck"
    Disabling unused clock "cam_ick"
    Disabling unused clock "cam_mclk"
    Disabling unused clock "dss_ick"
    Disabling unused clock "dss_96m_fck"
    Disabling unused clock "dss1_alwon_fck"
    Disabling unused clock "des1_ick"
    Disabling unused clock "sha11_ick"
    Disabling unused clock "rng_ick"
    Disabling unused clock "aes1_ick"
    Disabling unused clock "ssi_ick"
    Disabling unused clock "mailboxes_ick"
    Disabling unused clock "mcbsp_ick"
    Disabling unused clock "mcbsp_ick"
    Disabling unused clock "gpt10_ick"
    Disabling unused clock "gpt11_ick"
    Disabling unused clock "mcspi_ick"
    Disabling unused clock "mcspi_ick"
    Disabling unused clock "mcspi_ick"
    Disabling unused clock "mcspi_ick"
    Disabling unused clock "hdq_ick"
    Disabling unused clock "mspro_ick"
    Disabling unused clock "des2_ick"
    Disabling unused clock "sha12_ick"
    Disabling unused clock "aes2_ick"
    Disabling unused clock "icr_ick"
    Disabling unused clock "pka_ick"
    Disabling unused clock "hsotgusb_ick"
    Disabling unused clock "ssi_ssr_fck"
    Disabling unused clock "hdq_fck"
    Disabling unused clock "mcspi_fck"
    Disabling unused clock "mcspi_fck"
    Disabling unused clock "mcspi_fck"
    Disabling unused clock "mcspi_fck"
    Disabling unused clock "mcbsp_fck"
    Disabling unused clock "mcbsp_fck"
    Disabling unused clock "mspro_fck"
    Disabling unused clock "gpt11_fck"
    Disabling unused clock "gpt10_fck"
    Disabling unused clock "iva2_ck"
    Disabling unused clock "dpll4_m6x2_ck"
    Disabling unused clock "dpll4_m3x2_ck"
    Disabling unused clock "dpll3_m3x2_ck"
    Disabling unused clock "sys_clkout1"
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
    Waiting for root device /dev/mmcblk0p2...
    mmc0: new high speed SDHC card at address 0007
    mmcblk0: mmc0:0007 SD4GB 3.70 GiB
    mmcblk0: p1 p2
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    VFS: Mounted root (ext2 filesystem) on device 179:2.
    Freeing init memory: 60K
    beagle#

    also i type the command free on  the shell   

    it shows    the mem is total 16M

    but if i use the x-loader to load u-boot and then run the u-boot to load the kernel ,the log is 

    Memory: 128MB 128MB = 256MB total, is something wrong with the boot environment?

  • Hi Ye Cai,

    Probably you are skipping some initializations in the u-boot. I find something ambiguous in your booting sequence. The right booting sequence is "x-loader, u-boot and kernel". If the memory size is correct when using this sequence there is no problem. If my understanding is not right explain more detailed your booting steps and environment please.

    BR

    Tsvetolin Shulev