LC60: How many instruction did my application use?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LC60: How many instruction did my application use?

ソリューションへジャンプ
2,427件の閲覧回数
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,264件の閲覧回数
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,264件の閲覧回数
CrasyCat
Specialist III
Hello
 
I am not aware of such a feature.
Why do you need to know that?
 
CrasyCat
0 件の賞賛
返信
1,264件の閲覧回数
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,265件の閲覧回数
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 件の賞賛
返信