MPC8560ADS Flash Error : Low VPP

[fltgpcdot]

Hi,

I am trying to erase , blank check and program a u-boot image in MPC8560 Rev A ADS board  Flash using Code Warrior Development Studio Linux Application edition (linux Hosted) flash programmer. The emulator is Code Warrior USB TAP.

I have used following configuration file in flash programmer
CW_PowerArch_Linux_8.7/CodeWarriorIDE/CodeWarrior/CodeWarrior_Plugins/
Support/Flash_Programmer/EPPC/85xx/8560_ADS_RevA_FLASH_boot.xml

I am getting following error when I try to erase one sector or all sectors of flash

: -------------------------

Using Algorithm: intel16x2j3.elf
 


======================================================================
=== Target Configuration Settings
=== Connection:       CodeWarrior USB TAP
=== Target Processor: 8560
=== Target Init File: /usr/local/Freescale/CW_PowerArch_Linux_8.7/CodeWarriorIDE/CodeWarrior/PowerPC_EABI_Support/Initialization_Files/PQ3/8560ADS_RevA_init.cfg
======================================================================
Connecting......Connected


======================================================================
=== Execute: Erase
=== Timestamp:  Wed May 21 16:43:43 2008
=== Flash Device:         IN28F640J3
=== Flash Organization:   4Mx16x2
=== Flash Mem Start Addr: 0xFF000000
=== Flash Mem End Addr:   0xFFFFFFFF
======================================================================
Informing other connection clients that the target is being 'clobbered'.
Loading Flash Device Driver at: 0x00002000
Flash Driver Buffer is at:      0x00003F90
Flash Driver Buffer Size is:    0x0001E070
Done

Initialization Command Succeeded
Erasing Sector 0xFF000000 to 0xFF03FFFF ...
Erasing Sector 0xFF040000 to 0xFF07FFFF ...
Erasing Sector 0xFF080000 to 0xFF0BFFFF ...
Erasing Sector 0xFF0C0000 to 0xFF0FFFFF ...
Erasing Sector 0xFF100000 to 0xFF13FFFF ...
Erasing Sector 0xFF140000 to 0xFF17FFFF ...
Erasing Sector 0xFF180000 to 0xFF1BFFFF ...
Erasing Sector 0xFF1C0000 to 0xFF1FFFFF ...
Erasing Sector 0xFF200000 to 0xFF23FFFF ...
Erasing Sector 0xFF240000 to 0xFF27FFFF ...
Erasing Sector 0xFF280000 to 0xFF2BFFFF ...
Erasing Sector 0xFF2C0000 to 0xFF2FFFFF ...
Erasing Sector 0xFF300000 to 0xFF33FFFF ...
Erasing Sector 0xFF340000 to 0xFF37FFFF ...
Erasing Sector 0xFF380000 to 0xFF3BFFFF ...
Erasing Sector 0xFF3C0000 to 0xFF3FFFFF ...
Erasing Sector 0xFF400000 to 0xFF43FFFF ...
Erasing Sector 0xFF440000 to 0xFF47FFFF ...
Erasing Sector 0xFF480000 to 0xFF4BFFFF ...
Erasing Sector 0xFF4C0000 to 0xFF4FFFFF ...
Erasing Sector 0xFF500000 to 0xFF53FFFF ...
Erasing Sector 0xFF540000 to 0xFF57FFFF ...
Erasing Sector 0xFF580000 to 0xFF5BFFFF ...
Erasing Sector 0xFF5C0000 to 0xFF5FFFFF ...
Erasing Sector 0xFF600000 to 0xFF63FFFF ...
Erasing Sector 0xFF640000 to 0xFF67FFFF ...
Erasing Sector 0xFF680000 to 0xFF6BFFFF ...
Erasing Sector 0xFF6C0000 to 0xFF6FFFFF ...
Erasing Sector 0xFF700000 to 0xFF73FFFF ...
Erasing Sector 0xFF740000 to 0xFF77FFFF ...
Erasing Sector 0xFF780000 to 0xFF7BFFFF ...
Erasing Sector 0xFF7C0000 to 0xFF7FFFFF ...
Erasing Sector 0xFF800000 to 0xFF83FFFF ...
Erasing Sector 0xFF840000 to 0xFF87FFFF ...
Erasing Sector 0xFF880000 to 0xFF8BFFFF ...
Erasing Sector 0xFF8C0000 to 0xFF8FFFFF ...
Erasing Sector 0xFF900000 to 0xFF93FFFF ...
Erasing Sector 0xFF940000 to 0xFF97FFFF ...
Erasing Sector 0xFF980000 to 0xFF9BFFFF ...
Erasing Sector 0xFF9C0000 to 0xFF9FFFFF ...
Erasing Sector 0xFFA00000 to 0xFFA3FFFF ...
Erasing Sector 0xFFA40000 to 0xFFA7FFFF ...
Erasing Sector 0xFFA80000 to 0xFFABFFFF ...
Erasing Sector 0xFFAC0000 to 0xFFAFFFFF ...
Erasing Sector 0xFFB00000 to 0xFFB3FFFF ...
Erasing Sector 0xFFB40000 to 0xFFB7FFFF ...
Erasing Sector 0xFFB80000 to 0xFFBBFFFF ...
Erasing Sector 0xFFBC0000 to 0xFFBFFFFF ...
Erasing Sector 0xFFC00000 to 0xFFC3FFFF ...
Erasing Sector 0xFFC40000 to 0xFFC7FFFF ...
Erasing Sector 0xFFC80000 to 0xFFCBFFFF ...
Erasing Sector 0xFFCC0000 to 0xFFCFFFFF ...
Erasing Sector 0xFFD00000 to 0xFFD3FFFF ...
Erasing Sector 0xFFD40000 to 0xFFD7FFFF ...
Erasing Sector 0xFFD80000 to 0xFFDBFFFF ...
Erasing Sector 0xFFDC0000 to 0xFFDFFFFF ...
Erasing Sector 0xFFE00000 to 0xFFE3FFFF ...
Erasing Sector 0xFFE40000 to 0xFFE7FFFF ...
Erasing Sector 0xFFE80000 to 0xFFEBFFFF ...
Erasing Sector 0xFFEC0000 to 0xFFEFFFFF ...
Erasing Sector 0xFFF00000 to 0xFFF3FFFF ...
Erasing Sector 0xFFF40000 to 0xFFF7FFFF ...
Erasing Sector 0xFFF80000 to 0xFFFBFFFF ...
Erasing Sector 0xFFFC0000 to 0xFFFFFFFF ...
Flash Programmer:  Flash driver reports the following error(s):  Chip reported Low VPP Error Status

