Search found 20 matches

And I forgot to to say:
Thanks for your help, Ttelmah

Both give just one pulse on my scope.....
I am programming with Pickit3, remove it, connect power, (make a reset) and look on my scope.
I don´t understand those things. I tried hundreds of settings ...

This code gives me only one peak on skope, then sleeping for ever............

Thanks Ttelmah. I am not able to aktivate the WDT as I want, but it works very well like this:
(Current consumtion is about 1 µA or less while sleep)

#include <18LF46K22.h>
#fuses NoWDT
...

Thanks, I forgot to say, I want to wake up the PIC by WDT. And I tried several settings for Interrupts / Timer1 / LFINTOSC - no success.
I read 2.2 / 2.7 / 3.3 in Datasheet, but maybe I understand so ...

I had many problems with the 18LF46K22:

The CTMU sometimes did not work while a PIN is set by PWM - the only solution was to check the PWM-timer if it will roll over and may wait with CTMU.
(Paras ...

Thanks PCM programmer, it works perfect without any problems - exactly as you wrote it!

wow! Thank you!!!
I had some other problems, but I will test it the next days and tell you if it works!

Yes, this is true: compiler is CCS 4.106.

Has anyone tried to run the 5-bit-DAC inside the new XLP PICs?

My 16LF1823 don't want to do anything. Output is everytime 0,0V at PIN12 = DACOUT (no external load, debugger or programmer - only sco ...

Found the solution:

In PIckit3 settings / Memory / manual select Memory ranges / EEPROM was not activated. Maybe this happens while changing the device.

Thanks Ttelmah, that is a good idea, and I will use it in future, but it did not solve the problem. Adding 100pF to VDD should help sometimes, but has no success too.

Hello,
if I write a value to the EEPROM with write_EEPROM(x,y) I can read it by using y=read_EEPROM(x).

But if I write to EEPROM by using #ROM 0xF000={y} the value is not really written to EEPROM ...

Thanks!
With your help, I found the (idiotic) mistake - I have forgotten:
8 Bit PIC => INT= 8Bit
16 Bit Pic => INT= 16 Bit
Additional the CCS compiler for dspic could be better. But pl ...

Hi,
I am used to work with PICs like 12Fxx or 18Fxxx and have some rules of thumb, how much time some code needs to execute. As code get more complex, speed of dspic30F drecreases in a terrible way. ...