On Fri, Mar 13, 2009 at 9:28 AM, Yusuf Caglar AKYUZ <[email protected]>wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Marcelo Guedes Silva wrote: > > I´m still with this problem. I follow three documents step-by-step, all > of > > them said similar things, but the final uImage file has some problem. > > One of this document is the quickstart in: > > > /opt/mv_pro_4.0.1/montavista/pro/documentation/docs/quickstart/cross-development/html > > > > I guess getting started guide is also mentionioning how to compile a > new kernel as welll. > > > Basically I copied the kernel source from > > > /opt/mv_pro_4.0.1/montavista/pro/devkit/lsp/ti-davinci_evm-arm_v5t_le/linux-2.6.10_mvl401 > > to a temp directory: /tmp/mykernel. > > How did you copy? In order to preserve sym links you have to copy > with "cp -aR" or better, create an archive and copy that. > I used "cp -R", but I suppose that kernel shouldn´t compile with this kind of problem. By the way, I going to follow your instruction. > > > There, I compiled the kernel with: "make menuconfig" and after "make > > uImage". > > > > Did you check if target system is DaVinci? I mean your tree maybe > distclean'ed, or not configured before. If you're unsure use a > defconfig and then make your changes on it. I don't remember MV > defconfig name but you can find with: > > make help | grep -i davinci > > or > > make help | grep -i dm644 > > Then use that defconfig with: > > make xxx_defconfig > make menuconfig > make uImage > I just done it. Same problem. One point that I forgot to mention is that I´m using *dm6467*, not dm6446 and don´t exist a davinci_dm646x_defconfig, only davinci_dm644x_defconfig. Did you sometime compile it to dm6467? I´m using the files from the DVSDK CDs (SPRC592A and SPRC597C). Now I´m suspecting that it´s old and doesn´t support dm646x EVM (I guess now that they put only a compiled version in the right way, but the source files are old). I saw that a linux version exists in http://wiki.davincidsp.com/index.php?title=Linux_Toolchain with a lot of patches to dm6467. I will try to use it. I´m downloading it now. > > > The uImage was copied to /tftpboot directory, that I configured properly > to > > work with tftp. The transfer happened right too. > > > > U-boot # tftp uImage 0x80400000 > > U-boot # bootm 0x80400000 > > > > And now I see the diamonds. You can see that the kernel started (the jpg > > picture), but for some reason, stopped without any warning. I tested with > > parameters to boot from /dev/ram *and* from /dev/nfs with: > > > > setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=10.0.0.100 > > root=/dev/nfs nfsroot=10.0.0.20:*<filesys path>*,nolock mem=120M > > davincihd_capture.channel0_numbuffers=4 > > > > Whatever your paramters other than "console" you should see smt > meaningful. > > > Both gets the same problem. > > > > Ideas? > > > > Maybe you should start from scratch. I mean take fresh tar.gz > source, copy it, extract it, build it with defconfig, boot it, if > succeeds menuconfig it, re-build, boot it, if fails look into > changes you made and so on... > > I can nothing else at the moment, I guess you have a very very > non-standard behavior which hints me that you're doing smt unusual. > > BTW, are you compiling your kernel on Windows? if not(and you > shouldn't be able to) you may use minicom given that you're not on a VM. No, I´m using CentoOS 5 in a Virtual Machine to compile. But I prefer the HyperTerminal console, just it. And it´s working fine with the pre-build kernels. > > > Regards, > Caglar > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org > > iEYEARECAAYFAkm6UYMACgkQ/nL+S5dojeieBQCeOvFzvu5nSeXUChq1ILAHHUAC > Q8AAnjLR0DdcE2vofume4ygOSOn4pvNr > =ZLwU > -----END PGP SIGNATURE----- > Thanks. Regards, Guedes
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
