Dear all,
Welcome to the FLEX Forum on the Evidence web site!
Feel free to write any question about the FLEX boards and about the Scilab/Scicos support for FLEX!
bye
PJ
Welcome!
Moderator: paolo.gai
Re:Welcome!
hi
is it posible to generate code from scicos
for dspic30F4011?
best regadrs
dejan
is it posible to generate code from scicos
for dspic30F4011?
best regadrs
dejan
Re:Welcome!
Although the setup we give on the Evidence web page has been tested and used on the Flex boards which hosts a dsPIC33FJ256MC710, there is no problem in generating code for other dsPIC as well.
If you want to do that, I also would like to ask if you can share it so we can put it on the next distribution of the ERIKA Enterprise and of the next FLEX pack.
The steps to do are:
1) take the template from .../Evidence/examples/pic30/pic30_scicos, copy in another directory under the examples directory, and customize the application and the template.xml to compile for your CPU
2) try the code generation; when generating, in the scicos dialog box use the ID of the new template you just made
3) see which blocks are compatible from dspic33 to dspic30. I guess most of the available templates will be compatible without problems. if not, you have to customize the functions, which are in the .../Evidence/contrib/scicos directory
Please note that we are working hard in these days for the support of Scicos 4.1.2, and the custom blocks you are going to write will need little modifications to work on the new version (we planned internally the release date around the second week of february).
bye
PJ
If you want to do that, I also would like to ask if you can share it so we can put it on the next distribution of the ERIKA Enterprise and of the next FLEX pack.
The steps to do are:
1) take the template from .../Evidence/examples/pic30/pic30_scicos, copy in another directory under the examples directory, and customize the application and the template.xml to compile for your CPU
2) try the code generation; when generating, in the scicos dialog box use the ID of the new template you just made
3) see which blocks are compatible from dspic33 to dspic30. I guess most of the available templates will be compatible without problems. if not, you have to customize the functions, which are in the .../Evidence/contrib/scicos directory
Please note that we are working hard in these days for the support of Scicos 4.1.2, and the custom blocks you are going to write will need little modifications to work on the new version (we planned internally the release date around the second week of february).
bye
PJ
Re:Welcome!
Thanks for quick replay
I try everything but nothing seems to work.
dsPIC30F and 33F are pin compatible, have similar
peripheral but C syntax for settings peripheral is not
generally the same, like settings oscillator…
Same peripheral don’t have same numbers of inputs and outputs.
Basically I need to change all C functions regarding to peripherals.
Maybe I don’t understand building process, please advice.
If I make some progress I will share whit you, of course.
Best regard
Dejan
I try everything but nothing seems to work.
dsPIC30F and 33F are pin compatible, have similar
peripheral but C syntax for settings peripheral is not
generally the same, like settings oscillator…
Same peripheral don’t have same numbers of inputs and outputs.
Basically I need to change all C functions regarding to peripherals.
Maybe I don’t understand building process, please advice.
If I make some progress I will share whit you, of course.
Best regard
Dejan
Re:Welcome!
Thanks for quick replay
I try everything but nothing seems to work.
dsPIC30F and 33F are pin compatible, have similar
peripheral but C syntax for settings peripheral is not
generally the same, like settings oscillator…
Same peripheral don’t have same numbers of inputs and outputs.
Basically I need to change all C functions regarding to peripherals.
Maybe I don’t understand building process, please advice.
If I make some progress I will share whit you, of course.
Best regard
Dejan
I try everything but nothing seems to work.
dsPIC30F and 33F are pin compatible, have similar
peripheral but C syntax for settings peripheral is not
generally the same, like settings oscillator…
Same peripheral don’t have same numbers of inputs and outputs.
Basically I need to change all C functions regarding to peripherals.
Maybe I don’t understand building process, please advice.
If I make some progress I will share whit you, of course.
Best regard
Dejan
Re:Welcome!
dejan wrote:
Then change ...\\Evidence\\ee\\contrib\\scicos\\cfg\\cfg.mk to compile your directory instead of the default one when the dspic30 is selected...
Merry Christmas and Happy New Year,
PJ
the oscillator setting is in the template application I cited in point 1) in the previous answer... you have of course to change it... you can also use the template app for dapicdem, If I\'m not wrong it should use a dspic30dsPIC30F and 33F are pin compatible, have similar
peripheral but C syntax for settings peripheral is not
generally the same, like settings oscillator…
The dspic33 dependent peripheral code is under .../Evidence/ee/contrib/scicos/src/pic30 ----> copy the directory with another name (example, .../Evidence/ee/contrib/scicos/src/dspic30)Same peripheral don’t have same numbers of inputs and outputs.
Basically I need to change all C functions regarding to peripherals.
Then change ...\\Evidence\\ee\\contrib\\scicos\\cfg\\cfg.mk to compile your directory instead of the default one when the dspic30 is selected...
Merry Christmas and Happy New Year,
PJ