Prpeller tool keeps crashing
TheGrue
Posts: 114
I am using my PPDB and trying to test some HB25 code and I keep getting a crash every 3rd-10th load of RAM on the PPDB. It hangs on "Checking COM8" See attached screen shot. The PropTool will not exit properly. It gives the attached error. I usually have to reboot the computer to get it to work again
Any Ideas? I tried uninstalling the PropTool 1.2.6 and reinstalling with the same results.
EurekaLog 6.0.18 Application: -------------------------------------------------------- 1.1 Start Date : Tue, 22 Sep 2009 20:29:32 -0700 1.2 Name/Description: Propeller.exe - (Propeller Tool) 1.3 Version Number : 1.2.6.0 1.4 Parameters : 1.5 Compilation Date: Mon, 11 May 2009 14:15:01 -0700 1.6 Up Time : 41 minutes, 21 seconds Exception: ------------------------------------------------------------------------------------- 2.1 Date : Tue, 22 Sep 2009 21:10:53 -0700 2.2 Address : 15000900 2.3 Module Name : Propeller.exe - (Propeller Tool) 2.4 Module Version: 1.2.6.0 2.5 Type : EAccessViolation 2.6 Message : Access violation at address 15000900. Read of address 15000900. 2.7 ID : 0F83 2.8 Count : 1 2.9 Status : New 2.10 Note : Active Controls: ------------------------------------------------------------- 4.1 Form Class : TMainForm 4.2 Form Text : Propeller Tool - PPC_Driver1.2 Demo Test 4.3 Control Class: TPTreeView 4.4 Control Text : Computer: ---------------------------------------------------------------------------------------- 5.2 Total Memory : 3063 Mb 5.3 Free Memory : 2196 Mb 5.4 Total Disk : 111.79 Gb 5.5 Free Disk : 66.21 Gb 5.6 System Up Time: 58 minutes, 33 seconds 5.7 Processor : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz 5.8 Display Mode : 1400 x 1050, 32 bit 5.9 Display DPI : 96 5.10 Video Card : Mobile Intel(R) 945GM Express Chipset Family (driver 6.14.10.4436) 5.11 Printer : HP Color LaserJet 2840 PCL 6 (driver 5.2.3790.184) Operating System: ------------------------------------ 6.1 Type : Microsoft Windows XP 6.2 Build # : 2600 6.3 Update : Service Pack 2 6.4 Language: English 6.5 Charset : 0 Registers: ----------------------------- EAX: 0178DD40 EDI: 00FCFC04 EBX: 00FC9804 ESI: 0012E7FC ECX: 00590000 ESP: 0012E7C0 EDX: 00000001 EIP: 15000900 Stack: Memory Dump: ------------------ ---------------------------------------------------------------------------
Any Ideas? I tried uninstalling the PropTool 1.2.6 and reinstalling with the same results.
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade, RetroBlade,·TwinBlade,·SixBlade, website
· 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) ZiCog (Z80) , MoCog (6809)
· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
I presume you are using either the inbuilt propplug on one of the parallax pcbs or an external propplug.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade, RetroBlade,·TwinBlade,·SixBlade, website
· 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) ZiCog (Z80) , MoCog (6809)
· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Does that byte of memory hold "A", 65, $41 or %01000001 ?
Yes it does...
·
to answer your question about the FTDI-driver. The comunication between Propeller-Chip and PC is done through a chip manufactured by FTDI (Future technology Devices International)
This is a chip that does the conversion from the USB-protocol to the V24 serial protocol. (RS232-serial)
That your PC can use this device the driver that is related to this chip has to be installed on your PC. In basic it's the same as you need the right graphic-chip driver that
your PC will show a picture on a VGA-screen. The fitting graphic-driver comes with your PC or the installation-DVD or maybe even included in your Windows-DVD.
So you don't have to care about the graphic-driver.
But there are so many devices all around the world that it is impossible for microsoft to incluse them all. So you have to install it when needed.
you will find the FTDI USB VCP Drivers here
best regards
Stefan
Yes to all questions, implies a driver problem, do as others have suggested, reinstall the ftdi driver.
Other possible causes might be a corrupted dll, or the wrong version of one, referenced in the software which crashed, BUT this fault might be extremely hard to track down.
If you get other faults as well, OR access violations, but a reference to a different adress each time, it's just as likely a hardware problem, in the case of access violations, usually memory.
Edit:
Sorry, I just realized, you get the access violation because you kill the proptool when it hangs.
Using a prop-plug? I've had similar problems after a unfortunate punishment of the plug, easily fixed by soldering a bad contact on the connector (rx line had intermittent contact)
Post Edited (H