• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 386 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.

OMAPL138 kernel error

le lemon
Intellectual 280 points

Other Parts Discussed in Thread: OMAPL138

hi：

    There is an error when my board is running in 372MHz,but my omapl138 support 456Mhz.

when the error occurs ,the print  like this.what is wrong with my system?

thanks

  • 0
    TI__Mastermind 43955 points

    Hi le lemon,

    Would you please, send us the log of your boot parameters, boot commands used and the output messages while booting the kernel in the form of a text file, so that we can have a closer look to your problem?

     

    Regards,

    Shankari

  • 0 in reply to Shankari G
    Intellectual 280 points

    Hi , Shankari

        Thanks for your reply.

     boot parameters and boot commands:

    bootdelay=1
    baudrate=115200
    bootfile="uImage"
    ethaddr=00:32:32:32:32:32
    bootargs=mem=128m console=tty0 root=/dev/mtdblock0 ro rootfstype=yaffs2 quiet
    stdin=serial stdout=serial stderr=serial
    ver=U-Boot 2009.11 (Jul 07 2011 - 16:50:38) filesize=4B29E fileaddr=C0700000
    ipaddr=192.168.0.138 serverip=192.168.0.145
    bootcmd=sf probe 0 30000000; sf read 0xc1700000 0x380000 0x80000; sf read 0xc0700000 0x80000 0x200000; bootm
    ot 2009.11 (Jul 07 2011 - 16:50:38)


    output messages :in text file

    Fullscreen 4466.1.txt Download 
    Linux version 2.6.33-rc42.9 (root@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Sat Oct 12 13:10:44 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DA850/OMAP-L138/AM18xx EVM
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c03a0178, node_mem_map c0400000
  DMA zone: 256 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 32512 pages, LIFO batch:7
DaVinci da850/omap-l138 variant 0x0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: mem=128m console=tty0 root=/dev/mtdblock0 ro rootfstype=yaffs2 quiet
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125696KB available (3392K code, 531K data, 136K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
console [tty0] enabled
Calibrating delay loop... 185.54 BogoMIPS (lpj=927744)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 144 gpio irqs
regulator: core version 0.5
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
regulator: VDCDC1: 3200 <--> 3300 mV at 3300 mV 
regulator: VDCDC2: 1750 <--> 3300 mV at 3300 mV 
regulator: VDCDC3: 950 <--> 1375 mV at 1300 mV 
regulator: LDO1: 1800 mV 
regulator: LDO2: 1150 <--> 1300 mV at 1200 mV 
i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi4.1-dma, peripheral, debug=0
Waiting for USB PHY clock good...
DA830 OTG revision 4ea11003, PHY 24972, control 00
musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn)
musb_hdrc: MHDRC RTL version 1.800 
musb_hdrc: setup fifo_mode 2
musb_hdrc: 8/9 max ep, 3904/4096 memory
musb_hdrc: USB Peripheral mode controller at fee00000 using DMA, IRQ 58
Registered /proc/driver/musb_hdrc
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
EMAC: MII PHY configured, RMII PHY will not be functional
yaffs Oct 12 2013 13:09:37 Installing. 
msgmni has been set to 245
io scheduler noop registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found Sharp_LK043T1DG01 panel
Console: switching to colour frame buffer device 80x30
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a 16550A
serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a 16550A
serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a 16550A
console [ttyS2] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
nand_read_bbt: Bad block at 0x0000011a0000
nand_read_bbt: Bad block at 0x0000100e0000
nand_read_bbt: Bad block at 0x000010900000
Creating 4 MTD partitions on "davinci_nand.1":
0x000000000000-0x000004000000 : "rootfs"
0x000004000000-0x00000c000000 : "firmware"
0x00000c000000-0x000010000000 : "sys"
0x000010000000-0x000038000000 : "user"
davinci_nand davinci_nand.1: controller rev. 2.5
spi_davinci spi_davinci.1: DaVinci SPI driver in EDMA mode
Using RX channel = 18 , TX channel = 19 and event queue = 1
m25p80 spi1.0: non-JEDEC variant of m25p64
m25p80 spi1.0: m25p64 (8192 Kbytes)
Creating 4 MTD partitions on "m25p80":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000050000 : "U-Boot Environment"
0x000000050000-0x0000007f0000 : "Linux"
0x0000007f0000-0x000000800000 : "MAC Address"
Read MAC addr from EEPROM: ff:ff:ff:ff:ff:ff
spi_davinci spi_davinci.1: Controller at 0xfef0e000 
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
ohci ohci.0: irq 59, io mem 0x01e25000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for cp210x
usbcore: registered new interface driver cp210x
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
mice: PS/2 mouse device common for all mice
usbcore: registered new interface driver usbtouchscreen
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: RTC power up reset detected
omap_rtc: already running
omap_rtc: split power mode
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Clocks: disable unused emac
Clocks: disable unused mcasp
Clocks: disable unused spi0
Clocks: disable unused vpif
VFP support v0.3: not present
regulator_init_complete: incomplete constraints, leaving LDO2 on
regulator_init_complete: incomplete constraints, leaving LDO1 on
regulator_init_complete: incomplete constraints, leaving VDCDC3 on
regulator_init_complete: incomplete constraints, leaving VDCDC2 on
regulator_init_complete: incomplete constraints, leaving VDCDC1 on
davinci_emac_probe: using random MAC addr: 96:8b:40:5a:f7:dc
emac-mii: probed
omap_rtc omap_rtc: setting system clock to 2000-01-12 04:22:41 UTC (947650961)
yaffs: dev is 32505856 name is "mtdblock0"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.0, "mtdblock0"
block 142 is bad
usb 1-1: new low speed USB device using ohci and address 2
input: Logitech USB Keyboard as /devices/platform/ohci.0/usb1/1-1/1-1:1.0/input/input0
generic-usb 0003:046D:C31D.0001: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-ohci.0-1/input0
input: Logitech USB Keyboard as /devices/platform/ohci.0/usb1/1-1/1-1:1.1/input/input1
generic-usb 0003:046D:C31D.0002: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-ohci.0-1/input1
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs2 filesystem) readonly on device 31:0.
Freeing init memory: 136K
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs_read_super: isCheckpointed 0
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=1:00, id=7c0f1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
my_spi_dev create
yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
save exit: isCheckpointed 1
save exit: isCheckpointed 1




  • 0 in reply to le lemon
    TI__Mastermind 43955 points

    HI le Lemon,

    From the log file, it seems to me that your kernel is trying to mount the YAFFS/YAFFS2 file system from NAND Flash.

    Using a wrong YAFFS image may also lead to errors like this. For more information please refer to http://processors.wiki.ti.com/index.php/Put_YAFFS_Image_to_Flash

    Before booting kernel, are you able to successfully flash the rootfilesystem (YAFFS2 ) into NAND? Did you use  MTD Utilities for flashing?

     If you are not very particular about using filesystem at NAND flash, you can opt using nfs filesystem which is comparitively easy.

    http://processors.wiki.ti.com/index.php/Alternate_Boot_Methods_for_OMAP-L137/DA830#From_NFS

    http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot

    http://processors.wiki.ti.com/index.php/Getting_Started_Guide_for_OMAP-L1

     

    Regards,

    Shankari.

     

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • 0 in reply to Shankari G
    Intellectual 280 points

    Hi ,Shankari:

        We deed use the YAFFS/YAFFS2 file system on NAND Flash. The system mount file system only once when

    the system start up ,we didnot access the nand flash before the system breakdown.Is there another  problem ?


    Thanks

  • 0 in reply to le lemon
    TI__Mastermind 43955 points

    Hi le lemon,

    Please answer our question on our previous post to help you further.

    Are you able to partition the NAND successfully?

    Before booting kernel, are you able to successfully flash the rootfilesystem (YAFFS2 ) into NAND? Did you use  MTD Utilities for flashing?

    It seems to me that the system is not able to mount the YAFFS filesystem properly from NAND.

     

    Regards,

    Shankari

     

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • 0 in reply to Shankari G
    Intellectual 280 points

    Hi ,Shankari

    1)Are you able to partition the NAND successfully?

    Yes,I did .

    2)are you able to successfully flash the rootfilesystem (YAFFS2 ) into NAND?

    Yes Idid

    3) Did you use  MTD Utilities for flashing?

    No ,I didn't.

     

    Thanks