• AVR Freaks

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

Page: << < ..111213 Showing page 13 of 13
Author
Gouthami c v
Starting Member
  • Total Posts : 83
  • Reward points : 0
  • Joined: 2019/07/11 01:55:44
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/07/18 23:21:31 (permalink)
0
Hi, i am using PIC24F04KA200 for this series MCC is notworking in MPLAB IDE. Can any one help for this.
 
 
 
Thanking you.
mcovington
New Member
  • Total Posts : 18
  • Reward points : 0
  • Joined: 2019/07/12 09:19:40
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/07/19 20:04:13 (permalink)
0
Maybe an option to generate fewer files and put more into the main .c file?  For smaller projects it would be convenient to end up with a single .c file (like the programs in textbooks and documentation).
 
oliverb
Super Member
  • Total Posts : 245
  • Reward points : 0
  • Joined: 2009/02/16 13:12:38
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/07/22 05:25:27 (permalink)
5 (1)
One request: currently I believe it is very difficult to migrate a MCC design to a different PIC. My specific issue was that if the project was for a 28 pin variant and I switched to a 44 pin variant the only way to get pin manager to accept the existance of ports D and E was to delete and rebuild the MCC configuration.
 
Please make it easier to change PIC.
 
Diesel888
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2019/07/25 19:35:04
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/07/31 17:13:07 (permalink)
0
Could the team consider adding PIC 18F8722 to MCC support, please.
This MC fits my purpose (and I'm part way through my project), and the 18F87K22 iteration is already supported, so perhaps it would not be too onerous a task for the team.
Dennis in Tasmania
 
*seems to be an issue with ADC though, but it looks like an offset I can measure then allow for (part of the reason I'd like to see MCC generated code for ADC).
 
acharnley
Super Member
  • Total Posts : 406
  • Reward points : 0
  • Joined: 2016/05/01 06:51:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/12/05 16:16:16 (permalink)
0
I love MCC, it's the best bit of software Microchip has done.

My two gripes, one minor and one major.

Minor

Not all interrupt handlers generate a function placeholder. For example most timers do something like -


 
 
 

void TMR0_ISR(void)
{
// clear the TMR0 interrupt flag
PIR0bits.TMR0IF = 0;
if(TMR0_InterruptHandler)
{
TMR0_InterruptHandler();
}
 
 
 
// add your TMR0 interrupt custom code
}
 
 
 


While the CLC interrupt handler is -


 
 
 
void CLC2_ISR(void)
{
// Clear the CLC interrupt flag
PIR5bits.CLC2IF = 0;
}
 
 
 


It's minor has I just insert my own at this point, but consistency would be nice.

Major

To generate the interrupt handling code for a peripheral one ticks the necessary box, however there is an assumption the interrupt is to be enabled there and then. Much of the time I just want the code in place and I'll enable the interrupt at a later time.

Rather than modifying the mcc generated code (I try to avoid doing this to prevent accidental changes) I have a config function which overwrites the mcc values before interrupt handling is enabled. For example:


 
SYSTEM_Initialize();
configLed();
configUvl();
 
INTERRUPT_GlobalInterruptEnable();
INTERRUPT_PeripheralInterruptEnable();


configUvl is reverting the value set by MCC code in SYSTEM_Initialize.

So basically "Enable interrupt" should be split into two boxes; 1. Support interrupt handling. 2. Enable interrupt (where 2 is dimmed out if 1. is not selected).
post edited by acharnley - 2019/12/05 16:19:42
Fantalucio
Starting Member
  • Total Posts : 60
  • Reward points : 0
  • Joined: 2003/11/07 12:44:52
  • Location: Verona - ITALY
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/12/13 03:38:06 (permalink)
5 (1)
Hi,
I think that it would be useful the possibility to export the PIN MANAGER configuration in a format suitable to share it with the hardware designer.
Ciao,
Lucio
Page: << < ..111213 Showing page 13 of 13
Jump to:
© 2019 APG vNext Commercial Version 4.5