• AVR Freaks

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

Page: << < ..678910.. > >> Showing page 6 of 13
Author
Jim Nickerson
User 452
  • Total Posts : 6329
  • Reward points : 0
  • Joined: 2003/11/07 12:35:10
  • Location: San Diego, CA
  • Status: online
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/09/11 09:02:17 (permalink)
0
sartoP
Hello,
in our High school () we have developed for student a PIC18 based board (information on the link -> picebs2.hevs.ch).
It will be great for our students to have the PIC18F87K22 included in the Code Configurator ;-)
 
Regards
 


Pascal,


I do not see any mention about where I might purchase this board as described on http://wiki.hevs.ch/uit/i...ardware/PICEBS/Welcome
cintet
Super Member
  • Total Posts : 77
  • Reward points : 0
  • Joined: 2007/12/10 09:44:08
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/09/11 13:21:00 (permalink)
5 (2)
Hi,
 
It would be nice to include basic signed/unsigned math functions (Add and Multiply Mode) using the Math Accelerator module for PIC16F1615/9.
 
Regards.
post edited by cintet - 2015/09/11 13:22:31
sartoP
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2015/06/11 05:43:42
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/09/13 01:41:55 (permalink)
0
This is not possible to buy this board. We are an high school and this board is only loan to students during their studies.

This board is used in the "embedded system laboratories".
 
We have developed this board to have a board with a good display, a recent PIC18 MCU and the CAN interface.
The "included PICKIT3" offers the ability for the students to just use the board without anything else (external power supply, external PICKIT, ...).

Regards
Wrathchild
Starting Member
  • Total Posts : 41
  • Reward points : 0
  • Joined: 2009/06/22 12:25:33
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2015/09/15 14:59:28 (permalink)
0
picworker
p.manning,
 
Thanks for you suggestions. 
 
We are considering several ways MCC can support multiple PIC targets in the future.  Using the MPLAB X project configurations might be part of the solution.

 
Having just tried the v3.10 IDE, MCC and XC8 v1.35 the current moves raise some questions.
 
MCC is Beta - so seems strange to be splitting off the plib from XC8, at least until a formal release - or was that unrelated to the MCC work?
 
What does this mean for the MLA? The previous transition in the MLA example code structures to the 'app', 'bsp' and 'framework' has more than likely grown on a large number of developers by now and lends itself well to the multi-target approach, code reuse and I consider a powerful element of the IDE.
 
So I'd second p.manning's request and look forward to a solution but would also suggest that it would have to also be demonstrated how apps equivalent to those in the MLA examples are to be built with such a tool.
 
That and PIC18Fx6J50 support in my case :)
jswanson
Super Member
  • Total Posts : 355
  • Reward points : 0
  • Joined: 2003/11/07 12:44:05
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/09/23 02:03:42 (permalink)
0
in the EEPROM code it would be good to have an option to enable interrupts while waiting for the write to complete.
jswanson
Super Member
  • Total Posts : 355
  • Reward points : 0
  • Joined: 2003/11/07 12:44:05
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/09/23 02:07:29 (permalink)
0
...
post edited by jswanson - 2015/09/23 02:08:40
vinbedded
Starting Member
  • Total Posts : 58
  • Reward points : 0
  • Joined: 2010/09/08 13:09:50
  • Location: Boston, MA
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/10/20 05:29:49 (permalink)
0
Will there be support for multiple configurations?  This would be very useful for products that vary in hardware usage or adding different add ons to your development boards.
 
When assigning peripherals to GPIO pins it would be helpful to have the list of peripherals on the left to be stationary as you scroll to the right to assign your pins.  It is very easy to get lost as you scroll 20 pins or more over.
katela
Super Member
  • Total Posts : 1419
  • 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 2015/11/05 05:25:19 (permalink)
0
Hi 
 
Could you support external LCD displays as well?
Like the popular HD44780 (16x2, 16x4) controllers as you used to support in the PIC18F Peripheral library (xlcd). It will be grat as well if you could support the graphical LCD and TFT LCD.
Thanks

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
pierreb
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2006/09/29 13:18:13
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2015/11/09 14:55:35 (permalink)
0
when will we see a code configurator for dsPIC33?
RISC
Super Member
  • Total Posts : 5379
  • Reward points : 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2015/11/09 16:33:26 (permalink)
4.5 (2)
Hi,
According to what I saw in a Microchip seminar, it seems dsPIC33 will be added later in 2016 in a future MCC v3.xx version
Regards
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 2015/11/10 08:39:56 (permalink)
3 (1)
dsPIC is planned for the first half of 2016
GoEk
Senior Member
  • Total Posts : 120
  • Reward points : 0
  • Joined: 2012/09/27 00:32:28
  • Location: Sweden
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2015/11/10 12:18:29 (permalink)
3 (1)
How about adding support for the EPMP module?
iDriveTheLateCar
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2015/09/21 13:10:46
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/11/12 22:18:35 (permalink)
0
Hi,
 
  MCC is a great tool.  I used it to set up all my peripherals using MCC 2 something.  After upgrading to the beta, and opening the tool, it didn't automatically read in the configurations created with the earlier version of MCC.  Is there a setting somewhere i missed?  There isn't an intuitive "preferences" or "options" menu to tell it where to look for files, so maybe its something else i'm missing.
 
