erasing the page FF and page FD ?

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

erasing the page FF and page FD ?

2,078 Views
qinxk
Contributor I

Dear:

After erasing the page FF and page FD

when I launch the debug, the following error happen:

Communication with the target failed:  The target MCU has no clock or wrong BDM clock speed is used or derivative is secured.

 

 

 

 

0 Kudos
11 Replies

2,047 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi,

Page FF covers global 0x7F_C000 – 0x7F_FFFF address range that includes the Flash configuration filed and the Flash Security byte.

danielmartynek_1-1600850777524.png

I assume the MCU is secure, please try the Unsecure command.

danielmartynek_2-1600850785676.png

Thank you,

BR, Daniel

 

0 Kudos

1,740 Views
kef2
Senior Contributor IV

Obviously your project is for other than S12XE derivative or you crafted it to use wrong *unsecure*.cmd file. Here's exceprt form unsecure cmd for S12XE. See different divider settings, no ECLKDIV at all.

Edward

 

// ver 0.2 (28-Mar-06)
// HCS12XE Core erasing + unsecuring command file:
// These commands mass erase the chip then program the security byte to 0xFE (unsecured state).

DEFINEVALUEDLG "Information required to unsecure the device" "FCLKDIV" 17 "To unsecure the device, the command script needs \nthe correct value for the FCLKDIV onchip register.\n\nDatasheet proposed values:\n\noscillator frequency\tFCLKDIV value (decimal)\n\n 16 \tMHz\t\t17\n 12 \tMHz\t\t13\n 8 \tMHz\t\t9\n 4 \tMHz\t\t5\n"

0 Kudos

2,043 Views
qinxk
Contributor I

Thanks! Your answer is very helpful for me.

Unsecure is failure as follow:

image.png

Using default configuration: (Bus clk maybe 40MHz)

image.png

0 Kudos

2,035 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi,

Can you take a look at the project and read what was written to the ECLKDIV / FCLKDIV registers?

What is the frequency of the oscillator?

 

Thanks,

BR, Daniel

 

 

0 Kudos

2,028 Views
qinxk
Contributor I

ECLKDIV/FCLKDIV = 0x28

OSCCLK = 8MHz

0 Kudos

2,002 Views
qinxk
Contributor I

Yes!

0 Kudos

2,018 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi,

Have you tried with CLKDIV = 0x28 = 40?

 

BR, Daniel

0 Kudos

2,001 Views
qinxk
Contributor I

Hi, yes

It is still failure!

0 Kudos

1,936 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi,

If you use a PE Micro debugger or OSBDM, please use the Unsecure12 PE Micro tool:

http://www.pemicro.com/downloads/download_file.cfm?download_id=16

 

It should unlock the MCU.

 

Thank you,

BR, Daniel

 

0 Kudos

2,066 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello,

Which MCU do you use?

 

Thanks,

BR, Daniel

0 Kudos

2,058 Views
qinxk
Contributor I
Hi, MCU is MC9S12XDG128MAL
0 Kudos