exxos's Atari, Amiga & retro forum

Hi All,

I've built an ACSI2STM based on the github (https://github.com/retro16/acsi2stm) but I cannot for the life of me get it working properly. I've got all the connections as per the documentation on this page and I've buzzed and checked for shorts as well. I've had my board under a microscope to check them out and hey all look very clean.

I've got an Atari 1040STe, GOTEK and external floppy drive with switchable TOS1.62/2.06. I have the drive select MOD (A-B, B-A) fitted so that I can boot from external drive as well if need be. I've tried with both TOS1.62 and 2.06 to boot this device to no avail.

When I plug my ACSI2STM into the hard drive port I don't see anything at all on the screen until I get to the desktop. I'm powering the device from a 3.3v serial device so that I can monitor the serial port of the device. I can see that it detects the SD Card and says that it is ready to go but I do not get anything showing on the screen that indicates a hard drive or partitions on the sd card as hard drives.

For all I can see the device is working but the Atari is not talking to it for some reason. I have had a look to see if I have got a dodgy DMA chip but it is marked as C398739-001A which I believe is one of the 'Good Ones' from what I've read.

The motherboard is marked as GX-211 VO 4090 Copyright Atari Corporation 1989 and above this is CA4003290-.

About a year and half ago I sent my Atari to be fixed by @rubber_jonnie and he had tested the port to make sure it was working back when he had it and it worked OK with the tests he had to perform on it to make sure it was working ok after the extensive track rebuild around the TOS chips that the board required.

Is there anything else I can do to get this thing working? I've tried using the BIN files supplied on the github for flashing and I've also used the Arduino software to flash the firmware but everything I try is a complete no go. It would appear that it's the Atari side that's not coming back with anything for some unknown reason. I've tried flashing the 4.10 firmware and I've also tried an earlier 3.01 firmware all to no avail. The latest firmware I burned onto it when I turned the machine on, the serial displayed something about Stack Canary 1 Died. Reviving, then it goes on with Stack Canary 2, 4, 8, 16, 32, 64, 128 all saying the same thing. I don't have the RTC bit attached to my device. so this could be related to that I guess. So it is talking in a sense but not a lot else.

EDIT: I've tried loading the ICD pro IDCHECK.PRG from my GOTEK drive and that doesn't find any drives at all on the port. It's as though the device is invisible to the Atari, regardless if it says READY TO GO on the serial output monitor on the PC.

If anyone can help it would be appreciated.

Kindest Regards,

Brett Rogers

Just to clarify, I ran all of the tests using an Atari diag cart and the full ST test harness after I completed the repairs and the ACSI port passed just fine.

@BrettRogersUK Have you tried programming the ACSI2STM with the STM Cube software and ST Link adapter? Might be worth a go.

Also, don't assume that it is the Atari that is at fault until you're able to test the ACSI2STM and verify it works, you'll end up chasing your tail round in circles.

rubber_jonnie wrote: 18 Jul 2023 23:33 Just to clarify, I ran all of the tests using an Atari diag cart and the full ST test harness after I completed the repairs and the ACSI port passed just fine.

@BrettRogersUK Have you tried programming the ACSI2STM with the STM Cube software and ST Link adapter? Might be worth a go.

Also, don't assume that it is the Atari that is at fault until you're able to test the ACSI2STM and verify it works, you'll end up chasing your tail round in circles.

That's what I'm afraid of doing. From what I see on the serial monitor when the device is plugged into the atari and I switch the Atari on, the device is actually working, giving a ready to go signal however, the atari isn't seeing that signal for some reason.

No I haven't tried the St cube software. Is it available on Linux and I don't have a ST link adapter. I only have an FTDI USB TTL adapter.

Thanks for replying anyway. The SAGA CONTINUES!!

I know the pic says it's not connected but I took the pic after I disconnected the device.

I note that some pins the ACSI port on the STE runs through a bank of 68R resistors and go to a 74LS244 and 74LS245 IC. I don't know maybe these have gone bad over time and need replacing??

With so many DMA issues on the STE, I suggest trying a STFM before you start thinking of more drastic action.

exxos wrote: 19 Jul 2023 00:17 With so many DMA issues on the STE, I suggest trying a STFM before you start thinking of more drastic action.

Hi,

Unfortunately I'm not in a position to do this. I only have this one Atari sadly. I don't know anyone with a a STFM either.

I'll try the suggestion from @rubber_jonnie first see if that makes any difference.

Another thing I may try if the above doesn't work is to reflow the port on the underside of the board just to mitigate any cracked or bad solder joints that have appeared over time.

Thanks,

Brett

It sounds like your floppy drive is still working -- can you confirm? If so then it's unlikely the board is spewing nonsense into the port.

Is it possible you don't have exactly the right Blue Pill board? One or more of the pins not in the position expected, or not conducting?

IIRC the firmware said you could use a Black Pill board too, but I don't actually think you can.

BW

BrettRogersUK wrote: 18 Jul 2023 22:43I'm powering the device from a 3.3v serial device so that I can monitor the serial port of the device.

You really need to power it from 5V and do not connect USB port on the Bluepill to anything. There is a 5V to 3.3V level converter on the board, and it requires 5V to be able to communicate with the Atari at all.

Badwolf wrote: 19 Jul 2023 10:18 It sounds like your floppy drive is still working -- can you confirm? If so then it's unlikely the board is spewing nonsense into the port.

Is it possible you don't have exactly the right Blue Pill board? One or more of the pins not in the position expected, or not conducting?

IIRC the firmware said you could use a Black Pill board too, but I don't actually think you can.

BW

Yeah the floppy drive is still working as is the external.floppy drive as well when using the drive switch.

Yeah it does mention something about a black pill on the github. I've had two of the STM32F103C8T6 boards now and get the same with both of them. I could understand if one wasn't right but two, I don't think even my bad luck would stretch that far to be honest 🤣🤣🤣

Regards,

Brett

tzok wrote: 19 Jul 2023 12:48 You really need to power it from 5V and do not connect USB port on the Bluepill to anything. There is a 5V to 3.3V level converter on the board, and it requires 5V to be able to communicate with the Atari at all.

I will give it a try and power it from the 5v using my FTDI serial device. I like to be able to monitor the serial port at the moment to see what's happening before I power it directly.

Regards,

Brett

Am I the only person noticing that the serial output isn't seeing the sd card and therefore is failing to mount an image? So of course the Atari won't see anything, as there is nothing to see.

I would say re-solder the sd card connector or check for shorts on it.