Fried Board
eddiet
Posts: 3
I was using the USB proto board to learn PASM, and somewhere along the line my board seems to have died. The computer is recognizing the FTDI chip, since it's showing up as a COM port, but the Prop is not communicating with it. My question is, could my poor programming have caused the Prop to be unable to communicate with the usb-serial adapter, or is it likely that I fried the prop chip itself? A quick check with an LED shows that chip is still at least somewhat alive when the power switch is flipped, with pin 0 high (I was just attempting to make it blink). I'm not sure if it's even possible for any code to completely prevent communicating with the serial adapter, but I'm wondering if I have any options other than a new board.
Thanks!
Thanks!
Comments
If it's just the FTDI chip that's bad, you could probably rig a connector for a PropPlug to your board...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
My Prop Info&Apps: ·http://www.rayslogic.com/propeller/propeller.htm
My Prop Products:· http://www.rayslogic.com/Propeller/Products/Products.htm
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
My Prop Info&Apps: ·http://www.rayslogic.com/propeller/propeller.htm
My Prop Products:· http://www.rayslogic.com/Propeller/Products/Products.htm
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Check out my new website!!
Use the Propeller icon!!
Follow me on Twitter! Search "Microcontrolled"
As I see it.
To many people not pay attention that most of boards not have series resistor between RX< pin From Propeller to RS-IC's.
And with badly programing that CAN Burn this pin else pin in supporting Serial IC!
Regards
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
The only thing connected at the time was an LED + resistor from P0 to ground, and the power supply was through the 3.3V regulator that came on the usb board.
Stranger things have happened. It would be fantastic to determine the actual cause of failure, but I also favor the concept of using time in a productive manner. This isn't a product that receives "failure attention" from our tech support guys so it could be a unique type of failure: destroyed Prop chip, an open, a bridge, failed or destroyed FTDI chip, etc.
So, let's just replace it! Perhaps the forum members will still resolve the problem, but it sounds like this one would become an RMA candidate.
Send me your shipping address by e-mail kgracey@parallax.com and we'll get a new one off to you right away. Keep the damaged board for parts.
Ken Gracey
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Ken Gracey
Parallax Inc.
Follow me at http://twitter.com/ParallaxKen for some insider news.
@eddiet: Post your program. Remember that PASM starts as soon as the power is on, but spin has a 1.5 second delay. Since you were learning PASM, you could be blocking the RX/TX pins with your program as soon as the power is on. If you have another prop on hand, you can fix this. Or you can just chop the wires leading to the EEPROM and see if it works. If you want the EEPROM back, though, you will need some SMD soldering technique. :-O
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Check out my new website!!
Use the Propeller icon!!
Follow me on Twitter! Search "Microcontrolled"
Really?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
@microcontrolled: While it is true pasm starts straight away, it is not as you believe.
When power is applied, the prop runs pasm code from ROM which then looks for the download signal on P31/30 (forget which is rx, think it is P30). If nothing is found within a certain time, then it will copy the eeprom (32KB) into hub RAM and then loads spin into cog 0 which executes the eeprom code.
However, once the prop is running and you connect the propplug (if it is seperate)... P31/30 may be connected and doing something else and hence a conflict could arise. Therefore it is important for the series resistors to be in the line to the propplug. Now you initialte a download to the prop and it issues a reset, the prop stops all cogs, initialised everything and restarts and runs the pasm boot code from ROM and continues as I described above.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)·
· Prop OS: SphinxOS·, PropDos , PropCmd··· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBlade Props: www.cluso.bluemagic.biz
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Leon Heller
Amateur radio callsign: G1HSM
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I always have someone watching my back.
It's part of why a lot of us will never give other like-products a second look... [noparse]:)[/noparse]
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Are you Propeller Powered? PropellerPowered.com
Visit the: PROPELLERPOWERED SIG forum kindly hosted by Savage Circuits.
FWIW.. I grabbed a arduino as a suggestion from a buddy ( Lego Mindstorm User ) and I have to say, your right.. It doesn't even come close to the Parallax Platform..
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I always have someone watching my back.
Graham