Closed zh522130 closed 2 months ago
Ok, the functions have been added, it should go farther now.
Ok, the functions have been added, it should go farther now.
Thank you very much for the amazingly quick resolution. I tested it, and the error no longer occurs.
I have another issue that's outside the scope of this issue.
When I use the same OpenOCD on native x64, there are no problems, but on ARM64, it reports an error:Error: CMSIS-DAP: SWD not supported
.
sh: lscpu: not found
sh: lscpu: not found
PageSize:4096 Running on Unknown CPU with 4 Cores
Will use time-based emulation for rdtsc, even if hardware counter are available
Will use Software counter measured at 1.0 GHz emulating 2.0 GHz
Params database has 14 entries
Box64 v0.3.1 17fa9303 built on Sep 7 2024 13:52:55
BOX64: Didn't detect 48bits of address space, considering it's 39bits
Counted 19 Env var
BOX64 LIB PATH: BOX64 BIN PATH: ./:bin/:/bin/:/sbin/:/usr/bin/:/usr/sbin/:/userdata/:/userdata/bin/:/data/bin/:/data/bin/pcba_test/
Looking for ./openocd
argv[1]="-f"
argv[2]="./test.cfg"
argv[3]="-s"
argv[4]="scripts"
Rename process to "openocd"
Using native(wrapped) libusb-1.0.so.0
Using emulated libhidapi-hidraw.so.0
Using native(wrapped) libm.so.6
Using native(wrapped) libutil.so.1
Using native(wrapped) libdl.so.2
Using native(wrapped) libpthread.so.0
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux-x86-64.so.2
Using native(wrapped) librt.so.1
Using native(wrapped) libbsd.so.0
Using native(wrapped) libudev.so.1
Open On-Chip Debugger 0.12.0+dev-00597-ga5a30519f (2024-08-03-11:02)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : Using CMSIS-DAPv2 interface with VID:PID=0x0d28:0x0204, serial=012345ABCDEF
Error: CMSIS-DAP: SWD not supported
Do you have any troubleshooting suggestions for this?
Not sure of what is happening no. As a strater, to debug, use BOX64_LOG=2
to see every wrapped function call,It will be very chatty, but you should have all the detail you need (assuming the issue is something on a function call).
To rule out box64 dynarec issue, you can also try to run with BOX64_DYNAREC=0
to have it slowly run on interpreter.
Thank you for your suggestion.
The log is as follows:
I run
nm /usr/lib/libusb-1.0* | grep libusb_dev_mem_alloc
and it displayed:This indicates that the symbol
libusb_dev_mem_alloc
does exist.