Thanks, I was mislead by the fact that the MSSP2 definitions are also present in the P18F27K40.mlk file...stefan.filipovic wrote: ↑10 Aug 2020 11:56Hi Dany,
According to the datasheet (page 23), PIC18F27K40 is available only in 28-pin packages. But only 40/44-Pin MCUs have two I2C modules.
Kind regards,
Search found 3854 matches
- 11 Aug 2020 15:53
- Forum: mikroProg™ programmer and debugger
- Topic: P18F27K40: only one I2c bus mentioned.
- Replies: 3
- Views: 1278
Re: P18F27K40: only one I2c bus mentioned.
- 07 Aug 2020 19:57
- Forum: mikroProg™ programmer and debugger
- Topic: P18F27K40: only one I2c bus mentioned.
- Replies: 3
- Views: 1278
P18F27K40: only one I2c bus mentioned.
Hi, small remark:
when the P18F27K40 is chosen in MikroProg, only one I2c bus is mentioned in stead of 2.
I do not know if other processors or other peripherals show similar deviations.
when the P18F27K40 is chosen in MikroProg, only one I2c bus is mentioned in stead of 2.
I do not know if other processors or other peripherals show similar deviations.
- 09 Jul 2020 20:45
- Forum: mikroProg™ programmer and debugger
- Topic: Please power the target when starting the ICD debugger
- Replies: 1
- Views: 967
Please power the target when starting the ICD debugger
I have seen a few very cryptic error messages when trying to start the ICD debugger due to the fact that I forgot to power the target from the programmer. (See here: https://forum.mikroe.com/viewtopic.php?f=192&t=76752 ) Is it possible (and sensible) to power the target automatically when starting t...
- 09 Jul 2020 20:42
- Forum: mikroProg™ programmer and debugger
- Topic: Voltage Options slider value wrong
- Replies: 2
- Views: 1487
Voltage Options slider value wrong
Reference: https://forum.mikroe.com/viewtopic.php?f=192&t=76927 . Ths same attentionpoint as in above link is valid for the 'slider' in 'Voltage Options'. There a value is shown that does not correspond with the actual value selected with the slider (always 27V). The value becomes correct only after...
- 08 Jul 2020 20:09
- Forum: mikroBasic PRO for PIC General
- Topic: Button library (short-long press)
- Replies: 6
- Views: 1987
Re: Button library (short-long press)
Hi Community, i am looking for a solution by using the button library, for a way to detect a long time push and a short time push. Does this possible by using the provided library ? Thank for advice Fabrice Perhaps this can help: https://libstock.mikroe.com/projects/view/39/utilities , part 'Button...
- 03 Jul 2020 19:19
- Forum: mikroProg™ programmer and debugger
- Topic: Program Memory Size: 0K
- Replies: 4
- Views: 1548
Re: Program Memory Size: 0K
I have no problem at all unzipping your Rar file. The one found on the mikroE website gives an error here (using IZarc).
Thanks!
- 03 Jul 2020 19:16
- Forum: mikroProg™ programmer and debugger
- Topic: Program Memory size value?
- Replies: 4
- Views: 2132
- 03 Jul 2020 11:55
- Forum: mikroProg™ programmer and debugger
- Topic: Program Memory Size: 0K
- Replies: 4
- Views: 1548
Re: Program Memory Size: 0K
hi HexReader, thansks for your answers. :D Seems to be a completely harmless feature that does not seem to affect programming. Indeed, it does not affect programming. As far as I can tell, sizing seems to work OK when mikroProg is run from mikroC IDE. With mP (dsPIC/Pic24) it keeps showing 0K when s...
- 01 Jul 2020 20:38
- Forum: mikroProg™ programmer and debugger
- Topic: Program Memory size value?
- Replies: 4
- Views: 2132
Program Memory size value?
Hi, for the P24FJ64GB002 three different values are shown for the program memory size in mikroProg suite v2.80: a - 21K as "Program Memory Size" at the bottom of the config window b - 64KB as "Flash Memory" in the MCU info window c - 43K in the "Code Memory dump" window. I can understand a (number o...
- 01 Jul 2020 20:09
- Forum: mikroProg™ programmer and debugger
- Topic: Program Memory Size: 0K
- Replies: 4
- Views: 1548
Program Memory Size: 0K
Hi, in version 2.80 of MikroProg Suite (I can not UnRar v2.90 for some reason) the text "Program Memory Size: 0K" is shown. The selected PIC is the P24FJ64GB002. It seems to become Ok after manually selecting another PIC and reselect the original one. The "code memory dump" shows the correct number....
- 30 Jun 2020 21:34
- Forum: mikroProg™ programmer and debugger
- Topic: Mikroe Debugging unable to start
- Replies: 17
- Views: 5246
Re: Mikroe Debugging unable to start
Hi, I am trying to debug my board but when i try to start the debugger, the debugger unable to. I am able to program the board successfully but unable to start debug. I am trying to debug on a PIC32MX570F512L and my mikroProg is version 2.11. The program/debug pins are not use elsewhere (PGD, PGC)....
- 30 Jun 2020 21:26
- Forum: mikroProg™ programmer and debugger
- Topic: Enable monitoring voltages
- Replies: 1
- Views: 845
Enable monitoring voltages
What is "Enable monitoring voltages" doing? This is not in the documentation.
Thanks in advance.
Thanks in advance.
- 19 Jun 2020 19:20
- Forum: mikroPascal PRO for dsPIC30/33 and PIC24 Beta Testing
- Topic: v7.1.0 - IDE hanging on splash screen
- Replies: 13
- Views: 5157
Re: v7.1.0 - IDE hanging on splash screen
Thanks very much Jovana.jovana.medakovic wrote: ↑18 Jun 2020 09:26Hello,
The workaround for this issue at this moment is to open the IDE by opening a project file rather than the compiler .exe itself.
One more time, I apologize for the inconvenience caused by this.
Kind regards,
Jovana
- 16 Jun 2020 17:53
- Forum: mikroPascal PRO for dsPIC30/33 and PIC24 Beta Testing
- Topic: v7.1.0 - IDE hanging on splash screen
- Replies: 13
- Views: 5157
- 16 Jun 2020 17:43
- Forum: mikroC PRO for PIC General
- Topic: How to extract bytes from byte array that received in rx ?
- Replies: 13
- Views: 2716
Re: How to extract bytes from byte array that received in rx ?
You do not need a library function, but this:So, I have now in rx_buffer[] = { 0xAA, 0x1B, 0x11, 0x12, 0x00, 0x00, 0x13, 0x14, 0xFF }
and I only want D1=0x11, D2=0x12, D3=0x13, D4=0x14
Code: Select all
D1 = rx_buffer[2];
D2 = rx_buffer[3];
D3 = rx_buffer[6];
D4 = rx_buffer[7];