Helpful ReplyHot!Suggestions for the next release of MPLAB® Code Configurator

Page: 12345.. > >> Showing page 1 of 9
Author
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
2013/11/06 03:50:44 (permalink)
5 (4)

Suggestions for the next release of MPLAB® Code Configurator

This thread is dedicated to gathering suggestions related to what features could be improved or added in the next release of MCC. Please try to provide some arguments for your suggestions as they will help when proposing the idea to the team. Providing arguments will also help the team in better estimating what your needs are.
 
Please help us to improve MCC!
 
Regards,
The MCC Team
post edited by MCHP_Ryan - 2015/05/13 12:11:51
#1
mouse5312
New Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2008/10/07 07:23:23
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/07 05:45:33 (permalink)
0
Add the PIC32 family to the configurator
#2
sparkbuzz
Super Member
  • Total Posts : 172
  • Reward points : 0
  • Joined: 2013/03/22 02:32:41
  • Location: South Africa
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/07 07:08:00 (permalink)
0
I second the above! Please support PIC32, and the rest perhaps!
#3
Ivan Cenov
Super Member
  • Total Posts : 255
  • Reward points : 0
  • Joined: 2003/11/07 12:36:51
  • Location: Bulgaria
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/07 22:26:00 (permalink)
0
  1. Ability users to define its own code snippets that be merged into IC2 generated code.
  2. Ability users to define its own modules (perhaps software modules).
Example for (1):
RTClock. This is a module, that relies on one of the PIC timers (TIMER1, TIMER2,4,6). The selected base timer is configured to make interrupts at intervals, say, 2.5ms. This can be done in IC2. RTClock module defines software timers that have periods multiples of 2.5ms. Every timer has code associated with it. This code should be embedded into the base timer interrupt -- and if defined as user code snippet, it would be easy to embed it.
 
Example for (2):
The same RTClock module. It needs not only code snippets in the timer interrupt; it needs variable definitions, procedures (or macros) for setting, stopping, checking elapsed interval etc. So, an user defined module with possibility to be integrated to "system" IC2 modules would be great.
 
Ivan
 
