View Port Trial Ver 4.1.1 - Error Message - Was Unable to Connect But Now Succ

Bob Lawrence (VE1RLL)

This part works: Propeller chip Ver 1 was found on Com9

Background: The beta versions used to work. After I downloaded Version 4.1.4 I get the following message " Unable to connect" timed out, Com1= IO problem, Com2= IO problem, Com9=no configuration found


What I tried so far:
1. I manually deleted all old files, directories etc. versions (3)
2. I removed any references to Viewport that I could find in the Windows registry
3. I re-installed Viewport Version 4.1.4 and re-booted
4. In the Viewport Port Preferences I tried "Restore Defaults and Accept.

I Tried Viewport on both a Propeller Proto Board(10Mhz Xtal, 8xPLL) and a Hybrid board (6Mhz xtal, 16X PLL). Both boards work fine with the Propeller IDE for loading , Running programs etc.

Computer System Info:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name xxxxxxxxxxx
System Manufacturer NVIDIA
System Model AWRDACPI
System Type X86-based PC
Processor x86 Family 6 Model 10 Stepping 0 AuthenticAMD ~1830 Mhz
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 23/08/2004
SMBIOS Version 2.2
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Time Zone Atlantic Daylight Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 251.64 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.41 GB
Page File C:\pagefile.sys
///////////////////////////////////////////////////////////////////////////////////////////////////

DOT4 USB Printing Support USB\VID_03F0&PID_0917\00SGC1C10325
Generic USB Hub USB\VID_03F0&PID_1424\5&2F41F716&0&3
HID-compliant Optical Wheel Mouse HID\VID_046D&PID_C03D\6&68F63DC&0&0000
HP LaserJet 3330 Series PS DOT4PRT\VID_03F0&PID_0917&REV_0100\7&183F83C3&0&1
IEEE 1284.4 compatible printer DOT4\VID_03F0&PID_0917&REV_0100&PRINT\6&E4BF21C&0&0
Sound Blaster Live! 24-bit External USB\VID_041E&PID_3040&MI_00\6&359901FC&0&0000
Standard Enhanced PCI to USB Host Controller PCI\VEN_10DE&DEV_0068&SUBSYS_05311297&REV_A4\3&13C0B0C5&0&12
Standard OpenHCD USB Host Controller PCI\VEN_10DE&DEV_0067&SUBSYS_05311297&REV_A4\3&13C0B0C5&0&10
Standard OpenHCD USB Host Controller PCI\VEN_10DE&DEV_0067&SUBSYS_05311297&REV_A4\3&13C0B0C5&0&11
USB Composite Device USB\VID_041E&PID_3040\5&39841D1D&0&1
USB Human Interface Device USB\VID_046D&PID_C03D\5&63D1DE6&0&2
USB Root Hub USB\ROOT_HUB\4&1865C9CF&0
USB Root Hub USB\ROOT_HUB\4&2B1F7A74&0
USB Root Hub USB\ROOT_HUB20\4&25EA9806&0
USB Serial Converter USB\VID_0403&PID_6001\A4003GKU
USB Serial Port (COM9) FTDIBUS\VID_0403+PID_6001+A4003GKUA\0000

Pictures attached

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Aka: CosmicBob

Post Edited (Bob Lawrence (VE1RLL)) : 4/12/2009 2:43:39 AM GMT

Hanno

Hi Bob,
Sorry it's taken me so long to reply...
Thanks for the very informative post! I have a strong suspicion your problem is caused by the crystal's you're using.
The tutorials specify a crystal speed of 5mhz and pll of 16x in the top "CON" section. This sets the Propeller to an internal clock rate of 80Mhz when clocked with a 5Mhz crystal. The Conduit object uses the clock constants and the crystal to bitbang at 2Mbps, 1Mbps, and 115kbps.

First thing I would try is a board with a Parallax-standard 5Mhz crystal.
Next (or if you don't have one) I would edit the top spin file you're trying to load to reflect your setup- ie change the clkmode and xinfreq constants in the "con" section. The conduit will use this information to bit bang at the right baud rate. The problem you're seeing is that you're able to load the Propeller, but since the Propeller is talking at a wrong baud-rate (because it's misconfigured), ViewPort is not able to talk to it...

I'll add more info to diagnose these types of problems in future ViewPorts...

Good luck- let me know if that resolves it!
Hanno

Bob Lawrence (VE1RLL)

"First thing I would try is a board with a Parallax-standard 5Mhz crystal."

Hanno said...
Hi Bob,Sorry it's taken me so long to reply...

Actually your support is like your products...........Exceptional!! (capital E)

Hanno said...
I have a strong suspicion your problem is caused by the crystal's you're using.

I believe you are absolutely correct because after taking sometime to think it over before I went to bed last night(430am) I realized that when I tried Viewport before I had a 5Mhz Xtal installed on the Protoboard and the reason I changed it was because the Xtal quit. All I could find spare at the time was a 10Mhz Xtal. I actually have another 5Mhz Xtal somewhere but have not been able to find it for over 2 month or so. It's no problem to convert the programs to the Xtals that I have on hand. Thanks!! for the confirmation. I'll try it tonight but will start working a little earlier in the evening

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Aka: CosmicBob

Coley

Hanno said...
First thing I would try is a board with a Parallax-standard 5Mhz crystal.
Next (or if you don't have one) I would edit the top spin file you're trying to load to reflect your setup- ie change the clkmode and xinfreq constants in the "con" section. The conduit will use this information to bit bang at the right baud rate. The problem you're seeing is that you're able to load the Propeller, but since the Propeller is talking at a wrong baud-rate (because it's misconfigured), ViewPort is not able to talk to it...

Bob, this is exactly what I did to try out this great application, I changed the crystal settings to 6MHz and it works fine on all my Hybrids....

Nice work Hanno!

Regards,

Coley

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
PropGFX - The home of the Hybrid Development System and PropGFX Lite

Bob Lawrence (VE1RLL)

@Coley

Ok thanks for the info. As I mentioned above I tried Viewport before without any changes to the software (when I had a 5Mhz Xtal installed on the Proto board) and the reason I changed it was because the Xtal died.I forgot that it's now a 10Mhz I'll try it again in the next hour and give the trusty Hybrid board a workout.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Aka: CosmicBob

Bob Lawrence (VE1RLL)

I'm up and running.

@Coley

The Hybrid came through.

@Hanno

Thanks! again.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Aka: CosmicBob