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.

NDK initialization error!?

Dear Sir,

I think I found an error in NDK.

I have Ethernet function in my application, and the Ethernet sometimes works, sometimes fails.

I did some experiment to observe the Ethernet error.

When I clear all the data in DRAM to 0 before I run the Ethernet application, the ethernet function can work well.

If I don't do that, sometime it works, sometime it doesn't work.

If I set all the data in DRAM to 0xFF before I run the Ethernet application, the ethernet function fail.

Therefore, I think this is a bug caused by NDK initialization.

Some variables in NDK doesn't init well, and it depends on whether NDK "likes" the data in DRAM or not.   

So currently I can only clear the DRAM data to 0 with my boot loader before running Ethernet function.

Can someone help me to do the correct NDK initialization? (I already studied spru 523 & 524)

 

Best Regards,

 

Eric Fang

  • hola all

    Eric , i read your complete post and did my own research as well -  you 100% correct there is an error .

    I am currently working on DM648 EVM and using NDK 2 - same thing happens sometimes the code works other times it halts after printing the following lines:

     TCP/IP Stack "Hello World!' Application

    Using Mac Address: 00-21-ba-12-5a-0f

    On halting my PC pointer is pointing in UTL_halt,SYS_EXITFXN code section

    Currently i working on finding a solution as ti ppl never seem to reply :(  i am lost .

    I am going to do what you suggested - thank you .

    Can share you , DRAM clear function .

    Regards

    Amna

  • Amna and Eric,

    Sorry to hear the experience you've had. Since the end of last year, TI has added even more resources supporting the forums. I remember personally attempting to make sure all the forums questions in this forum were followed up. As you can see, there are a lot of traffic in this forum, and it is difficult for us to go back 18 months and see if there is anything that hasn't been resolved. Now that this post is resurfaced by your reply, I am sure you will get an answer very soon.

    That said, this is not the best subforum for your post. Please look for the BIOS forum and post a question there if needed.