bkw777 / pdd.sh Goto Github PK

Probably only affects TPDD1

Somehow I borked it up in the last few updates without noticing that if you do an ls, the ls works fine, but leaves the drive in an unexpected state, probably in fdc-mode left over from the condition command to get the write-protect status, when we expect it to be in operation-mode, and with bytes from the drive still un-collected by a read or a drain.

End result is most commands work, and ls works, but if you do a an ls then almost no commands work after that.

WORK-AROUND until I fix it:
Any time you do ls, then do a smack after that and verify that status responds "ready" instead of some error.

Bash 5.2 from macports, Monterey 12.7.3, Early 2015 macbook air, FTDI usb-serial adapter

fdc-mode read operations fail, ie rh/read_header rl/read_logical hang on trying to read after sending the command.

opr-mode commands mostly work but they're not 100% either. loading a small file works but larger files hang around 3.8k

ls mostly works, the dirent() commands work to display all the files, but the end of ls() does an fdc-mode command to get the disk write-protect status at the end and that fails.

• help() makes a blank screen in any terminal, regardless if white or black background, and blindly typing q enter doesn't exit either, requires ctrl-c to exit, and after ctrl-c the terminal is fine, so it's not the terminal codes but some kind of hang.
• the tty can get locked and unusable until reboot if you for instance unplug and re-plug the usb-serial adapter

Don't know what the issue is yet but it basically only starts to work then gets stuck on freebsd.
Maybe timing.

I have reproduced this issue on both

• Intel Macbook Pro + USB Serial Prolific
• M1 Macbook Pro + USB Serial FTDI
  Connected to a TPDD1, with factory cable

The script starts, asks which port to use (btw auto detect also does not work), then nothing happens.
The behaviour is the same even if you don't connect anything on the serial side ( eg no : TDPP at all)

Debug 1 or 2 says nothing either.

If your CTRL-C to exit the script, the script says it was at line 524 (if that info helps maybe...)

Cable setup is OK , serial adapters work & are supported, TPDD works, and not the cause of the problems. I can talk to my TPDD with the same cables and setup using Windows 11 virtual machin under Parallels and a Windows TPDD Client.