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.
On Fujinet project, picoboot is being used to boot applications not associated with an ATR file.
I've noticed that in my own xex files launched from there, unless I specifically set BOOTQ to 1 in the launched application, the reset handler plays up and jumps to Self Test instead of running the correct reset handler.
I traced this to BOOTQ not being set to 1 and the OS handling it different during soft reset. After going to Self Test, pressing RESET again would run the application again. So alternating between Self Test and the Application every time reset is pressed.
Rather than every application setting BOOTQ, it would be useful to set it in the loader itself before running INIT and RUN addresses.
This MR is for that change.
I've tested this on both actual hardware and through Altirra, reset handling no longer jumping to self test.