Matrix user forums

WDT509sleep.fcfx here's the new version; with faster blink rate and sleep woken up by the watchdog timer (i seem to have lost the 'double tap' on the blink though...) other then removing a 'NOP' at the end of the sleep command;which doesn't seem to do anything...?it seems to work OK. pity i can't t...

i quite agree; the newer little PICmicro's are incredible,but these are a tube i already have here...postage here is eye-watering like 15 euros for 1 chip :shock: the use of upper case is partly what threw me and the differences between 12F and 18F registers;i foolishly tried to change as little as ...

specifically adding the following C block

option_reg = option_reg | 0b00001111; //Configure watchdog to 1:128 Postscaler
wdtcon = 0b00000111; //Configure watchdog 1:256 Prescaler, Software Watchdog enabled

produces a C file but wont produce a hex file; throwing the following errors:-

i have a simple project which mis-uses the watchdog timer in a 12F509 to produce eye-catching warning flashes;my question is how do i get more control other than just enabling the WDT in the config's and ducking for cover :wink: ? the only forum example was,i think,for a 18F part.adding the 'c code'...

The Osc speed selection dropdown does stop at a maximum of 8Mhz,which is wrong for this chip. it's capable of 20Mhz clocked PWM. But your settings for the osc type are wrong.. you have ' EC on CLKIN pin ' selected...not the internal HS osc. I changed some of the settings and added a C-block for the ...

So, maybe not a hardware problem after all (unless it's all of them!) There seems to be a software problem causing contention between 'program' and 'run' pin states. Microchip really has thrown the banana peel with this thing. I noticed the PDF user guide for the IPE, released with MPLAB-X v4.20 and...

no,i checked that;as well as the pull-up/down an resistor value options on the clock and data lines
(under ISP settings) nothing stops this annoying problem.
you say yours is OK? i am beginning to wonder if my unit has a fault..?

yes, i agree;i posted this to help other people who may run into problems,and blame it on bugs in either their code/FlowCode/XC-8 etc. etc. it helps to know WHAT is not working,before spending hours chasing your own tail

Based on my experiments so far;the PK4 is a 'broken' piece of hardware...the programmer to go/SD card feature was promised two versions ago,when the PK4 was first advertised; it was one of the two reasons i bought the new model and is still absent from IPEv4.20... I've been in contact with microchip...

That is useful to know;i couldn't make much headway in all the scattered information i've gathered. but i completely forgot about communication sync speeds. :oops: i've also found the newer enhanced PIC's are much more complex than the older families. The 12F1572 has far more registers to get wrong,...

I looked for the long-awaited update of MPLAB-X on Microchips home page and it's now available! ...or should be. the link on their download tab is wrong! if you click on it, it downloads v4.15, the previous version. however some one on here has posted a link over an unrelated problem (though it is r...

PIC Clocks In FlowCode In The PIC By default PICs come with their internal oscillator enabled at a default value so they can be programmed reliably,without connecting an external crystal. The OSCCON register (responsible for configuring the PIC's operating speed) has 8-bits, Each bit has a value whi...

Thanks for that; i also found this, which clears up my confusion
viewtopic.php?f=68&t=19308
I had forgotten that OSCCON, though it is a 'configuration' ISN'T actually part of the CONFIG register...

strange; i still don't know if the C block is even required..the information available isn't clear on this point. i also spelt 'OSCCON' as 'OSCON'...XC-8 picked that one up :oops: i added the closing delay i missed out and it works! So exactly when IS a C-block setup required? i realise these newer ...

NOOOH! Don't sling it; or if you must,send it to me :lol: or keep it to re-flash the PICKit 3 when,not if,it bricks it's own firmware during the hokey cokey it performs EVERY time you change chip, IDE, or your pair of socks. and remember you can still use the other firmware versions for the PICKit2 ...

In answer to the question 'does this work with an OEM PICKit2 ?' the answer is most definately YES! i have two,an ancient black-button one and a newer red button version,as well as and a crappy 'sure' clone that won't operate unless you set the VDD voltage to <4.7Volts; all of these and three differ...

i am trying to get the OSCCON correctly set on a PIC 12F1572 but the 'project > options' selection i choose simply doesn't seem to work; the timings are way out. I read a post about another user having trouble with PWM clock speeds on the same chip, and it mentions an osc helper utility... just Wher...

Playing about with a tube of 12F1572 PIC's chosen as a more modern replacement for the 12F675 (and finding PICKit 4 wont work...) i had to juggle from MPLAB IPE to PICKit apps 2 and 3,only to find neither cover these chips. I remembered an updated device file i had...so,as the PICKit3 uses the SAME ...

the 32,768xxx is a standard 'wrist-watch' timing xtal; maybe the drop down just replaces the least significant digits with zeros (to make it easier to read?) The reason for using these xtals is they can be divided down to achieve exactly 1hz ticks (hence the 'watch' tag..) with the PIC family 32,768...

going back to the first principles,trying to follow the examples in the Elektor Flowcode book (based on version 6) SOOO much has changed, i may as well be reading a cookery book! clear as mud...:x i made a daft mistake and selected a switch icon instead of a decision icon; not remembering i had done...

after replicating some older instructions on this forum, i added the MikroElektronika EasyPICv7 board and its supporting programmer application to the options in Flowcode7. simply by selecting the file location of the programming software and adding it to the path box in 'programmer-options'. mikroP...

ah,so that's why the A2D dial component is missing...it's obsolete! talk about barking up the wrong tree... it really has been a few hair-pulling days;so much so that i managed to miss the bit about typing a value in the 'return value' box... it IS mentioned in training video 14,but i was snow blind...

i am still trying to get any headway with flowcodev7;i try to open the examples,only to find there is something missing,or a component has 'gone' in v7.it's driving me nuts! as the program was released LAST YEAR;i would expect the helpfiles and examples to actually be useable... being able to load a...

perfect! the -T switch worked..now i am able to 'compile to chip' and it powers the demo board after the program/verify cycle for anyone else who hits this snag, the configs; in the 'programmer' > 'paramenters' option that work are:- Location:- $(appdir)tools\PICkit2\pk2cmd.exe Parameters:- -B$(appd...

well,after gettting no response;i tried yet again...and got it to work,sort of... i added an entry for PICkit2 with the parameters from the webpage; no joy. then i ticked the ' default compiler for the platform C ' box then clicked on SAVE; THEN named the new the new setting name ' PICkit2 programme...