Shop OBEX P1 Docs P2 Docs Learn Events
P2 Edge Rev B, FlexProp 7.3.0 Program not saving to flash — Parallax Forums

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

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:

    Invalid option -SPI
    loadp2 - a loader for the propeller 2 - version 0.060 Sep 23 2023
    usage: loadp2
    [ -p port ] serial port
    [ -b baud ] user baud rate (default is 115200)
    [ -l baud ] loader baud rate (default is 2000000)
    [ -f clkfreq ] clock frequency (default is 80000000)
    [ -m clkmode ] clock mode in hex (default is ffffffff)
    [ -s address ] starting address in hex (default is 0)
    [ -t ] enter terminal mode after running the program
    [ -T ] enter PST-compatible terminal mode
    [ -v ] enable verbose mode
    [ -k ] wait for user input before exit
    [ -q ] quiet mode: also checks for exit sequence
    [ -n ] no reset; skip any hardware reset
    [ -9 dir ] serve 9p remote filesystem from dir
    [ -FIFO bytes] modify serial FIFO size (default is 1024 byte
    s)
    [ -? ] display a usage message and exit
    [ -DTR ] use DTR for reset (default)
    [ -RTS ] use RTS for reset
    [ -xDEBUG ] enter ROM debug monitor
    [ -xTAQOZ ] enter ROM version of TAQOZ
    [ -xTERM ] enter terminal, avoid reset
    [ -CHIP ] set load mode for CHIP
    [ -FPGA ] set load mode for FPGA
    [ -PATCH ] patch in clock frequency and serial parms
    [ -NOZERO ] do not clear memory before download (default)
    [ -ZERO ] clear memory before download
    [ -SINGLE ] set load mode for single stage
    [ -NOEOF ] ignore EOF on input
    filespec file to load
    [ -e script ] send a sequence of characters after starting
    P2
    [ -a arg1 [arg2 ...] ] put arguments for program into memory

    In -CHIP mode, filespec may optionally be multiple files with address
    specifiers, such as:
    @ADDR=file1,@ADDR=file2,@ADDR+file3
    Here ADDR is a hex address at which to load the next file, followed by = or +
    If it is followed by + then the size of the file is put in memory followed by
    the file data. This feature is useful for loading data that a program wishes
    to act on. For example, a VGA program which displays data from $1000 may be
    loaded with:
    @0=vgacode.bin,@1000=picture.bmp
    The main executable code must always be specified first

  • VonSzarvasVonSzarvas Posts: 3,597
    edited 2025-07-28 10:23

    @Mickster said:
    The switches haven't changed (I have two of these modules).

    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.

  • RaymanRayman Posts: 15,392
    edited 2025-07-28 14:55

    I’d try with prop tool or spin tools

    Or -single

    Or maybe add fake data so program is bigger…

  • @Rayman said:
    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 :+1:

  • Sure enough :+1:

    Blink1.spin2 saves to flash and runs after a power cycle. :|

  • I don't believe spin tools directly handles binaries(???).

    It does. Use F11 just like in Propeller Tool. Note that it does use its own loader.

Sign In or Register to comment.