Author |
Message |
Topic: Compiler command line v5.098 problem? |
Josep Robert
Replies: 24
Views: 53574
|
Forum: General CCS C Discussion Posted: Mon Dec 28, 2020 2:36 am Subject: Compiler command line v5.098 problem? |
Thanks Ttelmah
The code is 100.00% the same. The only difference is the compiler version used.
I've have the two versions installed; with the previous version a 7% less flash is used. |
Topic: Compiler command line v5.098 problem? |
Josep Robert
Replies: 24
Views: 53574
|
Forum: General CCS C Discussion Posted: Mon Dec 28, 2020 1:33 am Subject: Compiler command line v5.098 problem? |
Today I've received the last ccs command line compiler version v5.098.
I’ve recompiled some of my projects for PIC18LF47K40 and found that the used ROM increases a 6%-7%.
Looking at .lst file ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Thu Nov 19, 2020 12:18 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
Thanks to you temtronic.
The Microchip Compiled Tips ‘N Tricks Guide is quite old but very interesting to have in mind while designing.
http://ww1.microchip.com/downloads/en/DeviceDoc/01146B.p ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Wed Nov 18, 2020 4:23 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
Thanks for your reply temtronic.
The 'appnote' you recommend is very interesting:
AN606 Low Power Design Using PICmicro™ Microcontrollers
https://www.microchip.com/wwwAppNotes/AppNotes.asp ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Tue Nov 17, 2020 2:15 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
PIC consumes < 1uA.
Receives a 5 bytes order plus a heading break byte.
The PIC starts consuming 2500uA while receiving the order and transmitting the answer.
PIC goes to sleep again consuming & ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Tue Nov 03, 2020 7:31 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
Thanks for your answer Ttelmah.
You are right again.
Sorry for asking a question that I know that you are answering almost every day during more than a decade.
Once I have studied and understood ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Tue Nov 03, 2020 7:18 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
Thanks for your answer temtronic.
I need an average consumption current of 100uA. I want the two AA (Vdd 3.0V...1.8V) batteries last more than 2 years.
With all peripherals disabled I have consu ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Fri Oct 30, 2020 5:55 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
I have done more tests without success.
while(TRUE) // Whith this loop I'm able to awake the PIC to receive data but with a lot of errors!
{ // With this loop at ... |
Topic: PIC18LF47K42 doesn't awake when receives data by UART. |
Josep Robert
Replies: 12
Views: 29066
|
Forum: General CCS C Discussion Posted: Fri Oct 30, 2020 5:34 am Subject: PIC18LF47K42 doesn't awake when receives data by UART. |
I use PIC18LF47K42 for the first time.
I'm not able to awake the PIC when it receives a character by the UART1 using interrupts once it is asleep.
I'm forgetting something...
...This PIC has ... |
Topic: PIC18F47K42, Timer1 interrupt and sleep. |
Josep Robert
Replies: 2
Views: 11928
|
Forum: General CCS C Discussion Posted: Fri Oct 30, 2020 5:13 am Subject: PIC18F47K42, Timer1 interrupt and sleep. |
Thank you very much for your immediate help.
Now works fine.
Regards.
// PIC18F47K42, Timer1 interrupt and sleep...
// Migrating from PIC18LF47K40
#case
#include <18F47K42.h> ... |
Topic: PIC18F47K42, Timer1 interrupt and sleep. |
Josep Robert
Replies: 2
Views: 11928
|
Forum: General CCS C Discussion Posted: Wed Oct 28, 2020 7:09 am Subject: PIC18F47K42, Timer1 interrupt and sleep. |
While porting a code from PIC18LF47K40 to PIC18F47K42 that has the double of ram I found a problem that simplifying a lot is the following.
When I enable_interrupts(INT_TIMER1) regardless of disabl ... |
Topic: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
Josep Robert
Replies: 9
Views: 22192
|
Forum: General CCS C Discussion Posted: Wed Mar 04, 2020 4:41 am Subject: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
With this code I get the CRC-16 / KERMIT. It works fine. Thanks again Ttelmah for your help.
#include <18LF47K40.h>
#use delay(clock = 16MHZ, internal)
#FUSES WDT_SW
#FUSES WDT65 ... |
Topic: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
Josep Robert
Replies: 9
Views: 22192
|
Forum: General CCS C Discussion Posted: Wed Mar 04, 2020 3:55 am Subject: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
Thank you very much for your immediate help. Regards. |
Topic: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
Josep Robert
Replies: 9
Views: 22192
|
Forum: General CCS C Discussion Posted: Wed Mar 04, 2020 3:23 am Subject: I need CRC16-CCITT(KERMIT) not CRC16-CCITT(XMODEM) |
Hello.
I need to calculate the CRC16-CCITT(Kermit) but this routine gives me the CRC16-CCITT(XMODEM).
I don't know what to change to obtain the CRC16-CCITT(KERMIT).
I don't know to implement ... |
Topic: PIC18LF47K40 - restart_cause() returns unknown values. |
Josep Robert
Replies: 8
Views: 24745
|
Forum: General CCS C Discussion Posted: Thu Oct 03, 2019 4:12 am Subject: PIC18LF47K40 - restart_cause() returns unknown values. |
Hello!
When I try to use the restart_cause() function I obtain values that are not in the list of constants in 18LF47K40.h file.
Can you help me to obtain the real cause of any restart cause?
... |
|