exxos's Atari, Amiga & retro forum

Thanks for the reply.

When I downloaded the binaries for the ST they appeared to be just too big to fit in a pair of 27c512 - probably just a few K with a couple of strings and a couple of blocks of constant data values so I was hoping there might be a smaller image that would fit in the pair of 512k bit EPROMs I have available.

Slim chance probably, but I felt it worth asking.

Maybe the cart version is smaller? I don't have a board to use the cart versions directly or I'd give that a go.

Yeah. Now that you mention it, the cart version is 128Kbyte (2 pieces of 64Kbyte roms).

But TOS 1.04 and below is 192Kbyte just like the DiagRom for ST is. Your 27C512 only fits 512Kbit (64Kbyte) so it won't fit as you said. You could split the DiagRom in 6 parts and burn it on your 27C256 (32Kbyte). You have to move threee solder pads on the main STfm board though.

EDIT: Not all STfm version boards have those three solder pads. So maybe not a smart option for your broken boards.

Hmm, sounds like what I really want is a build with the same image size as the cart version but as a replacement for the existing TOS ROMs.

Then I could program up the 27c512s and replace the existing ROMs to diagnose & fix the faults, then re-fit the original ROMs or even upgrade to 1.04 at some point.

Thanks again for the info...gives me some ideas to work towards.

JezC wrote: ↑Sun May 26, 2019 5:20 pm When I downloaded the binaries for the ST they appeared to be just too big to fit in a pair of 27c512 -

A "pair" of ST ROM's is 27C1001 not 512... I have had diagrom running on a ST in place of the OS ROM's just fine.

PaulJ wrote: ↑Tue Feb 12, 2019 12:53 am Problem solved, had 2 HN27C4096 120ns eproms I got off eBay from China. One died in September last year. With the remaining chip it came down to the swapped byte image I tried in the bad half of the eprom rom over and over. It was programmed on two differient eprom programmers with no faults but the upper half of the eprom will not boot any image. Swapped bytes in the lower half and it work.. All this because I didn't want to make a first attempt in a one burn only chip. Shesh!!!

Thanks

I think I need to program a HN27C4096 to help me diagnose my H4 board. Can someone please confirm which file from Github I should use to program the chip?

Plan is to use this in the onboard PLCC44 socket and see what I get. Hoping someone can provide the file if it needs byte swapping.

kodak80 wrote: ↑Tue Dec 10, 2019 8:27 am I think I need to program a HN27C4096 to help me diagnose my H4 board. Can someone please confirm which file from Github I should use to program the chip?

Plan is to use this in the onboard PLCC44 socket and see what I get. Hoping someone can provide the file if it needs byte swapping.

.rom = unswapped
.bin = swapped
.hi/.lo split for the machine in the filename

Hi guys,

Is anyone willing to burn me up a Falcon compatible (PLCC44, E00000) copy of DiagROM for a moderate gratuity, or can point me to a seller? I'm hoping not to make a habit of ROM burning so don't think the programmer, adapters and blanks are a sensible investment yet.

@exxos Have you considered DiagROMs as a store option?

Cheers,

BW.

@Badwolf I am considering the ROM and got permission to distribute it in my store, but I only really deal in PLCC ROMs now. So I need to design a new cartridge to use the ROM first, but with so many projects ongoing I don't know when I will get chance to design it. Mostly people burn their own ROM's anyway.

I don't know if anyone even tested diagrom on the falcon.. It was built with the ST in mind.

exxos wrote: ↑Thu May 28, 2020 12:04 pm I don't know if anyone even tested diagrom on the falcon.. It was built with the ST in mind.

It should be easy to try on an emulator. I should really update this with Chucky's new changes. I'm kinda waiting for him to do a better ram test first.

terriblefire wrote: ↑Thu May 28, 2020 3:59 pm It should be easy to try on an emulator. I should really update this with Chucky's new changes. I'm kinda waiting for him to do a better ram test first.

Hatari just refuses point blank (even when padding to 512k). I think it's trying to be too clever As things progress with my board I may look into it into a bit more detail as I'm sure I'll hit a point the systest cart works but TOS doesn't.

BW.