AnsweredAssumed Answered

Flashing NOR image on P4080DS Using CodeWarrior 10.1.2 and SDK v1.2 Images

Question asked by Seth Wilhelm on Aug 6, 2012
Latest reply on May 7, 2014 by Adrian Teso

I have been having trouble with my P4080DS board and decided this morning to flash a U-boot image into the flash alt-bank to bring the u-boot up-to-date with v1.2 SDK.

 

I used the u-boot images supplied with the v1.2 SDK and followed the "Development Deployment" instructions in the QorID SDK Documentation.  After transfering the u-boot image (tftp), erasing the flash, and then writing to flash, I reset the board.  All seemed to go well, but the board has not responded over serial connection since.  I did this all to the alternate bank addrees (0xebf80000), which is even more confusing why the board is no longer responding.

 

Since my P4080DS was now now operational, I decided to download and install codewarrior (v10.1.2) in an attempt to use the USB TAP (REV G) to program the NOR flash with the 128MB image supplied on the SDK v1.2 iso.  I ended up installing CodeWarrior on Win XP because my normal development host (CentOS 6.2) does not seem to be supported.

 

I setup a "Power Architecture Project"

  • Processor: QorIQ_P4 -> P4080
  • Processing Model: AMP (one project per core )
  • Project Output: Application
  • Toolchain: Bareboard: GCC EABI e500mc
  • Language: C
  • Build Tools Arch: 32 bit
  • Floating Point: HW
  • Debugger Connection Type: HW
  • Core index: Core 0
  • New System: P4080DS, USB TAP
  • Trace Configuration: used default

I create a "Target Tasks"

  • Imported P4080DS_NOR_FLASH.xml from the CodeWarrior installation directory
  • Added a program/verify action
  • Used the QorIQ_SDK_V1.2_p4080DS_20120614_NOR_Flash_128M.bin file
  • File type:binary
  • Checked Erase sectors before program
  • Checked Restrict to Addresses in this Range (0xE8000000 to 0xEFFFFFFF)
  • Checked Apply Address offset
  • Added action.

I connected the USB tap to a powered off p4080ds and the PC.

I powered on the p4080ds

I execute the task. Failure.

 

The USB TAP's LEDs are as follows: tx/rx is flashing green, run/pause is solid red.

 

The error is not always the same if I try executing the task multiple times.   The most common error is failed to reset the target, core note responding.  Common errors are as follows.  I shortened the file path to only the file name.

 

fl::target -lc "FlashingROM-core0_ROM_P4080_Attach"
fl::target -b 0x2000 0x30000
fl::target -v off -l off
cmdwin::fl::device -d "S29GL01GP" -o "64Mx16x1" -a 0xe8000000 0xefffffff
cmdwin::fl::image -f "QorIQ_SDK_V1.2_P4080DS_20120614_NOR_Flash_128M.bin" -t "Binary/Raw Format" -re on -r 0xe8000000 0xefffffff -oe on -o 0xe8000000
cmdwin::fl::erase image
 Beginning Operation ...   
-------------------------
Performing target initialization ...   
Error:  Connect Failed.
Failed to reset the target
[CCS last error: p4080: Core not responding ](CCSProtocolPlugin)
Error: Connect Failed.

 

 

Another Errorfl::target -lc "FlashingROM-core0_ROM_P4080_Attach"
fl::target -b 0x2000 0x30000
fl::target -v off -l off
cmdwin::fl::device -d "S29GL01GP" -o "64Mx16x1" -a 0xe8000000 0xefffffff
cmdwin::fl::image -f "QorIQ_SDK_V1.2_P4080DS_20120614_NOR_Flash_128M.bin" -t "Binary/Raw Format" -re on -r 0xe8000000 0xefffffff -oe on -o 0xe8000000
cmdwin::fl::erase image
 Beginning Operation ...   
-------------------------
Performing target initialization ...   
 Downloading Flash Device Driver ...  
Error:  Couldn't write flash driver to target.  CCSProtocolPlugin : Error writing memory[CCS last error: Core not responding ]

 

 

I have updated the firmware on the USB TAP using the instructions in the USB TAP Users Guide.  Not the issue.

 

I have also tried both the "FlashROM-core_ROM_P4080_Attach" and "LC for Simple Flash" run configurations.  Not the issue. 

 

I have slowed down the JTAG frequency and disabled fast download... still the same problem.

 

What am I missing???

Outcomes