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
On 9/29/06, Michael Galassi <[EMAIL PROTECTED]> wrote:
>>Hello linux-ppc experts,
>>
>>I'm trying to use using wind river jtag probe to download uboot to our
>>switching box which is with PPC8343E/Intel 28F128J3D memory flash(16M).
>>Memory mapping is starting from 0xFF000000 to 0xFFFFFFFF which is 16M. The
>>JTAG software I'm using is visionclick8.
>>
>>The problem now is that I even couldn't erash flash, with following error
>>message:
>>
>>TF ERASE FFF00000..FFFFFFFF INTEL 28F128Jx ( 8192 x 16 ) 1 Device
>>Erasing Flash(s) ... Failed
>>!ERROR! - [msg100000] Failed while erasing the device(s)
>>>BKM>
>>!HALT! - [msg90009] Target Stopped : CheckStop taken; PC = 0x00007404 [EVENT
>>Taken]
>>>BKM>
>>
>>Does anyone has experiece to bring up this CPU, and could shed some lights
>>on it? Thank you in advance.
>>
>>- Reeve
>
>Your flash part[s] are almost certainly write-protected, or part of them
>is. Get the data-sheet for them and find what combination to write to
>them to un-protect them and try again. For the parts I'm using (micron
>MT28F128J3) writing 0x00600060 followed by 0x00d000d0 to the part does
>the trick.
>
>-michael
I must be lonely, responding to my own email :-).
The other option you have is re-build u-boot to run from ram (presumably
at some lower address), then use u-boot itself to clear the write
protect bits on your flash. U-boot's makefile has config targets for
ram & flash for some target boards which you may be able to take
advantage of. My first solution is probably still quicker if you're not
trying to debug u-boot itself.
-michael
_______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
