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

Page: < 12345.. > >> Showing page 2 of 12
Author
ric
Super Member
  • Total Posts : 22101
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/02/28 18:53:15 (permalink)
0
Rohan_Shah

Try to include the support for serial EEPROM device in I2C framework. Currently the I2C framework generated has following functions:

uint8_t I2C_ReadFrame(uint8_t i2cSlaveAddress, uint8_t *i2cReadPointer, uint8_t i2cFrameLength);
uint8_t I2C_WriteFrame(uint8_t i2cSlaveAddress, uint8_t *i2cWritePointer, uint8_t i2cFrameLength);
uint8_t I2C_WriteByte(uint8_t i2cSlaveAddress, uint8_t i2cData);

It is not possible to read the serial EEPROM device using this code. When we want to read the serial EEPROM, we need to first give write packet (containing start address) and then without giving stop condition we need to restart the read sequence.


That is not correct.
The ONLY time you need to use restart is in a multi-master system, to ensure another master doesn't jump in and change the selected address.
In a single master system, you can send a write frame which ONLY sends the address (as you do now), but instead of sending a restart, send a STOP and then a START, specifying a read address.
This will work exactly the same as using a restart.
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#21
picworker
Moderator
  • Total Posts : 47
  • Reward points : 0
  • Joined: 2013/10/21 14:45:47
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/02/28 19:23:11 (permalink)
3.5 (2)
Hi Northguy,
 
Thank you for your interest in MC2. 
The reason PIC16 were the first devices to be supported is a simple one.  The PIC16 devices are the most popular devices.  Not to worry though, PIC18 and PIC24 are on their way soon.
#22
MarkD
New Member
  • Total Posts : 9
  • Reward points : 0
  • Joined: 2003/11/07 12:43:55
  • Location: Toronto, Canada
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/03/02 18:21:47 (permalink)
0
Yesterday I was having a hard time setting up a relatively new processor, as there are not even any good examples to be found.     It's the PIC24FV16KM202,   I hope you select it as one of the first 24F parts to work on.    It is quite different from other 24F parts.
 
 
#23
jai.panghal
New Member
  • Total Posts : 27
  • Reward points : 0
  • Joined: 2012/04/19 05:12:30
  • Location: Delhi, India
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/03/06 10:41:37 (permalink)
0
 
 
Please make provision for software I2C, USART, SPI. Lets suppose someone needs SPI nore in numbers than a IC have. In this case he have to write own software SPI.
So make next version of MCC so POwer full that it can generate code for software SPI,USART adn I2C.
 
Thanks  
#24
NorthGuy
Super Member
  • Total Posts : 5308
  • Reward points : 0
  • Joined: 2014/02/23 14:23:23
  • Location: Northern Canada
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/03/09 09:08:35 (permalink)
0
I2C has addresses, SPI often uses chip select pin, UART can be shared too, so you usually do not need very many of these. You save more money by re-using modules than by bit-banging.
#25
evplasmaman
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2012/03/31 21:55:22
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/03/13 18:11:21 (permalink)
0
Would it be possible to have a road map for the micros in the future releases? I have a few designs that I am working on and would love to be able to use MC2. However I don't want to pick one of the ones that won't be supported soon. I assume, similar to the 16F release, that not all of the family would be supported initially.
#26
techwsg
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2012/08/09 04:13:30
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2014/03/20 16:34:44 (permalink)
0
Hi, thank you for your wonderful efforts on this MCC will the new version support the very powerful disPIC33EP512MU810 because as you already know this dsiPIC is really popular and used by some third party development tools and every hardware module of it has many initialization and configuration requirement and I am looking specifically about HSPWM and ADC so if would support it you make my life much easier to me.
#27
Maarten
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2012/06/25 10:59:12
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2014/03/30 04:06:27 (permalink)
0
Dear Florin,
Recently I used the MCC (V 1.1) to configure a PIC16F1825. I 'm using the ADC, UART Timers and GPIO.
 
Till now I found two issues I'm confused about (1 and 2)  and two remarks (3 and 4). Hope you can enlighten me.
(I do like the MCC, it will improve readability when more developpers will use it!)
BR.
Maarten
 
 
1. ADC
bool ADC_IsConversionDone()
{
    // start the conversion
    return ADCON0bits.GO_nDONE;

}

