search

kevinpt / opbasm

Open PicoBlaze Assembler
http://kevinpt.github.io/opbasm/
MIT License
60 stars 13 forks source link

KCPSM6.exe assembler log file compatibly #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello again,

I wrote some python scripts to parse the KCPSM6.exe log file. In particular I 
annotated the source code with special comments to mark the beginning and 
ending of a subroutine.

;; function _lcd_writebyte
_lcd_writebyte:   LOAD Reg_Tmp0, Reg_Arg0
                  [...]
                  Return
;; end function

These lines also appear in the (formated) log file. KCPSM6.exe places the 
current instruction address in front of every line. Your opbasm prints this 
addresses only in front of real instructions.

Would it be possible to add the (next) instruction address in front of every 
log line for compatibly?

-----------
I use these 'function' - 'end function' markers to find the start and end 
address of subroutines, which I translate into a VHDL package as a simulation 
helper and into a token file as a chipscope helper.

See PicoBlaze Forum for more information on this topic:
http://forums.xilinx.com/t5/PicoBlaze/Contribution-of-PicoBlaze-add-ons/td-p/446
556

Original issue reported on code.google.com by Paebbels on 24 Jul 2014 at 6:02

GoogleCodeExporter commented 9 years ago 
I have updated the code in the Mercurial repository to put addresses on 
non-instruction lines in the log file. This will permit your log parsing script 
to work as with KCPSM6. You can retrieve it from the repository for use now or 
wait a week or two until I make another formal release.

Original comment by kevin.thibedeau on 28 Jul 2014 at 3:41