|
|
View previous topic :: View next topic |
Author |
Message |
ZextroM
Joined: 10 Apr 2012 Posts: 10
|
Why I don't acquire a precise PLL working? |
Posted: Mon Oct 29, 2012 4:58 pm |
|
|
Code: | #include <18F4553.h>
#device adc = 12
#include <stdlib.h>
#include <math.h>
//#fuses HS,WDT,WDT4,NOPROTECT,NOBROWNOUT,NOLVP,NOPUT,NOWRT,NODEBUG,NOCPD //for 18f4553
//#fuses HSPLL,WDT,WDT1024,NOPROTECT,NOBROWNOUT,NOLVP,NOPUT,NOWRT,NODEBUG,NOCPD //for 18f4553
#fuses HSPLL,PLL5,CPUDIV1,USBDIV,WDT,WDT1024,NOPROTECT,NOBROWNOUT,NOLVP,NOPUT,NOWRT,NODEBUG,NOCPD //for 18f4553
//////// Fuses: PLL1,PLL2,PLL3,PLL4,PLL5,PLL6,PLL10,PLL12,CPUDIV1,CPUDIV2
//////// Fuses: CPUDIV3,CPUDIV4,NOUSBDIV,USBDIV,XT,XTPLL,EC_IO,EC,ECPLL_IO
//////// Fuses: ECPLL,INTRC_IO,INTRC,INTXT,INTHS,HS,HSPLL,NOFCMEN,FCMEN
//////// Fuses: NOIESO,IESO,PUT,NOPUT,NOBROWNOUT,BROWNOUT_SW,BROWNOUT_NOSL
//////// Fuses: BROWNOUT,BORV45,BORV43,BORV27,BORV21,NOVREGEN,VREGEN,NOWDT
//////// Fuses: WDT,WDT1,WDT2,WDT4,WDT8,WDT16,WDT32,WDT64,WDT128,WDT256
//////// Fuses: WDT512,WDT1024,WDT2048,WDT4096,WDT8192,WDT16384,WDT32768
//////// Fuses: CCP2B3,CCP2C1,NOPBADEN,PBADEN,NOLPT1OSC,LPT1OSC,NOMCLR,MCLR
//////// Fuses: NOSTVREN,STVREN,NOLVP,LVP,ICSP1,ICSP2,NOXINST,XINST,DEBUG
//////// Fuses: NODEBUG,PROTECT,NOPROTECT,CPB,NOCPB,CPD,NOCPD,WRT,NOWRT,WRTC
//////// Fuses: NOWRTC,WRTB,NOWRTB,WRTD,NOWRTD,EBTR,NOEBTR,EBTRB,NOEBTRB
//#use delay(clock=20Mhz)
//#use delay(oscillator=12Mhz, clock=48Mhz)
#use delay(clock=48Mhz) |
It's so interesting not to get an accurate working on isis simulation when i try to adjust the newly PLL setting in my codes.
Even though I've just read and executed as the Ttelmah directions in
accordance with article from ccs's forum,
http://www.ccsinfo.com/forum/viewtopic.php?t=44305
I've mainly nothing in my hand. Could you please help me regarding this issue ? |
|
|
Mike Walne
Joined: 19 Feb 2004 Posts: 1785 Location: Boston Spa UK
|
|
|
ckielstra
Joined: 18 Mar 2004 Posts: 3680 Location: The Netherlands
|
|
Posted: Mon Oct 29, 2012 5:58 pm |
|
|
In this forum we don't like ISIS because it has many, many problems.
Your problem is that ISIS is not handling the crystal and PIC fuses.
Solution is to hard set the frequency in ISIS, somewhere hidden in the PIC properties (right click). |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9240 Location: Greensville,Ontario
|
|
Posted: Mon Oct 29, 2012 6:47 pm |
|
|
ISIS aka Proteus is full of bugs,errors and faulty DRCs.As you've found out , ISIS can't even do the SIMPLEST of PIC simulations, so do not be suprised when it can't figure out more 'complex' code.
Buy a few PICs,a breadboard and a handful of parts and build real circuits.
Once you get the 'blinking LED' program up and running ,you'll be suprised how easy it is to get real PICs to do real programs in the real world.
Do yourself a big favour and get rid of ISIS.
hth
jay |
|
|
ZextroM
Joined: 10 Apr 2012 Posts: 10
|
|
Posted: Tue Oct 30, 2012 3:22 am |
|
|
exactly guys. i ve already known why i needa complain about (isis or vsm) this bugs + erros on mentioned software ...
i just wondered, when i use the normal clock (right click 20Mhz) without pll option on my software, it works. although i changed pll option on my codes, i dont receive the same response from the isis ...
in order to monitor the us (micro second) triggering utility, i shoulda use oscilloscope to approve my circuitry which device i dont ve at my home
since now, i thank to you all for spending ur times to reply me ... thx once more guys ... |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|