Writing a xv6 port to zig and ran into an issue with the uart0 not being able to take in keyboard inputs. Ive tested it manually but for some reason the actual keyboard isn’t working. anyone implement it before or know how to debug it?

Don’t forget to mark the pointers volatile when you reference memory mapped I/O. const io_ptr: *volatile u8 = @ptrFromInt(0x12345678); What machine are you emulating with qemu?

emulating riscv64 and i use volatile ptrs here is my config [Screenshot 2024-08-08 at 12.32.36 PM]

I get interrupts but i dont get keyboard input data

I assume that you use the virt board. The sources are: qemu/hw/riscv/virt.c at master · qemu/qemu · GitHub From that file: UART0 is memory mapped and the base address is 0x10000000 The uart chip is ns16550a, it is the original ibm pc uart. There are 8 registers, the first (in the base address) is…

There is GitHub - tzx/nOSering: Attempt on RISC-V Operating System in Zig Amazing uart info: Serial UART, an in depth tutorial - Lammert Bies uart implementation in zig: nOSering/src/uart.zig at main · tzx/nOSering · GitHub blog post: Timmy Xiao

yep ive looked at all of those and emailed lammert, in that implementation he doesn’t actually get uart input but I’ve tried his config

found the bug was not in qemu, a interrupt enable bit wasn’t being set in my trap handler

Ziggit

UART0 Qemu Keyboard input

Help

language

Sze August 8, 2024, 8:24pm 9

Avoid Screenshots of Text/Code Site Feedback

Why avoid Screenshots of Text/Code? I dislike screenshots of text, because they are: less accessible (text can be read via screen-readers, or braille displays) less searchable (text recognition tools often aren’t easily available / not well integrated or may contain faults in their output) annoying (you can’t easily/reliably copy the text out of a screenshot) I think these are good reasons to keep the amount of screenshots of text low in the forum and only use them, when it can’t be avoided o…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled