Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #241 > unrolled thread

ProDOS Assembly Tools docs

Back to article view | Back to comp.sys.apple2.programmer

Contents

  ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-03-26 13:03 -0700
    Re: ProDOS Assembly Tools docs dog_cow@macgui.com (D Finnigan) - 2012-03-26 22:34 +0000
      Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-03-26 17:11 -0700
        Re: ProDOS Assembly Tools docs dog_cow@macgui.com (D Finnigan) - 2012-03-27 15:54 +0000
          Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-03-27 12:36 -0700
            Re: ProDOS Assembly Tools docs Antoine Vignau <antoine.vignau@laposte.net> - 2012-03-27 13:42 -0700
              Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-03-27 16:26 -0700
            Re: ProDOS Assembly Tools docs Steven Hirsch <snhirsch@gmail.com> - 2012-03-28 18:22 -0400
              Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-03-28 17:06 -0700
                Re: ProDOS Assembly Tools docs A2CPM <a2@wilserv.com> - 2012-03-30 12:42 -0700
                  Re: ProDOS Assembly Tools docs MarkLim <markpmlim@yahoo.com.sg> - 2012-04-07 01:03 -0700
                  Re: ProDOS Assembly Tools docs MarkLim <markpmlim@yahoo.com.sg> - 2012-04-07 00:57 -0700
                Re: ProDOS Assembly Tools docs A2CPM <a2@wilserv.com> - 2012-04-05 07:34 -0700
                  Re: ProDOS Assembly Tools docs A2CPM <a2@wilserv.com> - 2012-04-05 08:50 -0700
                  Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-04-05 09:55 -0700
                    Re: ProDOS Assembly Tools docs dog_cow@macgui.com (D Finnigan) - 2012-04-05 17:33 +0000
                      Re: ProDOS Assembly Tools docs A2CPM <a2@wilserv.com> - 2012-04-05 15:06 -0700
                        Re: ProDOS Assembly Tools docs markpmlim@yahoo.com.sg - 2012-04-07 00:45 -0700
                      Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-04-05 21:09 -0700
                        Re: ProDOS Assembly Tools docs Steven Hirsch <snhirsch@gmail.com> - 2012-04-06 08:09 -0400
                          Re: ProDOS Assembly Tools docs "Bill Garber" <willy46pa@comcast.net> - 2012-04-07 21:03 -0400
                            Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-04-07 19:02 -0700
                              Re: ProDOS Assembly Tools docs David Schmenk <dschmenk@gmail.com> - 2012-04-07 20:16 -0700
                            Re: ProDOS Assembly Tools docs A2CPM <a2@wilserv.com> - 2012-04-08 20:52 -0700

Page 1 of 2  [1] 2  Next page →

#241 — ProDOS Assembly Tools docs

I know I'll probably get crucified for this, but....

Looking for official documentation for ProDOS EDASM.  I know it was posted to the gmail account and promptly taken down over copyright issues.  However, since it was never determined who holds the copyright (besides Apple) and it isn't for sale on any of the Apple II sites, I was going to ask if someone who has a scan of the docs to send it to me with the caveat that I'd purchase it whenever it became available (or sell me their hard copy).  I have the DOS Toolkit Assembler manual, but there were enough changes between the DOS and ProDOS version to warrant the need for accessing the newer docs.

Thanks to John B. Matthews for describing some of the updates to the ProDOS EDASM on his website.

O.K.  Flame on...

Dave (donning flame-retardant suit)

[toc] | [next] | [standalone]

#242

David Schmenk wrote:
> I know I'll probably get crucified for this, but....
> 
> Looking for official documentation for ProDOS EDASM.  

Was this part of the ProDOS workbench? Do you know?

If so, then I have it, since I have the whole workbench set.

Picture for reference:

http://macgui.com/gallery/showphoto.php?pic_id=1355

-- 
]DF$
Mac GUI Vault - A source for retro Apple II and
Macintosh computing.
http://macgui.com/vault/

[toc] | [prev] | [next] | [standalone]

#243

