Hello all,
We were trying the procedure for NAND booting as mentined in spraao.pdf and
all the settings are exactly as mentioned. But we were not able to erase the
flash and rewrite it.If we say 'NO' to erase it, it would function properly
without any problem.
While debugging we found that, we are using the DaVinci chip
TMX320DM6446BZWT chip. Online help indicated us that we have the Silicon
version 1.3 and also that u need to use a perticular uboot for the perticular
silicon version..Failing to do so.. may result in the EVM becoming non
responsive.(reference u-boot-upgrade.html).
We currently are using uboot
version 1.1.3(obtained from terminal window).
Is this the correct version for our chip??? How to find out which uboot
version is suitable for which silicon version??
Thanks for the help in advance.
regards,
-Ketan
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/Title: U-Boot Upgrade
| |
Upgrading u-boot
These instructions are only to upgrade an existing u-boot and can only be done on boards that already have u-boot installed. The default u-boot installed on the DVEVM will work on all board configurations. The newer boards can accept the faster u-boot provided on the DVEVM CD. The following board configurations will work with the new faster u-boot.
If these instructions are not followed exactly or the upgrade fails for any reason, the board may have to be sent in for repair.
Revision Identification
The device revision can be determined by the device revision code marked on the top of the package. The location of the device revision code for the ZWT package is shown in Figure 1. Figure 1 shows an example of the types of DM6446 package symbolization.
Figure 1.
NOTES:
- Qualified devices are marked with the letters “TMS” at the beginning of the device name, while nonqualified devices are marked with the letters “TMX” or “TMP” at the beginning of the device name.
- “#” denotes an alphanumeric character. “x” denotes an alpha character only.
Figure 1. Example, Device Revision Codes for TMX320DM6446 (ZWT)
Silicon revision is identified by a code on the chip. If x is “blank”, then the silicon is revision 1.1; if x is “A”, then the silicon is revision 1.2, etc. Table 1 lists the silicon revisions associated with each device revision code for the DM6446 device.
Table 1. Device Revision Codes
| Device Revision Code (x) | Silicon Revision | Comments |
| A | 1.2 | TMX320DM6446AZWT |
| (blank) | 1.1 | TMX320DM6446ZWT |
u-boot Application Table
Full Speed DDR 162 MHz ARM 297 MHz
| NAND U-Boot | Alpha | Beta | Gamma | Delta |
| 1.3 Silicon | NA | NA | X | NA |
| 1.2 Silicon | NA | NA | X | OK |
| NOR U-boot | Alpha | Beta | Gamma | Delta |
| 1.3 Silicon | NA | NA | OK | NA |
| 1.2 Silicon | NA | NA | OK | OK |
After determining the board type, copy the u-boot binary from the
DVEVM CD onto a known
directory serviced by a tftp server. Please see DVEVM Getting
Started Guide (sprue66a.pdf) for instructions on mounting the DVEVM
CD. . The location of the upgraded u-boot is in the
"u-boot-upgrade" sub-directory of the DVEVM CD.
Either assign an ipaddr or run dhcp to assign the board an IP address.
DaVinci EVM # dhcp
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 44
*** Unhandled DHCP Option in OFFER/ACK: 46
*** Unhandled DHCP Option in OFFER/ACK: 44
*** Unhandled DHCP Option in OFFER/ACK: 46
DHCP client bound to address 146.252.161.186
TFTP from server 146.252.160.71; our IP address is 146.252.161.186
Filename 'library/davinci/0.4.2/uImage'.
Load address: 0x80700000
Loading: #################################################################
#################################################################
#################################################################
##############################
done
Bytes transferred = 1148596 (1186b4 hex)
Change the boot file from uImage the u-boot version to tftp.
DaVinci EVM # setenv bootfile <path-to-u-boot-on-tftp-server>/u-boot.bin
DaVinci EVM # tftp
TFTP from server 146.252.160.71; our IP address is 146.252.161.186
Filename 'library/davinci/0.4.2/u-boot.bin'.
Load address: 0x80700000
Loading: ###################
done
Bytes transferred = 94616 (17198 hex)
Unprotect the 1st 2 sectors of flash. Please note the filesize environment variable will now have the u-boot size no longer the uImage size (remember to change bootfile at the end).
DaVinci EVM # protect off 0x02000000 +0x$(filesize)
Un-Protected 2 sectors
Erase the flash area where the new u-boot will go.
DaVinci EVM # erase 0x02000000 +0x$(filesize)
Erasing sector 0 ... done.
Erasing sector 1 ... done.
Erase Operation Completed.
Erased 2 sectors
Copy the new u-boot. Note that tftp placed it in the same location as uImage and copy it to location 0x02000000.
DaVinci EVM # cp.b 0x80700000 0x02000000 0x$(filesize)
Copy to Flash.../done
Protect the u-boot flash area and run flinfo. If you try to run iminfo 0x02000000 you will get a "Bad Magic Number" because this is not a uImage file.
DaVinci EVM # protect on 0x02000000 +0x$(filesize)
DaVinci EVM # flinfo
Bank # 1: MY AMD 29LV256M (256 Mbit)
Size: 16 MB in 256 Sectors
Sector Start Addresses:
02000000 02010000 02020000 E 02030000 E 02040000 (RO)
02050000 02060000 02070000 02080000 02090000
020A0000 020B0000 020C0000 020D0000 020E0000
020F0000 02100000 02110000 02120000 02130000
02140000 02150000 02160000 02170000 02180000
02190000 021A0000 021B0000 021C0000 021D0000
021E0000 021F0000 02200000 02210000 02220000
02230000 02240000 02250000 02260000 02270000
02280000 02290000 022A0000 022B0000 022C0000
Remember to change the bootfile back to uImage and power cycle the
board, and the new u-boot prompt should show up.
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
