Alan-19950616 comments

Results 10 comments of


                                            Alan-19950616

Run NocTestAXI403 Fail

> Thanks for the report. I'll check on this @jerryz123 How is it going?

Run NocTestAXI403 Fail

I tried to increase **-Xmx** and **-Xss** in **.github/workflows/ci.yml**. I got the same error message as before. @jerryz123

thanks for your reply. This seems to be working, but there are new mistakes. **sbt.ForkMain 32891 failed with exit code 137** ![image](https://user-images.githubusercontent.com/46317534/217163623-0cb7374d-bee3-49e8-bf64-f85c6eb2aa44.png)

Run NocTestAXI403 Fail

@jerryz123

OpenOCD return error when using GDB to hit hardware breakpoints on hardware that doesn't support them.

Sorry, I got the wrong line number. https://github.com/riscv-collab/riscv-openocd/blob/cb2b3945143efda7196d14ae60c9877c289026a7/src/server/gdb_server.c#L1859

OpenOCD return error when using GDB to hit hardware breakpoints on hardware that doesn't support them.

OpenOCD log ``` Info : [riscv.cpu] Found 0 triggers Error: Couldn't find an available hardware trigger. Error: can't add breakpoint: resource not available ``` OpenOCD `-d3` log ``` 84595 Error:...

OpenOCD return error when using GDB to hit hardware breakpoints on hardware that doesn't support them.

GDB version `GNU gdb (GDB) 13.2.90.20230712-git` I want to make sure that the error code is `#define ERROR_TARGET_RESOURCE_NOT_AVAILABLE (-308)` and not `#define ERROR_NOT_IMPLEMENTED (-7)`.

OpenOCD return error when using GDB to hit hardware breakpoints on hardware that doesn't support them.

That's the problem I'm having, and I'm not expressing it clearly. At this point it is not possible to use commands such as continue or single-step unless the hardware breakpoint...

I want to add a verilator-generated uart model to systemc project, but there's a problem.

Thanks for the reply, I'm in active communication with verilator. Let me know if you find anything afterward. https://github.com/verilator/verilator/issues/4434

Using the `info reg all` command within gdb returns an `remote failure reply 'E0E'`

It's working. Close issues.