On Monday, March 26, 2012 3:34:34 PM UTC-7, D Finnigan wrote:
> David Schmenk wrote:
> > I know I'll probably get crucified for this, but....
> > 
> > Looking for official documentation for ProDOS EDASM.  
> 
> Was this part of the ProDOS workbench? Do you know?
> 
> If so, then I have it, since I have the whole workbench set.
> 
> Picture for reference:
> 
> http://macgui.com/gallery/showphoto.php?pic_id=1355
> 

This was the only image I could find:
http://www.pcmuseum.ca/details.asp?id=38275&type=software

It looks similar with the words "ProDOS Assembler Tools" at the top.

Dave...

[toc] | [prev] | [next] | [standalone]

#244

David Schmenk wrote:
> On Monday, March 26, 2012 3:34:34 PM UTC-7, D Finnigan wrote:
>> David Schmenk wrote:
>> > I know I'll probably get crucified for this, but....
>> > 
>> > Looking for official documentation for ProDOS EDASM.  
>> 
>> Was this part of the ProDOS workbench? Do you know?
>> 
>> If so, then I have it, since I have the whole workbench set.
>> 
>> Picture for reference:
>> 
>> http://macgui.com/gallery/showphoto.php?pic_id=1355
>> 
> 
> This was the only image I could find:
> http://www.pcmuseum.ca/details.asp?id=38275&type=software
> 
> It looks similar with the words "ProDOS Assembler Tools" at the top.
> 

Well, I'll look around and see if I can find where I put my workbench.

[toc] | [prev] | [next] | [standalone]

#245

I appreciate it. I'll explain a little what interested me about EDASM.   My PLASMA project needs an assembler to really be a full featured environment as well as develop the actual interpreter and loader.  I have been using the cc65 assembler but wanted something self-hosted. Along these same lines, I was thinking of a relocatable module format for PLASMA.  Why not kill two birds with one stone and combine the advantages of EDASM: disk based, able to run on a 64k machine, relocating object file format, with PLASMA. I can easily extend the relocatable object file format to include a byte code segment. I'm just missing some of the low level details of ProDOS EDASM so I don't break or misappropriate features EDASM relies on.  PLASMA could then be a linking loader for both EDASM generated REL files and PLASMA modules.  

Dave...

[toc] | [prev] | [next] | [standalone]

#246

