Author |
Message |
Topic: Warning 216 : How to prevent function mutualization |
tssir
Replies: 3
Views: 9523
|
Forum: General CCS C Discussion Posted: Tue Apr 18, 2017 11:46 am Subject: Warning 216 : How to prevent function mutualization |
#ORG solution not working with a "real world" large program (a 58ko hex file, for my current project). #ORG itself works, and puts isr code at the right place (checked on pic ROM). But [] op ... |
Topic: Warning 216 : How to prevent function mutualization |
tssir
Replies: 3
Views: 9523
|
Forum: General CCS C Discussion Posted: Tue Apr 18, 2017 3:12 am Subject: Warning 216 : How to prevent function mutualization |
Thank you for answer.
For a general use, i will dissociate interruption function from main function.
Both solutions :
1) I must use only elementary operations on interruption (add, shift, ...). ... |
Topic: Warning 216 : How to prevent function mutualization |
tssir
Replies: 3
Views: 9523
|
Forum: General CCS C Discussion Posted: Mon Apr 17, 2017 2:34 pm Subject: Warning 216 : How to prevent function mutualization |
Hello,
I use
#include <16F1705.h>
#fuses INTRC_IO,NOWDT,NOMCLR,NOPROTECT,NODEBUG,NOLVP
#use delay(clock=32MHZ)
struct SDummy
{
byte a;
unsigned int16 value;
} ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Sat Apr 01, 2017 2:45 am Subject: write_program_memory and 18F27J53 |
The answer is : NOWPDIS fuse
Datasheet :
"WPDIS:Write-Protect Disable bit
1= WPFP<5:0>, WPEND and WPCFG bits are ignored; all Flash memory may be erased or written
0= WPFP<5:0>, ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Sat Apr 01, 2017 12:46 am Subject: write_program_memory and 18F27J53 |
Thank you.
Good news ! It work for me too !!!
I take exactly same C code. Compile it, and flash it on hardware pic. Then read memory with PicKit3.
Compiled code is strictly the same as you.
My m ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Sat Apr 01, 2017 12:03 am Subject: write_program_memory and 18F27J53 |
Thank you very much for your test.
Did you have ASM or binary compiled code ? Thank you. |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Fri Mar 31, 2017 1:51 pm Subject: write_program_memory and 18F27J53 |
I am still not able to write PIC18F program memory with CCS ...
After many, many, many tries. Neither with ASM or C.
MPLAB simulator is not reliable. Memory self programming works in every way with ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Thu Mar 23, 2017 9:14 am Subject: write_program_memory and 18F27J53 |
Thank you for informations.
You are true, USB is useless for my test. It's a bad copy from other project to get the FUSE and clock line. No impact on result.
I know that it is not the place to fin ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Thu Mar 23, 2017 8:05 am Subject: write_program_memory and 18F27J53 |
I use ccsc 5.043 and Mplab-X 3.55.
New test code :
#include <18F27J53.h>
#fuses NOWDT,NOSTVREN,NOXINST,NODEBUG,NOCPUDIV,NOPROTECT,INTRC,NOCLOCKOUT,NOFCMEN,NOIESO,NODSBOR,NODSWDT,NOIOL1WAY,N ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Wed Mar 22, 2017 2:33 pm Subject: write_program_memory and 18F27J53 |
Thank you very much for your test.
Then the source code seems ok.
I usualy manage application config flash memory with an ownmade library (based on write_program_memory). It works with some other ... |
Topic: Difference to use between .c and .h included files |
tssir
Replies: 2
Views: 8133
|
Forum: General CCS C Discussion Posted: Tue Mar 21, 2017 1:29 pm Subject: Difference to use between .c and .h included files |
C file is for "to compile" code. H (header) file for declarations (structure, class, function prototype, macro, ...).
With "normal" compiler, each .c files become an .o (object). ... |
Topic: write_program_memory and 18F27J53 |
tssir
Replies: 15
Views: 32086
|
Forum: General CCS C Discussion Posted: Tue Mar 21, 2017 12:06 pm Subject: write_program_memory and 18F27J53 |
Hello,
I can't write flash program memory, by pic itself.
A simple example :
#include <18F27J53.h>
#fuses NOWDT,NOSTVREN,NOXINST,NODEBUG,NOCPUDIV,NOPROTECT,INTRC,NOCLOCKOUT,NOFCMEN,NOI ... |
Topic: ADC not working on simple 16F1705 program |
tssir
Replies: 3
Views: 9502
|
Forum: General CCS C Discussion Posted: Tue Feb 14, 2017 10:21 am Subject: ADC not working on simple 16F1705 program |
YES !!!!
Thank you very much.
I replaced a macro (define) by sAN3 for my test. It was wrong.
This small program works with :
set_adc_channel(3);
Now i can compare and search why my main progr ... |
Topic: ADC not working on simple 16F1705 program |
tssir
Replies: 3
Views: 9502
|
Forum: General CCS C Discussion Posted: Tue Feb 14, 2017 8:33 am Subject: ADC not working on simple 16F1705 program |
Hello,
I use 16f1705 on a large project, and i have strange behaviour from it's ADC. Returned value is always 1014(dec).
If i use ADC_CLOCK_DIV_2 instead of ADC_CLOCK_DIV_64, value is random (358, ... |
Topic: Interruption loops ... despite flag clear |
tssir
Replies: 4
Views: 14059
|
Forum: General CCS C Discussion Posted: Thu Sep 08, 2016 1:00 am Subject: Interruption loops ... despite flag clear |
I found a clue ...
It seems that both interruptions are mixed.
On RC changes, #INT_RA is called.
I try this code :
#INT_RA
void handler_ra(void)
{
// Rapid blink
output_bit ... |
|