Write Failure on COM3

Kurt Finnie

I'm using a propeller demo board.

While loading a program to ram that has worked many times before, I now receive a "Write Failure on COM3" error message after "Loading RAM". F7 finds the propeller, F8 shows only 1300 longs used, F9 says it compiles properly. I've swapped cables, turned everything off/on, changed USB ports, all to no avail.

Other programs consistently load properly.

What should I be looking for?

Kurt

FrameShift.

Are you using the latest Propeller Tool software?

There was a bug in the 1.1 release relating to write errors.

Propeller Downloads

dwelve

I had the same problem... I think my program was using too long despite the prop tool displaying that I had plenty of free space left. I found that trimming off my debug code to save space helped. Maybe someone with more experience and know-how can better explain this.

MagIO2

I have the same problem. PropellerTool tries to write stuff to the propeller and then stops with the message 'connection lost'. I see that the problem depends on the code-size. I have a laptop with which I can write very little test programs successfully. As soon as I include the FullDuplexSerial, it's to big and it does not work.
With my computer in the workshop upload of the same program works fine. But these days I figured out, that this computer also has problems to write an eeprom file which almost has 32k.

Kurt Finnie

I installed the software on another computer and it worked just fine.
I then reinstalled the software on the first computer and it works just fine now.

Microcontrolled

This is the same problem as I have had many times. If I switch to my "not-a-piece-of-junk" computer; it works fine. It could be the FTDI drivers. It works once I reinstalled the software, try that and it might work.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Toys are microcontroled.
Robots are microcontroled.
I am microcontrolled.