PPDB - No Comm

BADHABIT

I just got a PPDB and the Prop Tool says no prop chip found on any port. ·· I have been running a PropRPM and it works\ed fine.

Is there something I'm missing? When it is plugged in (mini USB) Device Mgr shows COM6 w/the FTDI driver.

Any would be greatly appreciated.

Post Edited (BADHABIT) : 4/26/2009 4:14:37 PM GMT

Cluso99

can pst (parallax serial terminal) find the ppdb? This may be worth a try first.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:

· Home of the MultiBladeProps: TriBladeProp, SixBladeProp, website (Multiple propeller pcbs)
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: Micros eg Altair, and Terminals eg VT100 (Index)
· Search the Propeller forums (via Google)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm

BADHABIT

From what I can tell, which is very little, the terminal is sending to the board, and maybe the chip. the tx radio bttn flashes when I type and the Rx LED flashes on the board.

That's about all I can figure to do w/the terminal.







Post Edited (BADHABIT) : 4/26/2009 2:25:34 AM GMT

Vaati

Huh... Although I don't have a PPDB nor a fully functional Prop connection [noparse]:([/noparse] I would think that it would be a connection problem on the board. i.e.; the prop or the EEPROM isn't in just right... If I were you, I would check all your connections just to make sure...

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
3.1415926535897932384....

BADHABIT

I have quadruple checked and rechecked all pins. Then put it back in the RPM board(it worked), then pulled it out and back to the ppdb. Then I tried the eeprom from the RPM to use the prog from that, but nothing happens then either.
Then put it back in the RPM
Then I·put the prop and RPM eeprom back in the ppdb and still nothing.

What's wierd is: the RPM program·should be running off the eeprom, but the difference between the factory ppdb and the RPM one I've been using is not observable.

You still haven't got your s/u to work yet V ?

Post Edited (BADHABIT) : 4/26/2009 3:06:40 AM GMT

BADHABIT

Does anyone know how to use the RS-232 port to load on the PPDB?

nomad

hi,
i have too a ppdb

first the ppdb in the factory setup. -> no connection to the rs232 -Port

following steps:
1) starting the PropTool
2) connected the usb-port to the pc-usb-port
3) power on -> bigBlue-Led must be ON
4) the usb-leds should be blinking
3) on prop tool control is the comPort OK ->

if this OK
connect GroundPin on Left Up-side to the GND on the rightside down look on the schematicsi
testing the chipPins 0 - 27
if check Ok

