Hi,
I don't have experiences related to dBUG and coldfire, but I think we can
find some ways to find the reasom of problem.
Firstly, you have checked the border of 64MB of SDRAM, so if you write
0x5A into 0x3FFFFFF, what are the values at 0x2FFFFFF, 0x1FFFFFF, or 0xFFFFF.
and what if you write 0x5A to 0x4000000, what happens?
Then, if there is really working 64MB SDRAM, can you find an old stable
version of Linux, and then run it with your ramdisk configuration, check the
results.
If is good, we can get that, there is something wrong during the porting,
especialy related to memory, so you can compare the codes related to HW/LSP,
maybe it is there.
If not, I don't have any more ideas now, you can ask Ungreg, it is the
guru of coldfire.
I hope I am helpful, and good luck to you.
May-14-2007
will <[EMAIL PROTECTED]> wrote: Hi Tao,
I used a modified dBUG as my bootloader and I have used the 'mm' and 'md'
commands to test my memory.
The test result was just fine when I modified and read the very border of the
64M memory. I am confused and the hardware designer is
unreachable now. I port the kernel to the platform just according to the
circuit diagram. Can you give me any suggestion?
Thans!
BR,
Will Huang
> Hi, Mr. Huang, > I think you don't need to set the CS in kernel. As for the
> SDRAM, it is not easy to make it work, so first, I think you'd better check
> the problem in your bootloader, some bootloaders such as u-boot can do memory
> write and read, so you can use these operations to check if the SDRAM on
> board can be accessed properly. If not, the problem is in your bootloader, so
> you may need to ask the hardware engineer, what is parameters of SDRAM, and
> then how to initialize it to work properly. > In summay, testing the SDRAM
> from bootloader if possible, then when it is passed the test, starting you
> kernel load and boot. > Good luck to you.
ÏÖÔÚ¹ºÂò21CNÆóÒµÓÊÏä,¼´¿ÉÓÃ100Ôª»»5000Ôª!
ÖíÄêÐдóÔË£¬²ÂͼӮ»°·Ñ£¡
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
will <[EMAIL PROTECTED]> wrote: Hi Tao,
I used a modified dBUG as my bootloader and I have used the 'mm' and 'md'
commands to test my memory.
The test result was just fine when I modified and read the very border of the
64M memory. I am confused and the hardware designer is
unreachable now. I port the kernel to the platform just according to the
circuit diagram. Can you give me any suggestion?
Thans!
BR,
Will Huang
> Hi, Mr. Huang, > I think you don't need to set the CS in kernel. As for the
> SDRAM, it is not easy to make it work, so first, I think you'd better check
> the problem in your bootloader, some bootloaders such as u-boot can do memory
> write and read, so you can use these operations to check if the SDRAM on
> board can be accessed properly. If not, the problem is in your bootloader, so
> you may need to ask the hardware engineer, what is parameters of SDRAM, and
> then how to initialize it to work properly. > In summay, testing the SDRAM
> from bootloader if possible, then when it is passed the test, starting you
> kernel load and boot. > Good luck to you.
ÏÖÔÚ¹ºÂò21CNÆóÒµÓÊÏä,¼´¿ÉÓÃ100Ôª»»5000Ôª!
ÖíÄêÐдóÔË£¬²ÂͼӮ»°·Ñ£¡
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
---------------------------------
8:00? 8:25? 8:40? Find a flick in no time
with theYahoo! Search movie showtime shortcut.
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
