Skip to contentSkip to conversation

Problem with data cache on MPC823E

DISCUSSION Jan Damborsky 2 participants 3 messages Jan 21, 2003 – Jan 22, 2003

lore
Share & tools
lore
#0 lore raw

Hello people,

we have developed our board with MPC823E, FLASH memory
DRAM memory for embedded Linux porting, but we have problem with data cache. From time to time when CPU wants load data from DRAM to data cache, it makes four burst-reads instead of one for loading one cache line.
After this, all four words in cache line are loaded with the same first "critical word".
We don't know, why CPU repeats this burst-read four times. May be it is because we have floating BI (burst inhibit) CPU singnal.
We have set BIH bit in UPMA to zero.
When setting this BIH bit to one (burst inhibit), all works well. Does anybody have any help ?
Jan Damborsky

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#1 lore raw
Quoted 13 lines · In message <[email protected]> you wrote:

we have developed our board with MPC823E, FLASH memory
DRAM memory for embedded Linux porting, but we have problem with data cache. From time to time when CPU wants load data from DRAM to data cache, it makes four burst-reads instead of one for loading one cache line.
After this, all four words in cache line are loaded with the same first "critical word".
We don't know, why CPU repeats this burst-read four times. May be it is because we have floating BI (burst inhibit) CPU singnal.
We have set BIH bit in UPMA to zero.
When setting this BIH bit to one (burst inhibit), all works well. Does anybody have any help ?

This pheomenon is typical for bad SDRAM initialization. Read the chip manufacturer's manual and follow the steps of the init sequence _to_the_letter_. It is _not_ sufficient to set up the UPM tables.

Best regards,

Wolfgang Denk

--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: [email protected] Committee, n.: A group of men who individually can do nothing but as
a group decide that nothing can be done. - Fred Allen

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

#2 lore raw
Quoted 13 lines

This pheomenon is typical for bad SDRAM initialization. Read the chip manufacturer's manual and follow the steps of the init sequence _to_the_letter_. It is _not_ sufficient to set up the UPM tables.

Best regards,

Wolfgang Denk

But we dont use SDRAM, but DRAM EDO SIMM module. I think these RAM types dont require special initialization.

Thanks,
Jan Damborsky

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/