• AVR Freaks

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

Page: << < ..111213 > Showing page 12 of 13
Author
FMStereo
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2019/02/07 03:04:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/02/08 08:45:25 (permalink)
5 (1)
Hello All
 
I'm using  PIC32MM0064GPM064 which is supported by MCC. I will not ask for include any uController, first, because I do not have the need and second, I hope Microchip includes them ASAP.
 
Now I have faced a change in my project HW where several pins have changed functionality. I had one *.mc3 file that had the project configuration, but now I face the need of 2 of those files. Since, I cannot place 2 in the same project, because they will generate the code in the same folder, the option I have is to create 2 different projects to support the 2 HW versions (as seen in others threads). Could a next release of MCC, at least, be able to configure the folder where the generated code is placed? This way we could support different configurations and then manage them in the project configuration.
 
Another issue, quite annoying, is the fact that there is no feedback when MCC is opening. My PC is not the fastest one and it takes sometime to open it. If I press the MCC open/close button then I don't know if I really pressed or if it just opening. Just a little feedback...
 
This suggestion can be trickyer. Would it be possible to make each peripheral configuration window similar with the image that is present in the respective datasheet chapter, it would be easier to configure and to understand. Sometimes, only the boxes to place numbers or select options is not very intuitive.
 
I wish the best for the MCC team, you guys have being doing a great job helping the developers to have a little bit more simple life.
 
Thanks
mpittman
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2016/04/05 08:17:25
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/02/12 07:08:07 (permalink)
0
At the very least, some consistency in the generated code, proper documentation of that code and ideally app note to go with them.  This is an absolute requirement if tools like MCC are ever to be successfully adopted.
meraviglioso
Starting Member
  • Total Posts : 41
  • Reward points : 0
  • Joined: 2019/01/01 15:15:35
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/02/27 14:38:49 (permalink)
5 (1)
another vote for expanding the USB stack.  Using the old MLA USB HID stack is fine but creates issues when you want to also use MCC to configure the other better supported peripherals.   It can't be that difficult to rebuild the old MLA stack to work with MCC, can it?
j2423
Super Member
  • Total Posts : 277
  • Reward points : 0
  • Joined: 2015/05/15 23:10:36
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/02/27 22:25:01 (permalink)
0
There's a bug in the CANbus config for PIC18F26K83.
 
If one selects INTOSC 64MHz all the appropriate TQ options appear in the CANbus module when it is installed.
 
BUT if one selects HS 16MHz with 4* PLL and then installs the CANbus module it's impossible to enter a sensible TQ selection.
 
That's a pity since inevitably with CANbus there's going to be an external time source.
m_alizd
New Member
  • Total Posts : 27
  • Reward points : 0
  • Joined: 2016/02/28 02:21:37
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/02/28 19:16:28 (permalink)
0
Hi All
 
My suggestion is for the unified bootloader generator, handling serial interface with RS-485 standard to be added.
This will require line direction handling (receive mode, transmit mode) and switching back and force between them to be added to the source code. I do this manually right now.
 
Also I notice the Autobaud detection code is always generated and in place, regardless of if we tick the Autobaud Detection Enable checkbox in EUSARTx configuration or not. Possible bug?
 
Cheers
Matt
 
Tim Cruise
Junior Member
  • Total Posts : 94
  • Reward points : 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/03/07 09:23:06 (permalink)
0
The present version MPLAB X 5.15 and MCC for PIC 8 bit are very buggy.  Following the instruction of adding the "LED blinking" example, I even cannot turn on a LED on my HPC Curiosity board successfully.  sad: sad
 
On the contrary, I can turn on all LEDs on my PIC24F Curiosity Board by adding LED library one by one inside MCC.  grin: grin
ashoksam
Starting Member
  • Total Posts : 49
  • Reward points : 0
  • Joined: 2018/11/04 22:05:35
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/03/18 00:21:24 (permalink)
5 (1)
If possible Please add 16 bit bootloader.
Liem Dung Phan
New Member
  • Total Posts : 20
  • Reward points : 0
  • Joined: 2017/09/14 21:09:39
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/04/03 21:56:00 (permalink)
0
1. In every interrupt configure, I think you should add a text box or a function to use to set user's callback.
I'm working on PIC32MM, Timer 1,2,... have a fuction to set callback but not with Core timer, I2C, ...


2. I2C driver is so difficult to adapt to the other platforms such as AVR/SAM which I2C devices are built on them. I'll modify everything if I replace AVR/SAM by PIC.

3. If user can add their MCUs (which are old and not supported) to MCC, it'll a great tool!
ashoksam
Starting Member
  • Total Posts : 49
  • Reward points : 0
  • Joined: 2018/11/04 22:05:35
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/04/03 22:49:50 (permalink)
0
Provide the datasheets for the peripherals in mplab code configurator.
 
