topic Re: HCS08 Flash Programmer for USBDM in OSBDM and TBDML

HCS08 Flash Programmer for USBDM

pgo — Tue, 08 Dec 2009 14:04:27 GMT

Dear All,

Attached is a stand-alone Flash programming utility for HCS08 devices.

Features

Command line usage is available for batch files.
GUI usage is available for interactive use.
Supports most HCS08 chips (Paged memory is not supported).
Trimming of internal target clock to specified frequency.
Programming of security options to leave the chip unsecured or secured after programming.
May be used to unsecure chips (by mass erase).
The code has been written in a modular fashion. It should be straightforward to re-use the flash programming code to create other custom programming utilities.

I have tested it on a range of devices and I have found no (more) bugs. However, no guarantees are given!

bye

1. Installation_1_0_3.zip

2. Source_1_0_3.zip

Message Edited by t.dowe on 2009-12-08 09:28 AM

Re: HCS08 Flash Programmer for USBDM

Obetz — Tue, 08 Dec 2009 22:09:17 GMT

Nice work!

Does it use the new USBDM 2.0 API? Can it be used with OSBDM?

Oliver

Re: HCS08 Flash Programmer for USBDM

pgo — Wed, 09 Dec 2009 08:00:16 GMT

Dear Obetz,

It uses the new USBDM V2 API so isn't usable with the earlier versions.

Sorry!

I'll consider back-porting it later but there are other things that should be done first (e.g. paged addressing) and I would like to try improving the clock trimming accuracy.

bye

Re: HCS08 Flash Programmer for USBDM

Obetz — Wed, 09 Dec 2009 16:54:17 GMT

Hello pgo,

thanks for the fast reply.

One more question: I don't see any options for the target supply voltage selection, do you intend to use the target supply present in the JM based hardware?

This would be very convenient for batch programming.

Oliver

Re: HCS08 Flash Programmer for USBDM

pgo — Tue, 15 Dec 2009 11:00:13 GMT

Dear Obetz,

The usual USBDM dialogue will open to configure the the target voltage etc. even if using a batch file.

However, there is a crude workaround. The dialogue now contains an option to "not ask again" i.e. the dialogue will not re-appear. You have to delete the config file to restore the dialogue!

Your suggestion is very good. I will add options to control the target power when I have time.

bye

Message Edited by pgo on 2009-12-15 02:00 PM

Re: HCS08 Flash Programmer for USBDM

osorakunakamori — Tue, 09 Feb 2010 04:15:10 GMT

Dear pgo,

Wow! Very nice work. This is terrific!!

Question - what do you think it takes to enhance it to support JM128 flash programming?

Thanks

Re: HCS08 Flash Programmer for USBDM

pgo — Tue, 09 Feb 2010 07:36:26 GMT

Dear osoraku,

Do you mean MCF51JM?

I haven't looked at coldfire V1 yet. I'm currently doing a HCS12 version.

It wouldn't be too hard I expect. It depends on how uniform the Flash and Clocks are between the different Coldfire chips. There are also some memory configuration issues that don't exist in the HCS08 chips.

So - on the list but not very soon.

"The list"

Paged memory support for HCS08 (e.g. AC128) - done but needs more thorough testing

HCS12 programming - partially done but has some issues with non-uniform BDM interfaces and security.

Coldfire V1 - not started.

bye

Message Edited by pgo on 2010-02-09 10:37 AM

Re: HCS08 Flash Programmer for USBDM

osorakunakamori — Wed, 10 Feb 2010 04:31:53 GMT

Dear pgo,

Thanks for your response. You are right, I was referring to CF v1.

Thanks again for all the great work.

Re: HCS08 Flash Programmer for USBDM

osorakunakamori — Wed, 10 Feb 2010 05:04:36 GMT

Dear pgo,

Another question - does the flash program in the constant byte array "flashProgram[]" come from the coldfire project in HCSO8_FlashProgramming? I was trying to compare the code in the s-record file to the bytes in the array ... they start out the same but soon diverge. What process did you use to create the contents of flashProgram[] ?

Thanks.

Re: HCS08 Flash Programmer for USBDM

pgo — Wed, 10 Feb 2010 08:52:45 GMT

Dear Osaraku,

The source code for the routine is provided as part of the Codewarrior project (HCS08_FlashProgramming.rar) included in the Zip file.

It's based on some app note on Flash programming or something - I can't remember! It's pretty trivial though.

I don't know what "coldfire project in HCSO8_FlashProgramming" is

bye

Re: HCS08 Flash Programmer for USBDM

osorakunakamori — Wed, 10 Feb 2010 09:23:19 GMT

Dear pgo,

Oops .. I meant "Codewarrior project in (directory) HCS08_FlashProgramming".

My point was just that I don't understand why the code in the s-record file for this project doesn't match the code in your constant byte array. Thus I was trying to figure out how one gets the proper definition of the constant byte array from the output of the Codewarrior project. Doea it need massaging in some way?

Thanks!

Re: HCS08 Flash Programmer for USBDM

pgo — Wed, 10 Feb 2010 15:08:20 GMT

Dear osaraku,