Testing: RS232 as
on lower left side are rs232-pins p0 - p4 (form left to right
connect chipPin30 to p2 (TX)
connect chipPin31 to p4 (RX)

testing the rs232 with a serial-object z.b. fullSerialDuplex

at the ppdb no stuff is connected read the little docu and the schematics.
regards nomad
connect chipPin 30 to

BADHABIT

That's what I figured about rs232. But since that didn't work either I thought there may be a dift way to hook it up.

When you first hook up the board did you have to do anything to get the usb connect to work?

StefanL38

hello,

to quote the obvius

did you install the FTDI-driver ?

BADHABIT

yes Captain O

a few times

Oldbitcollector (Jeff)

Any chance we could get you to attempt any of the following and report back?

1.. Switch USB cables. (cross check the cable)
2.. Switch USB ports. (You'd be surprised)
3.. Install the Propeller Tool on a friends computer and test.

What type of power connection are you using?

OBC

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?

Visit the: The Propeller Pages @ Warranty Void.

Vaati

BADHABIT said...

You still haven't got your s/u to work yet V ?

No, I have not. I attempted to use the Serial to Propeller schematic from the Propeller Diagrams, Schematics, and Images page. There is a thread about the problem with my circuit as well. I am going to just get the Prop Plug though and worry about the seril circuit later.

Now did your PPDB come with a manual or booklet? If so, look in there for the troubleshooting info, and see if that'll help.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
3.1415926535897932384....

BADHABIT

1 - tried that
2 - tried that along with uninstalling/reinstalling ports
3 - tried that on 3 comps total

The Power is 9v 400Ma - attached is a shot f the power in and 3.3v out waveforms

I'm really starting to think something is wrong w/the effing thing. If it worked it should run the EEPROM program from the PropRPM that already has a prog on it, instead it makes no diff between a blank one.


yesterday <-- · <-- PPDB

Post Edited (BADHABIT) : 4/26/2009 3:35:42 PM GMT

nomad

hi,
power-supply ; on the ppdb: -> the bigBlue must be go ON
>>> have you the propeller-chip correct install ??

board in the left side (on german sockel) is a sign (sockel - sign chip sign must be the same

|

---

o | o chip
|

---

sockel

regards nomad

nomad

hi,
in the booklet, is no troubleshooting info :-(
ragards nomad

nomad

hi,
BADHABIT: wrote
>
>Posted Yesterday 6:38 PM (GMT -7) Quote This PostIgnore Posts From BADHABIT.Alert An Admin About This Post.
>I just got a PPDB and the Prop Tool says no prop chop found on any port. skull I have been running a PropRPM and it works\ed fine.

>Is there something I'm missing? When it is plugged in (mini USB) Device Mgr shows COM6 w/the FTDI driver.

>Any idea would be greatly appreciated.

> Post Edited (BADHABIT) : 4/26/2009 1:45:55 AM GMT

i think when you starting the ppbd and you see COM& is connected & the Blue Led on upper Left-Side in ON
it's ok the ppbd is then OK
BUT, you can't run a programm, then you make a test with the intern blue led on the rightside
1) chipGND to connect to the GND on lower right side
2) chipPin[noparse][[/noparse]0] to blueLedPing[noparse][[/noparse]0]
3) write a little programm
DIRA[noparse][[/noparse]0]~~ 'is output
outa[noparse][[/noparse]0] ~ ' set low

repeat
!outa[noparse][[/noparse]0] ' now should blinks

regards nomad

BADHABIT

No blinky

Prog loaded/verified on RPM

'' PPDB Test
''
'Program loaded to eeprom
con time=5_000_000

PUB Flash
dira[noparse][[/noparse]0] ~~
outa[noparse][[/noparse]0] ~

repeat
!outa[noparse][[/noparse]0]
waitcnt(time+cnt)

kwinn

Did you repair the power supply problem between the time you posted the waveforms and this mornings post?

BADHABIT

I didn't know there was one. It's the same supply used w/RPM. Just thought it was interesting that the supply had that

jazzed

BADHABIT said...

The Power is 9v 400Ma - attached is a shot f the power in and 3.3v out waveforms

...

That's a sh***y waveform. What happens to it if you pull the Propeller off the board?
Maybe you need to call Parallax tech support Monday and discuss this.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Steve


Propalyzer: Propeller PC Logic Analyzer
http://forums.parallax.com/showthread.php?p=788230

Toby Seckshund

The PSU traces are not good. The Smile from the 9V side is to be expected ( if it is a non regulated "wall wart" ) but the 3.3V should never dip unless the reg runs out of headroom or is going into current limiting. Is that causing restarts endlessly?

I hate the non reg PSUs they give ridiculous volts on light loads and then those volts die back at the slightest hint of work to be done! (But then I can get my SMPSUs free)

BADHABIT

It is, but a flat line from a 9 volt btty doesn't change anything.

I will be talking with them 2mro

Toby Seckshund

The current limiting option would probably show itself by the language formed, after placing a finger on the reg.

jazzed

Toby Seckshund said...
The current limiting option would probably show itself by the language formed, after placing a finger on the reg.

Ouch!!
Guess you could use it·for a water heater

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Steve


Propalyzer: Propeller PC Logic Analyzer
http://forums.parallax.com/showthread.php?p=788230

BADHABIT

·It actually was the Power Supply. I guess that effed up waveform actually did have neg. consequences.

·

Post Edited (BADHABIT) : 4/27/2009 8:14:32 PM GMT