• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 360 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem flashing the NAND on a dm8168 custom board

Inigo Oyarbide
Intellectual 720 points

Hi all, 

I am fighting with a dm8168 based custom board, with DDR3 memory and the same NAND memory as in the EVM8168 board.

I can flash the NAND memory in the EVM kit, and when I boot, I runs OK.

When I want to do the same in the custom board, I am following all the steps described in the 

DM816x AM389x PSP Flashing Tools Guide.  Despite of, when I run the Script (NETRA External Memories -->doall after loading DM816x.gel from the EZSDK path ~/ti-ezsdk_dm816x-evm_5_05_02_00/board-support/host-tools ; in CCSv5.5 in Disassembly box appears the next:

???? Target failed to read 0x00000004 [code=0x1]
00000008: ???? Target failed to read 0x00000008 [code=0x1]
0000000c: ???? Target failed to read 0x0000000C [code=0x1]
00000010: ???? Target failed to read 0x00000010 [code=0x1]
00000014: ???? Target failed to read 0x00000014 [code=0x1]
00000018: ???? Target failed to read 0x00000018 [code=0x1]
0000001c: ???? Target failed to read 0x0000001C [code=0x1]
00000020: ???? Target failed to read 0x00000020 [code=0x1]
00000024: ???? Target failed to read 0x00000024 [code=0x1]
00000028: ???? Target failed to read 0x00000028 [code=0x1]
0000002c: ???? Target failed to read 0x0000002C [code=0x1]
00000030: ???? Target failed to read 0x00000030 [code=0x1]
00000034: ???? Target failed to read 0x00000034 [code=0x1]
00000038: ???? Target failed to read 0x00000038 [code=0x1]
0000003c: ???? Target failed to read 0x0000003C [code=0x1]
00000040: ???? Target failed to read 0x00000040 [code=0x1]
00000044: ???? Target failed to read 0x00000044 [code=0x1]
00000048: ???? Target failed to read 0x00000048 [code=0x1]
0000004c: ???? Target failed to read 0x0000004C [code=0x1]

So, when I load the nand-flash-writer.out, It stucks and nothing happens.

Why occurs this? I have also re-built the u-boot with the data obtained with the DDR3Init program, and change the files it says. 

If I use a different GEL file (one modified with data obtained with DDR3Init), I can load the nand-flash-writer.out and it will run?

I need to modify the DM816x.gel file to detect correctly the DDR3 memory and flashing the NAND?

Thank you, 

Best Regards, 

Inigo

  • 0
    Prodigy 110 points
    I am also see this on my board (customized)... TI guys please help us. DM816x_AM389x_PSP_Flashing_Tools_Guide.pdf => see page 4-5: Ensure that the image (e.g. u-boot.noxip.bin) to be flashed is present in the Windows XP Machine • Load nand-flash-writer.out and run it ("Run -> Load -> Load Program" Navigate to "nand-flash-writer.out" file, open it and then run it). nand-flash-writer.out should be available in the release package Start the application from Run -> Resume. Or hit F8 • Select option 1 when prompted. Select option 2 only in case if you want to erase the whole NAND Choose your operation Enter 1 ---> To Flash an Image Enter 2 ---> To ERASE the whole NAND which path to be used for u-boot.noxip.bin, where it is located in CCS5.2 where is the option 1 prompt, in debugger or serial terminal regards vivek
  • 0 in reply to vivek gupt
    Intellectual 405 points

    anyone goodluck on that? when I load nand-flash-write.out, nothing come out either on my costom board. it seems have no problem on the dm816x evm board.

  • 0 in reply to Kevin_Chen
    Guru 31670 points

    Kevin,

    Make sure that the DDR3 leveling parameters are taken care of properly in your custom board. When loading the program to memory, CCS itself does a read back and verify whether the program is loaded properly or not. If this verification fails you'll see the error messages from CCS itself. If you verification is successful, you can try step through the code using CCS and try to see where exactly its getting stuck.