> > In any case I would assume that after 0x60000 (i.e. 384k) no data would > > be present, and by erasing it nothing would happen. But By erasing it > > u-boot stops working. > > > > The commands I give are: > > > > nand erase 0x00060000 0x00400000 > > nand write 0x80700000 0x00060000 0x00400000 > > reset > > > > Do you want to update u-boot from u-boot? I never tried that, I thought ubl > obb layout and u-boot layout are not compatiple. i have the same problem when i run "nand erase 0xa0000" on DM6467 and then uboot cannot work.
On 29 January 2010 16:41, Ottavio Campana <[email protected]>wrote: > On Tue, Jan 26, 2010 at 09:42:43AM +0200, Caglar Akyuz wrote: > > On Monday 25 January 2010 06:49:23 pm Ottavio Campana wrote: > > > I'm trying to put u-boot on a custom board based on dm6446 in a > NAND > > > memory. > > > > > > I find some mismatches between the montavista linux kernel and > u-boot > > > 2009.11 . > > > > > > > Are they using the same ecc/oob layout? In the past(2.6.10 era), it is > known > > that u-boot montavista linux kernel do not use the same layout. Does > > montavista linux kernel suppose to work with u-boot 2009.11? > > mmm.. I don't know. By the way, I find a solution, I discovered that > u-boot 2009.11 and bootargs "live" in the first MB of the nand, thus as a > workaround I consider my nand divided into three parts: 1m of bootloader, > 4m for > the kernel and the rest for the rootfs. > > But I still dont' know where u-boot puts its stuf... > > > > Particularly, in > linux-2.6.18_pro500/arch/arm/mach-davinci/board-evm.c > > > the variable davinci_nand_partitions has 4 elements bootloader of > 265KB, > > > params 128K, kernel 4M and filesystem the rest of the memory. > > > > > > But u-boot 2009.11 has a different partitions layout specified > by > > > mtdparts=davinci_nand.0:384k(bootloader)ro,4m(kernel),-(filesystem) > > > > > > > Correct me if I'm wrong but this is a kernel command line parameter. It > has > > nothing to do with u-boot partitions. does u-boot even support nand > > partitions? By looking at the documentation at [1] I see it is just an > > interface to use dynamic partitioning feature of Linux. > > well, mtdparts seems to be hardcoded in the kernel. By passing the variable > nothing changes. > > > > In any case I would assume that after 0x60000 (i.e. 384k) no data > would > > > be present, and by erasing it nothing would happen. But By erasing > it > > > u-boot stops working. > > > > > > The commands I give are: > > > > > > nand erase 0x00060000 0x00400000 > > > nand write 0x80700000 0x00060000 0x00400000 > > > reset > > > > > > > Do you want to update u-boot from u-boot? I never tried that, I thought > ubl > > obb layout and u-boot layout are not compatiple. > > no, just putting kernel and rootfs on the nand. > > In any case, it somehow works, I just would like now to understand what > u-boot > 2009.11 really does. > > Ottavio > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source >
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
