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 about initialization of DDR3 in ethernet boot

I am using evm6670 to boot my application from ethernet.My procedure is "hex6x,bconvert64x,bootpacket,pscendpkt"

Here is rmd file:

tharq_5ue.out
-a
-boot
-e _c_int00
-map ethboot.map
-order M
ROMS
{
ROM1: org = 0x0400, length = 0x800000, memwidth = 32, romwidth = 32
files = { tsrio.btbl }

}

First,I used MSMC to boot a simple application and it worked,while I modified cmd file and put some data in DDR3,it did not work.According to a professor,I tried to integrate ddr init code to my application but it still doesn't work.

It seems that evm6670.gel has also initialized DDR3,but gel cannot be compiled thus I need to convert gel in C.

My question:

(1)Do I need a DDR config table after hex6x?Before ethernet boot,I tried SPI boot and it worked.In SPI boot mode,I have added a ddr config table after application(.out)passed hex6x.Here in ethernet boot,do i need to add a table?

(2)If I have to initialize ddr3 in application instead of gel,how to convert gel to a C file?Is there any way?

Thank you!