Re: change from GT16 to GT16A programming

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

Re: change from GT16 to GT16A programming

Jump to solution
1,365 Views
yyLeung
Contributor I

Dear all,

In past, we use codewarrior (ver. 5.6.1.1506 ) to program GT16 CPU and works fine. (But we need to select GT60 when programming and real-time debug). The hardware uses Zigbee module (MC13192 as external clk)

Now we need to change the CPU to GT16A. However, the program cannot be download to the CPU with the error as listed below

(Error loading programming algorithm – load aborted)

(Error occurred during Flash programming)

(ERROR 14 during programming!)

 

Then we try to select GT16 when programming the GT16 CPU and GT16A CPU. It can download into the CPU but halt while running in real-time debugger as listed below

STARTED
Frequency change to ~3910272hz.
RUNNING
HALTED

 

It stop at the DisableInterrupts command in start08.c  as listed below

void _Startup(void){

#ifdef __ELF_OBJECT_FILE_FORMAT__
  DisableInterrupts;  /* in HIWARE format, this is done in the prestart code */
#endif

 

If anyone can give me a hand.

regards

martin

 

Labels (1)
Tags (1)
0 Kudos
1 Solution
355 Views
peg
Senior Contributor IV
Hello Martin,

I believe the following may be your problem.
The flash programming algorithm for the GT16 contains a bug. This bug does not affect operation/programming with the GT16 but if you try to use it with a GT16A the bug will be exposed by changes that exist with the A version. Had the problem not been there the same algo would work for both.
So the answer is: Make sure you are using the GT16A algorithm with the GT16A

Some other posts on this for further research:

7187
6712
8006

View solution in original post

0 Kudos
1 Reply
356 Views
peg
Senior Contributor IV
Hello Martin,

I believe the following may be your problem.
The flash programming algorithm for the GT16 contains a bug. This bug does not affect operation/programming with the GT16 but if you try to use it with a GT16A the bug will be exposed by changes that exist with the A version. Had the problem not been there the same algo would work for both.
So the answer is: Make sure you are using the GT16A algorithm with the GT16A

Some other posts on this for further research:

7187
6712
8006

0 Kudos