8-bit MicrocontrollersのトピックRe: Compiler Listings

Compiler Listings

bobw — Thu, 22 Apr 2010 03:33:53 GMT

For the life of me, I cannot get the compiler to generate listings for HCS08 and CFV1 using CW 10.0.

Anyone?

CrasyCat — Thu, 22 Apr 2010 19:15:43 GMT

Hello

There are 2 ways of achieving that:

1- If you want to check assembly code for a selected number of files:

- Open the source file in an edit window

- Click right inside of the edit window and select Disassemble. A new edit window is opened showing disassembly listing for selected file.

2- If you want to check assembly code for a all files within the project:

- Open the project Propertied dialog

- Go to theC/C++ Build -> Settings page

- Go to HCS08 Compiler -> General panel

- Add option -Lasm to the Other flags edit box

- Click on OK to save the changes

- Rebuild the application. You should see the generated .lst files in your build directory.

CrasyCat

bobw — Fri, 23 Apr 2010 01:15:11 GMT

Thanks CC.

What's confusing is that, in the Output options folder directly above the General folder, there is the following option:

"Generate Listing File (e.g. %n.lst)(-Lasm)" This lead me to believe the option should be set here.... -Lasm=%n.lst

This really needs some clarification, since compiler listings are OUTPUT options, not GENERAL options.

bobw — Fri, 23 Apr 2010 02:30:35 GMT

That worked for the HCS08. Thanks. Now how about for Coldfire?

CrasyCat — Fri, 23 Apr 2010 16:24:35 GMT

Hello

For Coldfire

1- If you want to check assembly code for a selected number of files:

- Open the source file in an edit window

- Click right inside of the edit window and select Disassemble. A new edit window is opened showing disassembly listing for selected file.

2- If you want to check assembly code for a all files within the project:

- Open the project Propertied dialog

- Go to theC/C++ Build -> Settings page

- Go to ColdFire-> Language Settings panel

- Add option -S to the Other flags edit box

- Click on OK to save the changes

- Rebuild the application. You should see the generated .s files in your build directory.

I have notified the doc team that this needs to be better documented.

CrasyCat