Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Hello!
I finally decided to start a thread about a project I've been doing for the past 8 months. Currently it can be considered "alpha" or maybe "early beta" stage, but - despite literal meaning of these terms - the things that are already done (and there's quite a lot of them) work pretty...
dspic33 lcd
1. RTFM
2. RTFM
3. yes - you should change to MAX3232 and use 4 charge capacitors 100n and one bypass cap on the voltage supply pin - 100n also. this caps cost almost nothing so don't try to find what will happen if you omit some of them.
4. the best osc is the one you need... RTFM...
1. it does not
2. no
3. yes (that is a stupid question...) in fact - potyo2 is very very close to the original.
4. find the lates archive in this topic
0x41 0x56 0x45!!
i think that 'which is the most pow powrt MCU' is determined by figures, which can be found in the datasheets, not by the votes of their users.
0x41 0x56 0x45!!
adc interrupt dspic
I don't know much about ADC beside what can be seen in the datasheet:
at the beginning you need to declare an array and a pointer:
#define N 128
unsigned int array[N];
unsigned int* array_pointer=array;
than you need to perform your conversion N times in this way...
your question was answered like 5 times already, but you are still waiting for the answer...
the value in datasheet IS real capacity. If you don't believe us, that hex is almost 3x bigger than the code it contains - it's a pity, we'll have to live with that... you even had the answer WHY it is...
dspic input capture problems
by 'directly' i mean changing this field to DEBUG [; , there is also an indirect way - you need to specify a dummy table variable, and locate it under address 0x800. it's size should be 80bytes (40 words). however switching build mode to DEBUG is smarter [;
verify...
icd2.5
1. false - pickit can program low voltage chips without problems.
2. true - pickit2 cannot debug pic24, dspic30 and dspic33. icd2 also allows more breakpoints.
3. pickit2 is usually just enough for someone interested in 8-bit PICs. it's not better, it's just more suitable for most of...
32bit timer dspic
change build mode in mplab from RELEASE to DEBUG. in new versions there is a dropdown menu in the center of top toolbar. in older mplab you need to find some build options and change them to 'build for ICD2'. ICD2 uses first 80b of RAM, that's why you cannot see the variables...
input capture dspic
the buffers should not be read via ICD2. you need to examine your variables - do they change or are alwaysl 0? the buffers usualy show 0 in ICD2. that is a hardware limitation i suppose. probably you'd lost the contents of the buffer if ICD2 would read that.
another thing -...
icd2 clone
dspic30 is a 5V chip - all clones will support it
dspic33 and pic24 are 3.3V chips (3.6V max) - only clones with level conversion support them (potyo2), but some people say, that 5V clones also do - the PGC, PGD and MCLR lines are sometimes 5V tollerant (only those pins, which have...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
