Impossible to program 9S08QE64 Demo with CPROGHCS08 programmer. What is wrong?

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

Impossible to program 9S08QE64 Demo with CPROGHCS08 programmer. What is wrong?

2,326 Views
robert2000
Contributor II

I am usual of CodeWarrior Development Studio for HC08 family. I am now starting with HCS08 family.

For that, I am using :

           - MC9S08QE64

           - USB MULTILINK Interface Revision C

           - CodeWarrior 6.0

           - Software Demo QE64 Assembler

 

I am observing the following when I try to program the device with the HCS08 P&E Multilink/Cyclone Pro Connection:

           - First try after connection Error 14 happen

- After Abort Postload command file correctly executed

           - Connection looks OK: I can modify any port with debbugger

           - Executing again loading of QE64 Demo . The CPROGHCS08 programmer (Version 1.49) Status Window shows the following:

Windows NT detected

Ethernet functionnality not enabled; Socket Error #10065 No route to host

Copyright 1999,2000 P&E Microcomputer Systems, Inc

 

CMD>RE

USB HCS08/HCS12 MULTILINK detected -Flash Version 5.67

Initializing. Target has been RESET and is active

 

CMD>CM C:\Program Files\Freescale\CodeWarrior for Microcontrllers V6.0\prog\P&E\9S08QE64.S8P

USB HCS08/HCS12 MULTILINK detected -Flash Version 5.67

Initializing.(Recommended TRIM=$00B1,FTRIM=0) (Bus Freq=7968khz) Initialized

;version 0.04 ALPHA 01/08/2007, copyright P&E Microcomputer Systems, www.pemicro.com [9s08qe64]

;device Freescale, 9S08QE64, All

;begin-cs

Loading programming algorithm... Done.(FCDIV=$AC)

 

CMD>FM

Erasing. /

 

 

The / after Erasing is continously turning . The system keep this state and never goes to the next step.

 

So it is impossible to program. What is wrong?

Labels (1)
0 Kudos
6 Replies

530 Views
J2MEJediMaster
Specialist I
Are you really running CodeWarrior 6.0 on Windows NT, or is that just the software calling it wrong? According to the spec sheet, the required operating systems are Win 2K/Win XP/Vista.

---Tom

0 Kudos

530 Views
robert2000
Contributor II
Tom,
Thanks for your reply.
I am not running CodeWarrior on Windows NT but on Windows XP
But the debbuger is writing WindowsNT  in the status window???
Best regards
Robert
0 Kudos

530 Views
peg
Senior Contributor IV
Hello Robert,

You presumably don't have a demo board with onboard BDM interface? (Like the 128 demo)

The P&E software DOES report WinXP as NT if you look at the copyright date 2 lines below you can get an idea why.

Why are you not using the latest CodeWarrior?

Is this a self made board that the QE64 is on? Is it known to work?

What is this "Software Demo QE64 Assembler"?



0 Kudos

530 Views
robert2000
Contributor II
Hello Peg
 
Right: I don't have a demo board with onboard BDM interface. The application board is very small and I have a cable about 25cm long from the BDM connector to the board.
That is may be the issue. I will mofify this first and then I will look to the different software upgrade.
 
Thanks a lot and best regards
 
Robert
0 Kudos

530 Views
peg
Senior Contributor IV
Hello again Robert,

As well as, or because of, the not so current version of CodeWarrior you are using not very current firmware in your USBBDM current is 5.72 (or even 5.77 as noted in another post today).
Also it is using an alpha version of the algorithm, V1.01 is current.

5.72 firmware along with 1.01 algo DOES work. I am not saying the combination you are using doesn't, but you may as well update anyway. If you want to use CodeWarrior updating to the latest version will probably update to these (or later) in one fell swoop.
If not or if it doesn't both of these versions are available from P&E.
P.S. I don't use CodeWarrior but P&E standalone tools.
0 Kudos

530 Views
robert2000
Contributor II
Hello Peg,
 
This is the result of my different experiences:
 
1)Put a BDM connector close the board: No change still wrong
2)Upgrade P$E firmware in my USBBDM current  5.77 : No change still wrong
3)Upgrade CodeWarrior software to 6.2: The debbuger is working fine.
 
Thanks again for your advices and best Regards
 
Robert
0 Kudos