Timestamp:  Wed May 21 16:43:46 2008
: -------------------------

Using utility file: FlashUtility.elf


======================================================================
=== Target Configuration Settings
=== Connection:       CodeWarrior USB TAP
=== Target Processor: 8560
=== Target Init File: /usr/local/Freescale/CW_PowerArch_Linux_8.7/CodeWarriorIDE/CodeWarrior/PowerPC_EABI_Support/Initialization_Files/PQ3/8560ADS_RevA_init.cfg
======================================================================
Connecting......Connected


======================================================================
=== Execute: Blank Check
=== Timestamp:  Wed May 21 16:44:09 2008
=== Flash Device:         IN28F640J3
=== Flash Organization:   4Mx16x2
=== Flash Mem Start Addr: 0xFF000000
=== Flash Mem End Addr:   0xFFFFFFFF
======================================================================
Informing other connection clients that the target is being 'clobbered'.
Loading Flash Utility Driver at: 0x00002000

Performing Blank Check from 0xFF000000 to 0xFF03FFFF ... Passed

Performing Blank Check from 0xFF040000 to 0xFF07FFFF ... Passed

Performing Blank Check from 0xFF080000 to 0xFF0BFFFF ... Passed

Performing Blank Check from 0xFF0C0000 to 0xFF0FFFFF ... Passed

Performing Blank Check from 0xFF100000 to 0xFF13FFFF ... Passed

Performing Blank Check from 0xFF140000 to 0xFF17FFFF ... Passed

Performing Blank Check from 0xFF180000 to 0xFF1BFFFF ... Passed

Performing Blank Check from 0xFF1C0000 to 0xFF1FFFFF ... Passed

Performing Blank Check from 0xFF200000 to 0xFF23FFFF ... Passed

Performing Blank Check from 0xFF240000 to 0xFF27FFFF ... Passed

Performing Blank Check from 0xFF280000 to 0xFF2BFFFF ... Passed

Performing Blank Check from 0xFF2C0000 to 0xFF2FFFFF ... Passed

Performing Blank Check from 0xFF300000 to 0xFF33FFFF ... Passed

Performing Blank Check from 0xFF340000 to 0xFF37FFFF ... Passed

Performing Blank Check from 0xFF380000 to 0xFF3BFFFF ... Passed

Performing Blank Check from 0xFF3C0000 to 0xFF3FFFFF ... Passed

Performing Blank Check from 0xFF400000 to 0xFF43FFFF ... Passed

