Sukandar Kartadinata

problem connecting to DEMO9S12XEP100

Discussion created by Sukandar Kartadinata on Aug 10, 2012

Hi,

I'm having problems connecting to the DEMO9S12XEP100.

I followed all steps in the User Manual.

The board in standalone mode works fine, i.e. potentiometer and light sensor can be mapped to the LEDs by pushing the buttons.

I installed CodeWarrior Development Studio for S12(X) V5.1

I installed CW12 V5.1 Processor Expert v3.04 Sevice Pack from the DVD

I installed the "Additional Components" from the SofTec CD (there was also a service pack on there related to version 4.5 which I didn't install)

Driver installation after connecting the board via USB worked fine - there's no exclamation mark next to the driver in the device manager.

 

Problems start when I select Project>Debug in CodeWarrior.

I get an error message: "Communication Error. Make sure the USB cable is connected to the instrument and retry"

 

I restarted the application as well as the system, but also get the same error.

Later I enabled "Show Protocol" and got this:

 

executing C_layout.hwl

!OPEN source 0 0 60 39
NO CONNECTION
!Source < attributes MARKS off
!OPEN assembly 60 0 40 31
!Assembly < attributes ADR on,CODE off,ABSADR on,SYMB off,TOPPC 0xF88C
!OPEN procedure 0 39 60 17
!Procedure < attributes VALUES on,TYPES off
!OPEN register 60 31 40 25
!Register < attributes FORMAT AUTO,COMPLEMENT None
!OPEN memory 60 56 40 22
!Memory < attributes FORMAT hex,COMPLEMENT None,WORD 1,ASC on,ADR on,ADDRESS 0x80
!OPEN data 0 56 60 22
!Data:1 < attributes SCOPE global,COMPLEMENT None,FORMAT Symb,MODE automatic,UPDATERATE 10,NAMEWIDTH 16
!OPEN data 0 78 60 22
!Data:2 < attributes SCOPE local,COMPLEMENT None,FORMAT Symb,MODE automatic,UPDATERATE 10,NAMEWIDTH 16
!OPEN command 60 78 40 22
!Command < attributes CACHESIZE 1000
!bckcolor 50331647
!font 'Courier New' 9 BLACK
!AUTOSIZE on
!ACTIVATE Data:2 Command Procedure Data:1 Source Register Assembly Memory
done C_layout.hwl

Loading Target ...
Communication settings:
SETCOMM DRIVER PROTOCOL NOPERIODICAL
Loading Communication DLL
==> C:\Programme\Freescale\CWS12v5.1\prog\gdi\softec_bdm12.dll
GDI: DiGdiOpen()==> DI_OK
GDI: DiGdiVersion()==> DI_OK
GDI: DiGdiGetFeatures()==> DI_OK
GDI: DiGdiAddCallBack(8192)==> DI_OK
GDI: DiGdiAddCallBack(16384)==> DI_OK
GDI: DiCommGetAcceptableSettings()==> 0
Initializing STARTUP command file:
CMDFILE STARTUP ON ".\cmd\SofTec_HCS12_startup.cmd"
Initializing RESET command file:
CMDFILE RESET ON ".\cmd\SofTec_HCS12_reset.cmd"
Initializing PRELOAD command file:
CMDFILE PRELOAD ON ".\cmd\SofTec_HCS12_preload.cmd"
Initializing POSTLOAD command file:
CMDFILE POSTLOAD ON ".\cmd\SofTec_HCS12_postload.cmd"
GDI: DiGdiInitIO()
GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_HASCOMMUNICATIONCMD)
GDI: DiGdiVersion()==> DI_OK

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)
==> DI_ERR_FATAL
GDI: DiErrorGetMessage()==> 1
GDI: Error Message ==> Communication error. Make sure that the USB cable is connected to the instrument and retry.
Initializing STARTUP command file:
CMDFILE STARTUP ON ".\cmd\SofTec_HCS12_startup.cmd"
Initializing RESET command file:
CMDFILE RESET ON ".\cmd\SofTec_HCS12_reset.cmd"
Initializing PRELOAD command file:
CMDFILE PRELOAD ON ".\cmd\SofTec_HCS12_preload.cmd"
Initializing POSTLOAD command file:
CMDFILE POSTLOAD ON ".\cmd\SofTec_HCS12_postload.cmd"
GDI: DiDirectCommand(communication)
GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)

GDI DLL called: DI_CB_MTWKS_EXTENSION_Callback(MTWKS_CB_PROJECTACCESS)
==> DI_OK
GDI: DiDirectReadNoWait()==> DI_OK
GDI: DiDirectAddMenuItem()==> DI_OK
Error: The debugger is currently not able to run
due to loss of contact with hardware.
No Link To Target

in>

Outcomes