Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

[PIC] DSPIC30F and DSPIC33fJ

Status
Not open for further replies.

Mohammad Zubair

Junior Member level 3
Joined
Jan 13, 2015
Messages
25
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
214
Hi,

I have got a program written for DSPIC33FJ. I want to make it work on DSPIC30F3010.

What should I be doing to make the code of DSPIC33FJ make compatible for DSPIC30F3010.

Please Guide me, I am new with this
 

Aussie Susan

Advanced Member level 4
Joined
Jan 5, 2015
Messages
1,188
Helped
365
Reputation
730
Reaction score
362
Trophy points
83
Activity points
12,874
Which compiler are you using? Something like the XC16 will handle both families simply by setting the appropriate device in the MPLABx IDE (assuming that you have a correctly structured dsPIC33F program that references the <xc.h> include).
One of the biggest differences will be the set of peripherals that are available in each family and are used in your program. It may also be the case that some of the SFR names and bit field names that perform the same function will be different.
The configuration bits will probably be different and will need to be reviewed to find the dsPIC30 name for the dsPIC33 setting.
You could try compiling for the dsPIC30F device and see what errors are thrown up that wil help narrow down the areas of difference.
I must admit that your question does sound a bit like the "XY Problem" (http://xyproblem.info/) in that you think porting code is the solution to your real underlying problem. Typically applications that exist for embedded devices are designed to utilise the features and capabilities of the specific devices they run on. Things like CPU speed, RAM and ROM memory footprints, execution speed and available peripheral devices play a big part in device selection and code development.
Susan
 

Mohammad Zubair

Junior Member level 3
Joined
Jan 13, 2015
Messages
25
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
214
Thanks Susan for the reply
The compiler I am using is MikroC for DSPIC
 

milan.rajik

Banned
Joined
Apr 1, 2013
Messages
2,528
Helped
540
Reputation
1,078
Reaction score
523
Trophy points
1,393
Activity points
0
We can't confirm that it can be used but if you zip and post the complete mikroC project files then it can be said.
 

Status
Not open for further replies.
Toggle Sidebar

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top