deadsy/rvdbg

RISC-V Debugger

rvdbg's Issues

rvdb disables mouse

Hello,

I can see the GD32FV chips now. Debugger is a LPCLinkV2 with newest firmware.

./cmd/rvdbg/rvdbg --i daplink -t gd32v
2020/12/02 19:32:43 main.go:136 main(): INFO using debug interface: daplink
2020/12/02 19:32:43 rv13.go:68 New(): INFO 0.13 debug module
2020/12/02 19:32:44 rv13.go:133 New(): INFO hartsellen 10
2020/12/02 19:32:44 rv13.go:157 New(): INFO sbasize 0
2020/12/02 19:32:44 rv13.go:193 New(): INFO progbufsize 2 impebreak 1 autoexecprogbuf true
2020/12/02 19:32:44 rv13.go:194 New(): INFO datacount 4 autoexecdata true
2020/12/02 19:32:44 rv13.go:228 New(): INFO 1 hart(s) found
2020/12/02 19:32:44 hart.go:326 examine(): INFO hart0: MXLEN 32
2020/12/02 19:32:44 hart.go:334 examine(): INFO hart0: MISA 0x40901105
2020/12/02 19:32:44 hart.go:383 examine(): INFO hart0: unable to determine FLEN
2020/12/02 19:32:44 hart.go:407 examine(): INFO hart0: MHARTID 0
2020/12/02 19:32:44 hart.go:419 examine(): INFO hart0: nscratch 2 words
2020/12/02 19:32:44 hart.go:420 examine(): INFO hart0: datasize 4 words
2020/12/02 19:32:44 hart.go:421 examine(): INFO hart0: dataaccess memory(1)
2020/12/02 19:32:44 hart.go:422 examine(): INFO hart0: dataaddr 0xc0
2020/12/02 19:32:44 hart.go:432 examine(): INFO hart0: disassembler ISA RV32 ext "acim"
gd32v.0r> exit
However when started, the mouse
Bus 001 Device 015: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
gets unresponsive. Nothing in dmesg. Un/replug the mouse makes it usable again, until the next start of rvdb. Is your scan of the USB bus too aggressive?

Please add setup instructions

Hello,

github.com/deadsy/go-cli is not a submodule of github.com:deadsy/rvdbg.git. How do I setup to compile via 'make'?

Thanks