• AVR Freaks

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

Page: << < ..678910.. > >> Showing page 10 of 15
Author
j2423
Super Member
  • Total Posts : 283
  • Reward points : 0
  • Joined: 2015/05/15 23:10:36
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/02 11:53:39 (permalink)
0
Yeah, kind of like it was done to get the boss of someone's back.  ;-)
 
The launch of a new chip family is the perfect opportunity to promote MCC amongst all users.... In a few years everyone will have figured out their own routines.
 
p.s. UART1 - FLO bits are off by default in MCC and yet in Pin Manager one is obliged to select a pin for CTS1.
post edited by j2423 - 2018/01/03 02:25:39
ctigs1
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2017/06/18 08:39:10
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/13 12:24:42 (permalink)
0
Board support.
 
Make the ability to configure MCC for boards (like any of the Microchip produced boards), user defined boards, etc. to provide pre-defined labelling and code libraries for on board features like ethernet, LCD, LED's, switches, EEPROMS, RTC's, Temp Sensors, etc. with the option of choosing which ones you are using in your project.
 
This way the base code can be done for projects using features on a dev. board or demo board can be used without having to manually recode all the board hardware every time you start a project.
ns.mchp
Moderator
  • Total Posts : 87
  • Reward points : 0
  • Joined: 2013/10/21 16:06:20
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/15 11:04:09 (permalink)
5 (3)
Thank you for the feedback, we are actively working on this right now. And we should have a release in a near future. 
rh.owen
Starting Member
  • Total Posts : 7
  • Reward points : 0
  • Joined: 2011/01/11 02:20:01
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/24 02:08:23 (permalink) ☄ Helpfulby RDS Cliff 2018/03/27 20:35:08
5 (2)
Having finally started using MCC; I always seemed to pick a part that was not supported!!!
I would suggest:
1. Allow MCC to use custom file locations. After all, there is a hard coded location so this should not be too hard. This feature should be fine grained enough to include locations for main.c vs. the mcc headers, vs. that mcc source. By all means fill such a variable with the default locations.
2. The current Generate with merge seems to actually work quite well except that certain lines bounce around depending on some unknown factor that leaves me with annoying differences that I have to check each time. Why not have the code merge find and automatically match lines in each file rather than generating a difference if they have simply moved? I see this mostly in the mcc.h file in the file include list section.
3. Allow custom names for external interrupt pins (and others) and use them correctly. Custom names for other pins seem to work except for the odd situation where the name is not used in some code output.
4. Improve the block comment generator. There is an awful lot of content duplication and redundant or empty data which makes the header files in particular ridiculously large.
5. Allow custom names for modules. SPI1 is not very informative if I am using three SPI modules for different things.
6. Hurry up and add the dsPIC33EPxxxGMxxx series.
7. Please complete the QEI module support!
 
