VoyForums
[ Show ]
Support VoyForums
[ Shrink ]
VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1, 2, 3, 4, [5], 6, 7, 8, 9 ]

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Date Posted: 05:04:28 12/01/02 Sun
Author: Potter
Subject: Re: 16f84A to 16f628 migration
In reply to: Virtuax 's message, "Re: 16f84A to 16f628 migration" on 04:13:22 12/01/02 Sun

If you work in assembler (MPASM) use the CBLOCK directive like this

;define some variables
CBLOCK 0x20
var1 ;register variable
var2
var3
ENDC

var1 is assigned to register 0x20
var2 to 0x21
etc etc
You need to use the BANK directive if exceeding the bounds of the default (1st) bank of registers. In your code just refer to them by name eg
MOVF var1,0
MOVWF var2



>Thanks electrix, but didn`t work.
>16f84 GPR start at 0x0C and 16f628 at 0x20.
>This is not clear for me how to change from 0x0c to
>0x20.
>Could you explain this?
>I found the best tool to learn how PIC works here:
>http://www.bubblesoftonline.com/
>
>Virtuax

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Replies:

[ Contact Forum Admin ]

Forum timezone: GMT-8
VF Version: 3.00b, ConfDB:
Before posting please read our privacy policy.
VoyForums(tm) is a Free Service from Voyager Info-Systems.
Copyright © 1998-2019 Voyager Info-Systems. All Rights Reserved.