RE: MPC860 CP / CPM Misbehaving
From: Martin, Tim <hidden>
Date: 2005-05-13 23:57:24
Wolfgang, The SDRAM timings (UPM registers) are setup by a BDM/JTAG debugger script. The same script is run when I download the other software, which works. That being said, I wasn't the one who wrote the UPM portion of the script and it is one of the few things I haven't verified, so it does sound like a likely candidate. Thanks for the tip. Tim -----Original Message----- From: wd@denx.de [mailto:wd@denx.de] Sent: Friday, May 13, 2005 4:42 PM To: Martin, Tim Cc: 'linuxppc-embedded@ozlabs.org' Subject: Re: MPC860 CP / CPM Misbehaving In message [ref] you wrote:
I'm using a custom MPC860 based embedded board and having problems with
SCC1
and SMC1 reception. I have SCC1 setup in ethernet mode, and SMC1 setup in UART mode. The general problem manifests itself as getting receive buffer descriptors (BDs) from the CPM with the OV bit set (bit 14 of the RxBD status/control field, "Overrun. Set when a receiver overrun occurs during reception").
...
This isn't a board hardware problem, the board runs fine with other
software
(different operating system, etc). It's most likely a configuration
problem
on my end.
<speculation> Are you 100% sure that your SDRAM is working fine when stressed with burst mode accesses? See http://www.denx.de/twiki/bin/view/DULG/UBootCrashAfterRelocation </speculation>
My thoughts are that it's almost as if the CP (CPM RISC processor) or SDMA is being occasionally frozen out while the core PowerPC MPC860 processor
is
You may see "funny" problems when your SDRAM is not working right.
And yes, this may happen especially on DMA transfers which will use
burst mode.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
... Hiroshima 45 ... Chernobyl 86 ... Windows 95 ...