topic Re: Post Linked: How to generate automatically s19 with burner in CodeWarrior for MCU

How to generate automatically s19 with burner

CecchiSandrone — Mon, 01 Oct 2007 19:08:11 GMT

Hi,

I read the docs about burner tool for CW. What that I want is to generate the s19 file at the end of the compiling and linking processing, automatically and without executing manually burner tool. I looked under the target options but there isn't an option to do this. Any ideas?

Re: How to generate automatically s19 with burner

CrasyCat — Mon, 01 Oct 2007 19:48:01 GMT

Hello

Is your application an ANSI C application or a relocatable assembly application?

If you create your project using the wizard, this will be done automatically.

After linking the burner will be invoked automatically and it will generate a file with extension .abs.s19 in the project bin directory.

CrasyCat

Re: How to generate automatically s19 with burner

CecchiSandrone — Mon, 01 Oct 2007 20:00:57 GMT

Mmm...in the bin folder I found a .sx file. Maybe it's the file generated, because it has the same size as another .s19 manually generated. The problem is that when I try to download to the device with the embedded bootloader I receive "Firmware download failed - mismatch found on address=0x1600".

Re: How to generate automatically s19 with burner

Alban — Mon, 01 Oct 2007 20:24:01 GMT

Hi,

SX extension is used because the format can be a S19 or a S2.
The content of the S-Record depends on your configuration of the S-Record in the Target Settings.
You can define what kind of S-Record you want to create and even its file name.

Cheers,
Alban.

Re: How to generate automatically s19 with burner

CecchiSandrone — Mon, 01 Oct 2007 20:42:03 GMT

Thanks Alban.

Where can I find settings S-record exactly? I'm using CW 5.7.0 but I can't find this option.

Re: How to generate automatically s19 with burner

BlackNight — Mon, 01 Oct 2007 20:50:43 GMT

Hello,
there is as well the linker option -B to generate an S-Record:
OUTPUT:
-B Generate S-Record file

Of course this does not allow you to finetune things as using the burner.exe.

See as well the other replies for your question: the burner.exe typically uses a .bbl (batch burner language) file as input.
If you are using e.g. a make file, you can use it on the burner.exe command line as well, or together with the burner.exe -F option.

Hope this helps.

Re: How to generate automatically s19 with burner

Alban — Mon, 01 Oct 2007 20:58:53 GMT

ALT+F7 --> Target --> Burner for HC12 --> Command Line Arguments

Post Linked: How to generate automatically s19 with burner

Alban — Mon, 01 Oct 2007 21:34:52 GMT

Notice for reader following this thread.

The hardware side is handled in
Re: MC13213 EVK - Embedded bootloader - Download apps without BDM programmer?
in the 8-Bit MCU board.

Cheers,
Alban.

Re: Post Linked: How to generate automatically s19 with burner

JimDon — Mon, 01 Oct 2007 23:26:41 GMT

Maybe I've missed some thing, but I thought he wanted to use the tool that talks to the embedded boot loader.
"The problem is that when I try to download to the device with the embedded bootloader I receive "Firmware download failed - mismatch found on address=0x1600"

Because I don't think that Burner.exe will talk to embedded boot loader.

And please clarify this - Is the error message you are getting is coming from the tool that came with the board and talks to embedded boot loader?

It is possible that the s-records generated by CW are not of the correct format for this tool, in which case you may need to run a bat file to convert them first. This can be done automatically at the end of the build.

But first lets clarify the problem.

Re: Post Linked: How to generate automatically s19 with burner

CecchiSandrone — Tue, 02 Oct 2007 00:04:06 GMT

Ok I try
After the build from CW I obtain a file .sx. To have a .s19 I tried to rename the .sx to a .s19 and even generating it from the .abs with burner tool.

In both cases I receive "Firmware download failed - mismatch found on address=0x1600".

Re: Post Linked: How to generate automatically s19 with burner

JimDon — Tue, 02 Oct 2007 00:54:00 GMT

ok, "burner tool" - the one that came with the board and talks to to embedded boot loader vis USB port?

