Reflashing the TF536

[ErinW]

I decided to flash the firmware to the "tf536r2_2020_04_22" version, and sure enough, the board began booting to CF and floppy again just like it did before.

So being a bit more confident that I was flashing the card correctly, I decided to try it again with the "tf536r2_main_top_AMIGA_FULL_PHASE_7.jed" version. And sure enough, it went back to the same odd behaviour that prompted me to post yesterday. I tried flashing it one more time with the new version, but the behaviour remains the same.

So for the moment, I've flashed it back to the original version, and it's booting again. So at the very least I'm confident that I'm flashing the card correctly.

I suspect that if the card does have a RAM issue, it may help to explain why I was seeing so many core dump issues when trying to load Sierra titles (and others) with WHDLoad?

[alenppc]

No, this is something else. The Sierra games need a few whdload settings altered and I test the ram on every card before I ship it out. Plus they crash mostly on machines with just 512K chip ram.

But in any case, send it back and I’ll replace it with a different one that boots on my A500 with the new firmware. If that one also starts exhibiting the same behaviour then the issue lies somewhere else with your particular A500.

[ErinW]

Thanks again @alenppc, much appreciated!

[richx]

If anyone wants to use the original Raspberry Pi Model B Rev 1 to program, which has GPIO21 on "pin 13" instead of GPIO27, a file needs to be modified in the https://github.com/matrix-io/xc3sprog sources:

./xc3sprog-master/sysfscreator.cpp:
change ": IOSysFsGPIO(4, 17, 22, 27)"
to ": IOSysFsGPIO(4, 17, 22, 21)"