Jump to content
Sign in to follow this  
plaasjaapie

Some Pic Programming Issues In Boostbasic

Recommended Posts

I'd like to create some example programmes in BoostBasic that go beyond what Punerjot has done. He's been very kind and sent me some schematics showing how to duplicate his PIC16F628 board. I've got external crystals to duplicate his system backordered. They should be in late next week if UPS is any guide.

 

I worry though, that I'm not going to be able to move beyond his setup because I've not been able to find an equivalent of the __CONFIG anywhere in the BoostBasic documentation and have been guessing about how to do it without a lot of success so far.

 

My first thought was to simply import MPASM assembler into Punerjot's programme and get at it that way. Unfortunately, aspects of MPASM assembler don't seem to be very happy in BoostBasic, notably...

 

__CONFIG

 

...and things like, for example, ...

 

CBLOCK 0x20 ; Declare variable addresses starting at 0x20

dataL

ENDC

 

...amongst others.

 

Is there a way out of this? :-(

Edited by plaasjaapie

Share this post


Link to post
Share on other sites
I worry though, that I'm not going to be able to move beyond his setup because I've not been able to find an equivalent of the __CONFIG anywhere in the BoostBasic documentation and have been guessing about how to do it without a lot of success so far.

 

My first thought was to simply import MPASM assembler into Punerjot's programme and get at it that way. Unfortunately, aspects of MPASM assembler don't seem to be very happy in BoostBasic, notably...

 

__CONFIG

A hole in the documentation, we use the same #pragma as in

BoostC, eg:

#pragma DATA     _CONFIG,  _WDT_OFF & _HS_OSC & _LVP_OFF & _CP_OFF & _PWRTE_OFF

...and things like, for example, ...

 

CBLOCK 0x20 ; Declare variable addresses starting at 0x20

dataL

ENDC

 

...amongst others.

 

Variables are allocated space automatically, but if you want one at a

specific address:

 

Dim myvar@0x123 As Volatile Byte

 

Looks like another hole in the documentation.

 

 

Regards

Dave

Share this post


Link to post
Share on other sites
A hole in the documentation, we use the same #pragma as in BoostC, eg:
#pragma DATA     _CONFIG,  _WDT_OFF & _HS_OSC & _LVP_OFF & _CP_OFF & _PWRTE_OFF

 

YES!!! ALL RIGHT! :-D

 

Thanks Dave!

Edited by plaasjaapie

Share this post


Link to post
Share on other sites

Your content will need to be approved by a moderator

Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×