OSBDM and TBDMLのトピックRe: Verifying mc9s12xep768

Verifying mc9s12xep768

dflash — Sun, 22 Dec 2024 22:04:01 GMT

I have been able to use MemoryDump to read the p and d flash from chip mc9s12xep768 as detailed in this post:

https://community.nxp.com/t5/OSBDM-and-TBDML/Copying-mc9s12-flash-memory-with-usbdm/m-p/2008312#M3993

It would be interesting if there was a debug version of MemoryDump to see what it is doing.

However I have not been successful verifying with HC12S.

There are a number of things I've noticed.

Firstly it detects cc92 as an id. but according to the table that is not right:

TableID.png

and in this post with a similar chip it was cc94

https://community.nxp.com/t5/OSBDM-and-TBDML/Erasing-and-Flashing-mc9s12xep768/m-p/1754397

If this was so then the way it tries to access might be different causing it to fail. Perhaps this information is in hcs12_devices.xml.

If I unselect what HC12S id chooses and use xep 100 then it starts to read but gives the following message:

9s12_disagree.png

Secondly I have checked and a ceramic resonator appears to provide an 8MHz clock which I measured rather approximately on an oscilloscope - so I wondered what is the rate at which the processor BDM communicates with the usbdm device? - it seems 250KHz according to MemoryDump. otherwise if it was 4MHz then maybe my Dupont type leads are not sufficient.

There is only a decoupling capacitor on the reset pin on examination no external watchdog.

This is the message I get when HC12S chooses the processor xep linear cc92

9s12.png

Re: Verifying mc9s12xep768

pgo — Mon, 23 Dec 2024 13:11:21 GMT

Hi,

There is a debug version of Memory dump installed by the .deb.

The chip I have is a MC9S12XEP100 and identifies as CC94.

Note the info at the bottom of the table:

pgo_0-1734958815004.png

The last few bits are described as minor mask set revision and are ignored in the XML file (sdidMask).

Several SDID are treated as equivalent for MC9S12XEP100-family and MC9S12XEP-Linear:

An 8MHz clock leads to an BDM interface frequency of 4MHz.

The Communication Speed selection in memory dump is not used for HCS12. It is there for some other targets.

Really clutching at straws here but how long is the ribbon cable on the BDM?

Check for noise on the power supply.

bye

Re: Verifying mc9s12xep768

pgo — Mon, 23 Dec 2024 13:15:20 GMT

PS.

Memory dump uses generic HCS12 code and does not use the device data at all really.

bye

Re: Verifying mc9s12xep768

dflash — Mon, 23 Dec 2024 16:59:25 GMT

Hi
the leads are 8", there does not seem to be any significant noise on the power supply at least that I saw on the oscilloscope.

I wonder if there is a way to test the actual usbdm device.

It was new and I did update the Firmware to 4.12.2. The Firmware verify is as follows:

firmware.png