From: jeff angielski <jeff@theptrgroup.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bad CPU identification on MPC8544DS
Date: Tue, 03 Mar 2009 14:04:05 -0500 [thread overview]
Message-ID: <1236107045.8988.27.camel@penguin> (raw)
Despite the SVR being the same (0x803c0011), the latest u-boot is
misidentifying the CPU when compared against the original 1.3.0 u-boot.
The CPU is a 8544E but u-boot is reporting 8533E.
The wierd part of this is that according to the Chip Errata for the
MPC8544E, the SVR *should* be 0x803c01xx - which is different than both
the 1.3 and latest git version are reading.
Can any of the Freescale guys explain this discrepancy between the
manual, the Freescale BSP u-boot, and the latest u-boot?
Using the u-boot that is built with the LTIB and ships with the
MPC8544DS board:
U-Boot 1.3.0-rc3 (Mar 28 2008 - 11:13:50)
CPU: 8544_E, Version: 1.1, (0x803c0011)
Core: E500, Version: 2.2, (0x80210022)
Clock Configuration:
CPU: 999 MHz, CCB: 399 MHz,
DDR: 199 MHz, LBC: 24 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Using the latest u-boot:
U-Boot 2009.03-rc1-00031-gd82fd0f-dirty (Mar 03 2009 - 13:09:00)
CPU: 8533E, Version: 1.1, (0x803c0011)
Core: E500, Version: 2.2, (0x80210022)
Clock Configuration:
CPU0:1000 MHz,
CCB:400 MHz,
DDR:200 MHz (400 MT/s data rate), LBC:25 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: MPC8544DS, System ID: 0x12, System Version: 0x20, FPGA Version:
0x31
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next reply other threads:[~2009-03-03 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 19:04 jeff angielski [this message]
2009-03-04 5:17 ` [U-Boot] Bad CPU identification on MPC8544DS Pieter
2009-03-06 13:39 ` jeff angielski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1236107045.8988.27.camel@penguin \
--to=jeff@theptrgroup.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.