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

Page: << < ..1112 > Showing page 11 of 12
Author
NicholasLee
Starting Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2014/11/11 09:40:37
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/07 13:53:00 (permalink)
5 (1)
Please can you add MCC support for the PIC18F66J11
 
I have a customer who uses this chip exclusively, and being able to configure each project quickly and efficiently with MCC would be incredibly helpful.
 
Thank you.
katela
Super Member
  • Total Posts : 1191
  • Reward points : 0
  • Joined: 2013/06/11 05:25:18
  • Location: South Africa
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/07 14:34:00 (permalink)
3 (1)
MCC supports only new devices, if that device is "very" old, it's unlikely Microchip will be interested to support it. You can use a newer PIC with same features you are looking in the old one.

Free online Microcontroller Tutorials and Projects for Hobbyists and students. From beginners to advanced. Website: www.studentcompanion.co.za
YouTube Tutorials: https://www.youtube.com/StudentCompanionSA
NicholasLee
Starting Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2014/11/11 09:40:37
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/07 15:15:23 (permalink)
4.5 (2)
1) It is an "In Production" part, "Recommended for automotive designs". I have kids older than this chip.
2) You didn't read my post where I said that it is my customer's chosen part, so I can't affect that choice. 
3) It's not helpful to undermine my request to Microchip for development support for one of their production devices.
katela
Super Member
  • Total Posts : 1191
  • Reward points : 0
  • Joined: 2013/06/11 05:25:18
  • Location: South Africa
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/07 15:18:31 (permalink)
3 (1)
I didn't mean to undermine your request, that was just my opinion.
And I said: if that device is "very" old
post edited by katela - 2018/07/07 15:32:30

Free online Microcontroller Tutorials and Projects for Hobbyists and students. From beginners to advanced. Website: www.studentcompanion.co.za
YouTube Tutorials: https://www.youtube.com/StudentCompanionSA
Wieschebrock
Super Member
  • Total Posts : 205
  • Reward points : 0
  • Joined: 2005/01/22 07:57:44
  • Location: Germany
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/11 00:29:47 (permalink)
0
Please update and correct the  I2C driver and the EEPROM "Library 1.00" 
 
For PIC24 and DSPIC33 (others I have not tested) they are very buggy/inefficient and not useful at this time
 
Mysil has gone an extensive rewrite of the I2C interrupt driver and EEPROM "Library 1.00", based on MCC's I2C driver. 
See Mysils thread here 
 
 
hardeng
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2018/07/12 18:25:46
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/13 04:52:35 (permalink)
0
There seems to be a bug in MCC 3.55.1 for IOC in the pin module. Using for PIC16LF15344. MPLAB X v4.15. When IOC is enabled but then using the easy setup to choose the edge detector for the desired pin the interrupt for that pin is disabled in the generated PIN_MANAGER_Initialize() function. 
 
/**
    IOCx registers
    */
    //interrupt on change for group IOCBF - flag
    IOCBFbits.IOCBF4 = 0;
    //interrupt on change for group IOCBN - negative
    IOCBNbits.IOCBN4 = 0;
    //interrupt on change for group IOCBP - positive
    IOCBPbits.IOCBP4 = 0;
    //interrupt on change for group IOCCF - flag
    IOCCFbits.IOCCF4 = 0;
    //interrupt on change for group IOCCN - negative
    IOCCNbits.IOCCN4 = 0;
    //interrupt on change for group IOCCP - positive
    IOCCPbits.IOCCP4 = 0;
 
The respective bits should be set if enabled. Note all IOC bits are cleared in pin initialise (disabled). Additionally changing the IOC edge detector type via the pin module easy setup does not reflect the correct setting in the register tab. Enabling IOC on a pin via the registers tab in pin module and then running generate works correctly.
post edited by hardeng - 2018/07/13 04:54:19
brightlightbeam
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2016/02/20 08:50:53
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/07/16 10:36:49 (permalink) ☄ Helpfulby Alvaro 2018/10/12 13:01:56
0
Hello,
 
