The Museum of HP Calculators

HP Forum Archive 19

[ Return to Index | Top of Index ]

HEPAX VASM listing?
Message #1 Posted by Geir Isene on 4 Jan 2010, 11:07 a.m.

Has anyone seen the HEPAX VASM listings?

      
Re: HEPAX VASM listing?
Message #2 Posted by Meindert Kuipers on 4 Jan 2010, 12:47 p.m.,
in response to message #1 by Geir Isene

I do not think the commented sources exist, a disassembly listing is the best that can be done,

Meindert

      
And... (was: HEPAX VASM listing?)
Message #3 Posted by Vieira, Luiz C. (Brazil) on 4 Jan 2010, 12:59 p.m.,
in response to message #1 by Geir Isene

... MLDL´s disassembling is fast and configurable. I also added some extra XROM names in the XROM.TXT file to help debugging lists with self references.

Cheers.

Luiz (Brazil)

            
Re: And... (was: HEPAX VASM listing?)
Message #4 Posted by Geir Isene on 4 Jan 2010, 1:42 p.m.,
in response to message #3 by Vieira, Luiz C. (Brazil)

Could you send me?

                  
Re: And... (was: HEPAX VASM listing?)
Message #5 Posted by Vieira, Luiz C. (Brazil) on 4 Jan 2010, 2:01 p.m.,
in response to message #4 by Geir Isene

Hi, Geir;

if you see the ROM.TXT file that comes with the 1.50 and 1.51 versions of the mldl2k.exe you will see:

// File format:
// XROM 25,01 [FUNCTION] comment 
// File must be in same directory as executable
// All lines not starting with  XROM  are ignored and treated as comments
// Single or double quotes can be used. lines may be empty
// Spaces are treated as delimiters, use quotes when there are spaces in the name
// otherwise the quotes may be ignored
// XROM numbers must be 2 digits!
// Anything after the function name is printed as coment in the disassembly listing
// A label starting with : will be treated as the title of the XROM and will be used 
// as comment for functions that do not have their own comment. Do not use quotes here
// This type of label may be repeated and will be used for XROM's after it

// for example for group headings // the table is scanned sequentially // Extended Functions, XROM 25 XROM 25,00 :Extended Functions ROM XROM 25,00 "-EXT FCN 1C" XROM 25,01 "ALENG" XFUN: Returns numbers of chars in ALPHA XROM 25,02 ANUM XROM 25,03 APPCHR XROM 25,04 APPREC ....

The only thing you need to do is to add the listing with the XROM numbers and the names of the functions you need. Also, you can remove the list with the XROM you do not need. If you tell me which ones you need, I can add to the existing XROM.TXT and send it back to you. I actually added some XROM to the original and saved four different XROM.TXT files so far, each for an specific group of modules. The default comes with:
Extended Functions and CX Ext. Fcn (XROM 25)
TIME and CX TIME (XROM 26)
PRINTER 2E (XROM 29)
HPIL MASS ST and CTL FNS (XROM 28)
Extended IO Fcn (XROM 23)
PLOTTER (XROM 17 & XROM 18)
HP-IL DEV (XROM 22 & XROM 24)
WAND (XROM 27)
DAVID Assembler (XROM 02)
As you can see, there are no repeating XROM numbers, and I guess only the first occurrence would show up. I think these are Meindert´s first choices for a general purpose disassembling, but chances are that other XROM other than these ones appear, than I decided to modify the original XROM.TXT and suppress the ones I'd not use in some cases as I added others I would need. Let me know if you need a custom XROM.TXT and shich XROM functions you need listed.

Hope this helps.

Cheers.

Luiz (Brazil)

Edited: 4 Jan 2010, 2:03 p.m.

                        
Re: And... (was: HEPAX VASM listing?)
Message #6 Posted by Meindert Kuipers on 4 Jan 2010, 2:08 p.m.,
in response to message #5 by Vieira, Luiz C. (Brazil)

The disassembler uses a simple text search, and returns the first XROM match found, unless the XROM number is found in its own ROM, or in the other ROM in case of an 8K ROM, this always takes preference (or at least that is how it should be, but I realize now that I have never actually tested this ...). Of course, this only makes sense when disassembling user code.

The new version of the disassembler is even more configureable, and it is nearly finished, apart from the option of disassembling according to SDK41 (useful for re-assembly ...)

Meindert

                              
Re: And... (was: HEPAX VASM listing?)
Message #7 Posted by Geir Isene on 4 Jan 2010, 4:14 p.m.,
in response to message #6 by Meindert Kuipers

As I have awkward access to a Windows computer, and running MLDL2K.exe under Wine is funky) - anyone care to send a listing of the HEPAX module? (g@isene.com)

EDIT: Never mind - I got around the quirkiness and have a working program running under wine on my Linux laptop. I will traverse the HEPAX listings and see if I can make it do what I want it to :-)

Edited: 4 Jan 2010, 4:40 p.m.

                                    
(edited)You have mail... (was: HEPAX VASM listing?)
Message #8 Posted by Vieira, Luiz C. (Brazil) on 4 Jan 2010, 5:01 p.m.,
in response to message #7 by Geir Isene

Let me know if it suffices.

Cheers.

Luiz (Brazil)

Oops! It took me longer than it took you to edit the message... Anyway, the lists will be in good hands.

Edited: 4 Jan 2010, 5:08 p.m.

                                          
Re: (edited)You have mail... (was: HEPAX VASM listing?)
Message #9 Posted by Geir Isene on 4 Jan 2010, 5:18 p.m.,
in response to message #8 by Vieira, Luiz C. (Brazil)

You saved me some work nevertheless. Thanks :-)

                                                
My pleasure! (N.T.)
Message #10 Posted by Vieira, Luiz C. (Brazil) on 4 Jan 2010, 5:37 p.m.,
in response to message #9 by Geir Isene

...


[ Return to Index | Top of Index ]

Go back to the main exhibit hall