Debug4x
|
10-01-2017, 09:14 AM
Post: #1
|
|||
|
|||
Debug4x
Maybe I am too dumb to get it done, but perhaps someone here can help me. Yesterday I tried to transfer a SysRPL program from this forum to my 50G and thought I could use DEBUG4x. Is there a way to make it recognize FPTR2 calls, I already exchanged suprom49 against the newest I could find, building the project still fails.
Arno |
|||
10-01-2017, 03:37 PM
(This post was last modified: 10-01-2017 04:53 PM by DavidM.)
Post: #2
|
|||
|
|||
RE: Debug4x
(10-01-2017 09:14 AM)Arno K Wrote: Is there a way to make it recognize FPTR2 calls, I already exchanged suprom49 against the newest I could find, building the project still fails. FPTR2 ^xxxxxx is an appropriate syntax for the built-in compiler on a 50g, but hp's original RPLCOMP (which Debug4x uses) doesn't recognize that form. Generally speaking, you can usually replace "FPTR2 ^" with "FLASHPTR " (note the ^ and space) to compile the code with Debug4x. As an example, seeing the following in 50g-syntax code: Code: FPTR2 ^RADDext ...would compile properly in Debug4x as: Code: FLASHPTR RADDext * Edited to fix a typo. |
|||
10-01-2017, 03:40 PM
Post: #3
|
|||
|
|||
RE: Debug4x
Thank you, I'll try that.
Arno |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)