Exxos's PiStorm blog

[exxos]

Every single pin and the connector was bent :roll: so that was no fun getting it to fit :roll:

1.jpg

[exxos]

@Steve looking at your image, it looks like you have another board under the pi storm ?

stack1.jpg

[exxos]

Soldered the connector on now... Need to solder the header pins on next.. Probably have to wait until tomorrow now.

e1.jpg

[Steve]

Yeah TOS decoder... I don't even know if I need it. But either way, I couldn't remove it since it's stuck in the socket too hard lol.

[exxos]

Yeah TOS decoder... I don't even know if I need it. But either way, I couldn't remove it since it's stuck in the socket too hard lol.

Opps :)

I assume its not needed anyway. I did snoop in the config and it does list ETOS256K , so it must be fine with TOS206 space.

EDIT:

Actually it must need the decoder board otherwise nothing would be driving the ROM, unless its internal the the PI stuff ?

[stephen_usher]

The only version of TOS I could get to boot to the desktop was 2.06. EmuTOS would sometimes get there but the virtual processor emulation would soon reset itself after loads of "Bad status" messages, meaning that it's reading incorrect LC1/2/3 values, which are set by the PiSTorm board's state machine.

This was from the virtual ROM in the emulator on the Pi by the way. I didn't have a version of 2.06 in my ROM switcher... maybe I should try that when I get back from Cornwall.

P.S. We all know just how sensitive to bus timing the ST chipset is, you more than most.

[Steve]

By the way, I just checked which version of the firmware I use on my H5 and it's from the GitHub commit June 25th 2023. So if you're familiar with GitHub you can download that version from the repo and try it.

[exxos]

By the way, I just checked which version of the firmware I use on my H5 and it's from the GitHub commit June 25th 2023. So if you're familiar with GitHub you can download that version from the repo and try it.

Was the original firmware stable, the one which had 50% ram speed ?

[Steve]

I wasn't using Pistorm then afaik. In the early Badwolf days. I came in when Cryptodad fixed the st-ram speeds.

edit: I just re-read my old Discord logs, and although June 25th 23 version of the Github code was the best version for me. I wasn't necessarily using the firmware of that. It was something in ps_protocol.c that had changed which needed to be reverted to June 25th. I think I was on a newer firmware. So, it's not necessarily the firmware that's the issue.

edit2: So for instance, if you try out all the latest stuff on your H5, and for whatever reason you get difficulty. Keep the latest firmware on your pistorm, but try pulling the older Git repo from June 25th 23.

[exxos]

@Steve If you know how to change the builds from GitHub might be an idea if you can try older builds. We need to know if the original stuff was stable before various mods were done to speed up the ram access etc