From: "Mathews, Phil" <Phil.Mathews@innocon.com>
To: "Michael Galassi" <mgalassi@c-cor.com>,
"Reeve Yang" <yang.reeve@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Need help on PPC8343E bringup
Date: Fri, 29 Sep 2006 18:43:18 -0400 [thread overview]
Message-ID: <3E8081396F6B524BA2854E7FA3F16438042EB1FD@mail.innocon.com> (raw)
In-Reply-To: 200609292214.k8TMEZfw006857@penguin.ncube.com
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
From: linuxppc-embedded-bounces+phil.mathews=innocon.com@ozlabs.org on behalf of Michael Galassi
Sent: Fri 9/29/2006 6:14 PM
To: Reeve Yang
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Need help on PPC8343E bringup
>Thanks Machael.
>
>On my flash data sheet, there are some command about security:
>
>Lock Block | Block Address | 0060h | Block Address | 0001h
>Unlock Block|Block Address| 0060h | Block Address | 00d0h
>
>So I guess it needs two write cycle to perfomr the command, and the unlock
>command should be 006000d0. I tried that but still get the same error. Bad!
>:(
>
>Another questions is that is there any way to change CPU register directy?
>For 8343E all registers are mapped to 1m starting from 0xff400000. I want to
>change on 0Xff400c08, but visionclick reject me to write on that address.
>
>- Reeve
Actually no, I made the assumption that you have two 16 bit wide flash
parts, one providing bits 0:15, the other 16:31. Most PPC projects end
up doing this. The write 0x00600060 ends up sending a 0x60 to the flash
on the low bits and another 0x60 to the flash part on the high bits.
The second write of 0x00d000d0 likewise sends a single 0xd0 to each
flash part.
If your tool gave you a command called mw which had a usage somewhat
like:
mw <size> <address> <data>
where size is b/byte, w/word, l/longword you might you might try:
mw l 0x00600060 0xff000000
mw l 0x00d000d0 0xff000000
Does that make sense to you?
PS: some people here have nothing better to do than whine about
top-posting, safe yourself the grief and respond bellow the
post.
PS: Technicaly this is not a Linux topic, I'm responding here
because this does turn out to be of general interest.
-michael
Actually the comands should be:
mw l 0xff000000 0x00600060
mw l 0xff000000 0x00d000d0
BTW - you don't have to bellow the post, you can just type them quietly :-)
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: Type: text/html, Size: 2988 bytes --]
prev parent reply other threads:[~2006-09-29 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:08 Need help on PPC8343E bringup Reeve Yang
2006-09-29 21:33 ` Michael Galassi
2006-09-29 21:39 ` Michael Galassi
2006-09-29 22:03 ` Reeve Yang
2006-09-29 22:14 ` Michael Galassi
2006-09-29 22:43 ` Mathews, Phil [this message]
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=3E8081396F6B524BA2854E7FA3F16438042EB1FD@mail.innocon.com \
--to=phil.mathews@innocon.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgalassi@c-cor.com \
--cc=yang.reeve@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox