• AVR Freaks

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

Page: << < ..1112131415 > Showing page 14 of 15
Author
Gerry0
New Member
  • Total Posts : 7
  • Reward points : 0
  • Joined: 2014/02/09 11:00:13
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/01/09 13:01:49 (permalink)
0
Now the MCC when I ask to generate the code, tell me that I have several warnings of resources that I'm not using and I cancelled in MCC like TIMER1 for example and other modulus that I'm not using. 
Liem Dung Phan
New Member
  • Total Posts : 22
  • Reward points : 0
  • Joined: 2017/09/14 21:09:39
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/01/09 21:09:54 (permalink)
0
Hi,
Some suggestion for the next release:
1. Fix slow and high CPU usage while openning.
2. Add more configures for USB. Now, to work on USB, I use both MCC and MLA, so complex!

 

Attached Image(s)

ric
Super Member
  • Total Posts : 28975
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/01/09 21:26:06 (permalink)
0
I think you missed the "Lightweight USB stack" in the title.
To get all options, you need a "Full USB stack".
I don't know if Microchip supply one, but that would be the real request.
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
kaamil1984
Junior Member
  • Total Posts : 45
  • Reward points : 0
  • Joined: 2014/05/01 14:02:25
  • Location: Chair at the desk in my workshop ;)
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/01/23 15:50:59 (permalink) ☄ Helpfulby luker 2020/02/10 01:41:25
5 (2)
Hi guys,
 
First of all - thank you for all great work in MCC development.
 
I have one suggestion.
 
Can you change the way how entries in xml are ordered in *.mc3 files?
 
I have problem with version control (I'm using Git). The problem is, that after one little change in MCC my *.mc3 config file has a lot of changes because entries are reordered.
 
For example - I changed something in ADC configuration and this is what I see in diff:
 

 
Have a nice day
Kamil
 
post edited by kaamil1984 - 2020/01/23 15:54:27

Attached Image(s)

luker
Super Member
  • Total Posts : 183
  • Reward points : 0
  • Joined: 2015/04/17 06:24:04
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/02/10 01:43:44 (permalink)
0
I second #264 "VCS-friendly *.mc3 files".
 
I just wanted to ask for the same and had to get to the last post to find someone already did.
 
oliverb
Super Member
  • Total Posts : 343
  • Reward points : 0
  • Joined: 2009/02/16 13:12:38
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/02/10 02:13:00 (permalink) ☄ Helpfulby kaamil1984 2020/02/10 07:14:23
5 (1)
Not quite sure how this would work but I'd like to see support for more than one MCC configuration in the same project, perhaps by defining a configuration name that would be added as a prefix to the configuration functions.
 
Two scenarios:
1: I have a project that can be conditionally compiled for two different PICs
2: I have a program that reconfigures a CLC in response to a menu option
 
Think I might have asked about this already?
kaamil1984
Junior Member
  • Total Posts : 45
  • Reward points : 0
  • Joined: 2014/05/01 14:02:25
  • Location: Chair at the desk in my workshop ;)
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/02/10 07:35:26 (permalink)
0
oliverb
Not quite sure how this would work but I'd like to see support for more than one MCC configuration in the same project, perhaps by defining a configuration name that would be added as a prefix to the configuration functions.
 
Two scenarios:
1: I have a project that can be conditionally compiled for two different PICs
2: I have a program that reconfigures a CLC in response to a menu option



I think scenario 1 is pretty common problem. I think it can be done if you create two projects with shared source files.
 
However if MCC could allow multiple configurations such way, that code generator would add some #define directives in generated files that could be really nice feature easy to integrate with build configurations.
 
But scenario 2 - I don't know how MCC could deal with that. I have UARTs, PWMs and other stuff configurable in software and I usually just manually rewrite registers after MCC.
 
Sobottech
Super Member
  • Total Posts : 285
  • Reward points : 0
  • Joined: 2015/12/02 03:32:17
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/02/28 01:02:34 (permalink)
0
Hello,
 
it would be great, if there would be some more visualization for configurations. For Example, you can config a PWM. It would be very nice, if MCC would calculate a graph/plot/the corresponding calculated PWM. It would help to be faster and to get a direct response, depending of the settings of each register. It also would prevent mistakes, debugging and signal checking. It also would be perfect just to through in values in that graph, how you need the configuration (Duty Cycle, Period, PGxPhase, PGxDC,…) to look like and the registers are configured automatically to match this needs. For other modules it would be also nice to have a calculated view of the configuration. It also would help to through in more graphs in one window, to see the timings. Having the possibility to use these graphs also with CLC and to show what the configured CLC is doing (signal in/signal out), graphically, would be perfect. Should be possible to calculate what the µC is doing and plot it, shouldn’t it?
Sobottech
Super Member
  • Total Posts : 285
  • Reward points : 0
  • Joined: 2015/12/02 03:32:17
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/03/05 07:10:28 (permalink) ☄ Helpfulby Ihor 2020/03/25 16:09:35
5 (1)
Please support virtual Pins feature.
Ihor
New Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2012/07/09 00:09:33
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/03/25 18:01:47 (permalink)
0
Please add actual useful information **which already exists in the data sheet** to the peripheral setup screens.  For example:
 
1) On the HRPWM block each PWM generator kind of has its own setup, and kind of not.  Its not obvious that you have to check boxes inside of a drop down box to "Select" the PWM generators which will be shown. 
 
