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

Page: << < ..1112 Showing page 12 of 12
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)
0
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 : 273
  • 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 : 18
  • 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
Starting Member
  • Total Posts : 49
  • Reward points : 0
  • Joined: 2017/07/22 23:51:52
  • Location: Earth
  • 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
New Member
  • Total Posts : 18
  • 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)
0
If possible Please add 16 bit bootloader.
Page: << < ..1112 Showing page 12 of 12
Jump to:
© 2019 APG vNext Commercial Version 4.5