Propeller Not recognized on Custom PCB design.
greybeard
Posts: 65
in Propeller 1
Background: Some time ago I build a simple prototype that contained a 3.3V regulator, an EPROM, a Propeller 40 pin DIP, and FT232RL with reset circuit. With a lot of feed back from the community it finally worked well and continues to work. With lessons learned, I integrated the Propeller in the larger project PCB. The first one worked without problems. Revisions had to made to the project PCB but still used the Propeller as used previously. Basically had to move some components around.
When I assembled the key components with the Propeller, 3.3V Regulator, EPROM, FT232RL and reset circuit on the new PCB but the Propeller is not found by the Propeller Tool. I used a pre-programmed EPROM which the Propeller runs successfully on start up. Just a simple program to set pins on and off at 1 second intervals.
I used the MPROG3.5 from FTDI and USBVIEW from FTDI to inspect the FT232RL. The FT232RL is not a counterfeit and is recognized. In addition, the Device Manager (WIN8.1 PRO) installs a COM port. The RX (pin 5) and TX (pin 1) lines from the FTDI to the pins 30 and 31 on the Propeller through a 150 ohm resistor. I did an ohm check from the respective pins on the FTDI chip and the Propeller and it measured 149 ohms on each.
I put a scope on both lines during the Propeller Tool hardware identification process. I didn't seen any activity on either. I do see activity on the DATA+ and DATA- input lines to the FTDI chip.
At first blush it would appear that the FTDI chip is malfunctioning but I don't want to replace it until I have explored all possibilities.
Does anyone have recommendations.
When I assembled the key components with the Propeller, 3.3V Regulator, EPROM, FT232RL and reset circuit on the new PCB but the Propeller is not found by the Propeller Tool. I used a pre-programmed EPROM which the Propeller runs successfully on start up. Just a simple program to set pins on and off at 1 second intervals.
I used the MPROG3.5 from FTDI and USBVIEW from FTDI to inspect the FT232RL. The FT232RL is not a counterfeit and is recognized. In addition, the Device Manager (WIN8.1 PRO) installs a COM port. The RX (pin 5) and TX (pin 1) lines from the FTDI to the pins 30 and 31 on the Propeller through a 150 ohm resistor. I did an ohm check from the respective pins on the FTDI chip and the Propeller and it measured 149 ohms on each.
I put a scope on both lines during the Propeller Tool hardware identification process. I didn't seen any activity on either. I do see activity on the DATA+ and DATA- input lines to the FTDI chip.
At first blush it would appear that the FTDI chip is malfunctioning but I don't want to replace it until I have explored all possibilities.
Does anyone have recommendations.
Comments
Recommendations can not go forward without it.
===Jac
I did a loop back by connecting P31 to P30 on the Propeller Chip (not on the socket but directly on the pin of the chip). The Propeller terminal echoes everything I type, even at max speed (3000000 baud). No funny chars echoed.
So.....kind of rules out the FT232 as the source of the problem. So...What am I missing.
Usually the most frustrating problem has the simplest solution!!!
-Phil
I have attached 4 Images. The first is the Reset Circuit as drawn on the schematic. A comparison with existing designs will show a striking similarity. The Second image is the properties from Eagle of the 2n2222. Notice it is a T018 case. Image 3 is the pin configuration of the TO18 2N2222 transistor as cut from a datasheet. and FINALLY THE CULPTRIT is the layout. PIN 1 is tied to ground, Pin 2 is tied to the top of the resistor and to RT232 DTR through a capacitor and Pin3 is tied to the to the Propeller RESET and the pushbutton switch. Reference the schematic for the correct connections.
I don't know how this could happen!!!!! If the library is correct then I rotated, mirrored, swapped, or twisted the layout but I can't think of the combinations that would produce this. I'll back-track through the libraries and see what I can find.
Once I correct install a part with the proper connections I will post an update.
Thanks for the support.
The shown package has a rather strange pin-numbering scheme, but the pin-mapping is still the normal E-B-C
I basically forced the ST2N2222 into the board by putting a 'L' bend in the Base lead and rotating it 180 degrees. Works fine. Propeller Tool recognizes the Propeller and downloads code. Runs Well.
PS: The ST2N2222 wasn't used in my original Test Prototype. UGH!!!!
Thanks for the support.
You might want to put some kind of note on that board re the unconventional ST 2N2222 or maybe just replace it with a plastic 2N3904. After all, we're not using any special features known only to 2N2222.
http://www.st.com/st-web-ui/static/active/en/resource/technical/document/datasheet/CD00253894.pdf
-Phil
Plastic versions are often referred to as P2N2222
Any general purpose NPN transistor should work.
The transistor circuit causes a short pulse to ground on the reset line when DTR goes active (which is 0V on the ttl side is the Ftdi232 output)
The internal pull - up resistor in the Prop is only enabled if the BOE pin is in the right state (grounded I think, from work)
I've gotten caught by this one before and now just make sure to check any 3-lead component. Glad you were able to find out what was going on and that it worked!