chad5200 Posted February 8 Author Share Posted February 8 49 minutes ago, mozzwald said: Looking at your logs there I see that lseek is not called when there were 2 timeouts in a row. The other had a single timeout and received an out of order packet and continued to lseek. Perhaps it's getting stuck after 1 timeout error Right but here is one where the BASIC load failed with a single timeout: [15:07:47] [15:07:47] CF: 31 52 67 00 ea [15:07:47] disk sio_process() [15:07:47] ACK! [15:07:47] ATR READ [15:07:48] Timeout after 1000 milliseconds. Retrying [15:07:49] TNFS OUT OF ORDER SEQUENCE! RETRYING [15:07:49] ->SIO write 256 bytes [15:07:49] COMPLETE! [15:07:49] I am really thinking there are occasions where the "TNFS OUT OF ORDER SEQUENCE" error occurs but the FujiNet does not actually attempt to correct the packet sequence request because the log isn't even showing the follow up "tnfs_lseek" message. Every time mine fails, it corresponds to that situation. However, every time that a "TNFS OUT OF ORDER SEQUENCE" event occurs and it is followed up by a "tnfs_lseek success" it succeeds. I really wish I understood the code enough to troubleshoot this. Hoping one of the FujiNet developers would take a look at that part of the code which appears to be around here: https://github.com/FujiNetWIFI/fujinet-platformio/blob/master/lib/TNFSlib/tnfslib.cpp#L1250 and here: https://github.com/FujiNetWIFI/fujinet-platformio/blob/master/lib/TNFSlib/tnfslib.cpp#L598 1 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.