OK, I have it but that is too many pages to scan, sorry :-(
av

[toc] | [prev] | [next] | [standalone]

#248

Tease

[toc] | [prev] | [next] | [standalone]

#247

On 03/27/2012 03:36 PM, David Schmenk wrote:

> I appreciate it. I'll explain a little what interested me about EDASM.   My
> PLASMA project needs an assembler to really be a full featured environment
> as well as develop the actual interpreter and loader.  I have been using
> the cc65 assembler but wanted something self-hosted. Along these same
> lines, I was thinking of a relocatable module format for PLASMA.  Why not
> kill two birds with one stone and combine the advantages of EDASM: disk
> based, able to run on a 64k machine, relocating object file format, with
> PLASMA. I can easily extend the relocatable object file format to include a
> byte code segment. I'm just missing some of the low level details of ProDOS
> EDASM so I don't break or misappropriate features EDASM relies on.  PLASMA
> could then be a linking loader for both EDASM generated REL files and
> PLASMA modules.

Very interesting.  About 22 years ago, I looked into using REL format for the 
CardZ180 host-side device drivers.  Ended up using a kludgy relocation bitmap 
scheme because I couldn't find out much of anything about REL.

I'm really surprised that none of the other 8-bit assemblers used relocatable 
object code.  Seems like OMF for the IIgs is where that came into play.

[toc] | [prev] | [next] | [standalone]

#249

On Wednesday, March 28, 2012 3:22:11 PM UTC-7, Steven Hirsch wrote:
> 
> Very interesting.  About 22 years ago, I looked into using REL format for the 
> CardZ180 host-side device drivers.  Ended up using a kludgy relocation bitmap 
> scheme because I couldn't find out much of anything about REL.
> 
> I'm really surprised that none of the other 8-bit assemblers used relocatable 
> object code.  Seems like OMF for the IIgs is where that came into play.

Merlin Pro/8 could use a REL format for building and linking modules into a final binary, but the format wasn't documented as far as I could tell.  Merlin under ProDOS requires a //e or //c but a II+ is my weapon of choice, so it kind of limits the options as well.

Dave...

[toc] | [prev] | [next] | [standalone]

#250

Hi, y'all!

    A disassembly of the "LINKER" module of the ProDOS EDASM package
has been sent to the group's GMail account.

Willi

[toc] | [prev] | [next] | [standalone]

#259

On Mar 31, 3:42 am, A2CPM <a...@wilserv.com> wrote:
> Hi, y'all!
>
>     A disassembly of the "LINKER" module of the ProDOS EDASM package
> has been sent to the group's GMail account.
>
> Willi

 I have also disassembled EdAsm's Linker Module.

Currently, I am porting it to MPW IIGS assembly language because of
the RECORD feature. Now I can use syntax like

	ldy	#XtrnRecord.externNum
	lda	(xtrnRecP),Y		;xtrnRecP is the zpage location $8C
	sta	MiniESDRec+ESDRecord.externNum

where

XtrnRecord	RECORD	0
symNamePtr	DS.W	1	;offset: 0	ptr to a record in SymbolicName table
($9200)
entryPtr	DS.W	1	;offset: 2	Ptr to an ENTRY record; NULL initially
fileNum		DS.B	1	;offset: 4	file # of src file (also called module #)
flags		DS.B	1	;offset: 5	flagByte
symbolNum	DS.B	1	;offset: 6	symbol # referred to by an RLD record
externNum	DS.B	1	;offset: 7	extern number (< 255)
sizeof		EQU		*	;8 bytes
			ENDR

			and

ESDRecord	RECORD	0
flags		DS.B	1	;offset: 0	flagByte
relAddr		EQU		*	;offset: 1	If symbol is ENTRY-type
externNum	DS.B	1	;offset: 1	If symbol is EXTRN-type
unused		DS.B	1	;offset: 2
sizeof		EQU		*	;3 bytes
			ENDR

miniESDRec	DS	ESDRecord	;an instance of ESDRecord

This makes the code more readable especially when one has to deal with
a variant record.

As an aside, after upgrading to an i7 last year, I took the
opportunity to learn the basics of x86/86-x64 assembly using NASM. The
record syntax is similar to MPW assembler. Incidentally, there is a
copy of MPW IIgs tools (v1.2) on the
 original Golden Orchard (GO) CDROM.

[toc] | [prev] | [next] | [standalone]

#260

On Mar 31, 3:42 am, A2CPM <a...@wilserv.com> wrote:
> Hi, y'all!
>
>     A disassembly of the "LINKER" module of the ProDOS EDASM package
> has been sent to the group's GMail account.
>
> Willi

 I have also disassembled the EdAsm's Linker Module.

Currently, I am porting it to MPW IIGS assembly language because of
the RECORD feature. Now I can use syntax like

	ldy #XtrnRecord.externNum
	lda (xtrnRecP),Y		;xtrnRecP is the zpage location $8C
	sta MiniESDRec+ESDRecord.externNum

where

XtrnRecord    RECORD	0
symNamePtr DS.W    1	;offset: 0	ptr to a record in SymbolicName table
($9200)
entryPtr          DS.W    1	;offset: 2	Ptr to an ENTRY record; NULL
initially
fileNum          DS.B    1	;offset: 4	file # of src file (also called
module #)
flags	              DS.B    1	;offset: 5	flagByte
symbolNum   DS.B    1	;offset: 6	symbol # referred to by an RLD record
externNum     DS.B    1	;offset: 7	extern number (< 255)
sizeof             EQU    *	;8 bytes
                      ENDR

			and

ESDRecord	RECORD	0
flags	              DS.B	1	;offset: 0	flagByte
relAddR        EQU	*	;offset: 1	If symbol is ENTRY-type
externNum    DS.B	1	;offset: 1	If symbol is EXTRN-type
unused         DS.B	1	;offset: 2
sizeof           EQU	*	;3 bytes
                    ENDR

miniESDRec	DS	ESDRecord	;an instance of ESDRecord

This makes the code more readable especially when one has to deal with
a variant record.

As an aside, after upgrading to an i7 last year, I took the
opportunity to learn the basics of x86/x86-64 assembly using NASM. The
record syntax is similar to  MPW assembler. Incidentally, there is a
copy of MPW IIgs tools (v1.2) on the original Golden Orchard (GO)
CDROM.

Mark

[toc] | [prev] | [next] | [standalone]

#251

Hi, y'all!

    'ENTRY' is the mnemonic to use to define an address that can be
referred to be another module.  'DEF' and '.DEF' are synonyms for this
mnemonic.  'EXTRN' is the mnemonic to use to define a reference to an
address in another module.  'REF' and '.REF' are synonyms for this
mnemonic.  'ZXTRN' is the mnemonic to use to define a reference to a
page zero address in another module.  'ZREF' is a synonym for this
mnemonic.  Finally, 'REL' is the mnemonic to use to get the assembler
to generate a 'REL' file instead of a 'BIN' file.

Willi

[toc] | [prev] | [next] | [standalone]

#252

Hi, y'all!

    Oops, missed a spot!  It's 'ZDEF', the page zero version of
'DEF' (or 'ENTRY' or '.DEF').

Willi

[toc] | [prev] | [next] | [standalone]

#253

On Thursday, April 5, 2012 7:34:56 AM UTC-7, A2CPM wrote:
> Hi, y'all!
> 
>     'ENTRY' is the mnemonic to use to define an address that can be
> referred to be another module.  'DEF' and '.DEF' are synonyms for this
> mnemonic.  'EXTRN' is the mnemonic to use to define a reference to an
> address in another module.  'REF' and '.REF' are synonyms for this
> mnemonic.  'ZXTRN' is the mnemonic to use to define a reference to a
> page zero address in another module.  'ZREF' is a synonym for this
> mnemonic.  Finally, 'REL' is the mnemonic to use to get the assembler
> to generate a 'REL' file instead of a 'BIN' file.
> 
> Willi

John Matthews' site has pretty much documented everything needed to code with EDASM.  The only thing I would update, and the reason I was looking for the actual documentation, was some symbol table information.  The MACRO bit ($040) is apparently unused, just as in the DOS version.  I plan on co-opting this for PLASMAs needs.

Dave...

[toc] | [prev] | [next] | [standalone]

#254

David Schmenk wrote:
> On Thursday, April 5, 2012 7:34:56 AM UTC-7, A2CPM wrote:
>> Hi, y'all!
>> 
>>     'ENTRY' is the mnemonic to use to define an address that can be
>> referred to be another module.  'DEF' and '.DEF' are synonyms for this
>> mnemonic.  'EXTRN' is the mnemonic to use to define a reference to an
>> address in another module.  'REF' and '.REF' are synonyms for this
>> mnemonic.  'ZXTRN' is the mnemonic to use to define a reference to a
>> page zero address in another module.  'ZREF' is a synonym for this
>> mnemonic.  Finally, 'REL' is the mnemonic to use to get the assembler
>> to generate a 'REL' file instead of a 'BIN' file.
>> 
>> Willi
> 
> John Matthews' site has pretty much documented everything needed to code
> with EDASM.  The only thing I would update, and the reason I was looking
> for the actual documentation, was some symbol table information.  The
MACRO
> bit ($040) is apparently unused, just as in the DOS version.  I plan on
> co-opting this for PLASMAs needs.
> 

I looked around for my documentation, but it appears to be stored away
somewhere inconvenient. I may be able to get to it this weekend if you still
have an interest.

-- 
]DF$
Mac GUI Vault - A source for retro Apple II and
Macintosh computing.
http://macgui.com/vault/

