hi all,
Is it possible??i mean all the command listed in the PBP green book can be used for dsPIC??
thanks
hi all,
Is it possible??i mean all the command listed in the PBP green book can be used for dsPIC??
thanks
Short answer: No.
PBP works with PIC10, 12, 16 and 18 "only".
I'd probably take a look at MikroElectronikas mikroBASIC PRO for dsPIC or move over to the dark side....
Hi,
The subject was discussed some times ago ...
looked Melabs had no real project for 16 bits ...
May be Charles Leo could make a little " update " about the future ...
BTW CCS C compiler also is a possibility ( take care to recent versions > 4.110 : somewhat buggy ...)
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
And why would 16-bit PICs be interesting? A PIC16 is rated at 5MIPs and the fastest PIC18s are rated 16MIPs (typically 10MIPs). The 16-bit PIC24/dsPIC are rated from 16-40MIPs. However, MIPs (million-instructions/second) are very misleading and do not not take into account things like instruction and data sizes. So how, for example, does a 10MIPs PIC18F97J60 compare to a 16MIPs PIC24FJ64GA004 - is the PIC24FJ 1.6x faster? In real world testing and benchmarking, it is more like 13-23x. Comparing PIC32s which are rated at 40-80MIPs, the disparity gets even larger. Instead of 4-8x that of a PIC18, it can be as much 160x. Take a look at the CoreMark figures (last column) in the table below.
Why pay for overpriced toys when you can have
professional grade tools for FREE!!!
(post removed)
Last edited by Demon; - 15th May 2011 at 22:18.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
(post removed)
Last edited by Demon; - 15th May 2011 at 22:18.
Why pay for overpriced toys when you can have
professional grade tools for FREE!!!
I wouldn't make a statement like that (EDIT: Until Microchip closes the production line or issues a formal statement).
http://www.microchip.com/en_US/family/16bit/index.html
Microchip’s 16-bit, PIC24 MCUs and dsPIC® Digital Signal Controllers provide designers with an easy upgrade path from 8-bit PIC® microcontrollers and a cost effective option to 32-bit MCUs. The broad product line includes everything from eXtreme Low Power microcontrollers to high performance digital signal controllers. Combined with hardware and free software these 16-bit products make the design of Control, mTouch™ Sensing, Graphics, Connectivity, Digital Power Conversion, Smart Sensing and Motor Control solutions easy to implement.
Originally Posted by Demon
Simple answer - no. Programmers do not generate INHX32 files - that is the job of the compiler. The files required by a PIC12/16/18 is very different from that of a dsPIC. While it may be possible to take a PIC12/16/18 HEX file and burn it into a dsPIC, it will not do what you expect it to.
Why pay for overpriced toys when you can have
professional grade tools for FREE!!!
Why not? I've never used or seen a DSpic but thought this an interesting subject so I did some googling:
dsPIC30 is a 16bit mcu:
http://ww1.microchip.com/downloads/e...Doc/70102K.pdf
PIC 24F are also 16bit mcu:(p. 62)
The format supported is the Intel® HEX 32 Format (INHX32).
http://ww1.microchip.com/downloads/e...tes/91025a.pdf
It would seem it's just a matter of using a programmer that generates INHX32 hex files. I have no clue which format is generated by my MeLabs U2 programmer. The most I could find was:(p. 2)
The formats supported are the Intel HEX Format (INHX8M), Intel Split HEX Format (INHX8S), and the Intel HEX 32 Format (INHX32).
INHX8M? INHX8S? INHX32?The melabs programmer software is compatible with the standard Microchip HEX format files.
So, is it possible that finding a programmer that generates INHX32 hex files is the only hurdle to using PIC Basic Pro on dsPIC devices?
Or am I totally not seeing something?
EDIT: This is from 18F2550.INC in PBP folder:
So a PIC 18F2550 is apparently programmed in INHX32 format, why couldn't a dsPIC?LIST p = 18F2550, r = dec, w = -311, w = -230, f = inhx32
Last edited by Demon; - 16th May 2011 at 15:23.
My Creality Ender 3 S1 Plus is a giant paperweight that can't even be used as a boat anchor, cause I'd be fined for polluting our waterways with electronic devices.
Not as dumb as yesterday, but stupider than tomorrow!
In august 2011 Rmteo told me:
Sure looks like you are not going to find the solution here any time soon.
Using from 2012 another compiler for pic24: MikroBasic. Many bugs, not a complete forum as this one... but working.
And Proton seems to make the first steps in the 16bit world just the previous few months. But looks more promissing than Mikroe with the tons of bugs.
Well, I wish too for the step forward, but on a stable compiles. And Charles I am sure will do this when he is ready. I feel that the time comes...
Ioannis
yes i have looked at mikrobasic perhaps for the arm processors , not look at the bugs that may come with it as yet
i also cant see why microchip cant put larger amount of ram/prom in 18f products , would be great for say 256k/ 384k option , but that reserved for 16/32bit devices
You answered your self.
So, it seems that we have the freedom to "choose" which PIC to use. I say, they make us to choose the bigger chips for more memory.
Ioannis
Bookmarks