From memory, there is some pre-amble code that's commented out and it's relocated to origin $0000. It may have another origin for testing.

The code is further patched on-the-fly by the C program execution. The table (dc.w?) in the assembly code is the list of addresses needing patching.

I hope this is clear.

bye

Message Edited by pgo on 2010-02-10 06:09 PM

Re: HCS08 Flash Programmer for USBDM

mov — Fri, 12 Mar 2010 22:14:24 GMT

Hi, pgo!

Thank you for great work!

When i try to recompile source of FlashProgrammer - i got an error in line #include "USBDM_API.h" - no such file. Can you add this header to sources for me and other peoples, who whish recompile project.

Regards, mov.

Re: HCS08 Flash Programmer for USBDM

pgo — Sat, 13 Mar 2010 18:01:10 GMT

Dear mov,

The header file is part of USBDM available here:

USBDM - Version 2 (JS16/JMxx Versions)

I prefer to distribute it in this way as it should track any changes in the DLL.

You will probably need the DLL to link against as well.

bye

Re: HCS08 Flash Programmer for USBDM

mov — Sun, 14 Mar 2010 00:18:55 GMT

Dear, pgo!

Thank you for fast reply!

Yes, i need the DLL to link. But i can't find configuration "USBDM Debug DLL" in project "USBDM_DLL_V2" which the referenced in the project "FlashProgrammer". When i try to link library from

"1. Installation_1_0_3" - got some errors "undefined reference to " `USBDM_ConfigureDialog' and `USBDM_GetErrorString'. The same error occurs when i try to link renamed DLL's from USBDM_DLL_V2 project. Looks like a missing declarations in "USBDM_API.h".

Please help me with this problem.

Re: HCS08 Flash Programmer for USBDM

pgo — Sun, 14 Mar 2010 08:32:31 GMT

Dear mov,

Sorry! I overlooked the fact that the programmer software has a later version of the USBDM.dll.

Attached is the required header file (I hope) along with corresponding DLLs to ensure that they are consistent.

bye

Re: HCS08 Flash Programmer for USBDM

mov — Sun, 14 Mar 2010 14:04:10 GMT

Thank you very much, pgo! Now building done ok.

mov

Re: HCS08 Flash Programmer for USBDM

joncas — Thu, 06 May 2010 16:46:45 GMT

Hello PGO,

thank you again for another great utility!

The only problem I run into is that the stand-alone flashprogrammer seems not able to unsecure chips.Even using the reset line and cycling the target power doesn't succeed -- it gives an error that it can't communicate with the target.

In the Hiwave debugger when launched from Codewarrior 6.3 also one has to first explicitly choose the "Unsecure" command in the HCS08 Open Source BDM menu in order to be able to reprogram a target.

Is there some way to achieve this automatically when needed by modifying the command files, and how could one unsecure chips with the standalone utility (i.e., have the standalone utility do what the unsecure.cmd does from Hiwave) ?

Many thanks and best regards!

Robert

Re: HCS08 Flash Programmer for USBDM

pgo — Fri, 07 May 2010 08:00:55 GMT

Dear joncas,

The programming utility should unsecure the chip without any special action required.

It really sounds like a connection problem rather than an unsecuring problem.

Can you provide the following information and I will try to figure out what is happening:

What HCS08 chip is being programmed?
Can the utility program a blank or unsecured chip?
Can the utility detect the device SDID and select the correct device?
What is your BDM hardware?
What is you BDM firmware & DLL version numbers (reported on the USBDM connection dialogue)?
Does the "cycle power" dialogue appear?

bye

Re: HCS08 Flash Programmer for USBDM

joncas — Fri, 07 May 2010 15:38:22 GMT

Hello PGO,

I found that it was my mistake : I was not correctly setting the Clock type and parameters!

The Flash Programmer is Version 1.0.3,

BDM firmware 2.0

DLL 3.1.1

BDM hardware is one I made myself with a JM60.

With a HCS08QE128 (SDID 0x1.015) or HCS08AC128 (SDID 0x0.01B) the SDID is read, but the device type is not recognized and so the Clock type is left on "External" which doesn't work. If I set it to S08ICSV3 it's ok for the QE128, and the AC128 uses S08ICGV4.

With a HCS08LG32 the device type is correctly set, so the clock is also configured automatically after clicking on "Detect SDID".

With the correct clock settings, all three work fine, even with a secured chip.

So, my apologies for taking your time...

When using the USBDM from Codewarrior 6.3 or 6.3.1 and Hiwave.exe with Open Source BDM dll v. 3.05, with a CF1 device a secure chip is automatically unsecured without any additional steps, but with the three HCS08 parts I tried one has to first manually select the "Unsecure..." command from the "HCS08 Open Source BDM" menu, otherwise one gets the error message "Error while loading diagnostic algorithm to target system. The chip may be secured or the derivative selected may be wrong."

But this is not a big deal, and it may be due some configuration setting I missed in the command files, but in case it's of any interest, I attach three gdi log files -- one of the failure when trying to program a secured device, one of the sucessful unsecure command, and one of the success programming of the unsecured device.

Many thanks for providing this great tool!