PropTool 2.9.3 fails loading a (not too) large P1 program
Ding-Batty
Posts: 281
This is about the "Error: communication stalled due to system problem" that seems to happen sometimes. I started seeing that failure after installing V2.9.3, but only for some of my programs, and it seemed to happen only with the largest program images.
In fact, the large program is loaded, but PropTool reports a communications failure.
I have reduced the problem to a simple test program, which has a large LONG array in a DAT section, and when the size is increased by one LONG, the failure is triggered.
Program (also attached as no_op_memory.spin):
CON { General constants }
_CLKMODE = XTAL1 + PLL16X
_XINFREQ = 5_000_000
DAT
' Make the binary image big. Too big, and P1 load fails in PropTool 2.9.3 on
' a Windows 7 machine with the latest FTDI drivers.
'KeepMemory LONG 0[6083] ' Loads OK
KeepMemory LONG 0[6083 + 1] ' Fails
' PropTool error dialog:
' "Error: communication stalled due to system problem"
' ========================================================================
PUB Main
repeat ' wait forvever.
This happens after a fresh install of 2.9.3. It does not happen with the old PropTool 1.3.2, nor the other Spin compilers.
My system:
Window 7, 32GiB memory
latest FTDI drivers, downloaded today from the FTDI website (I had originally allowed the PropTool installer to also install its USB drivers, but I saw the driver version seemed to be from 2016.)
I tried quite a few settings variations for the COM port (Advanced settings), but nothing seemed to help.
I saw that Prof. Braino (@profbraino) had reported this back in Aug. 2023, and I was surprised that no one responded.
Comments
A little more info:
I've tried both USB2 and USB3 ports -- no difference.
I'm using a Propeller Board of Education, item 32900 Rev. B
Tip! If you report this issue to support@parallax.com you would catch the attention of the PropellerTool author. Jeff is covering that desk at the moment
Thanks! E-mail sent.