another bug of USBDM?

[wangbaode]

Hi pgo.

I think i find another bug of usbdm.

I'm using usbdm to debug MKE02Z64. In my project,I use EEPROM of KE02.when i debug through usbdm.I find there is nothing in EEPROM address.

I think in EEPROM ,0xff should be filled.

bye

[pgo]

Hi Wang,

There are two things preventing this showing the correct values:

• Codewarrior appears to be accessing the memory as long words (4-bytes). This is not working.  The EEPROM only supports byte accesses.  It is necessary to edit the MKE02Z64.mem file and change as follows:

• The second problem is that USBDM tries to optimise memory accesses - This doesn't work correctly in this case so I will have to remove this optimisation.  You can replace the files in the ......\Freescale\CW MCU v10.6\MCU\bin\plugins\support\ARM\gdi directory with the attached files to do this.  These have not been tested very much so keep the original files in case you need to restore them.

Note: USBDM does not support programming the EEPROM.

bye

[wangbaode]

hi pgo,

I debug the same project through openSDA. the value in eeprom is right.

[pgo]

Hi Wang,

The current version of USBDM corrects the USBDM bug but I believe it will still require the fix to the MKE02Z64.mem file.

I'm surprised openSDA works without this change as it is a limitation of the target chip (I thought).

bye