|
It works now. The problem were indeed the MS0..3 lines. In my design I had the MS0..3 lines connected as follows: MS0: separate pulldowns on both DSPs, this because we had sometimes troubles booting the DSPs and found that with a pulldown at MS0 it was fine. MS1: connected between the DSPs plus to the SDRAM MS2: open on both DSPs MS3: open on both DSPs It seems that this is not how it should be. The EZ-KIT board has pullups on MS0..3. It worked when I connected the MS0 between the DSPs. The Master drives the MS0..3 lines and in my case MS0, MS2, MS3 were driven to high and MS1 to low (asserted) (which is valid, because the 21065 data sheet says: "an MS3-0 line which is mapped to SDRAM may be asserted even when no SDRAM access is active.") So in essence, the MS0 line of the Slave was driven high (by the Master) and not low anymore (by the pulldown resistor). But why the MS0 line has to be high in order to have the Multiprocessor IOP register access working escapes me. The 21065 datasheet says that the MS0..3 signals can be I/O/T while the manual says that they can be O/T. What is correct? Obviously they can act as an input. I guess one should connect pullups to MS0..3 in any case. Daniel > -----Original Message----- > From: Mike Rosing [mailto:] > Sent: Wednesday, June 02, 2004 3:13 PM > To: Daniel Weiss > Cc: > Subject: RE: [adsp] 21065 Multiprocessor troubles > On Wed, 2 Jun 2004, Daniel Weiss wrote: > > > The IDs are fine. I can read them in the SYSTAT register of > each processor and they are as they should be. Maybe the > MS0..3 lines are indeed required. I have to try that. > > The IOPs of the processor with ID 10 are on addresses 0x200 > upwards. The ones of the processor with ID 01 are from 0x100 upwards. > > Worth a try to hook them up. I don't see why, but I've never tried it > either! Keep us posted on how you find the solution. > > Patience, persistence, truth, > Dr. mike |
IIR filter coefficients
Started by ●June 1, 2004
Reply by ●June 3, 20042004-06-03
