P2 Edge Rev B, FlexProp 7.3.0 Program not saving to flash

in Propeller 2
Been a while since I worked with this stuff but I remember that I could run a program, cycle the power and the program would still be there and would auto-start. Now it doesn't store to flash, or have I forgotten something?
The switches haven't changed (I have two of these modules).
Even when I select "Compile and flash" I get a message in the terminal:
ERROR: timeout waiting for checksum at end: got 1
Try increasing the FIFO setting if not large enough for your setup
Press enter to continue...
Can't find anything re: FIFO
Comments
Maybe I'm mistaken. Used an older version and the terminal gives me:
Make sure the FLASH switch is ON-upward (and the two arrow switches OFF). -- if FLASH is already on, then toggle it on/off a couple times; might just be a lazy connection from sitting/bashing around.
Also ensure the SD card is removed (if you have one inserted
Still the same with both Rev B modules. I get the same message as in OP. The binary is only 7KB
Just realized that the #2 module fired-up blinking an LED so clearly that program was successfully stored, many moons ago.
I’d try with prop tool or spin tools
Or -single
Or maybe add fake data so program is bigger…
Cheers, Ray.
Yeah I had the same idea re: prop tool. It doesn't complain when sending the binary but the progress indicator is done in the blink of an eye and the program doesn't execute. I don't believe spin tools directly handles binaries(???).
Ya know what, I'll get back to my desk and try some regular SPIN programs to see if any different
Sure enough
Blink1.spin2 saves to flash and runs after a power cycle.
It does. Use F11 just like in Propeller Tool. Note that it does use its own loader.
Ah, forgot to correct myself; it was Propeller IDE that I tried. Really nice looking IDE, wish it supported FlexBasic
So I found FlexProp 5.5.2 archived in my DropBox and now I have success
What am I to deduce? Edge Rev B not compatible with newer FlexProp? I don't see that being the case.
I guess I need to go grab my KISS modules.
Craig
Hi Jon,
As far as I can tell, you can't load a binary (compiled with FlexProp) in order to use F11(??)
Right now I am compiling with FlexProp 7.3.0 and then when I need to stick my program in flash I just use FlexProp 5.5.2 to Flash Binary.
Sorry, I may have misunderstood; I thought you wanted to compile and load a binary which F11 will do.
That said, @macca has another tool that is a GUI loader for precompiled modules. This was made to help developers help their customers. You can get it from Marco's web site: https://maccasoft.com/en/propeller-firmware-loader/
It looks like something is broken in the flash programmer in loadp2 for Windows, which is weird: I don't know how we've missed that.
Fortunately, proploader can also program flash, so on the command line you can do something like:
to flash and run a program like "blink.binary".
You can also use the FlexProp GUI to do this if you go to "Commands > Configure Commands" and change the "Flash command" string to:
(which is very similar to the "Wifi run command" just above it, but with
-e
for "flash eeprom" instead of-r
for "run serial", and without the%9 -q
)There’s a thread about this we need to find….
Another trick is to make a fake spin2 file with only the binary embedded in a dat section…
@JonnyMac
Oh wonderful, many thanks, worked straightaway
@ersmith

Darn it
I knew that this "Commands" (or something) had to exist. How the heck did I miss it
Many thanks.
Also, the latest terminal "Hit enter to continue" simply does a CR/LF whereas the older terminal would close.
Was it this one?
Found it:
https://forums.parallax.com/discussion/175848/is-there-a-recommendation-for-binary-distribution-of-p2-code/p1
Think need to use -SPI option for loadp2
Undocumented? been a while...
I'm guessing -SPI has since been changed to -FLASH
PS: Tested with -FLASH, and -v to get any reporting ...
And pressing reset button repeats the terminal prints, so successful test.
Bingo
