Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

uboot env:

U-Boot > printenv
flashuboot=tftp 0xc0700000 mityomap/u-boot-ubl.bin; sf probe 0; sf erase 0x10000 0x80000; sf write 0xc0700000 0x10000 ${filesize}
flashkernel=tftp 0xc0700000 mityomap/uImage; sf probe 0; sf erase 0x100000 0x280000; sf write 0xc0700000 0x100000 ${filesize}
flashubl=tftp 0xc0700000 mityomap/UBL_SPI_MEM.ais; sf probe 0; sf erase 0 0x10000; sf write 0xc0700000 0 0x10000
flashrootfs=tftp 0xc2000000 mityomap/mityomap-base-mityomapl138.jffs2; nand erase 0 0x08000000; nand write.jffs2 0xc2000000 0 ${filesize}
mtdids=nand0=nand
mtdparts=mtdparts=nand:128M(rootfs),-(userfs)
bootargsbase=mem=96M console=ttyS1,115200n8
flashargs=setenv bootargs ${bootargsbase} ${mtdparts} root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
bootdelay=4
baudrate=115200
oldbootargs=mem=96M console=ttyS1,115200n8 mtdparts=nand:128M(rootfs),-(userfs) root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
bootargs=console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=64M@0xc4000000 root=/dev/nfs nfsroot=192.168.0.112:/home/mitydsp/targetfs,nolock ip=dhcp
autoload=no
oldserverip=10.0.0.23
serverip=192.168.0.112
bootfile=uImage-da850-omapl138-evm.bin
oldbootcmd=sf probe 0; sf read 0xc0700000 0x100000 0x280000; bootm 0xc0700000
bootcmd=dhcp;setenv serverip 192.168.0.112;tftpboot;bootm
ipaddr=192.168.0.135
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:50:c2:fc:69:5a
ver=U-Boot 2009.11 (Mar 31 2011 - 19:39:18)

Environment size: 1393/65532 bytes

I have build the kernel with codes in git://support.criticallink.com/home/git/linux-davinci.git

No more output is seen on the console after "booting the kernel"

refer to this article: http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux

re-building the kernel with CONFIG_DEBUG_LL enabled, still no more output.

Derek,

I'm unclear with what you changed between when it was last working and now.

-Jonathan

Hi Jonathan,

Thank you for your reply

I'm using the Industrial IO Development Kit with MityDSP-L138F. No change was made before running setup.sh in DVSDK 4.03.

Is the DVSDK 4.03 suitable to the kit?

Hi Derek,

The kernel that comes with the DVSDK (uImage-da850-omapl138-evm.bin) will not work with the MityDSP-L138 and Industrial I/O board, it is setup to work with the OMAP-L138 EVM kit from TI. You should be able to replace that with the uImage provided with the MDK and get past your current boot. You also need to specific the correct console port. The MityDSP-L138 console port must be ttyS1. The EVM uses ttyS2. You need to use the correct console in the bootargs parameter (see the "oldbootargs" you made, the consoles are not the same).

-Mike

Derek,

Where you aware of this wiki page?
http://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Dv_sdk_notes

It may help getting the dv sdk working with our kernel.

-Jonathan

Hi Mike & Jonathan,

Really appreciate your help!

The kit could load the kernel now.

-Derek