As you may expect when using an 8 pin PIC I would like to have access to the gretest number of I/O pins. To do this I presumably need to use the internal 4Mhz clock and no MCLR.
As the Version 3 board is wired can I actually 'remove' the clock input?, I can go down to 1 pin with the R/C oscillator or would an option be to configure for the crystal oscillator and remove the crystal?
As for MCLR can I take it that the MCLR switch will simply act as an input switch when the PIC is not configured to use MCLR?
Any thoughts on the above will be welcome.
As an alternative I can use a PIC KIT 1 board for programming but my first thoughts are to stick with Dev Board 3 for ease of interface with Flowcode.
Version 3 Development board and 8 pin PIC's eg 12F675
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Hi Mark
Firstly your right about the reset switch acting like an input if the MCLR is disabled although i've not tested this idea on the Dev board.
As for the crystal oscillator changing to the internal oscillator will add I/O lines from your PIC aslong as the PIC is sat in connections that are going to switches / leds etc. If the pins are just wired straight to the oscillator circuitry then there is no point.
Firstly your right about the reset switch acting like an input if the MCLR is disabled although i've not tested this idea on the Dev board.
As for the crystal oscillator changing to the internal oscillator will add I/O lines from your PIC aslong as the PIC is sat in connections that are going to switches / leds etc. If the pins are just wired straight to the oscillator circuitry then there is no point.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
Mark
- Posts: 209
- Joined: Thu Oct 19, 2006 11:46 am
- Location: Bakewell, UK
- Has thanked: 20 times
- Been thanked: 16 times
MCLR swirch as input on Dev Board v3
Steve,
Thanks,
I have tested the use of MCLR as an input and it works fine.
Presumably the limitation of the oscillator pins not being readily usable even when configured as input/outputs is the same on the e-blocks processor board?
Thanks,
I have tested the use of MCLR as an input and it works fine.
Presumably the limitation of the oscillator pins not being readily usable even when configured as input/outputs is the same on the e-blocks processor board?
Go with the Flow.
- Steve
- Matrix Staff
- Posts: 3434
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
Hello Mark,
Yes, the same is true of the EB-006 multiprogrammer E-Block.
However, one solution for you may be to raise the 2 oscillator pins so that they don't go into the DIL socket and connect them to one of the free i/o lines (e.g. in one of the bigger DIL sockets). This would work for both the dev board and the multiprogrammer.
If you don't want to bend the pins of the chip, you could use another DIL socket or two between the chip and the DIL socket in the board, and bend the pins of one of these instead.
Yes, the same is true of the EB-006 multiprogrammer E-Block.
However, one solution for you may be to raise the 2 oscillator pins so that they don't go into the DIL socket and connect them to one of the free i/o lines (e.g. in one of the bigger DIL sockets). This would work for both the dev board and the multiprogrammer.
If you don't want to bend the pins of the chip, you could use another DIL socket or two between the chip and the DIL socket in the board, and bend the pins of one of these instead.