Performing Blank Check from 0xFF440000 to 0xFF47FFFF ... Passed

Performing Blank Check from 0xFF480000 to 0xFF4BFFFF ... Passed

Performing Blank Check from 0xFF4C0000 to 0xFF4FFFFF ... Passed

Performing Blank Check from 0xFF500000 to 0xFF53FFFF ... Passed

Performing Blank Check from 0xFF540000 to 0xFF57FFFF ... Passed

Performing Blank Check from 0xFF580000 to 0xFF5BFFFF ... Passed

Performing Blank Check from 0xFF5C0000 to 0xFF5FFFFF ... Passed

Performing Blank Check from 0xFF600000 to 0xFF63FFFF ... Passed

Performing Blank Check from 0xFF640000 to 0xFF67FFFF ... Passed

Performing Blank Check from 0xFF680000 to 0xFF6BFFFF ... Passed

Performing Blank Check from 0xFF6C0000 to 0xFF6FFFFF ... Passed

Performing Blank Check from 0xFF700000 to 0xFF73FFFF ...  260719 Failures
 
     Non Blank Found at 0xFF700000 expected: FF actual: 27
     Non Blank Found at 0xFF700001 expected: FF actual: 05
     Non Blank Found at 0xFF700002 expected: FF actual: 19
     Non Blank Found at 0xFF700003 expected: FF actual: 56
     Non Blank Found at 0xFF700004 expected: FF actual: BD
     Non Blank Found at 0xFF700005 expected: FF actual: 3E
     Non Blank Found at 0xFF700006 expected: FF actual: EE
     Non Blank Found at 0xFF700007 expected: FF actual: 66
     Non Blank Found at 0xFF700008 expected: FF actual: 41
     Non Blank Found at 0xFF700009 expected: FF actual: 5A
     Non Blank Found at 0xFF70000A expected: FF actual: 58
     Non Blank Found at 0xFF70000B expected: FF actual: 75
 
Timestamp:  Wed May 21 16:44:39 2008

************************************************************************************************************

While erasing the flash driver is reporting
"Chip reported Low VPP Error Status "

and blank check is not sccessfuk for some locations though they have been erased in earlier operation

Anyone kindly help me.

Thanks

Deepak

[Black]

Please try erasing only the sectors you need (not all the sectors) by selecting them with the Ctrl key and the left mouse click to see if it makes a difference. Please use the CodeWarrior USB TAP default settings in project settings->Remote Debugging panel->Connection->CW USB TAP->Edit Connection.

The error message that you get might have several causes including a wrong board switches position:

- Write signal not getting to the flash devices, "Write Protect" Enabled in the Chip Selects for the flash device

- WRITE disabled in MMU please check the BAT, TLB registers

- WE signal blocked by target hardware

- Algorithm writes to wrong location, confirm flash base address, confirm MMU configuration

For more details please consult the board manual for the right switches position.

As a first step you must to be able to debug stationery project created with CodeWarrior EPPC New Project Wizard for your evaluation board in RAM using a board-specific init.cfg file (in the project's EPPC Debugger Settings panel). Furthermore, "Verify Memory Writes" must be checked in the project's EPPC Debugger Settings panel. Once the debugger can step and run through the main code on the board with Verify Memory Writes on, you can build the ROM version of the project and program the flash.

I hope this helps.

[Black]

I also recommend upgrading to CodeWarrior Power Architecture 8.8.1 and see if the problem continues. It is available for download as an evaluation version here.

[JasonLee]

Has anyone else encountered this issue, or does anyone have any more ideas on a workaround?

I am currently trying to program the flash memory of an MPC8540 board, which also uses an Intel Strata IN28F640J3 flash memory, and I am getting the same error:

"Chip reported Low VPP Error Status"

I am using a CodeWarrior USB TAP jtag debugger to access the flash memory, and I have verified that it is operating correctly and communicating with the processor.

I am using CodeWarrior 8.8.3 (the newest available version). 

Regarding Black's suggestions:

 

---

Black wrote:

The error message that you get might have several causes including a wrong board switches position:

- Write signal not getting to the flash devices, "Write Protect" Enabled in the Chip Selects for the flash device

- WRITE disabled in MMU please check the BAT, TLB registers

- WE signal blocked by target hardware

- Algorithm writes to wrong location, confirm flash base address, confirm MMU configuration 

---

I'm not very experienced with programming flash memories, so I'm not highly confident that Write Protect is enabled, or if the MMU is configured correctly.  If anyone can help with checking these settings, it would be greatly appreciated.

Thanks,

Jason Lee