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

Optimization of Serial Data #2

Closed
Kirb0031 opened this issue Aug 9, 2016 · 3 comments
Closed

Optimization of Serial Data #2

Kirb0031 opened this issue Aug 9, 2016 · 3 comments
Labels
enhancement A feature request or other kind of enhancement.

Comments

@Kirb0031
Copy link
Contributor

Kirb0031 commented Aug 9, 2016

Regarding MEGA65/m65dbg#3 and serial speed issues.

Current serial output is inefficient (repeats banner every time, includes spaces, etc).
A more efficient, but less human readable, protocol for use with m65dbg was suggested
which should improve debugging performance.

@Ben-401
Copy link
Contributor

Ben-401 commented Aug 10, 2016

maybe improve the existing format by not repeating banner etc, but keep this human-readable-format for users that do not want to use the m65dbg.
the fpga-side serial-debugger could by default use the above human-readible-format, and when it recieves a special message from the m65dbg, the fpga-serial-debugger could switch its format to the optimised one.

@gardners
Copy link
Contributor

gardners commented Aug 10, 2016

This is the general plan: we can implement a command that switches the
mode. That said, I am also comfortable with us making m65dbg a mandatory
tool for using the serial debugger, if it results in significantly improved
utility.

gardners added a commit that referenced this issue Feb 14, 2017
Implement F018A/B support for MEGA65 as specified in Issue #2.
@rdpeake rdpeake added the enhancement A feature request or other kind of enhancement. label Feb 5, 2021
@lydon42 lydon42 added the cleanup Issue Cleanup - possibly already fixed issue label Jan 9, 2022
@lydon42
Copy link
Member

lydon42 commented Aug 17, 2024

This was not worked on for 8 years, so I think we close it for now. If the need arises a new issue should be created.

@lydon42 lydon42 closed this as completed Aug 17, 2024
@lydon42 lydon42 removed the cleanup Issue Cleanup - possibly already fixed issue label Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A feature request or other kind of enhancement.
Projects
None yet
Development

No branches or pull requests

5 participants