AW: [microblaze-uclinux] ethernet + EMC

["Schunke Jan-Hendrik" <Schunke@shf-communication.de>]

Hi John,

The D0-D7 signals on the P160 are shared for FLASH/SRAM and LCD connector. The LCD signals are buffered by the cool runner. Did you accidently reprogram the coolrunner and it pulls down the lines now? There are also some signals that control the coolrunner: PLD_LCD_RWN, PLD_LCD_EN ... I would check these, too.

I have taken a quick look at your mhs and that seems to be ok. 

Jan


> -----Ursprüngliche Nachricht-----
> Von: John Williams [mailto:jwilliams@itee.uq.edu.au] 
> Gesendet: Dienstag, 26. August 2003 09:38
> An: microblaze-uclinux@itee.uq.edu.au
> Betreff: [microblaze-uclinux] ethernet + EMC
> 
> 
> Hi folks,
> 
> Trying to bring up networking on uClinux, first step I've put 
> a xilinx 
> ethernet MAC core in my project (surprisingly enough called 
> mbvanilla_net :).
> 
> Anyway I've found that when I include the MAC core, all of a 
> sudden my 
> EMC peripheral (which drives the flash and SRAM) doesn't 
> work.  The low 
> byte of all reads in the EMC address space returns 0xFF...the high 3 
> bytes are fine...
> 
> I can query the ethernet MAC device ID register, and the BRAM and DDR 
> memory are unaffected.
> 
> So, I can upload an image direct into DDR and execute it, no 
> problems, 
> however my bootloading process of reading from flash and so on can't 
> work - all reads from flash are corrupted by this 0xFF byte.
> 
> Has anybody had any experiences, positive or negative, re: 
> using the EMC 
> and EMAC in the same target?  I've attached the mhs and ucf files for 
> reference.
> 
> Any ideas of where to look would be greatly appreciated.
> 
> Thanks,
> 
> John
> 

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/