- OR -

burner.exe that comes with Code Warrior ?

Re: How to generate automatically s19 with burner

CecchiSandrone — Tue, 02 Oct 2007 01:40:04 GMT

No I'm talking about burner.exe from CW. I don't know the first one. Maybe do you mean test tool?

Message Edited by Cecchi Sandrone on 2007-10-01 08:41 PM

Re: How to generate automatically s19 with burner

JimDon — Tue, 02 Oct 2007 02:29:11 GMT

Well, in your original post on the original thread you said:
"3) Download .s19 file via USB connection with test tool"

So, you are no longer trying to do things that way.

Ok, well first of all the the embedded bootloader is out of the picture, and you will be using the BDM with burner.exe. Also, pushing the buttons will not matter because the burner.exe will reset the board with the BDM when it burns.

I also think that you will need to set "Build Extras", "Use External Debugger" and fire off the burner from there. I have not used burner.exe myself, but I have used this method when I needed to do other things with the output.

Re: How to generate automatically s19 with burner

CecchiSandrone — Tue, 02 Oct 2007 02:59:11 GMT

Ah, maybe there's a little misunderstanding...

In that post (http://forums.freescale.com/freescale/board/message?board.id=CW816COMM&thread.id=3336) the problem is how to download an application to the board without using the BDM programmer.
In this post the question is how generate the .s19 from .abs automatically, during the CW build.
I hope that the two problems are more understandable now.

Message Edited by Cecchi Sandrone on 2007-10-01 10:00 PM

Re: How to generate automatically s19 with burner

peg — Tue, 02 Oct 2007 05:37:40 GMT

Hi,

Well as I said before here:

http://forums.freescale.com/freescale/board/message?board.id=CW816COMM&message.id=463

you should find the .s19 in the bin directory under your project as Project.abs.s19

The link that is now broken (probably due to the forum re-arrangement) was pointing out that s19 generation is an option and although it is on by default, maybe it has been switched off. Unfortunately as it works for me and I don't normally use CW, I can't help you with where it was.

Perhaps you can find it yourself or some one reading this can now assist you.

Of course this depends on whether I am on the right track with what you are asking.

Re: How to generate automatically s19 with burner

JimDon — Tue, 02 Oct 2007 08:17:18 GMT

Ya, your right I did totally misunderstand. Sorry.
Disregard that last post.

Now, are you still getting that error when you try to burn using the "test" tool ?
Because it could be that the s19 file generated from CW might not be correct format.

Re: How to generate automatically s19 with burner

CecchiSandrone — Tue, 02 Oct 2007 15:52:04 GMT

I tried to configure Burner for HC08 under target settings and you can see how from attached images. The problem is that I don't know how to set S19 record in the content tab. As you can see in the "Command file" tab the script generated is:

OPENFILE "%ABS_FILE%"
format=motorola
busWidth=1
origin=0
len=0x10000
destination=0
SRECORD=Sx
SENDBYTE 1 "%ABS_FILE%"
CLOSE

And it specifies SRECORD=Sx. Where can I find the correct SRECORD format for my platform?
Thanks

Edit: it seems that if I click on execute, in Burner for HC08 options, the file .abs.s19 is created. The problem with the download with embedded bootloader however persists (Firmware Download Failed - Mismatch found on address 0x1600). Maybe the .s19 generated must be compatible with Embedded Bootloader.

Message Edited by Cecchi Sandrone on 2007-10-02 11:12 AM

Message Edited by Cecchi Sandrone on 2007-10-02 11:19 AM

Re: How to generate automatically s19 with burner

CrasyCat — Tue, 02 Oct 2007 17:30:51 GMT

Hello

It looks like there are restriction on the kind of s record the bootloader can download.

Does the bootloader only support S1, S2 or S3 records?

Is there a limitation in the line length?

Does he have trouble with S0 records?

You can fine tune almost everything with the burner, but you need to know what you are expecting as output.

Additionally are you sure the address 0x1600 does not come twice in the S record file?

Is this address a valid FLASH address?

CrasyCat