OMAP-L137 starter kit

Chakra said:

Does the Starter kit work in standalone mode?

It will, but early boards will not have any U-Boot loaded into flash, so it may not out of the box.

Chakra said:

Is there any simple method to check the system startup time.

For a rough measurement you could just use a stopwatch, however for more specific timing information there are better ways, for example there is a Printk-times patch that you can add to the kernel that will make it print a time value every time the kernel prints something, this allows you to see exactly what is happening when during the boot and to see what parts of the boot may be taking too long so that you may be able to optimize them.

Chakra said:

I am bit confused with the user guide ,is there any simple procedure  to check the Starter kit.

For looking into the Linux boot time you would need to go through the procedures to flash U-Boot into the SPI flash of the EVM as discussed in section 4.1 of the OMAP-L137 PSP User's Guide.

Chakra said:

I would like know the difference between LINUX and ITRON with respect to  the speed and performance.(which would you prefer?).

 I am not very familiar with ITRON so it would be hard for me to say, I would probably prefer Linux due to my familiarity with it and that all the software collateral TI provides is written for it, using a third party OS would mean a great deal more software development work, as well as being more 'on your own' for supporting the software.

Hi,

．Does the Starter kit work in standalone mode?

No, so to burn U-boot on FLASH, do section 4.1 (page) of the getting started guide (document SPRUGI8) - this document comes with the software package that can be downloaded according to:

https://community.ti.com/forums/p/2094/8075.aspx#8075

Thankyou for the information,

According to the manual I loaded the U-boot into the spi-flash,
and while downloading the kernel the "dhcp" command didn't work,
so I set the IP address of EVM manually and succesfully downloaded
the kernel using tftp,
finally if I boot the kernel,the kernel is hanging in an endless loop
saying
"Sending DHCP and RARP requests ...... timed out!"
IP-Config: Reopening network devices...

Please let me know if you have any suggestion

Regards.

U-Boot 1.3.3 (Jan 22 2009 - 22:15:37)

I2C:   ready
DRAM:  64 MB
In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
More than one PHY detected.
Hit any key to stop autoboot:  3  2  1  0
4096 KiB W25X32 at 0:0 is now current device
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-2.6.18_pro500
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1982924 Bytes =  1.9 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................................... done, booting the kernel.
Linux version 2.6.18_pro500 (x0029463@aspbuild11) (gcc version 4.2.0 20070126 (prerelease) (MontaVista 4.2.0-3.0.0.0702771 2007-03-10)) #1 PREEMPT Fri Nov 14 15:15:33 IST 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: DaVinci DA8XX EVM
Memory policy: ECC disabled, Data cache writethrough
DaVinci DA0800 variant 0x0
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 8192
Kernel command line: mem=32M console=ttyS2,115200n8 root=/dev/ram0 rw initrd=0xc1180000,4M ip=192.168.1.11[A[C[C[C[C[C[C[C[C[C[C[C[C[C[C[D[C1[B
PID hash table entries: 256 (order: 8, 1024 bytes)
Clock event device timer0_0 configured with caps set: 03
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 24080KB available (3437K code, 646K data, 156K init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 4096K
NET: Registered protocol family 16
DaVinci: 128 gpio irqs
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.1 (2006/08/19) Phillip Lougher
NTFS driver 2.1.27 [Flags: R/W].
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
yaffs Nov 14 2008 15:13:15 Installing.
JFS: nTxBlock = 220, nTxLock = 1762
SGI XFS with no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
LTT : ltt-facilities init
LTT : ltt-facility-core init in kernel
DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO map 0x1c42000 mem 0xfec42000 (irq = 25) is a 16550A
serial8250.0: ttyS1 at MMIO map 0x1c20400 mem 0xfed0c000 (irq = 53) is a 16550A
serial8250.0: ttyS2 at MMIO map 0x1d0d000 mem 0xfed0d000 (irq = 61) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
netconsole: not configured, aborting
Davinci EMAC MII Bus: probed
MAC address is 00:0e:99:02:f1:b6
TI DaVinci EMAC Linux version updated 4.0
i2c /dev entries driver
physmap platform flash device: 01000000 at 60000000
physmap-flash physmap-flash.0: map_probe failed
nand_davinci nand_davinci.0: Using 4-bit hardware ECC
No NAND device found!!!
nand_davinci nand_davinci.0: no nand device detected
Creating 3 MTD partitions on "Windbond spi nand flash":
0x00000000-0x00020000 : "U-Boot"
0x00020000-0x00024000 : "U-Boot Environment"
0x00024000-0x00400000 : "Linux"
dm_spi.0: davinci SPI Controller driver at 0xfec41000 (irq = 20) use_dma=1
dm_spi.1: davinci SPI Controller driver at 0xfee12000 (irq = 56) use_dma=1
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
ohci ohci.0: irq 59, io mem 0x01e25000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver libusual
musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
Waiting for PHY clock good...
musb_hdrc: USB Host mode controller at c28a0000 using DMA, IRQ 58
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
rtc-da8xx rtc-da8xx.0: rtc intf: proc
rtc-da8xx rtc-da8xx.0: rtc intf: dev (254:0)
rtc-da8xx rtc-da8xx.0: rtc core: registered rtc-da8xx as rtc0
rtc-da8xx rtc-da8xx.0: TI DA8xx Real Time Clock driver.
IPv4 over IPv4 tunneling driver
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc-da8xx rtc-da8xx.0: setting the system clock to 2000-01-01 05:09:12 (946703352)
Time: timer0_1 clocksource has been installed.
Clock event device timer0_0 configured with caps set: 08
Switched to high resolution mode on CPU 0
Sending DHCP and RARP requests ....