Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UP9600: XMODEM sends stray $FF at beginning #5

Open
mist64 opened this issue Feb 25, 2022 · 2 comments
Open

UP9600: XMODEM sends stray $FF at beginning #5

mist64 opened this issue Feb 25, 2022 · 2 comments

Comments

@mist64
Copy link
Owner

mist64 commented Feb 25, 2022

When running the XMODEM test with the UP9600 driver, CCGMS sends an $FF byte before sending NAK/'C'.

This does not happen with the User Port or SwiftLink driver.

This reproduces with CCGMS 2021; it is not a CCGMS Future regression.

@mist64
Copy link
Owner Author

mist64 commented Feb 25, 2022

Also, it sends a stray $00 at the end part of the transmission protocol:

  • in: last byte (CRC)
  • out: ACK ($06)
  • in: EOT ($04)
  • out: $00 – instead of ACK ($06)

@mist64
Copy link
Owner Author

mist64 commented Feb 25, 2022

Both issues are probably caused by the call to enablexfer, which happens at exactly these spots. These ultimately call into up9600_enable, which does a lot of CIA#1 setup, which may cause an extra byte to be sent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant