Contend with 16F690´s Port A
Contend with 16F690´s Port A
Hi all. I´m just trying to turn on the leds on a EB004 E-block, connected to a 16F690´s Port A (20MHz) by a EB-006-7 multiprogrammer (XTAL/FAST). The flowchart consists in a single output box with 0b11111111 PORT A. Simple, BUT why none of them turn on ?? Coiled with this little issue, so a little help to this friend. Thanks.
- Attachments
-
- Teste 16F690.fcf
- (4.5 KiB) Downloaded 376 times
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: Contend with 16F690´s Port A
Not only do I agree with Kenrix2,
But I would like to add:
Port A0 and port A1 will be port B7 and B6 on Eb006 respectively (not 100% sure on all the connections, will check them out tonight).
Port B will not work the way you think it should.
For example if you want to use port B6 and B7 on the EB006 programmer, then that will be B0 and B1 on the programmer.
So If you have LED Eblock connected, and enable B6 and B7, then LED D0 and D1 will light respectively.
I know its got nothing to do with question about portA, but i thought I would mention it just in case you decide to use port B (4,5,6 or 7) for any reason.
Martin
But I would like to add:
Port A0 and port A1 will be port B7 and B6 on Eb006 respectively (not 100% sure on all the connections, will check them out tonight).
Port B will not work the way you think it should.
For example if you want to use port B6 and B7 on the EB006 programmer, then that will be B0 and B1 on the programmer.
So If you have LED Eblock connected, and enable B6 and B7, then LED D0 and D1 will light respectively.
I know its got nothing to do with question about portA, but i thought I would mention it just in case you decide to use port B (4,5,6 or 7) for any reason.
Martin
Martin
Re: Contend with 16F690´s Port A
Thanks 2 <Kenrix2>. I knew Port C is the only 16F690´s port with a logic behavior, at least dealing with Eblocks, i.e
RC0 turns on LED 0, RC1 turns on LED 1..... RC7 turns on LED 7.
As <Medelec35> said 2 of 4 avaluable pins of Port B give us a surprise: RB6 address LED 0 and RB7 address LED 1 on
the EB-004 Led board. It´s a fact. But the doubt remains almost the same: - how many LEDS will turn on a EB004 LEd board
connected to a 16F690´s Port A, via an EB-006 Multiprogramer ? One, two or none of them ?
RC0 turns on LED 0, RC1 turns on LED 1..... RC7 turns on LED 7.
As <Medelec35> said 2 of 4 avaluable pins of Port B give us a surprise: RB6 address LED 0 and RB7 address LED 1 on
the EB-004 Led board. It´s a fact. But the doubt remains almost the same: - how many LEDS will turn on a EB004 LEd board
connected to a 16F690´s Port A, via an EB-006 Multiprogramer ? One, two or none of them ?
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: Contend with 16F690´s Port A
You can get a few working if you connect to port A and pot B of the programmer.Karbulla wrote:But the doubt remains almost the same: - how many LEDS will turn on a EB004 LEd board
connected to a 16F690´s Port A, via an EB-006 Multiprogramer ? One, two or none of them ?
If can let you know a bit later, what pins of port A connect to which pins of portA and portB of Eb006.
Its something like 3 pins of port A connect to port B
and 2 pins or port A connect to port A itself.
Martin
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: Contend with 16F690´s Port A
As promised:
Below is a list Microcontroller connections verses Programmer connections
Test carried out using EB006 V7 using internal oscillator and J18/19 on A6&7
Below is a list Microcontroller connections verses Programmer connections
Code: Select all
Chip Programmer
A0 B7
A1 B6
A2 B2
A3 Not connected
A4 A6
A5 A7
Martin
Re: Contend with 16F690´s Port A
This idea, where we connect PIC´s pins simultaneously to Port A and Port B may be implemented by E-Blocks
(EB006 + EB004) or should I use discrete LEDs and PIC ?
Ask this cause I tried the E-Block version and seems impossible to EB004 (leds) links to different Port in the
same "Pin Connections" window.
(EB006 + EB004) or should I use discrete LEDs and PIC ?
Ask this cause I tried the E-Block version and seems impossible to EB004 (leds) links to different Port in the
same "Pin Connections" window.
- 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:
Re: Contend with 16F690´s Port A
Hello,
The EB006 correctly routes the 18, 28 and 40 pin chips to the correct port pins.
However the 8, 14 and 20 pin devices have a very different style so to allow these to work we had to re-route the ports for these chips slightly.
It may be worth moving to a 28-pin or 40-pin device for simplicity and extra I/O?
The EB006 correctly routes the 18, 28 and 40 pin chips to the correct port pins.
However the 8, 14 and 20 pin devices have a very different style so to allow these to work we had to re-route the ports for these chips slightly.
It may be worth moving to a 28-pin or 40-pin device for simplicity and extra I/O?
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
Re: Contend with 16F690´s Port A
Frankly I´d like to explore the idea to re-route Ports in the 16F690 (20 pins) for a simple reason:
I got about 15 of them, and doing so, I´d give a good use to them. All I know is that we have to
setup the internal oscillator releasing OSC1, OSC2 pins to behave as adittional I/Os, but and the
rest ? Could this change of Ports be implemented with E-Blocks or have I to implement it discretly ?
Any clue about this issue will be welcome. Thanks.
I got about 15 of them, and doing so, I´d give a good use to them. All I know is that we have to
setup the internal oscillator releasing OSC1, OSC2 pins to behave as adittional I/Os, but and the
rest ? Could this change of Ports be implemented with E-Blocks or have I to implement it discretly ?
Any clue about this issue will be welcome. Thanks.