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

Page: << < ..6789 Showing page 9 of 9
Author
guy_g
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2011/02/10 07:19:13
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/05/26 04:08:43 (permalink)
0
Any chance of adding Capacitive Sensing Module (CPS) peripheral support? I assumed the mTouch library would use it, but it seems not. Or am I missing something?
 
Currently I'm using pic16f1939, I haven't checked other devices for CPS.
 
Keep up the good work!
 
JensKaa
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2017/05/26 03:47:44
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/05/27 09:09:03 (permalink)
0
It would be nice if MPLAB Code Configurator made interrupt handling consistent, ex. TMRx has a function called TMRx_SetInterruptHandler the NCO doesnt. 
 
 
jswanson
Super Member
  • Total Posts : 284
  • Reward points : 0
  • Joined: 2003/11/07 12:44:05
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/06/09 07:54:40 (permalink)
3 (1)
Have options for the DATAEE routines for blocking.  Currently the DATAEE_WriteByte routine blocks after the write with interrupts disabled.  It would be good to have an option to block BEFORE reads/writes or not at all and leave it to the user to check (like the XC8 routines).  I always have to change the routines as I can't disable the interrupts for 5ms while waiting for a write.

uint8_t DATAEE_ReadByte(uint8_t bAdd)
{
// Wait for write to complete
while (EECON1bits.WR)
{
}
EEADRL = (bAdd & 0x0ff); // Data Memory Address to read
EECON1bits.CFGS = 0; // Deselect Configuration space
EECON1bits.EEPGD = 0; // Point to DATA memory
EECON1bits.RD = 1; // EE Read
NOP(); // NOPs may be required for latency at high frequencies
NOP();
return (EEDATL);
}

molrse
Starting Member
  • Total Posts : 40
  • Reward points : 0
  • Joined: 2016/05/15 11:16:16
  • Location: 0
  • Status: online
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/06/17 14:34:58 (permalink)
0
PIC32 # SET, CLR, and INV for I/O Port Registers
 
Is it possible to have the MCC with the option for PIC32 generating code implementing the recommendation 12.2.8 for I/O Port registers?
 
(61120E.pdf # Section 12. I/O Ports)
IgnacioFrances
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2017/06/26 07:07:10
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/06/27 04:09:42 (permalink)
0
I suggest adding support for new pics. I am using now the PIC18F27J13 and unfortunately it is not supported.
swmcl
Senior Member
  • Total Posts : 125
  • Reward points : 0
  • Joined: 2014/05/10 13:54:42
  • Location: Queensland
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/07/16 16:11:20 (permalink)
0
Hi,
 
User custom naming of all pins (EUSARTs in my case) ...
Also having a separate section called 'user generated files' alongside the already created 'MCC generated files' under the 'header files' and 'source files'.
JanJansen
Super Member
  • Total Posts : 486
  • Reward points : 0
  • Joined: 2012/08/25 03:26:34
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/08/12 07:42:38 (permalink)
0
Hello, maybe you can support the I2S peripheral for the PIC32MX170F256B ?
tread
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2017/06/08 11:10:12
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2017/08/23 09:55:32 (permalink)
0
Auto Generated Bootloader or at lease something to make the process a little bit easier to implement.
A few things to make the process easier 
1) Dual partition manager
2) Linker script creator for variable bootloader sizes
3) Basic implementation of USB or UART bootloaders. I would also add i2c and spi but if you are able to get the USB and UART working then It wouldn't be hard to figure out i2c or spi.
 
I know I know..... there are mla applications for the bootloader but I can promise you just from reading forums that it is still a very difficult implementation with the application notes. Also I still cant get the EZBL to compile the demo application on pic24fj1024gb610 on an explorer 16 board (THEY ARE YOUR DEV BOARDS!!!) with XC16 > 1.26.
 
API Library Documentation for all MCC generated code, I know its variable dependent of the mcu , i know there are notes but still.
 
Combining peripherals together.

Example: I have an RTC that communicates over i2c with my pic24fj. The i2c api is great, the rtc api is great. I don't have to do much to implement the two but couldn't there be a way to enable the internal RTCC api to work with an external RTC?
post edited by tread - 2017/08/23 09:59:31
Page: << < ..6789 Showing page 9 of 9
Jump to:
© 2017 APG vNext Commercial Version 4.5