Hi,
I am now using EVM8168 (RevG). Now I managed to migrate to DVRRDK4.0. After checking some info, I flashed the uboot_NAND_DM816X_UD_DVR to the NAND via u-boot in EZSDK5.05.
After setting the switch2 to (CS0WAIT) 00100_10010 (BTM0) and sw3 to (SPI)01(NAND), I reboot the system. The terminal cases some info as it has been booted successfully.
.......
WR_DATA_RATIO_BYTE_LANE0: 0x000000AE
WR_DATA_RATIO_BYTE_LANE1: 0x000000C4
WR_DATA_RATIO_BYTE_LANE2: 0x000000D4
WR_DATA_RATIO_BYTE_LANE3: 0x000000E6
I2C: ready
DRAM: 2 GiB
NAND: HW ECC BCH8 Selected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
NAND bus width 8 instead 16 bit
No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC or NAND, using default environment
Net: Ethernet PHY: GENERIC @ 0x01
DaVinci EMAC
Hit any key to stop autoboot: 0
UBOOT #
I didn't take care to the "No NAND device found!!!" -- actually, the u-boot was indeed read and run from the NAND -- How could be any errors in the NAND?
However, when I tried to set the bootarg and using the 'saveenv' cmd, the U-boot hangs:
UBOOT # saveenv
Saving Environment to NAND...
Erasing Nand...
Warning: Erase size 0x00002000 smaller than one erase block 0x00020000
Erasing 0x00020000 instead
===========[UBOOT hangs ]==============
Besides, nothing was showed when I using "nand info" cmd.
UBOOT # nand info
UBOOT #
Also, "nand erase" refuses to work:
UBOOT # nand erase 0x0 0x260000
no devices available
UBOOT #
I have no idea with this issue. Could you give me a hand? Since the NAND runs perfectly in EZSDK5.05, I don't regard this issue as an indication of Hardware Error.
Naroah
Sep/12/2013
