Importing Simulink Generated Code into Mplab - Revision history

LubinKerhuel at 09:34, 4 March 2011

2011-03-04T09:34:37Z

LubinKerhuel: /* Step 2 : MPLAB */

2010-11-08T23:36:38Z

Step 2 : MPLAB

LubinKerhuel at 09:59, 25 April 2010

2010-04-25T09:59:39Z

LubinKerhuel at 23:19, 15 December 2008

2008-12-15T23:19:50Z

LubinKerhuel at 17:40, 14 June 2008

2008-06-14T17:40:35Z

LubinKerhuel: New page: MPLAB project with imported C files and library files (.a) previously generated with simulink This example explain how t...

2008-06-14T17:38:22Z

New page: tumb|400px|frame|right|MPLAB project with imported C files and library files (.a) previously generated with simulink This example explain how t...

New page

[[Image:CompilingSimulinkCodeWithMPLAB.png|tumb|400px|frame|right|MPLAB project with imported C files and library files (.a) previously generated with simulink]]
This example explain how to import simulink generated C files (using Real Time Workshop Embedded Coder and the dsPIC blockset) into a MPLAB project. This method should not be used in normal operation because the Blockset compile the generated files so as to obtain the binary file (.hex and .elf). However, compiling the C files within MPLAB allows to debug the software using the MPLAB deugging capabilities.

For this demonstration, I use the simulink model described in the example for Explorer 16 Development Board (with the dsPIC 33FJ256GP710 or PIC 24JF128GA010 microcontroller).

The model file is in the toolbox directory : '''examples\dsPIC_33f_Explorer16.mdl'''

This method do not use the MPLAB function to import C code from simulink that may be difficult to use.

==Step 1 : Simulink==

*Compile the model
The model must be compiled in simulink (the dsPIC blockset must be installed) to get the matlab lirarys compiled so as to import them easily in MPLAB.

Real Time Workshop creates the subdirectory '''dsPIC_33f_Explorer16_dspic\Source'''. It contains the .C and .h source files generated.

==Step 2 : MPLAB==

#'''Create a new project'''
#'''Select the target device''' (The same as defined in the simulink model : 33fJ256GP710)
#'''Select Language Toolsuite''' : Use the C30 Compiler ( free student version available on the microchip website)
#'''Import C sources files''' (from *Toolbox* \ examples \ dsPIC_33f_Explorer16_dspic \ Source )
#'''Import h source files''' (from *Toolbox* \ examples \ dsPIC_33f_Explorer16_dspic \ Source )
#'''Import Matlab library and PIC/dsPIC library''' : (all .a files in the ''*Toolbox*\examples\dsPIC_33f_Explorer16_dspic\Source'' directory ; The .a library corresponding to the PIC in the Microchip directory ''C:\Program Files\Microchip\MPLAB C30\lib'' for 24f pic, use the 24Fxxx file ( I use the coff version)
#'''Import Linker script file''' for the chosen PIC/dsPIC ; from the microchip directory : C:\Program Files\Microchip\MPLAB C30\support\gld
#'''Compile'''

==Remarks==
Illustrations were realized with MPLAB 7.52.

===Know bug===

with MPLAB 7.60 and get the following message during the compilation process:

"''A language-plugin exception occurred and was logged''"

It seems to be an MPLAB error. Refere post about this error on the microchip forum.
My advice would be to use MPLAB 7.52.

===Why you should avoid to use MPLAB===

I would not recommend to import C code files generated with simulink into MPLAB for the following reasons :

*I is easier to maintain and improve code using simulink
*Adding personnal C code can be easily done in simulink using the dsPIC block "call C function"
*There should be no low level bug
*High level debugging is easier in real-time, using MPLAB debugger usually add strange behaviour and make the debugging very hard.

MPLAB should only be used if the generated C code contains bug, or to debug peripheral ( If you find bugs in peripheral C code, please let me know)

← Older revision		Revision as of 09:34, 4 March 2011
Line 52:		Line 52:

	[[Category:Example]]		[[Category:Example]]
−
−	~~------~~
−	~~<comments />~~

← Older revision		Revision as of 09:59, 25 April 2010
Line 50:		Line 50:

	[[Category:Example]]		[[Category:Example]]
		+
		+	------
		+	<comments />

← Older revision		Revision as of 23:19, 15 December 2008
Line 48:		Line 48:

	MPLAB should only be used if the generated C code contains bug, or to debug peripheral ( If you find bugs in peripheral C code, please let me know)		MPLAB should only be used if the generated C code contains bug, or to debug peripheral ( If you find bugs in peripheral C code, please let me know)
		+
		+	[[Category:Example]]

← Older revision		Revision as of 17:40, 14 June 2008
Line 1:		Line 1:
−	[[Image:CompilingSimulinkCodeWithMPLAB.png\|tumb\|~~400px~~\|~~frame~~\|right\|MPLAB project with imported C files and library files (.a) previously generated with simulink]]	+	[[Image:CompilingSimulinkCodeWithMPLAB.png\|tumb\|350px\|thumb\|right\|MPLAB project with imported C files and library files (.a) previously generated with simulink]]
	This example explain how to import simulink generated C files (using Real Time Workshop Embedded Coder and the dsPIC blockset) into a MPLAB project. This method should not be used in normal operation because the Blockset compile the generated files so as to obtain the binary file (.hex and .elf). However, compiling the C files within MPLAB allows to debug the software using the MPLAB deugging capabilities.		This example explain how to import simulink generated C files (using Real Time Workshop Embedded Coder and the dsPIC blockset) into a MPLAB project. This method should not be used in normal operation because the Blockset compile the generated files so as to obtain the binary file (.hex and .elf). However, compiling the C files within MPLAB allows to debug the software using the MPLAB deugging capabilities.

@@ Line 17: / Line 17: @@
 ==Step 2 : MPLAB==
 #'''Create a new project'''
 #'''Select the target device''' (The same as defined in the simulink model : 33fJ256GP710)