PiStormST Update + Cyberlegends retro computer event is coming!

Подписаться 1,3 тыс.

Просмотров 2,3 тыс.

50% 1

It's been a while since I gave you a PiStormST update, so here it is it.
PiStorm is, basically, fully working, but the ST-RAM access speed is half what it should be. I explain why here and show off some of the fancy features PiStorm lets you have.
ALSO: Saturday 24th September 2022 is the CYBERLEGENDS RETRO COMPUTER SHOW in Hythe, Hampshire, UK.
Entry is free, but please book a ticket at cyberlegends.eventbrite.co.uk
Enter the raffle to win a fully populated and tested H5 STF recreated motherboard. You don't need to attend the event and all proceeds go to the MyelomaUK charity: www.exxosforum.co.uk/forum/vi...
I'll be going and displaying some of my projects. Do drop by for a chat!
/ thetechnoshed
0:00 Introduction
0:18 Cyberlegends retro show 24th September 2022
2:35 PiStormST development update
7:27 Booting stock TOS2.06
8:51 EmuTOS, 68040, 512MB TT-RAM
10:43 MiNT
13:01 Cyberlegends flyer
References:
PiStorm: github.com/captain-amygdala/p...
Discord for PiStormST and to discuss development: / discord
My PiStormST playlist: • PiStormST: building a ...

Наука

Опубликовано:

22 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 16

@DeadCat-42 19 дней назад

Removed my 68000 and socketed the mb. Got my pistorm built except... Need round header pins lol

@GadgetUK164 Год назад

Fantastic update, very cool =D It will be interesting to see if you can find a way around the read problem!

@thetechnoshed Год назад

Thanks! Winding the wick up on the RPi clock is next obvious step. Wish I could lay hands on an RPi4.

@a8converterman Год назад

Thanks for the update, I was born in Dibden Purlieu and family still live in the area. Co-incidentally I am taking them out to the Bombay Sapphire Distillery tour followed by lunch out on Saturday and so will try and pop along later in the afternoon.

@mrnother Год назад

Thank you so much for your efforts and this very interesting update!

@magicroomstudios Год назад

Can't wait for this to get sorted! Great work so far! Thank you for tackling this. I picked up a Pi-Storm board for a Amiga 500 - but I am totally a Atari user primarily, I only own two Amiga machines - so my first question was - Can this work on a Atari??? Great to see it will eventually work well!

@thetechnoshed Год назад

She's pretty stable now, but the RAM access speed is too slow. I've not had the time to make any update videos recently, but head over to the PiStorm Discord channel for the latest.

@madigorfkgoogle9349 Год назад

ahaaaa! So I was right even with my fading memory. So you are skipping cycle due to Amiga system CLK that is emulated by PiStorm being lower as Atari ST system CLK. I guess you have to get in touch with PiStorm programmers or have a close look at m68k emulation software. What I think is that the PiStorm is pulling the CLK from Atari but only for cycle beginning and then it is using its own Raspi system CLK and the m68k emulation software to divide the CLK from Raspi CLK. And since this is Amiga m68k emulator, the BUS CLK used is lower then ST CLK. So the software CPU is bit to slow to finish up the writing and has to start from begin in next cycle. The task is to find out how to change the BUS CLK of m68k emulator from Amiga system CLK to ST CLK, I bet it is just software adjustment. But as I said Im not familiar with the PiStorm. Will closely watch your success, mate. Cheers!

@thetechnoshed Год назад

PiStorm doesn't emulate the Amiga or ST clock. It's driven by it. You've got the wrong end of the stick here, I'm afraid.

@madigorfkgoogle9349 Год назад

@@thetechnoshed Why would you have problems with synchronization if the PiStorm would pull the CLK from the ST crystal, clock by clock? This doesnt look like it, what you describe looks like that it is taking just the cycle begin and then its running internal CLK and not pulling the ST or Amiga CLK from crystal via CPU socket pin. But again, Im not familiar to PiStorm, so I might be wrong. I was thinking that the emulation is on CPU pins level first, but maybe due to multiple CPUs emulation there are some "workarounds" and not all signals are strictly pulled clock by clock, can you somehow see on the PiStorm what is being used? Like timing, registers etc.? PiStorm is a software CPU emulator and not bare metal application after all. I hope I dont bother you too much, since my knowledge is long gone and you are much more competent. But sometimes even "stupid" ideas can open horizon for new solution. But I have to admit that your videos caught my interest.

@thetechnoshed Год назад

I hoped I explained it in the video. The combination of emulator and hardware simply takes too long to go from end of one cycle to the start of the next one. It misses its 'slot' and has to wait for the next available access to memory. This can be shown to be true by speeding up the emulation for writes (by not waiting for the hardware to confirm): you get 100% speed. It's as simple as that. The reason it shows on the ST and not the Amiga is due to a combination of three different factors which I have also explained. 1) Clock speed is higher on ST 2) Data is available later on ST 3) We must check for bus error on ST.

@madigorfkgoogle9349 Год назад

@@thetechnoshed well, that in a nutshell is exactly what I said from start on.

@thetechnoshed Год назад

No, you were theorising about an emulated Amiga clock. There is no emulated Amiga clock. This is the *emulator software* that's taking too long to execute. The software is not clocked, emulated or otherwise. I appreciate the interest and thanks for taking the time to post, but I'm afraid this is misinformation.