Flashy Clock - Yet another DEV board

[derkom]

It needs music, you know, the sort you used to hear in department store lifts

Here you go.

[exxos]

Here you go.

[PhilC]

Well done @derkom laughed out loud to that one.

[exxos]

Yeah its like people have nothing better to do or something...

Anyway, here's a new version...

[stephen_usher]

I'd prefer the "Are you being served?" theme music... far less harsh.

[exxos]

I have been doing testing with various TOS versions.. bizarrely it works fine with EMUTOS and TOS104, but while TOS206 works and can run GB6 all fine from flash.. when obtaining the flash bank versions, it always crashes after displaying bank 2's info

[Icky]

And for those of you wanting to know how to prep your Flashy Clock port on the H4 this is what it looks like. Its made using a SIL pin socket and using a single and a two pin socket in the PAD1 and JP14 respectively.

IMG_4990 (2).jpeg (99.45 KiB) Viewed 3514 times

I then use a socket pin header as a jumper in JP14 just like the one in the picture below if the Flashy Clock board is not in place

IMG_4991.jpeg (129.46 KiB) Viewed 3514 times

And then in situ as also shown by @exxos a few days earlier.

IMG_4992.jpeg (298.05 KiB) Viewed 3514 times

[exxos]

I had to file a bit of my 68K socket to get them to fit Probably is better fitting those single row header sockets than a actual 68K socket like I did

I have got the firmware and software all working really nice, but TOS206 isn't placing nice, it always crashes on accessing bank 3 of the flash.. EMUTOS and TOS104 work fine, it all behaves. So I am not sure why TOS206 is being grumpy. I am currently waiting for Icky to test out his board to see if he has the same issue or not. I have a feeling my board has a bad flash or PLD as I have had loads of odd problems over what icky found.

[exxos]

Have been doing a little bit of probing today on the thing.. I think this is pretty much the most bizarre thing I have ever come across

To summarise,All TOS versions work fine running from flash.. UNTIL you try and change the boot ROM in TOS206 and it goes nuts.

The code is basically this...

Code: Select all

IF A = 1 THEN POKEW(&HFF896C),&B00  ' SET BANK 1
IF A = 2 THEN POKEW(&HFF896C),&B01  ' SET BANK 2
IF A = 3 THEN POKEW(&HFF896C),&B10  ' SET BANK 3 GOES NUTS TOS206 
IF A = 4 THEN POKEW(&HFF896C),&B11  ' SET BANK 4

And this is totally repeatable every time when I POKE values in STOS. I can poke 00,01,11 just fine, but poking 10 its like it writes to a random address in RAM or something and the screen goes nuts and crashes out. And yet I can poke any other number listed above just fine all day.

All that the PLD logic does is to latch D0,D1 and it issues DTACK. nothing else! So PLD wise, it does not care what the actual bits are set at

The address I used above is actually the second address I have tried. I have tried poking in steem and get bus error as expected. I have tried reading from the address and get bus error also. So there is definitely nothing on the ST using that address. I even looked through the TOS206 sources and see no mention other than the normal RTC registers which cause no issues anyway.

To demonstrate... I did a quick video, I poke, 0,1,3,2 in that order...

Normally it does a lot more corruption and starts scrolling bus error and address error in STOS. I have to power down the machine as a simple reset just goes back to STOS scrolling bus error.





FF it gets back is correct when it crashes on the first "10" read.. but even just poking to that address causes it to go nuts. I repeat this all works fine running from TOS104 or EMUTOS as well.

So I have no idea where to go from here, as this fault shouldn't happen. I can only assume the PLD is faulty in some way.

[Icky]

@exxos - Been a bit distracted today but have time to do the same tests on my board.