Flash programmer error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Flash programmer error

1,096 Views
Mohsin455
Contributor IV

Hi All,

 

             I am trying to download a binary image using CW10.2 Beta and I am getting the following error. Any clues whats happenning. The following is the console output

 

 

fl::target -lc "LC for Simple Flash (1)"
fl::target -b 0x20000000 0x10000
fl::target -v off -l off
cmdwin::fl::device -d "FTFL_PFlash512" -o "128Kx32x1" -a 0x0 0x7ffff
cmdwin::fl::image -f "D:\\K60_Tower_Kit\\uTaskerV1_4-014.bin" -t "Auto Detect" -re on -r 0x0 0x7ffff -oe off
cmdwin::fl::erase image
 Beginning Operation ...    
-------------------------
Auto-detection is successful.   
  File is of type Binary/Raw Format.   
 
Performing target initialization ...    
 Downloading Flash Device Driver ...   
 Reading flash ID ...
Erasing Sector 0x00000000 to 0x000007FF   
Erasing Sector 0x00000800 to 0x00000FFF   
Erasing Sector 0x00001000 to 0x000017FF   
Erasing Sector 0x00001800 to 0x00001FFF   
Erasing Sector 0x00002000 to 0x000027FF   
Erasing Sector 0x00002800 to 0x00002FFF   
Erasing Sector 0x00003000 to 0x000037FF   
Erasing Sector 0x00003800 to 0x00003FFF   
Erasing Sector 0x00004000 to 0x000047FF   
Erasing Sector 0x00004800 to 0x00004FFF   
Erasing Sector 0x00005000 to 0x000057FF   
Erasing Sector 0x00005800 to 0x00005FFF   
Erasing Sector 0x00006000 to 0x000067FF   
Erasing Sector 0x00006800 to 0x00006FFF   
Erasing Sector 0x00007000 to 0x000077FF   
Erasing Sector 0x00007800 to 0x00007FFF   
Erasing Sector 0x00008000 to 0x000087FF   
Erasing Sector 0x00008800 to 0x00008FFF   
Erasing Sector 0x00009000 to 0x000097FF   
Erasing Sector 0x00009800 to 0x00009FFF   
Erasing Sector 0x0000A000 to 0x0000A7FF   
Erasing Sector 0x0000A800 to 0x0000AFFF   
Erasing Sector 0x0000B000 to 0x0000B7FF   
Erasing Sector 0x0000B800 to 0x0000BFFF   
Erasing Sector 0x0000C000 to 0x0000C7FF   
Erasing Sector 0x0000C800 to 0x0000CFFF   
Erasing Sector 0x0000D000 to 0x0000D7FF   
Erasing Sector 0x0000D800 to 0x0000DFFF   
Erasing Sector 0x0000E000 to 0x0000E7FF   
Erasing Sector 0x0000E800 to 0x0000EFFF   
Erasing Sector 0x0000F000 to 0x0000F7FF   
Erasing Sector 0x0000F800 to 0x0000FFFF   
Erasing Sector 0x00010000 to 0x000107FF   
Erasing Sector 0x00010800 to 0x00010FFF   
Erasing Sector 0x00011000 to 0x000117FF   
Erasing Sector 0x00011800 to 0x00011FFF   
Erasing Sector 0x00012000 to 0x000127FF   
Erasing Sector 0x00012800 to 0x00012FFF   
Erasing Sector 0x00013000 to 0x000137FF   
Erasing Sector 0x00013800 to 0x00013FFF   
Erasing Sector 0x00014000 to 0x000147FF   
Erasing Sector 0x00014800 to 0x00014FFF   
Erasing Sector 0x00015000 to 0x000157FF   
Erasing Sector 0x00015800 to 0x00015FFF   
Erasing Sector 0x00016000 to 0x000167FF   
Erasing Sector 0x00016800 to 0x00016FFF   
Erasing Sector 0x00017000 to 0x000177FF   
Erasing Sector 0x00017800 to 0x00017FFF   
Erasing Sector 0x00018000 to 0x000187FF   
Erasing Sector 0x00018800 to 0x00018FFF   
Erasing Sector 0x00019000 to 0x000197FF   
Erasing Sector 0x00019800 to 0x00019FFF   
Erasing Sector 0x0001A000 to 0x0001A7FF   
Erasing Sector 0x0001A800 to 0x0001AFFF   
Erasing Sector 0x0001B000 to 0x0001B7FF   
Erasing Sector 0x0001B800 to 0x0001BFFF   
Erasing Sector 0x0001C000 to 0x0001C7FF   
 Erasing ...
 Erase Command Succeeded    
cmdwin::fl::write
 Beginning Operation ...    
-------------------------
Using restricted address range 0x00000000 to 0x0007FFFF   
Programming file D:\K60_Tower_Kit\uTaskerV1_4-014.bin   
Auto-detection is successful.   
  File is of type Binary/Raw Format.   
 
 Downloading Flash Device Driver ...   
 Reading flash ID ...
Auto-detection is successful.   
  File is of type Binary/Raw Format.   

 

Downloading 0x0000EE98 bytes to be programmed at 0x00000000   
Executing program ....   
Error:  Program failed.   Flash driver reports the following error(s):  Security area can not be programmed
 
Error: Program failed. Flash driver reports the following error(s):  Security area can not be programmed

 

Thanks,

Mohsin

Labels (1)
0 Kudos
5 Replies

344 Views
Mohsin455
Contributor IV

Can anyone from Freescale please help ?

 

Regards,

Mohsin

0 Kudos

344 Views
J2MEJediMaster
Specialist I

It seems that the flash is somehow secured on the chip. I did a search using the phrase "unsecure" on the Kinetis forum (since you are using a Kinetis part), and got the following results:

 

http://forums.freescale.com/t5/forums/searchpage/tab/message?advanced=true&f=subject%2Cbody&filter=a...

 

One of these forum threads might fit your situation and offer a solution.

 

---Tom

 

0 Kudos

344 Views
Mohsin455
Contributor IV

Hi Tom,

 

               Thanks for your reply. I am not sure if its the same issue because I can debug individual programms by clicking the debug button. The issue comes up when loading a binary/hex file using "Flash File to Target".

 

There are some differences in how this is done using CW10.2 (which I am using) and using CW10.1 as in the following post

 

https://community.freescale.com/thread/103976

 

Thanks,

Mohsin

            

0 Kudos

344 Views
J2MEJediMaster
Specialist I

Depending upon how your CodeWarrior project is configured, when you click Debug the IDE might be downloading the program into RAM rather than flash, and so debugging works. From the communications trace, the IDE is talking to the part and erasing it. So, the evidence point to either the flash got secured somehow, or there's a secured region in the flash that you're trying to load the program in and the part balks at that.

 

Have you tried downloading any of the demo programs into flash successfully? That would tell you whether the part is secured, or if there's a secured area in flash.

 

Finally, since this problem seems to have appeared in v10.2, you might want to file an on-line service request to draw the engineers attention to this.

 

---Tom

0 Kudos

344 Views
Mohsin455
Contributor IV

Hi Tom,

 

                 Thanks for your reply. Yes, I am able to download programs to Flash normally. The issue is only when I use "Flash File to Target" option. 

 

I think its time to file an on-line service request.

 

Regards,

Mohsin

0 Kudos