From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by ozlabs.org (Postfix) with ESMTP id 7722B67A2E for ; Sun, 10 Apr 2005 14:57:57 +1000 (EST) Received: by rproxy.gmail.com with SMTP id g11so1911323rne for ; Sat, 09 Apr 2005 21:57:55 -0700 (PDT) Message-ID: Date: Sun, 10 Apr 2005 12:51:15 +0800 From: Yeo Keewee To: linuxppc-embedded@ozlabs.org In-Reply-To: <20050410020004.967A967B3E@ozlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <20050410020004.967A967B3E@ozlabs.org> Subject: Problem with customized MPC5200 board(copy from lite5200 design) Reply-To: Yeo Keewee List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, Our hardware group had designed a mpc5200 board using the same design as lite5200. Currently, we are using bdi2000(icecube config) to attempt to access the internal registers. By using the same procedure on lite5200, we can access the registers but we always could not do it on our board. Besides a hardware design flaw, is there any other init procedures that are required to use bdi2000 on our custom board? Did anyone face this kind of problem? rgds Yeo Kee Wee