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.

aemif interface problem

If got the following setup:

I connected an external chip via the J14 emif expansion to my dm365dvevm.

So now i want to read the memory registers with uboot, e.g. md.b 0x2000000 0x80 and get the following behav:

 

02000000: ff ff ff ff ff ff ff ff 00 00 ff 00 0f 80 ff ff    ................  
02000010: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  
02000020: 00 00 00 00 00 00 00 00 00 00 ff 00 0f 80 ff ff    ................  
02000030: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  
02000040: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  
02000050: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  
02000060: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  
02000070: 30 00 ff 00 00 00 fd ff 00 00 ff 00 0f 80 ff ff    0...............  

It wraps around every 16byte, thats fine. (It only has 16byte to read, and only 4 address lines are conn) So this is more like reading the same 16byte 8times in a row.

So it should actually read the same thing every time, which it does not in line 0 and 2. I get this behavior every time i reboot (reproducible) . After reading at least 3 times all 16byte, it behaves like it should.

 

Funny thing is: If i let the uboot init procedure read the registers e.g. 10times, it still exists by reading it with uboot afterwards. I first thought about some electrical things like capacities in the wires etc. (i'm not a hardware specialist ;) ), but if there would be some, this should have been gone if i read the emif first by the uboot init, or?

 

maybe someone got a similar problem some time and could help me out here,

Valentin