On 05/24/2010 11:02 AM, Kieran Bingham wrote:
Hi Guys,
Thanks - and yes I'm prepared to use CCS if necesarry - but UBoot
upgrades will be much easier from a running system :)
I'm on the DM365, but I can't determine the load address...
My nand mappings are :
[ 2.250000] Creating 4 MTD partitions on "nand_davinci.0":
[ 2.260000] 0x00000000-0x00660000 : "bootloader"
[ 2.270000] 0x00660000-0x00680000 : "params"
[ 2.270000] 0x00680000-0x00a80000 : "kernel"
[ 2.280000] 0x00a80000-0x20000000 : "filesystem"
And I've tried poking around the nand to look at where I might find
the UBoot source - but can't "find" it manually.
setenv a 0x80000
nand read.i 0x80700000 $(a) 0x1000; md 0x80700000
80700000: a1aced00 00000100 00000007 00000004 ................
80700010: 00000001 00000020 ffffffff ffffffff .... ...........
80700020: ffffffff ffffffff ffffffff ffffffff ................
80700030: ffffffff ffffffff ffffffff ffffffff ................
80700040: ffffffff ffffffff ffffffff ffffffff ................
80700050: ffffffff ffffffff ffffffff ffffffff ................
Anyone got any clues as the correct address?
Regards
--
Kieran
Liu, Yan wrote:
I don't know which product you are using. But, there is a way to
write uboot from uboot. Here is the sample command:
tftp 0x80000000 u-boot.bin
nand erase <starting_address_uboot_partition> 0x1C0000
nandecc sw
nand write.i 0x80000000 <starting_address_uboot_partition> 0x1C0000
The <starting_address_uboot_partition> can be found in booting log.
Typically, you will find the following part:
0x000000000000-0x000000080000 : "xloader-nand"
0x000000080000-0x000000240000 : "uboot-nand"
0x000000240000-0x000000280000 : "params-nand"
0x000000280000-0x000000780000 : "linux-nand"
0x000000780000-0x000020000000 : "jffs2-nand"
In my case, I use 0x80000 as <starting_address_uboot_partition>.
Hope this helps.
Regards,
Yan
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On
Behalf Of Kieran Bingham
Sent: Friday, May 21, 2010 1:03 PM
To: [email protected]
Subject: Flashing uboot from Uboot
Hi Guys,
As I'm running linux, I can't easily switch to running Windows for CCS.
I've been making changes to UBoot and testing them by setting the
TEXT_BASE at a different address in RAM, loading via TFTP, and
calling go $(loadaddr)
Now I would like to write this uboot binary to flash, so I've
recompiled it with the original TEXT_BASE, but I can't figure out
where I need to flash it in the NAND.
Is it possible to reflash uboot from within Uboot?
--
Regards
Kieran
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Kieran,
In the UBL source, I have bootloader.h which defines
APP_DESC_START_BLOCK_NUM to be 8. Block 8 of my NAND is supposed to
have the start of U-boot. Check your UBL source and you should be able
to find the starting block. Use U-boot's nand dump to view the nand
without copying to RAM. According to UBL, the data stored should
contain the APP_BOOT structure. You can examine it to make sure this is
correct.
To be honest, I haven't done this in a long time, I generally have setup
SD card booting or USB booting for reflashing boards.
My comment about CCS loading was only for emergency loading. It is not
desirable but sometimes necessary.
Steve
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