In the above code it looks to me that you can check if the conversion is done or not. As "ADCON0bits.GO_nDONE" is set to "1" to start the conversion it will be reset to "0" when the conversion is finished.
Should the return be: return !ADCON0bits.GO_nDONE;  ?
Then the result is true when the conversion is done...
 
2. ADC
This code from the ADC_GetConversion routine shows the (famous?) red curly line:   __delay_us(ACQ_US_DELAY);
As no errors appear when compiling I assume it will compile the right way... or??
 
3. GPIO
I enabled the Weak pull up for RA3 and it shows up in the pin manager as WPUA = 0x08;, seems correct to me! But no where I can find the weak-pull-up-enable-bit to be reset! ("OPTION_REGbits.nWPUEN = 0;"). Also I didn't notice a warning message when setting up the WPU for this pin.
(Similar, you get a warning that you should enable global interrupts in your code by yourself when you select an interrupt service to be implemented.)
 
4. EUSART
The EUSART_PutByte() routine will return a status but it is not in the description...
 
 
#28
florin.matei
Super Member
  • Total Posts : 36
  • Reward points : 0
  • Joined: 2013/10/23 00:55:13
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2014/05/21 10:07:47 (permalink)
0
Hi Maarten,
 
Thank you very much for the kind words. I'll try to answer your questions but please let me know if the information provided is not enough of if I can help out with anything else:
 
1.

1. ADC
bool ADC_IsConversionDone()
{
    // start the conversion
    return ADCON0bits.GO_nDONE;

}

In the above code it looks to me that you can check if the conversion is done or not. As "ADCON0bits.GO_nDONE" is set to "1" to start the conversion it will be reset to "0" when the conversion is finished.
Should the return be: return !ADCON0bits.GO_nDONE;  ?
Then the result is true when the conversion is done...

Yes you are right that was a problem but it is fixed in v2.0.
 
2. ADC
This code from the ADC_GetConversion routine shows the (famous?) red curly line:   __delay_us(ACQ_US_DELAY);
As no errors appear when compiling I assume it will compile the right way... or??

 
You will have no problems with the __delay_us() call although MPLAB X shows the red squiggly line. That's caused a different thing.
 
3. GPIO
I enabled the Weak pull up for RA3 and it shows up in the pin manager as WPUA = 0x08;, seems correct to me! But no where I can find the weak-pull-up-enable-bit to be reset! ("OPTION_REGbits.nWPUEN = 0;"). Also I didn't notice a warning message when setting up the WPU for this pin.
(Similar, you get a warning that you should enable global interrupts in your code by yourself when you select an interrupt service to be implemented.)

 
This is fixed in v2.0. Now the Pin Manager will enable or disable the Global WPU bit when at least one individual WPU is enabled. 

4. EUSART
The EUSART_PutByte() routine will return a status but it is not in the description...

 
The EUSART driver has been redesigned in the v2.0 release and these functions are not available anymore. The new EUSART driver should be simpler to use and understand. When you have time please take a look at it and let me know what you think.
 
Best Regards,
Florin
#29
Maarten
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2012/06/25 10:59:12
  • Location: 0
  • Status: offline
Re: Suggestions for the next release of MPLAB® Code Configurator 2014/05/21 10:29:41 (permalink)
0
Dear Florin,
 
Thanks for the update. Today I also found out V2.0 is released.
After my holidays I'll try to find time to check it out.
BR.
Maarten
 
#30
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 2014/05/21 13:31:28 (permalink)
0
Mark, 
 
Microchip released version 2.00 with 16 bit support and it supports the device that you are requesting. You could use the Release 2.00 for the PIC24FV16KM202 device. 
 
Please let us know if you have any suggestions or questions. 
 
#31
tom maier
Super Member
  • Total Posts : 2116
  • Reward points : 0
  • Joined: 2013/08/22 15:27:12
  • Location: earth
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/21 15:27:32 (permalink)
0
 
Oh, cool, it supports 16 bit. Now I'm interested. Those pic24s are a pain.
 
Is there a way to download the plugin without going through mplabx, and have mplabx load them from a local source? My development systems aren't on the net. I could put them on the net, if need be.
 
Also, does this require mplabx 2.10, or will 1.90 work? Is there any advantage to moving to 2.10?
 
