16/32 bits PIC support in PBP?

[Dave]

comwarrior, Thin Quad Flat Pac....

Dave Purola,
N8NTA

[Art]

I doubt PBP will ever support anything in the 16/32 bit devices for the reasons posted above.
You can't write for them directly in assembler with MPLAB,
so how could a high level language that compiles to assembler be of any use?
I can't see a version of PBP ever existing that compiles BASIC to C code for these devices,
it would just be plain silly because they are both fairly high level languages, and C is far superior.

The apparent lack of awareness of exactly what is being missed out on is rather unfortunate.

On the other hand I think there will always be reasons to upgrade PBP to later versions.
The way it compiles your basic code to asm can always be improved upon,
and new features can always be added for the chips it does support.

I don't see much of a long term future for PBP with the way Microchip is going though.

Having just started with a dsPic, I can recommend Micrchip's C-30 compiler.
When the free trial expires, all you lose are the code optimisation features that reduce
the program memory consumed by your program, etc.
Not too bad for a free product that would otherwise cost close to $500.

[Acetronics2]

I doubt PBP will ever support anything in the 16/32 bit devices for the reasons posted above.
You can't write for them directly in assembler with MPLAB,
so how could a high level language that compiles to assembler be of any use?
.

Hi, Art,

I won't be so sure ...

What are MPLAB ASM30 and ASM 32 , for you ???

Have a look to the relevant chapters in MPLAB HELP ...

Alain

one example for ASM32:

#include



</PRE>

############################


</PRE>

# main routine


</PRE>

############################


</PRE>

.text


</PRE>

.set noreorder


</PRE>

.ent main


</PRE>

main:


</PRE>

# Do something here


</PRE>

nop


</PRE>

# Infinite loop


</PRE>

1:


</PRE>

b 1b


</PRE>

nop


</PRE>

.end main


</PRE>

.globl main


</PRE>

[Art]

Ah, well I stand corrected.
Maybe I just made that assumption because I see no transitional asm file on the way from C code to hex file
when I compile a C-30 project. A member here recently prompted me to check.

The question is do the asm30 and asm32 products cost money that would have to be spent
in addition to the PBP compiler that supported them (if it ever did exist) ?

[rmteo]

The question is do the asm30 and asm32 products cost money that would have to be spent in addition to the PBP compiler that supported them (if it ever did exist) ?

I am not aware of MC ever charging for the use MPASM so my guess is that the same would apply to MPASM30 and MPASM32. The products are copyrighted by MC but since they are useable only with the copyright owners products, I don't think that there is an issue here. It is the same with other manufacturers AFAIK.