Ex:  If i am using uart peripheral in mplab code configurator the clean and clear document is required to configure the register values required for specific controller.So please look into this.
Thanks 
paulmtcuk
Starting Member
  • Total Posts : 43
  • Reward points : 0
  • Joined: 2007/08/23 05:16:51
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/04/11 13:11:40 (permalink)
0
Seems like 18FK42 I2C driver is bugged 
 
https://www.microchip.com/forums/m1094157.aspx
 
more detail
 
https://electronics.stackexchange.com/questions/431960/pic18f47k42-i2c-slave-mcc-code-incrementing-register-by-accident
 
(I can't post a new thread with more info -- the forum is also bugged!)
Tim Cruise
Junior Member
  • Total Posts : 94
  • Reward points : 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/04/12 11:09:34 (permalink)
3 (2)
I want monochrome GLCD display editor supporting 8 bit MCUs;
and low bit colour display editor supporting 16 bit MCUs.
 
Thanks for your attention and great jobs on MPLAB X IDE, MCC and MHC.    grin
mattlenz
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2019/04/12 01:44:00
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/04/15 22:41:41 (permalink)
0
I would really appreciate if the generated code and the .mc3 file would be consistent. What I mean is the following. When I create a project and generate the source code, close and reopen mcc, and generate the source code again without making any changes, both the .mc3 file and the generated code are modified (e.g. the ordering of includes, and of entries in the .mc3 xml). This makes it hard to track changes in a version control system when you actually make modifications.
typematrix
New Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/03/04 08:11:26
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/05/08 13:42:06 (permalink)
0
When people speak of bugs what do they mean , are they saying they are seeing bug in the code blocks generated
by MCC or just anomalies in the behaviors of MCC such as crashes or hang ups or error messages.
 
 
 
 
 
oliverb
Super Member
  • Total Posts : 209
  • 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/05/21 10:56:07 (permalink)
0
One anomaly I've seen is I tried to migrate a project from 28 pin to 44 pin, and I just could not get MCC to acknowlege the existance of ports D and E until I deleted the mcc file and folder and rebuilt the configuration from scratch.
sen
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2017/11/22 01:59:08
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/05/23 02:02:13 (permalink)
0
Very minor issue. Working with a pic18f87k22
MCC generates an external interrupt function pointer, default interrupt, and INTX_SetInterruptHandler(void (* my_interrupt)(void)) function, whereas the adc simply has a void ADC_ISR(void) meaning I have to write into the MCC generated file either to create an ADC_SetInterrupt... method or to write my function. I much prefer the former. Can ADC have the same please?
 
Cheers
sen
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2017/11/22 01:59:08
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/05/23 02:30:44 (permalink)
0
In the Pin Manager package view - being able to rotate the view, and flip it so you can view the component as if it was on the underside of a board. Obviously it would have to be made clear that the component had been 'flipped' in the view.
ttshaw1
New Member
  • Total Posts : 7
  • Reward points : 0
  • Joined: 2017/08/03 17:13:17
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/05/29 02:22:23 (permalink)
0
I'd love to have it be more clear how changing things in the simple settings menu changes registers. Maybe something like a tooltip that comes up whenever you select a dropdown or text box that lists the affected registers.
 
Using the simple settings makes initial setup of peripherals etc. easy, but if I need to change something on the fly it's back to the datasheets. If I could see the setting I want to change and have the relevant registers listed right next to it, that would speed up the code writing process considerably.
cintet
Super Member
  • Total Posts : 76
  • Reward points : 0
  • Joined: 2007/12/10 09:44:08
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/05/29 14:38:16 (permalink)
5 (2)
Hi,

I think would be nice for each module a text box input for notes (like the attached image). This would be usefull for add notes, or any thing that help to remember why I'm using each hardware module. Using manual configuration I always add a commented explanation like a reminder that help me for debug.
 

 
Thanks.
post edited by cintet - 2019/05/29 14:44:42

Attached Image(s)

ToddA
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2018/05/15 14:04:18
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/06/27 06:09:24 (permalink)
0
I know it is an older family, but I would like to see dsPIC30F devices added to MCC.
I have had good experience with MCC on PIC16F1788, and it was disappointing to see dsPIC30F was not supported.
 
Regards,
Todd Anderson
ToddA
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2018/05/15 14:04:18
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/07/10 07:01:28 (permalink)
0
Okay, I stepped into RTFM territory, when I suggested MCC for something it does not do, so I will add this as an enhancement request:
 
From https://www.microchip.com/forums/m1104586.aspx#1104625
"Is there a tool to configure how memory will be used in an application.
Block off areas. Group data at a specific location.....
This would build the needed linker script."
Page: << < ..111213 > Showing page 12 of 13
Jump to:
© 2019 APG vNext Commercial Version 4.5