Shop OBEX P1 Docs P2 Docs Learn Events
New Mother board caused PST Problems — Parallax Forums

New Mother board caused PST Problems

HarpritHarprit Posts: 539
edited 2010-10-03 14:55 in Propeller 1
Had a crash (power supply exploded)
Installed a new motherboard
Running Windows 2000
Now PST does not communicate with Prop program
Are there some BIOS settings that have to be reset?
Symptoms:
PST window appears when requested
Can enable and disable fine
Cannot output to PST screen, stays blank.
Program used to work just fine

Harprit.

Comments

  • vettezr1vettezr1 Posts: 77
    edited 2010-10-01 16:05
    Harpit some MB Bios have a section called advanced chips or I/O you may have to manually enable a serial or usb port especially if your I/O is on the the MB are you using serial or USB?? just look in your BIOS usally Del or F2 as you are booting up and it should be pretty clear hope this helps
  • HarpritHarprit Posts: 539
    edited 2010-10-01 18:57
    Could not find anything that sets Com5 in BIOS. USB and USB2 are enabled
    I am using a Parallax Prof Dev Board
    PST window says it is using Com5
    I reset all to defaults to make it like new
    Downloads program and executes just fine.
    Will not run demo programs from Parallax either
    H
  • HarpritHarprit Posts: 539
    edited 2010-10-01 19:54
    I did something to start it working but I do not know what I did!
    I will post again when I find out what causes this.
    H
  • max72max72 Posts: 1,155
    edited 2010-10-02 01:50
    If you want to check it the problem is related to the motherboard or to windows you could try to use a linux live and BST.
    Anyway if it now works no problem.. just don't touch anything!!! :-)

    Massimo
  • HarpritHarprit Posts: 539
    edited 2010-10-02 11:09
    Well its not fixed and I still don't know what the problem it.
    Once in a while the PST starts working (but there are problems still).
    No solid solution yet.
    Not even close!

    Harprit
  • max72max72 Posts: 1,155
    edited 2010-10-02 14:43
    If it is still not working, go for a live linux and bst.. if it works it's a windows issue, otherwise a MB problem....

    get a live distro iso, and either burn a CD o create a bootable pen using this:
    http://unetbootin.sourceforge.net/

    Massimo
  • jazzedjazzed Posts: 11,803
    edited 2010-10-02 14:49
    You might try BST for windows just to see if it works. It's also better than Propeller Tool in several ways. Surely you have the latest FTDI driver.
  • HarpritHarprit Posts: 539
    edited 2010-10-03 14:28
    First, thanks to every one who wrote to help.
    Here is what happened and what it took to fix it.
    Before the cash:
    I was reading 4 potentiometers as a part of what I needed.
    After the crash:
    I upped that to 6 pots because I needed more variables that I could manipulate in real time for what I was playing with. (DC servo motor/encoder control tuning)
    Though this was the only change to the program, this small change increased to load on
    the system enough that it could not support PST along with the rest of the load.
    I caught it because there was the slightest dimming of the power LED on the development board during the potentiometer read cycle. I looked there because the PWM signal on the oscilloscope was indicating a slight drop on the pulse height every now and then. This was not supposed to be happening! So...

    Changed to a power supply (wall wart) providing more amps and that fixed it. It took just about a week of pulling my hair out! I tend not to give up but it was getting pretty darned frustrating on this one.

    HSS
  • max72max72 Posts: 1,155
    edited 2010-10-03 14:37
    Thanks for sharing.
    While personal experience (and pain) is usually more persistent in my brain, learning from others is still a great value.
    Massimo
  • jazzedjazzed Posts: 11,803
    edited 2010-10-03 14:55
    Finding a solution in multiple variables is often more difficult.
Sign In or Register to comment.