Discovering PIC 16F18446 - TOGGLE "ASM WARNING - Invalid RAM location"

[flotulopex]

...only if you want your code to work correctly

Who wouldn't?

At this point, it's just about blinking that LED.

But after that, how will I be able to avoid any such kind of "mistakes"?

Please, please don't answer "Easy! Just rfm!!!"

For week-ends hobbyist like me, is it better to stay with more "modest" PICs and/or always use workarounds like instead of:

TOGGLE LATB.6
PAUSE 500

...I should choose to stay with:

LATB.6 = 1
PAUSE 500
LATB.6 = 0
PAUSE 500

[richard]

For week-ends hobbyist like me, is it better to stay with more "modest" PICs and/or always use workarounds like instead

it has nothing to do with with the pic chip at all. its simply incorrect usage of the pbp high level commands

Please, please don't answer "Easy! Just rfm!!!

did you even look at the link i suggested ? i don't know why i bother



all pbp "high level" commands that set a pin direction use a fixed offset to get to the tris reg
it simply will not work correctly from a LATx offset [serout , serout2, toggle,high,low,i2cread........................... ....... ie all of them

PORTx + offset always equals the TRISx register, LATx + offset does not equal the TRISx register ever

if you don't believe my then look at the lst file generated by your code

TOGGLE LATB.6
PAUSE 500

is improper use

TOGGLE PORTB.6
PAUSE 500

is proper use

LATB.6 = 1
PAUSE 500
LATB.6 = 0
PAUSE 500

is proper use

latb.6=!latb.6
PAUSE 500

is proper use