#32
tom maier
Super Member
  • Total Posts : 2116
  • Reward points : 0
  • Joined: 2013/08/22 15:27:12
  • Location: earth
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/21 15:38:10 (permalink)
0
 
Never mind... I found it at the bottom of the web page. For some reason when I first loaded the web page there was nothing there, and when I came back to it again, there was the download and the docs.
 
Thanks.
 
#33
tom maier
Super Member
  • Total Posts : 2116
  • Reward points : 0
  • Joined: 2013/08/22 15:27:12
  • Location: earth
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/21 15:52:24 (permalink)
0
 
 
From release notes:
 
System Requirements
    MPLABX IDE v2.05 or later
    XC8 compiler v1.31 or later
    XC16 compiler v1.21or later
 
 
16 bit Devices
PIC24F(V)08KM101
PIC24F(V)08KM102
PIC24F(V)08KM202
PIC24F(V)08KM204
PIC24F(V)16KM102
PIC24F(V)16KM104
PIC24F(V)16KM202
PIC24F(V)16KM204
PIC24FJ128GA306
PIC24FJ128GA308
PIC24FJ128GA310
PIC24FJ64GA306
PIC24FJ64GA308
PIC24FJ64GA310
 
a few more of the newer pic16s...
 
and some newer pic18s
PIC18(L)F23K20
PIC18(L)F24K20
PIC18(L)F25K20
PIC18(L)F26K20
PIC18(L)F43K20
PIC18(L)F44K20
PIC18(L)F45K20
PIC18(L)F46K20
PIC18(L)F23K22
PIC18(L)F24K22
PIC18(L)F25K22
PIC18(L)F26K22
PIC18(L)F43K22
PIC18(L)F44K22
PIC18(L)F45K22
PIC18(L)F46K22


 
#34
Rohan_Shah
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2013/08/03 01:27:17
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/29 04:35:45 (permalink)
4 (1)
@Ric: The datasheet has never mention this approach. I will try accessing serial eeprom in this way.
1. There does not seem to be the option to enable external interrupt.
2. When I select internal oscillator (8MHz) with 4xPLL enable, clock value remains 8MHz. All calculation of timings are also done on 8MHz. It should become 32MHz.
#35
joven
Starting Member
  • Total Posts : 66
  • Reward points : 0
  • Joined: 2007/06/06 08:13:03
  • Location: Portugal
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/29 15:28:47 (permalink)
0
was interesting if can generate the configuration for PPS of PIC32 MX/MZ.
#36
eyeball_56483
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2014/05/30 23:33:33
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/05/30 23:44:38 (permalink)
0
Please support PIC18F25K80 and dsPIC family.
 
#37
IonutB
Moderator
  • Total Posts : 115
  • Reward points : 0
  • Joined: 2008/08/04 09:43:55
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/06/02 01:44:54 (permalink)
3 (1)
Rohan Shah: what device are you using?
 
joven and eyeball_56483: those families of devices are planned for future MCC releases. 
#38
Rohan_Shah
New Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2013/08/03 01:27:17
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/06/02 02:13:15 (permalink)
0
I'm using PIC16f1939
#39
IonutB
Moderator
  • Total Posts : 115
  • Reward points : 0
  • Joined: 2008/08/04 09:43:55
  • Location: 0
  • Status: offline
Re:Suggestions for the next release of MPLAB® Code Configurator 2014/06/02 05:03:29 (permalink)
3 (1)
Rohan, there are two ways to use the 4x PLL:
 1) select PLLEN=ON and FOSC=INTOSC in the Configuration Bits section, FOSC as System Clock and 8MHz for INTOSC.
2) (software PLL) select PLL=OFF in the Configuration Bits section, FOSC as System Clock, check Software PLL Enabled and select 8MHz for INTOSC.
 
For more information please take a look at section 5.2.2.6 32 MHz Internal Oscillator Frequency Selection in the datasheet.
 
Regarding the external interrupts: if you're referring to the INT pin, you are correct - the MCC does not generate code to handle INT pin interrupts. However, interrupts-on-change are supported. You can select any PORTB pins in the Pin Manager and then check the IOCP/IOCN checkboxes. The MCC will generate an interrupt routine where you can add handling for PORTB external interrupts.
 
#40
Page: < 12345.. > >> Showing page 2 of 12
Jump to:
© 2019 APG vNext Commercial Version 4.5