Raspberry PI PICO ATARI ST Hard Drive Emulator (WIP)

[exxos]

That doesn't seem to happen. All that happens when I press reset is it seems to screw up the com port and I have to unplug the usb and restart the program. If I press esc I get the HDC prompt . So it's not like comms isn't working.

[dad664npc]

okay so if you see the prompt type status

[exxos]

okay so if you see the prompt type status

So the one in my test board is

Code: Select all

******************************************
BBaN RPP HDC
ATARI ACSI HDC Emulator
Build date May 18 2023  12:56:45
Release 1.01
Steve Bradford aka cryptodad
******************************************

CONTROLLER ID: 0

sd0: unmounted - command packets 0
sd1: unmounted - command packets 0
We have been running for 0 days 00:00:16
CPU clock is running at 150 MHz
SPI clock is running at 4294 MHz

So need to download all the files you sent and see which one that version is then.

EDIT:

Found that version and flashed in one of the new boards. Now it boots right up with HD11, though the write problems are still there :(

When trying to delete files from C: it does this..

Code: Select all

CMD_READ        tgt=0 lun=0 (0x08:00:a5:28:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:38:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:48:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:58:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:68:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:78:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:88:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:98:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a4:48:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a5:a8:08:00) (00)
TEST_UNIT_READY tgt=0 lun=0 (0x00:00:00:00:00:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a6:98:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ab:68:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ab:b8:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ac:28:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ac:38:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ac:68:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:ac:98:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:a4:48:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:9b:a8:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:8a:88:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:01:88:08:00) (00)
TEST_UNIT_READY tgt=0 lun=0 (0x00:00:00:00:00:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:00:b8:08:00) (00)

Then just pops up the usual error box on the desktop.

[Badwolf]

When trying to delete files from C: it does this..

Code: Select all

...
CMD_READ        tgt=0 lun=0 (0x08:00:a4:48:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:9b:a8:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:8a:88:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:01:88:08:00) (00)
TEST_UNIT_READY tgt=0 lun=0 (0x00:00:00:00:00:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:00:b8:08:00) (00)

Then just pops up the usual error box on the desktop.

Just out of interest (there are no CMD_WRITEs there), if you hit ESC to refresh the window, or reset the machine at this point, do you see a CMD_WRITE log message appear before the next command that works?

I've a theory something hangs before or during the write starts up on my one which stops the log flushing for whatever reason.

BW

[exxos]

Just out of interest (there are no CMD_WRITEs there), if you hit ESC to refresh the window, or reset the machine at this point, do you see a CMD_WRITE log message appear before the next command that works?

Not sure, it's "off my desk" now as the DFB1's have arrived. So I can't do any testing currently now.

But indeed I never saw any writes in the log during all the "hangs".

[DaveC]

Well the new firmware seems to work fine here with my STe, so that's me happy!

[chronicthehedgehog]

Well the new firmware seems to work fine here with my STe, so that's me happy!

Me too. I've been doing quite a bit of experimenting with partitioning and installing the likes of Neodesk etc and it feels really solid.

[dad664npc]

When trying to delete files from C: it does this..

Code: Select all

...
CMD_READ        tgt=0 lun=0 (0x08:00:a4:48:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:9b:a8:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:8a:88:08:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:01:88:08:00) (00)
TEST_UNIT_READY tgt=0 lun=0 (0x00:00:00:00:00:00) (00)
CMD_READ        tgt=0 lun=0 (0x08:00:00:b8:08:00) (00)

Then just pops up the usual error box on the desktop.

Just out of interest (there are no CMD_WRITEs there), if you hit ESC to refresh the window, or reset the machine at this point, do you see a CMD_WRITE log message appear before the next command that works?

I've a theory something hangs before or during the write starts up on my one which stops the log flushing for whatever reason.

BW

The debug prints are handled by CPU0 - occasionally a print will be missed because CPU0 loop is checking to see if a key has been pressed and if micro-sd cards have been inserted/removed

[Badwolf]

Just to confirm, I've quickly got my STFM mobo up and running and the open-source branch from Jan '21 with my minor mods for my board design faux pas does indeed work. Including write. I've not tried the latest commercial firmware yet, but I suspect that will if this does.

Ruddy 'bad' STE DMA strikes again! :)

BW

[JezC]

@exxos Any idea if/when you might have more of these available in your store?