mobilevil
Tue Feb 01 00:00:10 CST 2005
can't think of any, all i did was confirm the sdram wireing, changed mdcnfg
and maybe mdrefr, that's all...
27x require change of 1 or 2 more reigster.
and i didn't play with the intel diagnositic manager, i play with eboot
since day 1. add some debug serial message in the asm file and trace.
"jeffs" <anonymous@discussions.microsoft.com> wrote in message
news:2dd401c507b9$69415280$a601280a@phx.gbl...
Hello,
This same table is in the developers manual for the PXA255.
I swapped the hardware bits per this table. I then
changed the compatiblity bit in the MDCNFG register to
match. The diagnostics would not function correctly when I
did this. Trying to understand why.
Thanks for any help! -Jeff
>-----Original Message-----
>this one is for 26x but it's the same as 25x
>
http://developer.intel.com/design/pca/applicationsprocessors/manuals/278639.htm
>see page 30 and 31, wiring is different for 1111
compatiblity mode.
>
>"jeffs" <anonymous@discussions.microsoft.com> wrote in
message
>news:2a0801c50771$bd0fb7f0$a601280a@phx.gbl...
>>- the SDRAM interface for the PXA250/255 has an "SA1111
>> compatibiltiy mode" WHY? the SA1111 interfaces to the
>> SDRAM a bit differently than the PXA255. Both devices
>> drive the same SDRAM for DMA transfers. So they both must
>> be hooked up the same way. So the PXA255 has a bit you can
>> set that allows you to change the wiring slightly on the
>> SDRAM to match the SA1111. (it involves swapping 2 bits).
>>
>> - I swapped these bits and switched SDRAM to "normal mode".
>> (bit12 of mdcnfg). This should theoretically not be a
>> problem unless the SA1111 trys to do a DMA transfer.
>> DRAM : 2x13x9x32 (bank,row,col,buswidth)
>>
>> - RESULT : the diagnositics crash when doing the SDRAM
>> test. (The SA1111 MBREQ pin in inactive in this test)
>>
>> What am I missing here? There must be something more to
>> this. Any help would be greatly appreciated! -Jeff
>>
>
>
>.
>