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

Problem with initial state of the GPIOs #2

Open
wzab opened this issue Apr 5, 2020 · 0 comments
Open

Problem with initial state of the GPIOs #2

wzab opened this issue Apr 5, 2020 · 0 comments

Comments

@wzab
Copy link
Owner

wzab commented Apr 5, 2020

Due to the method how GUI and the emulated systems are connected, the initial state of LED may be not transferred correctly from the emulated machine to GUI and the initial state of buttons and switches may be not transferred correctly from GUI to the emulated machine.
I have added the "Reconnect" button in the GUI that toggles all inputs ans assures correct tracking of further changes. It also attempts to enforce the emulated machine to send the correct state of all the LEDs, but it does not work correctly.
At the moment, your emulated machine must toggle each LED (either in U-Boot or in Linux) to ensure that further changes of LED's state are correctly transferred.
Solving that issue probably requires redesign of the MPC8XXX model, using another emulated GPIO chip to provide virtual GPIOs, or switching from message based communication between GPIOs and GUI to shared memory (like in ivshmem in QEMU - https://github.com/qemu/qemu/blob/master/docs/specs/ivshmem-spec.txt ).

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