[toc] | [prev] | [next] | [standalone]

#255

Hi, y'all!

    I've found what appears to be coding errors in "LINKER".  The
first snippet of code that seems to be in error is as follows:
	LDA	WORDZ80
	SEC
	SBC	PTRZ84
	STA	RDWRPL+6
	LDA	WORDZ80+1
	SBC	PTRZ84+1
	STA	RDWRPL+6
The last line should be '+7' not '+6'.
    The second snippet of code that seems to be in error is as
follows:
L35B3	CMP	#'A
	BCC	L35A7
	CMP	#'F
	BCS	L35B1
	SBC	#6
	CLC
	RTS
The third line should be '#'G' if the subroutine is intended to return
with the carry flag clear if the accumulator contains an ASCII
hexadecimal digit on entry to the subroutine.
    Further analysis of the code may reveal if these apparent coding
errors are real bugs.

Willi

[toc] | [prev] | [next] | [standalone]

#258

On Friday, April 6, 2012 6:06:16 AM UTC+8, A2CPM wrote:
> Hi, y'all!
> 
>     I've found what appears to be coding errors in "LINKER".  The
> first snippet of code that seems to be in error is as follows:
> 	LDA	WORDZ80
> 	SEC
> 	SBC	PTRZ84
> 	STA	RDWRPL+6
> 	LDA	WORDZ80+1
> 	SBC	PTRZ84+1
> 	STA	RDWRPL+6
> The last line should be '+7' not '+6'.
>     The second snippet of code that seems to be in error is as
> follows:
> L35B3	CMP	#'A
> 	BCC	L35A7
> 	CMP	#'F
> 	BCS	L35B1
> 	SBC	#6
> 	CLC
> 	RTS
> The third line should be '#'G' if the subroutine is intended to return
> with the carry flag clear if the accumulator contains an ASCII
> hexadecimal digit on entry to the subroutine.
>     Further analysis of the code may reveal if these apparent coding
> errors are real bugs.
> 
> Willi