cobusve
Super Member
  • Total Posts : 495
  • Reward points : 0
  • Joined: 2012/04/02 16:15:40
  • Location: Chandler
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/25 17:02:45 (permalink)
0
@rh.owen thanks these are great suggestions! I am going to start working particularly on these:
1. I like this and start the process to include this. We will make the current structure the default and let you override this with the other MCC global options.
2. If the code does not generate in the same order it could cause subtle bugs, so we will fix the templates to retain the order.
3. We should definitely fix this
4. Yes there is a lot of noise, we are in the process of reducing this. 
5. Custom names, this can definitely be done. We are working on a mechanism which gives you this in practice called aggregators. The plan is that you can access it by using SPI[MYNAME].send(... or similar to that where MYNAME is actually implemented as an enum. We are working on making sure this generates the most efficient code.
6 and 7 I will pass this on to the guys who own that device
 
leosw
New Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2016/07/11 01:15:43
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/01/26 01:36:29 (permalink)
0
Hi there,
 
The CAN support of PIC18F chips can (and have to) be improved:
 
 * Support for RTR flag in receive and transmit frames. It must be an element of uCAN_MSG union.
 * Support of custom Acceptance filters: currently, it is possible to choose either acceptance filter 0 or 1 but this filters cannot be edited using the MCC editor.
 
Regards,
 
Léo
Awais
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2016/01/02 06:38:05
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/02/25 03:09:25 (permalink)
0
Hi,
I am trying to test mTouch with the following tools and libraries.
1. MPLAB X IDE ver 4.10
2. xc8 ver 1.45
3. MCC ver 3.45.1, core library ver 4.35
4. pic10/12/16/18 library ver 1.65.1
5. mTouch library ver 2.40
 
I observed that in "MCC->mTouch->Easy Setup" Window, vertical scroll bar is not appearing. If I switch to MCC ver 3.45.1, core library ver 4.26.1 then vertical scroll bar appears but I cannot use mTouch library ver 2.40.
 
I would like to add that on 32 bit OS, sometimes it shows the vertical scroll bar in "MCC->mTouch->Easy Setup" but not always.
 
Hope that Microchip will solve this issue in next version.
 
Regards,
Awais
post edited by Awais - 2018/02/27 13:26:16
luker
Super Member
  • Total Posts : 185
  • Reward points : 0
  • Joined: 2015/04/17 06:24:04
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/03/14 05:39:13 (permalink)
0
I second rh.owen's #2. Current example is the ADC1_SAMPLING_SOURCE enumeration in adc1.h for a  dsPIC33EP128MC506. After every change to any module within MCC, this header gets re-created with the enumeration items in different order. Since they all retain their values, I don't expect any issues should they be sorted alphabetically during code generation. That would reduce the need to check on that enumeration again by a large amount.
Though I'm not sure that the order of included files is similarly resistant to bugs, enumerations would definetly be a good start to eliminate spontaneous re-ordering.
catweazle
Starting Member
  • Total Posts : 26
  • Reward points : 0
  • Joined: 2010/08/23 09:23:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/03/20 02:01:26 (permalink)
5 (1)
please add USB HID class to USB lite.
catweazle
Starting Member
  • Total Posts : 26
  • Reward points : 0
  • Joined: 2010/08/23 09:23:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/03/20 02:08:23 (permalink)
5 (1)
add display support. user can define a display driver (eg. oled SSD1306 or TFT ST7735R.....) and MCC will provide a API to display text, draw lines  circles .... etc.
RDS Cliff
Junior Member
  • Total Posts : 69
  • Reward points : 0
  • Joined: 2016/09/23 11:50:05
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/03/27 20:40:51 (permalink)
0
For MCC for the PIC24FJxxx, DMA module Easy Setup tab:  For the pull down pick list for Trigger Source, could you sort the list alphabetically?  The list is really long to look through for the one source you need.
dlh98370
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2010/11/03 14:13:52
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/04/26 15:49:06 (permalink)
0
Why does code configurator not support dsPic30?
Passhero
New Member
  • Total Posts : 24
  • Reward points : 0
  • Joined: 2018/03/28 02:22:10
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/05/07 06:18:03 (permalink)
0
Please add "HTTP Webserver" to the TCP/IP Lite Stack.
catweazle
Starting Member
  • Total Posts : 26
  • Reward points : 0
  • Joined: 2010/08/23 09:23:28
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/05/22 22:46:00 (permalink) ☄ Helpfulby Wieschebrock 2018/07/11 00:20:04
5 (1)
Often I forget to generate code (having changed a little bit in interface setup) before building project. I would like to have a message window when building project and having changed interfaces setup to inform that I first have to generate setup ... (otherwise last interface changes would have no impact)
gavand
New Member
  • Total Posts : 11
  • Reward points : 0
  • Joined: 2016/09/28 11:02:47
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/05/23 00:08:47 (permalink)
0
namaste,
 
i didnt find my device dspic30f4011 in the list if you add it it will be helpfull.
qɥb
Monolothic Member
  • Total Posts : 3332
  • Reward points : 0
  • Joined: 2017/09/09 05:07:30
  • Location: Jupiter
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/05/23 02:15:04 (permalink)
5 (1)
gavand
i didnt find my device dspic30f4011 in the list if you add it it will be helpfull.

That is a 2006 device.
I think you will find that MCC only supports new devices.
 

This forum is mis-configured so it only works correctly if you access it via https protocol.
The Microchip website links to it using http protocol. Will they ever catch on?
PicForum "it just works"
Typhoon5
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2018/05/20 21:00:38
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/05/23 02:30:29 (permalink)
0
Hi,
I am try to using dspic33ep512mu810 but seems MCC not support this MCU yet.
wish this one can being supported soon.
qɥb
Monolothic Member
  • Total Posts : 3332
  • Reward points : 0
  • Joined: 2017/09/09 05:07:30
  • Location: Jupiter
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/05/23 13:14:44 (permalink)
0
Typhoon5
Hi,
I am try to using dspic33ep512mu810 but seems MCC not support this MCU yet.
wish this one can being supported soon.

That is a 2009 device, so the same as the previous answer, if it's not in MCC now, it never will be.
 

This forum is mis-configured so it only works correctly if you access it via https protocol.
The Microchip website links to it using http protocol. Will they ever catch on?
PicForum "it just works"
purdyd
Senior Member
  • Total Posts : 118
  • Reward points : 0
  • Joined: 2004/03/22 21:02:01
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/05/31 14:08:49 (permalink)
5 (1)
I'd like to see MCC keep pushing up to the pic32MK family. I motor control in particular would benefit from using mcc. And this is a newish processor
purdyd
Senior Member
  • Total Posts : 118
  • Reward points : 0
  • Joined: 2004/03/22 21:02:01
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/06/26 06:49:55 (permalink)
0
And since the ATSAMV7x seems to be moving into the MPLAB X IDE and XC32, I'd like to see that family as an option too.
 
What would make sense to me is that designers have an option for the 32 bit processors of using MCC and a library or the Harmony framework.
 
There are times Harmony makes sense, and others were it doesn't.  I think in the embedded world, choice is good.
 
 
Page: << < ..678910.. > >> Showing page 10 of 15
Jump to:
© 2021 APG vNext Commercial Version 4.5