FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

NOR flash programming issue CW 10.5

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NOR flash programming issue CW 10.5

‎06-14-2016 03:22 AM
2,389 Views
sureshk
Contributor II

Hi,

   In my custom board using processor T1040 . When i am trying to program the Uboot.bin into NOR flash , after programming few location it is showing error. I am able to fuse .pbl and iram files but not uboot.bin file.

 

check the below log file and error i am getting..

 

 

fl::target -lc "T1040_GCR-core00_RAM_T1040_Download"

fl::target -b 0x0 0x6130

fl::target -v off -l off

cmdwin::fl::device -d "JS28F00AM29EWL" -o "64Mx16x1" -a 0xe8000000 0xefffffff

cmdwin::fl::protect all off

Beginning Operation ...   

-------------------------

Performing target initialization ...   

Downloading Flash Diagnostics Driver ...  

Reading flash ID ...

Unprotecting all sectors...  

Unprotecting ...  

Unprotecting ....  

Unprotecting .....  

Unprotecting ......  

Unprotecting .......  

Unprotecting ........  

Unprotecting .........  

Unprotecting ..........  

Unprotecting ...........  

Unprotecting ............  

Unprotect Command Succeeded   

cmdwin::fl::device -sd all

cmdwin::fl::device -se 1018 1019 1020 1021 1022 1023

cmdwin::fl::erase list

-------------------------

Downloading Flash Device Driver ...  

Reading flash ID ...

Erasing Sector 0xEFF40000 to 0xEFF5FFFF  

Erasing Sector 0xEFF60000 to 0xEFF7FFFF  

Erasing Sector 0xEFF80000 to 0xEFF9FFFF  

Erasing Sector 0xEFFA0000 to 0xEFFBFFFF  

Erasing Sector 0xEFFC0000 to 0xEFFDFFFF  

Erasing Sector 0xEFFE0000 to 0xEFFFFFFF  

Erasing ...

Erase Command Succeeded   

cmdwin::fl::device -sd all

cmdwin::fl::device -se 1018 1019 1020 1021 1022 1023

cmdwin::fl::blankcheck list

Beginning Operation ...   

-------------------------

Downloading Flash Utility Driver ...  

Performing Blank Check from 0xEFF40000 to 0xEFFFFFFF ...   

Blank Checking ...

Blank Check Succeeded   

Blank Check Completed Successfully  

cmdwin::fl::image -f "C:\\Users\\cdot\\Desktop\\1040\\u-boot-gcr-jun14.bin" -t "Auto Detect" -re off -oe on -o 0xeff40000

cmdwin::fl::write

-------------------------

Programming file C:\Users\cdot\Desktop\1040\u-boot-gcr-jun14.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 0x00002000 bytes to be programmed at 0xEFF40000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF42000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF44000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF46000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF48000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF4A000  

Executing program ....  

Program Command Succeeded   

Downloading 0x00002000 bytes to be programmed at 0xEFF4C000  

Error:  Program failed.  Can not read target memory at location: 0x0000000000004130.Please make sure that the chip selects are properly configured.

The CWPP response code is: CCSProtocolPlugin : Error writing memory

[CCS last error: Core not responding ].

Error: Program failed.Can not read target memory at location: 0x0000000000004130.

Please make sure that the chip selects are properly configured.

The CWPP response code is: CCSProtocolPlugin : Error writing memory

[CCS last error: Core not responding ].

 

 

suggest the solution for debugging this issue.

 

and check my NOR flash settings in below screenshot.. I checked by increasing the Target RAM size also.

153550_153550.pngpastedImage_3.png

 

Regards,

  suresh kalepu

Labels (1)
Labels
0 Kudos
Reply
10 Replies

‎10-12-2016 07:03 AM
1,408 Views
shalakashinde
Contributor I

Hi Suresh,

I am getting the same error for PBL.bin file.

Is this error resolved?

What was the measure taken?

0 Kudos
Reply

‎06-21-2016 01:54 AM
1,408 Views
addiyi
NXP Employee
NXP Employee

Using to low jtag speed can cause this king of issues. I suspect the jtag speed because you are saying that pbl programming works fine.

Try also to check if pbl image is correctly programmed.

Adrian

0 Kudos
Reply

‎06-20-2016 10:34 PM
1,408 Views
addiyi
NXP Employee
NXP Employee

Did you change the jtag clock speed? What jtag speed are you using?

Adrian

0 Kudos
Reply

‎06-21-2016 01:18 AM
1,408 Views
sureshk
Contributor II

Hi Adrian,

    I tested with JTag speeds 4MHz and 12.5MHz. Still we are getting errors..

Thanks,

suresh k

0 Kudos
Reply

‎06-16-2016 11:29 PM
1,408 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello suresh kalepu,

I suspect there is problem with DDR controller initialization or the DDR is not stable.

I suggest you use SRAM initialization file (CPC as SRAM).

When you create a bare board project, please select Downlaod/Connect SRAM launch configuration, and use it to connect to the target board and execute flash programming tasks.


Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

‎06-17-2016 04:24 AM
1,408 Views
sureshk
Contributor II

Hi Wang,

       I am able to connect and download through DDR initialization .tcl file also. i am encountering this error when trying to fuse the NOR flash. with SRAM tcl file also i am getting errors.

        This error  also not consistent , mostly coming while fusing the uboot.bin

After frequent trials (approx. 10) once i am able fuse the UBoot file.

Thanks.

Regards,

  suresh kalepu

0 Kudos
Reply

‎06-24-2016 04:01 AM
1,408 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello suresh kalepu,

It's seems that this problem is caused by unstable hardware or IFC timing configuration(in tcl script).

I suggest you boot up the target board, and do more verification to do NOR flash programming under u-boot.


Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

‎07-21-2016 05:23 AM
1,408 Views
sureshk
Contributor II

Hi Yiping,

       I set the JTAG clk speed in CW to 1000kHz and able to fuse the NOR flash without errors. I thing JTAG clk speed is the issue.

Regards,

  suresh k

0 Kudos
Reply

‎06-14-2016 04:10 AM
1,408 Views
addiyi
NXP Employee
NXP Employee

Try using "Erase sectors before program" when you set Program action.

Adrian

0 Kudos
Reply

‎06-17-2016 03:56 AM
1,408 Views
sureshk
Contributor II

Hi Adrian,

       I am erasing the sectors before programming..You can check the same in screenshot..

Thank you.

Regards,

   suresh kalepu

0 Kudos
Reply