Error:resetting DM9000-Not responding dm9000 not found at 0x88000000 problem resolution

Error:resetting DM9000-Not responding
dm9000 not found at 0x88000000 id:0x00000000

From the error message to analyze, the ID number printed out is wrong.
Locate the error file first:
[Email protected]:/home/xjg/u-boot-2012.10# grep-r "Error:resetting DM9000"
DRIVERS/NET/DM9000X.C: printf ("Error:resetting DM9000, not responding\n");

The error occurred at the beginning of the reset function, stating that there was a problem with the previous step.
I have checked your lowlevel_init. s file, found a problem with the initialization of the clock.
The final positioning is in the following sentence to comment on it.
*/clk_ip1 * *
211/* LDR R1, =0XE9FDF0F9 @ fimd[0] usbotg[16]
212@ NANDXL[24]
213 str R1, [R0, #0x464] @ s5pc110_clk_ip1
214 */

Let's take a look at this step, why not?
s5pv210 can disable the clock operation of each IP if it's not required.
Look, it looks like a register of shielded clocks.
Modify it to look like this, indicating that the 26th bit of the register (Srom clock) is not shielded.
*/clk_ip1 * *
211 Ldr R1, =0XEDFDF0F9 @ fimd[0] usbotg[16]
212@ NANDXL[24]
213 str R1, [R0, #0x464] @ s5pc110_clk_ip1

214

Why is it related to the Srom clock? From the schematic you can know that dm9000 is the use of its own clock source, the dm9000 chip external to a 25MHz crystal oscillator.
Thanks for the guide of the Internet of Things lecture by Mr. Zhu:
210 Use the Srom interface to communicate with the network card. Remember how dm9000 got on top of 210? CSN1 chip selection signal.
This means that dm9000 is connected to the BANK1 above the srom of 210. This can explain why the Srom clock cannot be closed ....

Error:resetting DM9000-Not responding dm9000 not found at 0x88000000 problem resolution