Is the matrix'c content will be changed during code run time? If it is, then I don't think you can put it inside program memory. Program memory can be only used for storing fixed values (eg look up tables)
the values of the marix will be changed during code run time,
I can define store it as for example: const float E[64][32], but I can't change its values,
so if I want to change values during code run time, I cannot store these values to program memory too, right?
the values of the marix will be changed during code run time,
I can define store it as for example: const float E[64][32], but I can't change its values,
so if I want to change values during code run time, I cannot store these values to program memory too, right?
yes, since defining const float E[64][32] will result by putting this matrix inside your Program memory (Flash memory most probably - i never use PIC before), so for changeable/processed values, i think you have no other options than to use external RAM or change with uC with bigger RAM.
Wow,
you paid about twice the price of an ARM micro for a dsPIC..
A SAM7S32 or a LPC2103 would have provided more than double the computational power at a fraction of the price.
Well it is your choice.
Bob
Wow,
you paid about twice the price of an ARM micro for a dsPIC..
A SAM7S32 or a LPC2103 would have provided more than double the computational power at a fraction of the price.
Well it is your choice.
Bob
well ... if only buying a cheaper and more powerfull / featurefull µC could solve the problem, then that would be nice.
even changing micros just from PIC to AVR may take a reasobable time.. and here you are suggesting to jump into an altogether new world of ARM.
I am unsure what the problem was with a cheaper PIC. You can read/write to the program memory of 16F and 18F devices at run time. That's what makes boot loaders possible. Reading the datasheets will help you get the most out of your uC, no matter the brand.