Hi Thank you for your response. > Are you *sure* it's mapped at physical address 0xe0000000? (ie. have >you verified that you can access the device registers via u-boot or a >debugger?)
Yes, We have accessed the Micrel chip via U-boot setting (Micrel Chips Base addres) 0xE0000000 to the CS1 Start address Register. The LP_CS1 pin is configured to access the chip in U-boot. LINUX: We also probed the CS1 signal and found some noise in the signal (but wasn't any kind of pulse). It might not be the actual Chip Select pulse. But in U-Boot, we are getting proper Chip Select pulse. LINUX: The MBAR is mapped to default 0xF0000000 value. The BAT 2 settings in the "mpc52xx_set_bat" function, is set to map the 0xf0000000 area. Do we need to perform any similar BAT settings or any other settings to access the IO Device mapped at 0xE0000000 ? Thanks, Kala. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grant Likely Sent: Tuesday, November 13, 2007 9:21 AM To: Sri nava kala devi Valteti, TLS-Chennai Cc: linuxppc-embedded@ozlabs.org; Prakash Palanisamy, TLS-Chennai Subject: Re: MPC5200B - Mapping Micrel Ethernet Controller Chip On 11/12/07, Sri nava kala devi Valteti, TLS-Chennai <[EMAIL PROTECTED]> wrote: > > We are using MPC5200B based custom board. In that we have an external Micrel's ethernet controller mapped at 0xE0000000. > > We have taken Lite5200 code as a reference to port linux to our new board. We have integrated the ethernet driver given by the vendor (Micrel). > > Unfortunately, we are not able to access the chip mapped at 0xE0000000. Are you *sure* it's mapped at physical address 0xe0000000? (ie. have you verified that you can access the device registers via u-boot or a debugger?) The chip selects on the 5200 are programmable so you need to make sure that the chip select wired to the Micrel device is actually configured for base address 0xe0000000. There are up to 8 CS pins on the MPC5200B; LP_CS0 through LP_CS7. See section 9.7.1 in the MPC5200B user manual for details on how to configure them. > We performed the following steps to access the chip: > > i) We mapped this address range of the Ethernet Controller Chip in function "mpc52xx_map_io" as > > "io_block_mapping(0xE0000000, 0xE0000000, 0x10000000, _PAGE_IO)" You don't want to call this. ioremap is the only function you should need to call. But *first*, you must make sure the CS pin is configured correctly. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [EMAIL PROTECTED] (403) 399-0195 DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
