__trisc var not defined going from SX28 to SX48 [solved]

Yendor

I'm moving my project from an SX28 to SX48 for some additional breathing room.

When I compile the code on the SX48, the following error occurs:

··MOV FSR,#__TRISC

Error 3 Pass 2: Symbol <__TRISC> is not defined

I see __TRISX(0) var at $FF, but don't see __TRISC var·like I did on the SX28.

How does __TRISX function in collaboration·with __TRISC and the other __TRIS vars on the SX48?

Thanks!

[noparse][[/noparse]update] not sure if this is correct, but defining __TRISC as a byte var compiles, at least.



Post Edited (Yendor) : 5/17/2010 5:43:35 PM GMT

Bean

Yendor,
What line of SX/B code is generating the "MOV FSR,#__TRISC" line ?

The SX48 doesn't use individual __TRISA, __TRISB, etc variables because the SX48 can read and write the TRIS registers. On the SX28 they are write only.

Bean

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Use BASIC on the Propeller with the speed of assembly language.
PropBASIC thread http://forums.parallax.com/showthread.php?p=867134

March 2010 Nuts and Volts article·http://www.parallax.com/Portals/0/Downloads/docs/cols/nv/prop/col/nvp5.pdf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
There are two rules in life:
· 1) Never divulge all information
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you choose not to decide, you still have made a choice. [noparse][[/noparse]RUSH - Freewill]

Yendor

Thanks Bean
it's from am in line assembly instruction.
I am still unclear what to do,as of yet.
Any help appreciated!

It's from the serial code interrupt.

Zoot

Bean means attach your SX/B program (or the snippet that generates that assembly). I would post the whole program. You have SX48 defined in the device line?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
When the going gets weird, the weird turn pro. -- HST

1uffakind.com/robots/povBitMapBuilder.php
1uffakind.com/robots/resistorLadder.php

Yendor

Thanks for the guidance guys - I think I have this one figured out now.

Now I have another one, which comes up with another thread.