No BDM-connection

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

No BDM-connection

Jump to solution
19,226 Views
thommes
Contributor III

Hello,

 

I'm using the Mc9s12d64 on a selfdesigned board. My Problem is, that i can't communicatewith the chip.

The NoICE-DEbugger reports the error:

"BDM validation failed: MODE=0xFF BDMSTAT: =xFF

This may indicate incorrect MOD setting (MODA and MODB must be grounded), that the pod cannot reset the target, or an incorrect bus speed setting"

 

I testet the Mod's anb both A and B are grounded.

When i start the communication the Reset-line goes low for 19,5ms then back to 5V, same with the BKGD-line! THe bus speed is set correct (16MHZ crystal => 8MHz Busspeedhttp://dict.leo.org/ende?lp=ende&p=DOKJAA&search=crystal&trestr=0x801). What can be the issue fpr this problem. The crystal also works fine (tested with oscillioscpoe). Can the microcontroller be broken? That would be the first time, this happened....


Please, please help me, because i have no more ideas where i can look for solutions.


Thanks and regards,


Thommes

Labels (1)
Tags (3)
1 Solution
18,011 Views
thommes
Contributor III

PROBLEM SOLVED!!!

The BKGD-Pin of the MCU was not connected to the PAD. But while meassuring the Pin was pushed against it so it was connected....

Thank you very very much for your time and help.

View solution in original post

0 Kudos
Reply
23 Replies
780 Views
RadekS
NXP Employee
NXP Employee

I am afraid that ComPOD12 is not directly supported under CW5.1.

CW5.1 offers these default connection options for S12D64:

Full Chip Simulation

P&E USB BDM Multilink

P&E Cyclone Pro (USB, Serial or TCPIP)

Softec HCS12

Abatron BDI

TBDML

HCS12 Serial Monitor

I believe that NoICE debugger should have some function for unsecure or at least some function for manual commands (for write to registers). In attachment you can find command file for unsecure procedure from CW. I hope that this command file is easy to understand (wb=write byte, ww=write word, syntax: wb address data)


0 Kudos
Reply
780 Views
thommes
Contributor III

Perhaps you can also tell me, WHY could the MCU be secured. I have never written any Code on the Chip....

0 Kudos
Reply
779 Views
RadekS
NXP Employee
NXP Employee

MCU can be accidentaly secured for example in case of violently termination during MCU programming.

There is security byte at address 0xFF0F. Default value is 0xFE. Any other value means that MCU will be secured after next reset. More details about security at S12(X) devices you can get from attached document.


0 Kudos
Reply