Ivan brings up a good point. The host app and target app (the UBL) make certain assumptions about the memory map. These are issues that need to be addressed in a future release, but you need to remember that application was originally only intended for EVM usage, particularly for customers who weren't using CCS, or who were only on a Linux box. Since the source of both the host app and the target app are available, the necessary changes can be made.
But having said that it, it might be another issue. Try modifying the UBL program to report back some status on ECC values or the data seen in the verification step (NAND_VerifyPage function). Regards, Daniel Daniel J. Allred Software Applications Catalog DSP / Emerging End Equipment ________________________________ From: Ivan Tonchev [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 9:55 AM To: ketan deshpande Cc: Allred, Daniel; Linux DaVinci; Subashini Ravindran Subject: Re: UBL on custom board How much RAM do you have on your board? Is it < 256M? ketan deshpande wrote: Hi, We are trying the DVFlasher_1_12 with the custom designed board with NAND Flash. The NAND flash chip we are using is a big block device.When we try to flash the UBL we get the following messages. Attempting to connect to device COM1... Press any key to end this program at any time. Waiting for DVEVM... BOOTME commmand received. Returning ACK and header... ACK command sent. Waiting for BEGIN command... DVEVM: BEGIN BEGIN commmand received. Sending CRC table... CRC table sent. Waiting for DONE... DONE received. Sending the UART UBL file... DONE received. UART UBL file was accepted. UART UBL Transmitted successfully. DVEVM: TI UBL Version: 1.11, Flash type: NAND DVEVM: Booting PSP Boot Loader DVEVM: PSPBootMode = NAND WARNING! The DM644x is NOT in UART boot mode! Only continue if you are sure of what you are doing. Continue (Y/N) ? y Waiting for UBL on DVEVM... UBL's BOOTPSP commmand received. Returning CMD and command... CMD value sent. SENDUBL received. Returning ACK and header for UBL data... ACK command sent. Waiting for BEGIN command... UART UBL's BEGIN commmand received. Sending the Flash UBL code... Flash UBL code sent. Waiting for DONE... DONE received. All bytes of Flash UBL code received... DONE received. Flash UBL S-record decoded correctly. DVEVM: Initializing NAND flash... DVEVM: Correct devID found DVEVM: Writing UBL to NAND flash DVEVM: Number of blocks needed for header and data: 0x00000001 DVEVM: Attempting to start in block number 0x00000001. DVEVM: Unprotecting blocks 0x00000001 through 0x00000001. DVEVM: Erasing blocks 0x00000001 through 0x00000001. DVEVM: Writing header... DVEVM: NAND ECC failure! DVEVM: Starting UART Boot... DVEVM: BOOTPSP Waiting for UBL on DVEVM... UBL's BOOTPSP commmand received. Returning CMD and command... CMD value sent. SENDUBL received. Returning ACK and header for UBL data... ACK command sent. Waiting for BEGIN command... UART UBL's BEGIN commmand received. Sending the Flash UBL code... The above mentioned sequence keeps on repeating. What could be the problem?? regards, -Ketan ________________________________ SHOUT IT OUT! Tell everyone, from anywhere, that you're online on Yahoo! Messenger <http://us.rd.yahoo.com/mail/in/ymessenger/*http:/messenger.yahoo.com/ad dpresence.php> ________________________________ _______________________________________________ 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
