Ok so I found the culprit. I've written a program (years ago) that opens the serial port and just prints out what it reads. I call it stail for serial tail. And this detects when the propeller is being programmed, and shuts down the serial port so the loadp2 can do it's work, waits a second and tries to re-open the port.
And it appears that has changed its behavior, possibly my new underlying Linux or something. After fiddling with it, I don't seem to suffer from this stray reset. And guess what, the not-working.spin2 happens to work.
DIEZ 2026-02-01: sx1268_init:0
sx1268-send-test: 0
Lora1: sx1268: start send test.
Lora1: sx1268: chip is busy.
Lora1: sx1268: set standby failed.
Lora1: sx1268: chip is busy.
sx1268-send-test:failed
Comments
Ok so I found the culprit. I've written a program (years ago) that opens the serial port and just prints out what it reads. I call it
stailfor serial tail. And this detects when the propeller is being programmed, and shuts down the serial port so the loadp2 can do it's work, waits a second and tries to re-open the port.And it appears that has changed its behavior, possibly my new underlying Linux or something. After fiddling with it, I don't seem to suffer from this stray reset. And guess what, the not-working.spin2 happens to work.
So more investigation needed.