maybe a USB Bootloader for microcontrollers with built in USB module and also the capability to configure the USB module. (PIC18F14K50)
Also some microcontrollers have a CTMU but MCC does not feature the configuration. (PIC18F45K22)
 
Regards
Dr_Bean
Starting Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2012/04/18 07:13:40
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/08/29 06:14:25 (permalink)
4.5 (2)
in the CLCx configurators in MCC:  (e.g. using pic16f1503)
 
The CLC-inputs selection from timer overflows are called TMRxIF, whereas, they are actually TMRx_Overflow as correctly stated in the data-sheet. 
 
What's in the name... well:
This makes a big difference since TRMxIF actually stays high until manually reset (because it's a register-bit), whereas TMRx_Overflow is a pulse-signal with 1 timer-clk cycle length as the timer progresses.
 
spend hours on this stupid thing... so would be great if naming was more consistent!
alexconway
New Member
  • Total Posts : 26
  • Reward points : 0
  • Joined: 2009/07/14 08:40:24
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/09/06 05:06:02 (permalink)
0
nandpai
Please add support to processors like 18F67J94
 
Thanks.
 
 




I would also like support for the 18FxxJ94 family
Thanks
Maldus
Starting Member
  • Total Posts : 48
  • Reward points : 0
  • Joined: 2016/08/17 09:55:57
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/09/12 08:21:42 (permalink)
4.5 (2)
Every interrupt generated by MCC should have the weak attribute, to allow the user to define their own callbacks.
 
I'm referring in particular to the Interrupt-on-Change option for the input GPIOs. MCC generates the following interrupt routine in the pin_manager.c

 
/* Interrupt service routine for the IOCI interrupt. */
void __attribute__ (( interrupt, no_auto_psv )) _IOCInterrupt ( void )
{
    if(IFS1bits.IOCIF == 1)
    {
        // Clear the flag
        IFS1bits.IOCIF = 0;
        // interrupt on change for group IOCFB
        if(IOCFBbits.IOCFB7 == 1)
        {
            IOCFBbits.IOCFB7 = 0;
            // Add handler code here for Pin - RB7
        }
    }
}
 

 
I have to fill in the handler code in the generated file by hand, but the procedure has to be repeated every time I generate new code. Simply adding a weak attribute to the routine (or similarly to a custom handler to be defined, like it's done for the timer interrupts) would solve the problem.
post edited by Maldus - 2018/09/13 05:14:00
scrungy
Junior Member
  • Total Posts : 97
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/09/18 15:15:31 (permalink)
0
In version 2.5 you could print a copy of the graphical pin table.
I can't find out how to do that in 3.x and up.  I'm on the latest version of MCC, and it still is not there.
 
That desperately needs to be put back in.
 
post edited by scrungy - 2018/09/18 15:28:56
scrungy
Junior Member
  • Total Posts : 97
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/09/18 15:19:43 (permalink)
0
Please put the ability to print the graphical pin table back in MCC Please.
Trying to print a list of pins and register numbers out, including the port, the bit and my name for that pin.
Need this for documentation and to be able to check my work.
Used to be in 2.5
 
 
Rhinoman
Starting Member
  • Total Posts : 51
  • Reward points : 0
  • Joined: 2005/05/17 01:11:56
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2018/10/03 06:32:09 (permalink)
0
ctigs1
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.



I would like this too, can you give any idea of when this may be released?
Carsten22
New Member
  • Total Posts : 9
  • Reward points : 0
  • Joined: 2018/10/24 17:03:10
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2018/10/29 10:59:32 (permalink)
0
MCC is a great addition to tool chest.  I however I have been using my old MPLAB versions for probably way too long and using older PICs that  I am familiar with.  Also I have been using MPASM and continue to use it as opposed to C.  It would be of great help if it were easier to generate code directly for MPASM.  I am only know learning how to use MCC.  I have a new project that requires a new PIC with all the great capabilities and have to update my trusty old tools. Thanks for all the great work.
Rian
New Member
  • Total Posts : 6
  • Reward points : 0
  • Joined: 2018/12/10 09:47:37
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/01/07 13:59:19 (permalink)
0
The Memory module can generate code for EEPROM but not for HEF. I'm working with PIC16F1765 and it only generates code for the standard flash, not the High Endurance Flash that is a replacement for the EEPROM... Please provide support for HEF.
eenotce
New Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2015/09/16 17:01:54
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2019/01/10 14:01:12 (permalink)
0
There are two very simple features I would like to see added.
I would really like to see the addition of Pin Numbers in the Pin Module view which leads into having the option to sort the Pin Module and the Pin Manager:Grid views by pin number. This would be especially helpful when trying to plan a board layout or trying to find what pins are available in a certain location without having to do all the cross referencing. 
It would make board layout planning, pin/module selection and selecting open pins for parallel sequence naming much easier.
eenotce
New Member
  • Total Posts : 12
  • Reward points : 0
  • Joined: 2015/09/16 17:01:54
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/01/10 14:05:03 (permalink)
0
scrungy
In version 2.5 you could print a copy of the graphical pin table.
I can't find out how to do that in 3.x and up.  I'm on the latest version of MCC, and it still is not there.
 
That desperately needs to be put back in.
 


You can right click in the Pin Manager:Package View window and "Export Image" as a PNG. This is how I have been Printing them Off. Helps if you print one with no custom port names first and then one with your custom port names for debugging/layout etc..
 
I am currently running 4.05 and will upgrade to the latest after I finish some open projects.
post edited by eenotce - 2019/01/10 14:07:13
cray1283
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2018/05/17 01:48:06
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/01/15 02:10:16 (permalink)
0
PIC32MM USB bootloader
hungChun
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2016/05/31 02:08:06
  • Location: Taipei
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2019/01/22 18:51:38 (permalink)
0

ESUART

1. please add function to change baudrate and common settings , just like void EUSART1_Config(unsigned long int baudrate, 8, N, 1)
 
2. please stop polling in Read and Write function, it only works when you are showing a simple demo. if no data to read, you will be blocked in read function???
void EUSART1_Write(uint8_t txData)
{
while(0 == eusart1TxBufferRemaining)
{
}
...
}
 
uint8_t EUSART1_Read(void)
{
uint8_t readValue = 0;

while(0 == eusart1RxCount)
{
}
---
}
 
3. the Tx and Rx Buffer also make no sense if you want to receive a larger and continuously incoming data, like GPS or something like that, please provide a more general way to add my code, I can just get the initial and need to remove all other functions  for now.
 

I2C

1. Please add a way to generate software I2C driver, let we select SCL SDA Pin(from GPIO) and related settings, and then generate the driver functions 
 
 

Bootloader

1. Please add a way to read hex file from external Flash module, not just from RS232/USB/TCP, we want to download the hex file from network and save it in Flash, when I reboot, the bootloader just read from flash and do the programming
 

Others

1. When we select interrupt in modules, it will be added to the module file and interrupt_manager, we can set custom callback or use default callback. it seems we can do what we want in the callback, but actually it is in the interrupt and we should not do to many things(or do something that will jump). It is a bad style especially in ESUART, because we often use it communicate with others and do parse and response. (also when we use timer)
 
 
 
cintet
Senior Member
  • Total Posts : 73
  • 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/01/29 14:25:25 (permalink) ☄ Helpfulby cobusve 2019/01/30 00:38:36
0
Ability to program PIC16F1619 INLVLx registers
 
Thanks
Page: << < ..1112 > Showing page 11 of 12
Jump to:
© 2019 APG vNext Commercial Version 4.5