-
Notifications
You must be signed in to change notification settings - Fork 307
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
During scan openjocd assumes progbuf is available. This is OPTIONAL. Scan fails on this. #1017
Comments
My .cfg file: #debug verbosity 0-4 (2 normal error+warn; 3 debug; 4 extremely verbose) adapter speed 10000 adapter driver remote_bitbang set _CHIPNAME riscv set _TARGETNAME $_CHIPNAME.cpu riscv set_reset_timeout_sec 3600 gdb_port 3333 #riscv set_mem_access off #use system bus access vs program buffer for mem access init |
I thought that this assumption by OpenOCD that the target implements a progbuf had been addressed previously? At least for debug spec 0.13 or later targets? E.g. see here: |
@InspireSemi, can you please provide more context? |
This is during initial connection to the target. It has not gotten to opening up the gdb connection yet in openocd. BTW: The "other" openocd (upstream) does not exhibit this behavior. |
To echo what @en-sc said earlier, you'll probably need to capture and attach the verbose |
log.txt Again this is before gdb can even be connected to openocd. It is in the initial connect stage. |
I am moving back to the openocd from openocd.org for now. I will be more than happy (as time permits) to help you debug what is wrong. |
@InspireSemi, I'm sorry for the delay. I have analyzed the logs.
However, the abstract command fails with
Therefore, it is attempted to read
TLDR:This is not obvious by the error reported to the user, but the examination fails because the debugger is unable to read Why openocd.org version works?Setting |
I have not seen any issues with openocd.org. I am able to connect, set SW breakpoints, resume, halt (ctrl-C), dump memory, single step, etc.. I will post the logs from running openocd.org. I noticed that you are setting the ebreak bits in dcsr during initial connection and openocd.org is not doing this. It waits until gdb has connected to set them. |
cr2464_mmap.txt FYI: I had opened gdb with the wrong elf file. |
Do you need any further information? Logs, etc.. I can spare some cycles in helping to debug if needed.. |
@InspireSemi, again, sorry for the delay. This issue slipped my mind.
Yes, It would be nice if you could collect OpenOCD
|
I will get to this in a day or so.. |
Error: 19418 1342611 program.c:203 riscv_program_insert(): [riscv.cpu] Unable to insert program into progbuf, capacity would be exceeded (progbufsize=0).
Error: 19419 1342611 target.c:681 target_examine_one(): [riscv.cpu] Examination failed
Debug: 19420 1342611 target.c:682 target_examine_one(): [riscv.cpu] examine() returned error code -4
Debug: 19421 1342611 target.c:1782 target_call_event_callbacks(): target event 20 (examine-fail) for core riscv.cpu
Debug: 19422 1342611 target.c:3009 handle_target(): [riscv.cpu] Examination failed. Polling again in 5000ms
Debug: 19423 1342611 target.c:3002 handle_target(): [riscv.cpu] target_poll() -> -4, next attempt in 5000ms
The text was updated successfully, but these errors were encountered: