I meets two questions through USBDM to debug MKE04Z128VLK4.

[wangbaode]

hi pgo,

I meets two questions through USBDM to debug MKE04Z128VLK4.

1,when i use ARM programmer to detect chip,MKE04Z128VLK4 is not a member of the result. result only contains MKE04Z8 and MKE04Z64.

and chip ID is 4280040.

2,when i use codewarrior to debug MKE04Z128,a error dialog comes out.

I think it's a new question.

[pgo]

Hi Wang,

Thanks, I'll update the installation file.

I'm a bit puzzled as the PA60 is meant to have an ID of 0x0000.  It looks like there is actually a bug causing it to use the PT60 ID which it is aliased to.

bye

[pgo · Accepted solution]

Hi Wang,

there is an error in the arm_device.xml file.  Please find the entry for MKE04Z128M4 and change the 1st two digits of the sdid value to match the one your quoted.

e.g.

<sdid value="0x04000000" />

(only the 1st two digits are used 04 => MKE04xxx)

Let me know if this works for both cases.

bye

[wangbaode]

Hi pgo,

according to your suggestion. I change the sdid value as 0x04280040. USBDM works well.ARM programmer can detect MKE04Z128VLK4,and codewarrior can debug the chip through USBDM.

but USBDM still can't debug PA60.can i change sdid like MKE04Z128 to detect PAxx?

thanks.

[wangbaode]

hi pgo,

according to the way of MKE04Z128VLK4,I open hcs08_device.xml and find the entry of PT60.

I find the <sdid value="0x2040" />.but according to detected result,the id of pA60 is 0x4040.so I update the sdid as 0x4040.

I retry to detect MC9S08PA60.It's surprising that USBDM can detect pt60 and codewarrior can debug the chip.

so I think it's a mistake.could you recorrect the errors for a new version.

bye