LC60: How many instruction did my application use?

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

LC60: How many instruction did my application use?

跳至解决方案
2,414 次查看
BasePointer
Contributor II
Hi,
 
I'm using CW 6.1 and C for my LC60 application.
Can CW tell me how many instruction my application used?
Not program memory, I need instruction count.
 
Regards,
BP.
 
标签 (1)
标记 (1)
0 项奖励
回复
1 解答
1,251 次查看
CrasyCat
Specialist III
Hello
 
No this is not working either.
What you can do is either disassemble the .abs file and look at the listing file
or use the command DASM
 
1- Disassemble the abs file:
   - Open a Window Explorer window
   - Browse for {Install}\prog
   - Start Decoder.exe
  - Select "File" -> "Open" and select your .abs file name.
    The decoder will generate a file with extension .lst containing disassembled code of the application.
    As far as I remember the will will contains disassembly listing of all code and constant sections.
     
  You can also start the decoder from the command line if you prefer.
 
2- Use command DASM
    In order to disassemble code between 0x1870 and 0x19FF, enter the following commands in the
    command window:
      LF logfile.txt
      DASM 0x1870..0x19FF
      NOLF
 
   From the MAP file you can retrieve the start and end address of the memory areas used by the application.
 
I hope this helps.
 
CrasyCat

在原帖中查看解决方案

0 项奖励
回复
3 回复数
1,251 次查看
CrasyCat
Specialist III
Hello
 
I am not aware of such a feature.
Why do you need to know that?
 
CrasyCat
0 项奖励
回复
1,251 次查看
BasePointer
Contributor II
Hi,
 
I want to compare it with other companies requirements.
Can I save or export assembly window in hi-ware?
 
10x,
BP.
0 项奖励
回复
1,252 次查看
CrasyCat
Specialist III
Hello
 
No this is not working either.
What you can do is either disassemble the .abs file and look at the listing file
or use the command DASM
 
1- Disassemble the abs file:
   - Open a Window Explorer window
   - Browse for {Install}\prog
   - Start Decoder.exe
  - Select "File" -> "Open" and select your .abs file name.
    The decoder will generate a file with extension .lst containing disassembled code of the application.
    As far as I remember the will will contains disassembly listing of all code and constant sections.
     
  You can also start the decoder from the command line if you prefer.
 
2- Use command DASM
    In order to disassemble code between 0x1870 and 0x19FF, enter the following commands in the
    command window:
      LF logfile.txt
      DASM 0x1870..0x19FF
      NOLF
 
   From the MAP file you can retrieve the start and end address of the memory areas used by the application.
 
I hope this helps.
 
CrasyCat
0 项奖励
回复