2) The EasySetup page kind of helps, but there is little prompting of what many of the fields mean.  This gets exponentially worse when you go to the "register's"  view, where prompting is zero.  Just an endless alphabet soup of register names and fields.  In fact some repeat, not just by module but within modules that have more than 1 register that uses the same subfields.  The PWM module does both.  Its virtually impossible to understand what you are doing there.
 
3) Virtual pins could EASILY be supported but are not, and in fact can't be found anywhere in the pin module.  And the registers like RPINRxxx just refer to a number and not a signal.  again... no information, so for virtual pins you might as well just write RPINR1=0x27; yourself.
 
4) Help the user calculate required sampling time in the A/D module.  This is not covered in any of the documentation, including the fact that parameters are missing from the data sheet for the size of Chold, and Rss, which are required to calculate that.
 
5) The data sheets have nice graphical schematics that show you kind of where the bits go.  It would be really great if you could pick from those...  Kind of like the CLC module.  Obviously its "supported" to have pictures.  This would be really awesome for the PLL and OSC blocks, the PWM, anything which selects a lot of signals, maybe even the timers.
WeHongKongers
Super Member
  • Total Posts : 268
  • Reward points : 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/03/26 09:38:11 (permalink)
5 (1)
  1. Please optimise MPLAB X IDE so it can run much faster.
  2. Add a Energy Tracer similar to that of TI.
 
 
Rian
New Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2018/12/10 09:47:37
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/03/29 08:29:56 (permalink) ☄ Helpfulby jswanson 2020/07/02 04:03:26
0
When a timer/counter is used as a timer, please include a #define with the timer period entered in MCC... 
jswanson
Super Member
  • Total Posts : 368
  • Reward points : 0
  • Joined: 2003/11/07 12:44:05
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/06/02 07:54:07 (permalink)
0
1. It would be nice to have a comment section, particularly for things like timers.  The comment would allow you to put something useful like, "This timer is used for PWM".  The comment could be included in the header file.
2. A diagram showing how the periphersals are connected together.  Timers to PWM's or other timers.
cbeif
Starting Member
  • Total Posts : 66
  • Reward points : 0
  • Joined: 2012/05/09 14:28:30
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/06/30 14:26:01 (permalink)
0
There doesn't seem to be a quadrature module for MCC (at least for the dspic33ep512mc806)
sridhar6994
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2019/11/25 20:17:10
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/07/16 23:34:56 (permalink)
0
Hi
I am using mplab x ide v5.30 version 
I can able to develop bootloader using MCC and
I am trying to program using unified bootloader
The tol detects bootloader and program is also flashed,
But the application is not working, eventhough the bootentry pin is in OFF
I need suggestions on how to solve this problem
Thanks
 R Sridhar

Attached Image(s)

_dex
Senior Member
  • Total Posts : 122
  • Reward points : 0
  • Joined: 2008/03/19 13:57:34
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/07/28 03:44:01 (permalink)
5 (1)
Perhaps finally they can make order when Re-generate?
For example: If you just change a bit-rate for UART,CAN or SPI, the mcc Merge tool wants to always make some fool actions which, in the end doing nothing beside reordering the included header files. This is very annoying and applies as well for pin manager, they just reordering the lines.
Why not to prioritize them or use any clever logic to order them; even alphabetic ?
post edited by _dex - 2020/07/28 03:47:02

Attached Image(s)

floatingpoint
Super Member
  • Total Posts : 207
  • Reward points : 0
  • Joined: 2008/12/01 15:52:03
  • Location: below Equator
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/08/16 13:41:29 (permalink) ☄ Helpfulby SteveAtWork 2020/09/20 17:53:41
0
Yes,
 
Please order ALL generated output. EG alphabetical order.
Edit: As above, GIT is one of my most valuable development tools and it expects consistent input to generate meaningful output. This is also because reference data and documents would never be presented in an ad-hoc order.
 
FP
post edited by floatingpoint - 2020/08/17 14:18:12
SteveAtWork
Starting Member
  • Total Posts : 7
  • Reward points : 0
  • Joined: 2007/08/27 15:27:01
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/10/06 19:51:54 (permalink)
5 (3)
Yes, The frivolous reordering of items is beyond annoying as mentioned by _dex (28/07/2020) AND by someone back in 2013 (maybe in between as well, I skipped over all the pages 2-13). This has been a completely dumb thing for at least 7 years and a time waster and an upsetter of git. I often just ignore the proposed changes and then it stops complaining, but this takes time.  
 
The stack is generally getting more unified although there are some radical changes, removals and deprecations that have no backward compatibility. I have some projects that are "stuck" on older libraries as I don't have the time or economic value to up the library version on them.
 
acharnley
Super Member
  • Total Posts : 629
  • Reward points : 0
  • Joined: 2016/05/01 06:51:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/10/07 08:33:10 (permalink)
0
An obvious one, initialise the FVR with an option to delay, DAC's, then analog peripherals then digital's to avoid false interrupts. In other words the list should be given a priority of order (the user doesn't need to see it).
ishkabum
Starting Member
  • Total Posts : 58
  • Reward points : 0
  • Joined: 2020/09/24 07:42:09
  • Location: Washington DC
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2020/10/09 18:52:51 (permalink)
5 (1)
I2C library needs work. I can't even get an empty project to compile after generating the code in MCC. It's looking for i2c_master.h which was not generated.
Page: << < ..1112131415 > Showing page 14 of 15
Jump to:
© 2020 APG vNext Commercial Version 4.5