I have been using the newest 'Q' PICs which are faster, lots more memory and periphials and only cost $1.24.
Announcement
Collapse
No announcement yet.
Voodoo Main Discussion
Collapse
X
-
Originally posted by waltr View PostThese two PICs are very compatible (pin for pin the same) but there will be slight code differences.
Once the Source code is available I can take a look and port to a newer PIC.
I've been comparing the two datasheets, and also found this migration document -> http://ww1.microchip.com/downloads/e...doc/39647a.pdf
The 18F45K20 is much more complicated than this project requires.
The 18F4520 ADCs are enabled in sequential blocks using ADCON1, whereas the 18F45K22 uses ADCON1 to set the positive and negative voltage references. The ADCs can also be enabled/disabled individually using the ANSEL registers (ANSELA to ANSELE).
The T0CON register appears to be unchanged, but T1CON is quite different. Timer1 has many more features than the the 18F4520.
I'm not certain from the datasheet, but it looks like writing to EEPROM is also affected.
I think there are too many differences between the two to just compile this blindly and hope for the best.
Comment
-
Originally posted by MartyJ1963 View Post@Qiaozhi,,The mosfets, FQT7N10 (Q11, Q13), are they FQT7N10L or FQT7NLTF? or is either ok? And are they SOT-233 (Surface mount)< Thanks, Marty.
Also, cannot find a datasheet for an FQT7NLTF.
Comment
-
Ok... so 18F45K22 is a long shot.
No problem.
I am sure 100% that i can put 18F4520 in socket instead 18F45K22 and flash it as well.
I am only not sure if i can obtain 18F4520 in local shops.
...
Oh yes i can:
https://www.mgelectronic.rs/microchip-pic18f4520-ip
Now.. question is; since mikroBootloader is easy recognizing the board at USB and can connect it; is it correct if i only flash the hex simply into chip with mikroBootloader?
I have to ask this; i am not familiar with these "new" PIC's at all.
I am AVR freak totally. But i didn't payed much of attention on PIC's lately.
Comment
-
Similar question:
why ...Tools-me Programmer F11... or mikroProg Suite is not recognizing this development board as well?
Since both (mikroBootloader and me Programmer) are parts of MikorC Pro for PIC software.
What kind of problem is this?
(that's why i don't like MikroE and their "philosophy" at all)
...
Probably driver for my development board? Which is? Where to find it? Not on MikroE site for sure!
So i have now all the products from the very same manufacturer and those are not recognizing each other!?
Pfffffff!
Comment
-
Originally posted by 6666 View PostQiaozhi, could we get a full BOM please so we can source some of these parts thanks.
i hope he can sell all, i think it is a fair price too (the production, storage and amazno fees will take a big part of the price)
Comment
-
I wonder how will majority of people here program the PIC for this project?
Deeper i get into information on PIC18f series; clearer to me that this is not simple task as with Arduinos.
Easiness would be the deciding key when pick mcu for the project like this.
FTDI adapter is not enough. PIC must have bootloader installed to accept such programming.
George... what was you thinking?
Now you are pushed to sell programmed chips as well!
Comment
-
It's very easy. I can use PicKit3 to load the hex with ICSP directly. Since I can't work with MIKROE stuff - I don't have it (it isn't free is it?) I won't be able to modify/compile it etc but probably not going to need as per first evaluation of the project. If the PIC is just used to generate timings and some simple operations for the DISC/ADC I can try to transfer the code to my PIC32 project (huge thanks to waltr!).
My book arrived today in the forwarding company in UK (free next day UK delivery) so I will get it next week at my place. I can't wait.
Comment
-
Originally posted by ivconic View PostSimilar question:
why ...Tools-me Programmer F11... or mikroProg Suite is not recognizing this development board as well?
Since both (mikroBootloader and me Programmer) are parts of MikorC Pro for PIC software.
What kind of problem is this?
(that's why i don't like MikroE and their "philosophy" at all)
...
Probably driver for my development board? Which is? Where to find it? Not on MikroE site for sure!
So i have now all the products from the very same manufacturer and those are not recognizing each other!?
Pfffffff!
The Microchip PIC kits are no recognized either, so I use the Microchip X IPE to flash the PIC directly through the ICSP connector.
Update: Go to https://www.mikroe.com/ready-pic
and scroll to the bottom of the page. The bootloader software is there ... BUT - it only supports 16F877, 18F25K22, and 18F45K22.
Comment
Comment