>	LDA     WORDZ80
 >	SEC
 >	SBC     PTRZ84
 >	STA     RDWRPL+6
 >	LDA     WORDZ80+1
 >	SBC     PTRZ84+1
 >	STA     RDWRPL+6
 
 I agree this is a bug. However, it may never get executed if ESD is < 5K.
 
 >L35B3 CMP     #'A
 >      BCC     L35A7
 >      CMP     #'F
 >      BCS     L35B1
 >      SBC     #6
 >      CLC
 >      RTS
 
 I suspect the function of this routine is to return (A)= $30-$3F if on
 entry (A) = '0'-'9' or 'A'-'F'

[toc] | [prev] | [next] | [standalone]

#256

On Thursday, April 5, 2012 10:33:00 AM UTC-7, D Finnigan wrote:
> David Schmenk wrote:
> > On Thursday, April 5, 2012 7:34:56 AM UTC-7, A2CPM wrote:
> >> Hi, y'all!
> >> 
> >>     'ENTRY' is the mnemonic to use to define an address that can be
> >> referred to be another module.  'DEF' and '.DEF' are synonyms for this
> >> mnemonic.  'EXTRN' is the mnemonic to use to define a reference to an
> >> address in another module.  'REF' and '.REF' are synonyms for this
> >> mnemonic.  'ZXTRN' is the mnemonic to use to define a reference to a
> >> page zero address in another module.  'ZREF' is a synonym for this
> >> mnemonic.  Finally, 'REL' is the mnemonic to use to get the assembler
> >> to generate a 'REL' file instead of a 'BIN' file.
> >> 
> >> Willi
> > 
> > John Matthews' site has pretty much documented everything needed to code
> > with EDASM.  The only thing I would update, and the reason I was looking
> > for the actual documentation, was some symbol table information.  The
> MACRO
> > bit ($040) is apparently unused, just as in the DOS version.  I plan on
> > co-opting this for PLASMAs needs.
> > 
> 
> I looked around for my documentation, but it appears to be stored away
> somewhere inconvenient. I may be able to get to it this weekend if you still
> have an interest.
> 
> -- 
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.
> http://macgui.com/vault/

I have found the information I needed to proceed.  We are missing a good quality scan to archive, though.

Thanks,

Dave...

[toc] | [prev] | [next] | [standalone]

#257

On 04/06/2012 12:09 AM, David Schmenk wrote:

> I have found the information I needed to proceed.  We are missing a good
> quality scan to archive, though.

I found an excellent quality scan, which I've been unsuccessfully trying to 
e-mail to Dave (&)(*^)*^ gmail!!).

If someone wants to host it, contact me privately.  I'm not going to put it on 
the mailing list and risk it being the target of DMCA storm-troopers.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.apple2.programmer

csiph-web