topic Re: Fail to program FXTH87xx11 using USBDM in OSBDM and TBDML

Fail to program FXTH87xx11 using USBDM

sunrme — Tue, 09 Dec 2014 04:04:41 GMT

Hi all,

I tried to use USBDM to program the FXTH87xx . But in the list of chips in Flash Programmer this MCU is absent. So, I insert this in the hcs08_devices.xml:

<!ENTITY HCS08-alt-load-flash SYSTEM "HCS08/FXTH87xx11_Starter_Project_CW10.abs.s19">

&HCS08-alt-load-flash;

</flashProgram>

</memory>

</memory>

</device>

I'm not sure thay I use right values especially securityEntryRef section. But now flash Programmer detect my chip. But when I click Program Flash, on EraseMass status pop up error:

Hope someone can help me.

Regards

Re: Fail to program FXTH87xx11 using USBDM

sunrme — Wed, 10 Dec 2014 06:11:03 GMT

I attached log files, mb it will help

Re: Fail to program FXTH87xx11 using USBDM

georgepeterson — Thu, 11 Dec 2014 23:20:52 GMT

There does not seem to be much support for this device on the forum.

Re: Re: Fail to program FXTH87xx11 using USBDM

pgo — Wed, 17 Dec 2014 15:25:45 GMT

Hi Sunrme,

The error message in the supplied log file is very strange and appears to have nothing to do with the device being programmed. That is, the error should be impossible as it is complaining about a self check on the provided programming algorithm.

Could you please update to a more current version of USBDM as the one indicated in the log file is quite old.

http://sourceforge.net/projects/usbdm/files/Version%204.10.6/Software/

You will also need to update the BDM firmware.

And then try adding the following to the HCS08 config file and repost the logs please. This is basically the same as you suggested.

<device family="HCS08" name="FXTH87xx11">

<memory type="ram">

<memoryRange start="0x000090" size="0x28F" />

</memory>

<memory registerAddress="0x1820" type="flash" securityAddress="0xDFFB">

<securityEntryRef ref="HCS08-fnored-security" />

<memoryRange start="0x00C000" end="0x00DFFB" />

</memory>

<sdid value="0x0000" />

<flashProgramRef ref="HCS08-alt-load-flash-program" />

<note>Untested</note>

</device>

Re: Re: Re: Fail to program FXTH87xx11 using USBDM

sunrme — Thu, 18 Dec 2014 01:15:41 GMT

Hi pgo,

I updated firmware to Ver 4.10.6 and USBDM to 4.10.6.230. I added your configuration, but changed ssid from 0x0000 to 0x00C2, because after click detect chip, chip is not determined by the USBDM FLASH PROGRAMMER. And get the same issue, logs attached.

Re: Fail to program FXTH87xx11 using USBDM

pgo — Thu, 18 Dec 2014 06:00:58 GMT

Hi Sumne,

I mistyped - Could you change the RAM "size" to "end" as in you example.

bye

Re: Re: Fail to program FXTH87xx11 using USBDM

sunrme — Mon, 22 Dec 2014 04:30:01 GMT

Hi pgo,

I changed "size" to "end" and got this:

Re: Re: Re: Fail to program FXTH87xx11 using USBDM

pgo — Mon, 22 Dec 2014 06:21:14 GMT

Hi Sunme,

The log file indicates that you are trying to program the region [0x00DFFC..0x00E00A] (at least) which is not inside the area of Flash that is meant to be usually modified which is limited to

[0xC000..0xDFFF].

Where is you image file coming from? Does it contain the FXTH87xx on-chip routines as well as the new firmware you want to load?

If you wish to re-program the ENTIRE chip including overwritting the on-chip routine then the memory map would need to be modified.

If you can post the .sx file I can inspect it if you want.

PS. The above is based on my very limited understanding of the FXTH chip.

bye

Log file:

1.00:                          FlashProgrammer::doFlashBlock(): Exit ================

-0.00:                          FlashProgrammer::doFlashBlock(): Entry ===============

-0.00:                          FlashProgrammer::doFlashBlock(): op=OpBlankCheck, [0x00DFFC..0x00E00A]

-0.00:                          FlashProgrammer::doFlashBlock(): Checking RAM[0x000090..0x00028F]...

-0.00:                          FlashProgrammer::doFlashBlock():   ...Not in this region

