Searching \ for 'Help to identify old/unknown Assembler' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=help+identify+oldunknown
Search entire site for: 'Help to identify old/unknown Assembler'.

Truncated match.
PICList Thread
'Help to identify old/unknown Assembler'
1998\01\23@071847 by Christof

flavicon
face
Hi to all

Did anybody come across an assembler with the name of BCASM?

One collegue of mine is producing devices with PICs for some time and
his product has not changed for some years. Now he wants to do some
modifications, but the original software was written in 1992 with an assembler
with the name of BCASM. (This name he retrieved from the batch file defining
the DOS environmental variables). PIC's used are the 5X range.

The problem is now that this assembler created some pseudo-opcodes
(macro-like instructions) that are not included in the original assembler code.
This code was written under contract from a consultant, but in the meanwhile
another person is involved.

To re-write the whole code will be very lenghty and costly. Is somebody aware
of such an assembler or could put me on a track?

Your advice will be appreciated.

Regards,
Christof
__________________________________________________

Christof Tolken
Tel:  +27 (011) 974 1211
FAX:  +27 (011) 974 1271
Cell: 083 227 3546
spam_OUTctolkenTakeThisOuTspampixie.co.za
www: http://home.pix.za/ct/ct000004/
__________________________________________________

1998\01\23@085612 by Andy Kunz

flavicon
face
>The problem is now that this assembler created some pseudo-opcodes
>(macro-like instructions) that are not included in the original assembler
code.
>This code was written under contract from a consultant, but in the meanwhile
>another person is involved.

Some sample of the code might help, especially things that look unusual.

Andy


==================================================================
Andy Kunz - Statistical Research, Inc. - Westfield, New Jersey USA
==================================================================

1998\01\23@183216 by Greg Maki

flavicon
face
Christof,

You could read the device and then compare the assembly code with the
disassembled code from  the original PIC. That way you could determine what
the pseudo-codes were doing and then port it over to MPASM. Hope this helps.

Greg Maki

At 02:01 PM 1/23/98 +2, you wrote:
>Hi to all
>
>Did anybody come across an assembler with the name of BCASM?
>
>One collegue of mine is producing devices with PICs for some time and
>his product has not changed for some years. Now he wants to do some
>modifications, but the original software was written in 1992 with an
assembler
>with the name of BCASM. (This name he retrieved from the batch file defining
>the DOS environmental variables). PIC's used are the 5X range.
>
>The problem is now that this assembler created some pseudo-opcodes
>(macro-like instructions) that are not included in the original assembler
code.
{Quote hidden}

More... (looser matching)
- Last day of these posts
- In 1998 , 1999 only
- Today
- New search...