PropFORTH load error: chip lost on COM 16

Iamretired

I am trying to compile and load 'DevKernal.spin" of PropFORTH 5.5. These steps were followed:

1. Loaded DevKernal. spin from CurrentRelease\PropForth
2. Identify Hardware: Propeller chip Version 1 found on COM 16
3. Compile Current/ Load EEPROM
4. Loading Ram
5. Verifying Ram
6. ERROR: Propeller Chip Lost on COM 16
7. Identify Hardwaree: Propeller chip Version 1 found on COM 16

Prop is 'there' but it is lost?

I followed the PropFORTH install instructions ( I think ), but came up with an error.

NWCCTV

Have you tried a reset? I some times run in to this issue in Spin and just reset my prop and it seems to work after that.

prof_braino

That's a PropTool thing. If you have an old quickstart and PropTool 1.2.7 (or anything older than the current version 1.3.2) you need the 100k resistor on the Tx as a pull up. Without the pull up, it works sometimes, and doesn't work sometimes. The new tool and/or the new quickstarts haven't given me the problem.

Once you can load any spin file, the kernals (devkernel.spin) always work.

Iamretired

I have the same problem with Tachyon on the prop activity board. I tried RESET but it didn't help.
I downloaded Propeller Tool 1.3.2 and tried loading Tachyon again, but got same error.

Should I post this somewhere else if it is a prop tool problem?

Thank you for your responses.
John

prof_braino

I don't have the activity board. I only know of an issue with the old version Quickstarts on the old version proptool.

For Tachyon questions best talk to Peter Jakaki, the author; he's on these forums.

For Propforth issues, please talk to me.

Can you load ANY spin program? If you can load any spin program, then propforth will also load. If you cannot load another spin program, we can diagnose your set up.

Typically, this indicates a power supply issue, but I'm talking from anecdotes, not from experience with you board. Can you verify voltage and current?

mindrobots

Try a different USB port if possible. USB2.0 is preferred over USB3.0. Some Prop-BOEs have trouble with USB3.0 ports, the Activity Board I have seemed to work fine with USB3.0 but that's a potential problem. Can you try different USB cables?

At the point you are having problems, PropForth and Tachyon are simply Spin programs. Any loading issues are not related to it being a Forth, just a Spin program. You should have the same issues with any other large Spin programs you try and load.

The Activity Board should take power from your USB connection, so that shouldn't be an issue (again, try different USB ports and cables).

Iamretired

I tried com2 and got the same result. How can I direct this to a Parallax helper?

Thanks to each you who had suggestions. You make this forum great!

Johnmb

max72

What board are you using?
The prop is detected, so everything looks fine.
Loading to ram should be no problem (by the way Forths should be loaded to eeprom).
Could be a power supply issue?
Massimo
Edit: did you try a different cable, ane possibly pc?

Iamretired

The board is the Activity Board. I have also tried the 64K Quickstart board with the Human Interface Board
I have run several programs using USB power without a problem on both boards..
I have used two USB cables on two different ports: com16 and com2
The error occurs during Ram Verify at about the same point of the verify.
John

prof_braino

Sent you a PM. Please call me and I will try to talk you through it. Its a little weird the first time, after you get the hang of it, it just works every time.


I want to capture the exact nature of your questions, so I can put the question and the answer in the instructions.

Duane C. Johnson

Just a thought:
I run PropForth and FemtoBasic from TeraTerm terminal.
When loading the Spin code using PropTool I get the same error if I forget to disconnect the com port in TeraTerm.
Essentially there is a conflict with the two programs using the same com port.
Just disconnect the com port in the terminal and PropTool is happy.

Just a thought!
Duane J

prof_braino

I see as Duane described, you have to manually disconnect Teraterm, while proptool automatically disconnects itself whenit finishes programming.
Also, if you are using a virtual machine to run windows, you have to specifically grant permission to the virtual machine each time you re-plug the USB.

One more thing I noticed recently: On a very slow machine, I was ripping a disk with Handbrake in the background, and Proptool could not program the Quickstart. I guess there wasn't enough CPU power, even though Handbrake is supposed to be n the backgroup, and the proptool is supposed to be in the foreground. After Handbrake finished, Proptool programmed the quickstart normally.

prof_braino

We talked through the issues. This is an older Dell, but it should still be quite capable to run proptool and the terminal for propforth.

Turns out there were several USB devices that are sometimes noticed not to play well with others. After disconnecting the printer, scanner, and some thrird device, the PropTool was able to successfully program the kernel into the prop EEprom. After the PC was rebooted, Teraterm 3.1 was found unable to use 230400 baud.

Teraterm 4.71 (?) was able to connect at 230400, everything looks fine now.

He was able to locate propforth.htm, and started reading section 3. I advised finish reading section 3 before going to the Brody books, as section 3 points out many of propforth's commands that might be different from a workstation forth typically used with those references.

Iamretired

I am going through section 3. It is well written. I have used prop reset to clear the words I've defined and I've reloaded after I scrambled forth. It is easy to use and I am enjoying it
Thank you for getting me started.
John