How to use burner.bbl files in CW 10.1?

[ignisuti]

I added burner.bbl file in my Project_Settings > Linker_Files folder with the following code.

OPENFILE "%ABS_FILE%.s19" format=motorola busWidth=1 origin=0 len=0x1000000 destination=0 SRECORD=Sx SENDBYTE 1 "%ABS_FILE%" CLOSE format=intel OPENFILE "%ABS_FILE%.hex" SENDBYTE 1 "%ABS_FILE%" CLOSE

My goal is to get my project to output .hex files everytime I click the build button. What do I need to do to associate CW 10.1 with this burner.bbl file?

I'm pretty new to this. So, please bare with me if I'm way off base here.

[CrasyCat]

Hello

That mainly depends on the microcontroller you are targeting.

If your target is a HC08, HCS08 or RS08 MCU the bbl file is processed automatically at the end of the build process.

If your target is anything else then you need to associate a post build step to your project.

1. Create a batch file where you specify the command line to start the burner.exe in batch mode.
2. Open the project properties dialog. 
3. On the right hand side of the dialog, select Settings panel. 
4. Select the Build Steps tab.
5. Specify the name of the .bat file where you have embedded the call to the burner utility.

Keep in mind that current directory when you are building is the Build location specified in the project properties C/C++ Build panel. You may need to adjust the path so that the IDE can retrieve the .bat file relative to this location.

For example:
    My project is in D:\Freescale\Work\Eclipse\testcbe\testpostbuild
   My build location is D:\Freescale\Work\Eclipse\testcbe\testpostbuild\Debug
   My batch file is located in D:\Freescale\Work\Eclipse\testcbe\testpostbuild and is called postb.bat.

   My post build command is therefore ..\postb.bat.

CrasyCat

[ignisuti]

Thanks. I'm getting it to build a .hex file now, but not exactly what I was looking for. We have a file that converts S19 files into Hex files that we then use to load onto our microcontrollers. However, I guess there's more to it then than as our hex files don't look even close to the ones created by the Burner utility. The burner utlities hex files don't load through our process.