post edited by i_cenov - 2013/11/07 22:36:53
#4
Ivan Cenov
Super Member
  • Total Posts : 255
  • Reward points : 0
  • Joined: 2003/11/07 12:36:51
  • Location: Bulgaria
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/07 22:40:36 (permalink)
0
Plugin system, so as users can add features to IC2.
post edited by i_cenov - 2013/11/07 23:30:11
#5
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/13 02:15:02 (permalink)
5 (1)
Thanks everyone for the great suggestions. They`re all noted down and taken into account. Support for more peripherals and more devices will be added in the following months.
#6
rcardenas
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2013/04/02 10:13:53
  • Location: Dallas, TX/USA
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/13 12:13:20 (permalink)
0
I noticed that for the PIC16F1828/1823 there is no reference to the CPS Capacitive Sense module.
Is the CodeConfigurator providing code generation for EVERY module and peripheral in the PIC12 & PIC16 series?
#7
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/21 08:55:24 (permalink)
0
Hi rcardenas,
 
The v1.0 release has support for select peripherals. More peripherals and more devices will be added in the following months. I can't say neither when nor what devices/peripherals exactly. I can tell you that we want to release them as soon as possible. In what concerns peripherals and devices probably priorities may shift based on user requests and needs.
#8
rcardenas
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2013/04/02 10:13:53
  • Location: Dallas, TX/USA
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/11/21 11:37:24 (permalink)
5 (1)
Thanks for the feedback, I realize that we all live in a priority driven world, and unfourtunately the Real World interrupts are more arbitrary than the predictable world of MCUs.  ;-)
 
Keep up the great work your teeam is doing.  The more your facilitate the start-up process is a day faster to our project delivery
Thanks
#9
Rohan_Shah
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2013/08/03 01:27:17
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2013/12/27 06:07:25 (permalink)
5 (1)
Try to include the support for serial EEPROM device in I2C framework. Currently the I2C framework generated has following functions:
 
uint8_t I2C_ReadFrame(uint8_t i2cSlaveAddress, uint8_t *i2cReadPointer, uint8_t i2cFrameLength);
uint8_t I2C_WriteFrame(uint8_t i2cSlaveAddress, uint8_t *i2cWritePointer, uint8_t i2cFrameLength);
uint8_t I2C_WriteByte(uint8_t i2cSlaveAddress, uint8_t i2cData);
 
It is not possible to read the serial EEPROM device using this code. When we want to read the serial EEPROM, we need to first give write packet (containing start address) and then without giving stop condition we need to restart the read sequence.
#10
aflex
New Member
  • Total Posts : 14
  • Reward points : 0
  • Joined: 2014/01/06 03:53:50
  • Location: Santa Ana, CA
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/06 04:04:49 (permalink)
1 (1)
If there is any simpler way to use MPLAB compiler. Rather than having C files and other files in the folder can't we call it from somewhere else. Or adding a simple .exe file where we need to share the source path only. We can then use it in a LAN connected system also.

High Quality Manufacturer
#11
jakestew
New Member
  • Total Posts : 15
  • Reward points : 0
  • Joined: 2012/08/11 01:49:58
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/07 00:59:30 (permalink)
0
More device support!  12F1840 should be in the list.
 
I'd also consider a standalone version.  It would be handy to generate simple listings of register settings and the like.
#12
mecch
New Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2009/07/23 08:54:32
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/12 00:28:38 (permalink)
0
Dear friends
I have found that delay code is not generated for ADC channel switching. 
Here is the generated code for pic16F1827.
 
adc_result_t ADC_GetConversion(adc_channel_t channel)
{   
                 adc_result_t result;    // select the A/D channel   
                 ADCON0bits.CHS = channel;
                  // turn on the ADC module   
                  ADCON0bits.ADON = 1;    
                  // start the conversion   
                  ADCON0bits.GO_nDONE = 1;
                  // wait for the conversion to finish   
                  while (ADCON0bits.GO_nDONE)    {    }    
                  result = (ADRESH << 8) + ADRESL;   
                  // conversion finished, return the result   
                  return result;
}


#13
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/21 01:00:53 (permalink)
0
Hi everyone,
 
Thank you for the great suggestions!
 
aflex 
If there is any simpler way to use MPLAB compiler. Rather than having C files and other files in the folder can't we call it from somewhere else. Or adding a simple .exe file where we need to share the source path only. We can then use it in a LAN connected system also. 
 
 
alfex I'm not sure I understand correctly your question but it seems more like a compiler question. As far as I know XC compilers can be installed on a single computer and used in a network.
 
Here's what the XC compiler page says (https://www.microchip.com...us/devtools/mplabxc/):
Network Server License
  • Intended to have multiple users and can be installed on a network
  • Restricted to use by one user at a time. The license is available to the other users one hour after a compile takes place.
  • Might otherwise require a large number of compilers
  • Great for use by global companies with multiple design centers
  • Has a loan-out feature so that a license can be run like node locked for a specific amount of time
jakestew 
More device support!  12F1840 should be in the list. 
  
I'd also consider a standalone version.  It would be handy to generate simple listings of register settings and the like. 
 
More device support is on the way. The next version should contain 12F1840. 
Can you please give more information on what you are referring to when saying "standalone"? Do you mean having MCC as a tool external to MPLAB X so you can use it without firing up MPLAB X or is it something else?
 
mecch
Dear friends 
I have found that delay code is not generated for ADC channel switching.  
Here is the generated code for pic16F1827. 
  
adc_result_t ADC_GetConversion(adc_channel_t channel) 
{    
                 adc_result_t result;    // select the A/D channel    
                 ADCON0bits.CHS = channel; 
                  // turn on the ADC module    
                  ADCON0bits.ADON = 1;     
                  // start the conversion    
                  ADCON0bits.GO_nDONE = 1; 
                  // wait for the conversion to finish    
                  while (ADCON0bits.GO_nDONE)    {    }     
                  result = (ADRESH << 8) + ADRESL;    
                  // conversion finished, return the result    
                  return result; 


Thank you very much for reporting this problem. It should be fixed in the next release. 
 
Best regards,
Florin Matei
#14
mecch
New Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2009/07/23 08:54:32
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/22 07:16:10 (permalink) ☄ Helpfulby Al.THz 2015/04/24 08:11:52
5 (2)
I wish the information to write the code configuration is open to public. The users can write their configuration code for unsupported devices and share with others.  
#15
Amampondo
New Member
  • Total Posts : 6
  • Reward points : 0
  • Joined: 2013/10/22 06:53:57
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/28 14:14:13 (permalink)
3 (1)
What about the Initialization of the LCD Driver Module (16F1937 and others)?
Regards
Amampondo
#16
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/30 14:03:43 (permalink)
0
Hi Amampondo,
 
Thank you for your feedback. All the peripherals are on our "to do" list. The order in which they appear depends on the additional support required.
 
Best regards,
Florin Matei
#17
srobison
New Member
  • Total Posts : 6
  • Reward points : 0
  • Joined: 2014/01/28 11:44:24
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/01/31 14:58:00 (permalink)
0
+1 on the I2C post above, or provide an example of how to use the generated code to make it work.
Also, there seems to be a bug in the generated code for setting the PWM duty cycle:
//Writing to 2 LSBs of pwm duty cycle in CCPCON register
    CCP3CON |= ((dutyValue & 0x0003)<<4);

2 LSBs are only settable, never cleared.
#18
IonutB
Moderator
  • Total Posts : 85
  • Reward points : 0
  • Joined: 2008/08/04 09:43:55
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/02/03 06:18:42 (permalink)
0
Hi srobison,
 
The issue you're describing regarding the PWM duty cycle has been fixed in MCC v1.1, released last week. Please update your version using the following steps:
 
 1. In MPLAB X go to the Tools -> Plugins 
 2. Go to the "Updates" tab and click on "Reload Catalog" and wait for the update to finish. Now you should see MCC in the updates list. 
 3. Make sure the MCC check box in the "Update" column is selected and then click the "Update" button below 
 4. Follow the update wizard steps 
 
If you further encounter this issue (or any other), please don't hesitate to let us know.
 
Thanks
#19
NorthGuy
Super Member
  • Total Posts : 4398
  • Reward points : 0
  • Joined: 2014/02/23 14:23:23
  • Location: Northern Canada
  • Status: online
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/02/28 18:47:19 (permalink)
5 (1)
I wonder why from the multitude of available PICs only PIC16 got chosen. I understand there are more devices on its way, but why the initial selection is PIC16?
#20
Page: 12345.. > >> Showing page 1 of 9
Jump to:
© 2017 APG vNext Commercial Version 4.5