Exposes JagLink/ComLynx UART to USERIO port #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
B is already used by save states. Can you move to H? |
Thanks for looking, I've adjusted it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exposes JagLink/ComLynx UART to USERIO port
USERIO Pin 0 is RX
USERIO Pin 1 is TX
TestUART homebrew works with homemade JagLink to RS232 cable.
My copycat JagLink SNAC hardware appears to work. I'm able to use the TestUART ROM to send a character and it responds with the next character as described in the documentation. If you send an 'a' you get a 'b' returned for instance. However, it only works once and you need to reset the core to try again. Looking at the source to TestUART it looks like it should continue to run and respond to characters received.
None of the games are working at the moment. I have logic captures from each game trying to connect. What I noticed is only 1-2 bytes are sent from one or both Jaguar cores before TX is stuck low.
Aircars: The game fails unable to find another player.
BattleSphere/BattleSphere Gold: Unable to find another player, however, it seems to 'sense' the other MiSTer.
Doom: Locks up when looking for other players with or without my patch when trying to do multiplayer. The Option button should return you to the main menu.
Behind Jaggy Lines Bios (v1.06.d): UART game dumper when started(Button 6) produces an exception shortly after starting and spits out a couple of bytes over Jaglink. The exception varies but here is one example.
In SignalTap after the byte is sent it seems to sit in the register. I'm wondering if this is exposing a bug as all software exhibits the same behavior.
TestUART.zip
Jaguar_DS_JagLink_20250117.rbf.zip