http://linux.omap.com/pipermail/linux-omap-open-source/2008-August/012794.htmlOMAP 3430 from scratchkapil kumar kapil.ricky at gmail.comWed Aug 6 09:04:25 CDT 2008
Hello everybody, I just started to work on OMAP 3430 it with porting of LINUX 2.6 on a new board. thats how i proceed.. 1.I have dowonload the following for OMAP3430 from this source ( http://focus.ti.com/general/docs/wtbu/wtbusplashcontent.tsp?templateId=6123&contentId=4750) 2.6_kernel-v1.tar.gz u-boot-v1.0b.tar.gz x-load-v1.tar.gz and these also: rootfs.tar.tar rootfsosk.tar.tar rd-jffs2.bin rd-ext2.bin and then compiled using ARM TOOL chain to generate x-load.bin u-boot.bin vmlinux,zImage and uImage. 2.I flashed the u-boot.bin into starting address of NOR which is 0x10000000 and i made the dip switches settings to boot it from NOR which i can see in minicom OMAP34XX SDP # print bootargs=root=/dev/ram0 rw mem=64M console=ttyS0,115200n8 initrd=0x80600000,8M ramdisk_size=8192 bootdelay=3 baudrate=115200 netmask=255.255.254.0 bootfile="uImage" ipaddr=192.168.0.2 serverip=192.168.0.1 stdin=serial stdout=serial stderr=serial Environment size: 246/131068 bytes 3.For kernel i used tftpboot. Here are some of the commands. tftpboot 0x80000000 uImage When i gave bootm 0x80000000 kernel starts booting fine but in the end it gave error regarding filesystem RAMDISK: Couldn't find valid RAM disk image starting at 0. List of all partitions: 1f00 256 mtdblock0 (driver?) 1f01 256 mtdblock1 (driver?) 1f02 2048 mtdblock2 (driver?) 1f03 128512 mtdblock3 (driver?) 1f04 512 mtdblock4 (driver?) 1f05 512 mtdblock5 (driver?) 1f06 256 mtdblock6 (driver?) 1f07 4096 mtdblock7 (driver?) 1f08 125696 mtdblock8 (driver?) 1f09 512 mtdblock9 (driver?) 1f0a 256 mtdblock10 (driver?) 1f0b 128 mtdblock11 (driver?) 1f0c 2048 mtdblock12 (driver?) 1f0d 259200 mtdblock13 (driver?) No filesystem could mount root, tried: ext3 ext2 msdos vfat As no filesystem is there. 4.Then i tried to chechk with NFS booting i changed /etc/exports file with this entry: and then i restart it /usr/sbin/exportfs -ra I changed the bootargs to setenv rootpath /home/omap/workdir/rotfs2.6 setenv bootargs root=dev/nfs console=ttyS0,115200n8 noinitrd rw ip= 192.168.0.2 nfsroot=192.168.0.1:/home/omap/workdir/rootfs2.6,nolock mem=64M (This filessytem i got after unzipping the rootfsosk.tar.tar) so giving this command: bootm 0x80000000 It boots fine untill this problem comes PRCM:Voltage controllor address error. something like this This line keeps on displaying untill i press some key. But i am able to see my filesystem after a quite while. I dont have Camera attached to board,so does it cause this problem???? Please help me out. Now i want to clear my following doubts 1.NFS Booting:If i contibue with NFS booting what should be exact parameter??? why i am not able to proceed proprly ??? and i am not able to run my HELLO WORLD test prog its saying -sh ./hello.out :cannot found 2.Filesystem in Flash: If i try to boot from Flash what should i do?? (for omap3430sdp) i found some bin files in OMAP3430 BSP rd-ext2.bin rd-jffs2.bin I am guessing these for filesytem as name suggest. but how to make use of it. I searched in the web and mailing list also but didnt get satisfactory answer. Thanks Kapil Kumar |