thanks for your efforts.
GoEk
Senior Member
  • Total Posts : 120
  • Reward points : 0
  • Joined: 2012/09/27 00:32:28
  • Location: Sweden
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2015/11/13 09:02:26 (permalink)
0
iDriveTheLateCar
Hi,
 
  MCC is a great tool.  I used it to set up all my peripherals using MCC 2 something.  After upgrading to the beta, and opening the tool, it didn't automatically read in the configurations created with the earlier version of MCC.  Is there a setting somewhere i missed?  There isn't an intuitive "preferences" or "options" menu to tell it where to look for files, so maybe its something else i'm missing.
 
thanks for your efforts.


IIRC, there is a post here that mentions that the CC3 Beta does not support CC2 import yet.
Ivan Cenov
Super Member
  • Total Posts : 279
  • Reward points : 0
  • Joined: 2003/11/07 12:36:51
  • Location: Bulgaria
  • Status: offline
unsigned int constants 2015/12/11 00:34:44 (permalink)
3 (1)
I would like to propose using 'u' at the end of unsigned int constants:

LATA = 0x00u;
TRISA = 0x19u;
ANSELA = 0x11u;
// etc

LATA, TRISA and all SFRs are unsigned char variables. This change will make the code lint and MISRA more compatible.
scrungy
Senior Member
  • Total Posts : 134
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2016/02/05 06:51:07 (permalink)
3 (1)
I have lots of feedback on the new MCC and the older one.
 
For starters, create an interrupts.h file that has enable,disable,priority set macros.
UART1_SetPriority
UART1_EnableInterrupt
UART2_DisableInterrupt
EX_INT1_SetPriority
EX_INT1_EnableInterrupt
EX_INT1_DisableInterrupt
 
And put them in a single header file.
Also, in the interrupts.c file, include EACH and EVERY interrupt handler as dummies, so that all interrupts are caught.
Put the entries into that file with all of the ones selected in MCC at the top of the file.
 
I've been all over the generated files looking for enable/disable interrupts.
 
Secondly for the pins.
It is just crazy to generate a bunch of things like
#define WS_SetHigh()          _LATA6 = 1
#define WS_SetLow()           _LATA6 = 0
#define WS_Toggle()           _LATA6 ^= 1
#define WS_GetValue()         _RA6
#define WS_SetDigitalInput()  _TRISA6 = 1
#define WS_SetDigitalOutput() _TRISA6 = 0
 
Embed ed guys lime me (I have 30 years in this field) would prefer
#define WS_OUTPUT       LATA6
#define WS_INPUT         _RA6
#define WS_DIRECTION  _TRISA^6
NOT in the form of functions.  With ALL upper case to distingish this is a define.  AND the same thing for 
true and false.   MAKE THOSE UPPERCASE
I'd prefer
           WS_OUTPUT=0;
           WS_INPUT=1;
They don't look like functions that way.  What the actual generated code says to me is this:
"This was written by a bunch of amatures in the embedded world, with C++ background who can't think the way
normal embedded stuff is done."
 
I once came in behind a guy who was a C++ programmer trying to do embedded stuff.
He had 200+ functions for handling global variables.  A set function, a get function   What a nightmare.  And these
were real functions.   Total waste of code space, time, etc.  All because he was a C++ programmer.
 
 
 
cinpezzo
Starting Member
  • Total Posts : 65
  • Reward points : 0
  • Joined: 2011/08/02 14:28:53
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2016/02/11 02:37:21 (permalink)
0
Did yuo plan to implement PIC24EP support too?
 
Regards,
Nicola
carlopallini
Super Member
  • Total Posts : 135
  • Reward points : 0
  • Joined: 2015/03/09 07:06:07
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2016/02/19 01:08:25 (permalink)
0
Well, including USB support woulb be great.
scrungy
Senior Member
  • Total Posts : 134
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2016/02/22 07:12:15 (permalink)
0
When you do a PACKAGE on the project, allow the person to specify the file name.
I use package as a backup method.  But I have to go manually change the name of the prior one before doing it,
because it gives it the same name, quietly over writing it without notifying the user.
And explain what the pale yellow column *REALLY* means.
 
scrungy
Senior Member
  • Total Posts : 134
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2016/02/22 07:29:26 (permalink)
3 (1)
Provide an interrupts file that has a dummy handler for EACH interrupt on the chip.
so that they can be edited.
 
When creating a package, don't compile it for production.  Leave the generated code alone.
One common use is to send a project to customer support, and if it is built in the debug mode, leave it that way.
 
Fix the configurator so that if you go into a MCC generated module and manually change it, and re do the configuration, that it will only replace those lines it generates, leaving the other code alone.
 
Create a #define for EACH bit in each module.
There should be a definition for enable, disable, enable interrupt, disable interrupt.
 
In addition to generating the useless stuff like the psuedo functions, please generate an equivalent like standard developers would use.
so instead of    
#define U3TX_SetHigh()          _LATD4 = 1
generate in addtion
#define U3TX_PIN         _LATD4
 
US3TX_PIN=1;  // makes sense to an embeded guy.  Calling a "function" is worthless,
 
At the very least if you are going to *have* to generate the "funtion", generate an addition #define line.
Better would be to eliminate the function stuff all together.
 
There are no "functions" generated for enabling the UART, Disabling the UART, Enabling the UART interrupt, and Disabling the uart interrupt.  There should be defines for each of these on EVERY peripheral.
 
 
Page: << < ..678910.. > >> Showing page 6 of 13
Jump to:
© 2019 APG vNext Commercial Version 4.5