-0.00:                          FlashProgrammer::doFlashBlock(): Checking FLASH[0x00C000..0x00DFFB]...

-0.00:                          FlashProgrammer::doFlashBlock():   ...Not in this region

-0.00:                          FlashProgrammer::doFlashBlock(): Block -|-[0x00DFFC...] is not within target memory.

Re: Re: Re: Re: Fail to program FXTH87xx11 using USBDM

sunrme — Mon, 22 Dec 2014 06:35:52 GMT

Hi pgo,

I created an empty project, built it and try to flash. I don't have *.sx file, codeWarrior generated *.s19 file (attached).

Re: Fail to program FXTH87xx11 using USBDM

pgo — Tue, 23 Dec 2014 01:11:30 GMT

Hi Sunrme,

Could you change the end address in the XML file to 0xDFFF as it appears that there is a pseudo-vector table to be programmed as well. Also remove the references to security - in other words use the following:

<device family="HCS08" name="FXTH87xx11-Partial-Erase">

     <memory type="ram">

        <memoryRange start="0x000090" end="0x28F" />

     </memory>

        <memory registerAddress="0x1820" type="flash">

           <memoryRange start="0x00C000" end="0xDFFF" />

     </memory>

     <sdid value="0x002C" />

     <flashProgramRef ref="HCS08-alt-load-flash-program" />

     <note>Untested</note>

</device>

Make sure you select EraseSelective when programming.

bye

Re: Fail to program FXTH87xx11 using USBDM

georgepeterson — Tue, 23 Dec 2014 01:36:14 GMT

There appears to be some factory code in Flash that is needed, but unprotected.

I tried to reprogram my FXTH87 but before doing so I erased all of the user flash thinking this was safe. This effectively "bricked" the FXTH87 and made the TPMS functions unuseable. The problem seems to be that the erasing deleted NVOPT.

So I agree with only doing selective erase.

Re: Re: Fail to program FXTH87xx11 using USBDM

sunrme — Tue, 23 Dec 2014 01:58:00 GMT

Hi pgo,

Thank you for your help, USBDM flashed FXTH87 finally. I changed hcs08_devices.xml, but don't change EraseMass to EraseSelective, because when selected EraseSelective, I got fail (I added logs).

And it relly be cool if I can to debug in codeWarrior this chip. And when I try to do this I got issue:

Error launching fxth87_empty FLASH

Bad arguments passed to function

If you will help me with this, I will be grateful. But I don't know where get logs, only what generated CW (attached)

Re: Re: Fail to program FXTH87xx11 using USBDM

sunrme — Tue, 23 Dec 2014 02:07:36 GMT

Hi George,

I am so surprised about this unprotected code in Flash memory. So I think that, I already "bricked" my only two samples :smileycry:. So I can't to reprogram this memory range?

Are you using USBDM for flash and debug? Could you show settings that you using for this in the hcs08_devices.xml or may be some additional changes and settings. It will be really helpful.

Re: Re: Fail to program FXTH87xx11 using USBDM

georgepeterson — Tue, 23 Dec 2014 02:50:22 GMT

That was my experience; after I erased all flash, the FXTH87 could no longer use the firmware functions and I could not re-program it. If this is indeed the issue, I believe there is a way to restore the flash back to factory settings but I don't know how to do that.

I'm using the P&E debugger. The settings I'm using are straight from the Codewarrior help file (CW v10.6). I searched the help file for "flash programmer" and clicked on the top search result which walked me through the whole process.

Re: Fail to program FXTH87xx11 using USBDM

pgo — Tue, 23 Dec 2014 03:51:44 GMT

Hi Sunrme,

I have ordered a chip and if (big IF) I can mount it properly I will experiment with programming it.

It should be possible to debug as well with a bit of work - It may be necessary to add and image for the internal flash routines.

I will look at this in a while :smileyhappy:

bye

Re: Re: Fail to program FXTH87xx11 using USBDM

pgo — Tue, 23 Dec 2014 09:23:04 GMT

Follow-up

OK my sample arrived and with access to this I am able to do a proper job.

The first thing I did was create an image of the chip contents. This allows the chip to be returned to a "factory fresh" state if the firmware is accidentally erased.

Any way I have attached the following:

Image from a FXTH870511, FXTH870511_Image.sx I hope this is OK. If not Freescale can feel free to delete with accompanying rude words. I presume they won't object since the image is unprotected in the device and easily read.
Updated device file hcs08_devices.xml This adds three devices FXTH870000, FXTH87xx11-Full-Erase and FXTH87xx11
- FXTH870000 This is an alias for use with Codewarrior and doesn't appear in the stand-alone programmer.
- FXTH87xx11-Full-Erase This is a device entry that allows completely unprotected programming of the device. This can be used to re-program the device with the above image using mass-erase.
- FXTH87xx11 This is an entry that only allows programming the intended user area of the Flash. Due to limitations in the USBDM programmer it is not possible to prevent you from mass-erasing the device - You have to manually select selective erase.

Further tips:

To restore an accidentally erase device

Load the above image FXTH870511_Image.sx
Select Image for security
Select EraseMass
Program and verify to check it's OK

To program a user program (restricted to user flash area)

Load the above image file .....
Select Image for security
Select EraseSelective
Program and verify to check it's OK

To use with Codewarrior

Create project in usual way with a USBDM target interface.
Modify the USBDM options as shown below
- Security field from flash image (there won't be one)
- Selective erase (by sector)
You should be able to debug in the usual fashion

PS. Want to see the prototype? I can't really see it lasting long inside a tyre!

bye

Re: Fail to program FXTH87xx11 using USBDM

georgepeterson — Tue, 23 Dec 2014 20:50:39 GMT

Good stuff Pgo; I hope that will get Sunrme sorted.

Btw nice sample; looks like you need to clean the solder flux with isopropyl alcohol though. Sometimes leftover flux can get to a state where it shorts pins.

Re: Fail to program FXTH87xx11 using USBDM

sunrme — Tue, 23 Dec 2014 23:57:31 GMT

Hi pgo,

Actually I don't know how to thank you. Everything works greate, devices alive, debug works correctly, so really big THANK YOU!

Re: Re: Fail to program FXTH87xx11 using USBDM

pgo — Wed, 24 Dec 2014 06:35:50 GMT

Hi George,

Yes it was a recycled board and was the victim of using solder-wick to remove move the connector.

I've changed the picture to post cleaning - still not a work of art but it's been a long time since I did aerial wiring.

bye

Re: Re: Fail to program FXTH87xx11 using USBDM

pgo — Wed, 24 Dec 2014 06:36:39 GMT

You're welcome sunrme,

Thanks for letting me know it works.

bye

	<!--
	====================================================================================
	Experimental
	-->
	<device family="HCS08" name="FXTH87xx11">
	<memory type="ram">
	<memoryRange start="0x000090" size="0x28F" />
	</memory>
	<memory registerAddress="0x1820" type="flash" securityAddress="0xDFFB">
	<securityEntryRef ref="HCS08-fnored-security" />
	<memoryRange start="0x00C000" end="0x00DFFB" />
	</memory>
	<sdid value="0x0000" />
	<flashProgramRef ref="HCS08-alt-load-flash-program" />
	<note>Untested</note>
	</device>
	<!--
	====================================================================================
	Experimental
	-->

	1.00:	FlashProgrammer::doFlashBlock(): Exit ================
	-0.00:	FlashProgrammer::doFlashBlock(): Entry ===============
	-0.00:	FlashProgrammer::doFlashBlock(): op=OpBlankCheck, [0x00DFFC..0x00E00A]
	-0.00:	FlashProgrammer::doFlashBlock(): Checking RAM[0x000090..0x00028F]...
	-0.00:	FlashProgrammer::doFlashBlock(): ...Not in this region
	-0.00:	FlashProgrammer::doFlashBlock(): Checking FLASH[0x00C000..0x00DFFB]...
	-0.00:	FlashProgrammer::doFlashBlock(): ...Not in this region
	-0.00:	FlashProgrammer::doFlashBlock(): Block -\|-[0x00DFFC...] is not within target memory.

	<device family="HCS08" name="FXTH87xx11-Partial-Erase">
	<memory type="ram">
	<memoryRange start="0x000090" end="0x28F" />
	</memory>
	<memory registerAddress="0x1820" type="flash">
	<memoryRange start="0x00C000" end="0xDFFF" />
	</memory>
	<sdid value="0x002C" />
	<flashProgramRef ref="HCS08-alt-load-flash-program" />
	<note>Untested</note>
	</device>