-
Notifications
You must be signed in to change notification settings - Fork 30
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
Starting with JLink debugger or QEMU #4
Comments
config.txt
|
jlink.cfg
|
raspi4.cfg
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting with JLink debugger or QEMU (ARMv8)
Note, the openocd installed by
sudo apt-get install openocd
is not work on ubuntu 20.04. The error promptedError: invalid command name "dap"
. So you shall compile the openocd by yourself. Please refer to the link https://hackaday.io/page/4991-compiling-openocd-from-source-on-ubuntu-1604. (Though it is targetting for ubuntu 16.04, the 20.04 still follow these build steps.)1. JLink Brief
We should use the three command terminals to launch the Jlink debugger. They are openocd/telnet/gbd-multiarch separately.
40-pin gpio connect
gpio22-27 Alternative Function Assignments all are ALT4.
connect following gpio pin to jlink pin.
On the openocd command line, should type the cmd is:
On the telnet command line, should type the cmds are:
On the gdb command line, should ytpe the cmds are:
2. QEMU Brief
The QEMU is more simple and more quicker than the JLink debugger env.
On the QEMU side, just type the
qemu-system-aarch64 -machine raspi4 -nographic -kernel benos.bin -S -s
to launch the QEMU. For the gdb-multiarch side,gdb-multiarch --tui benos.elf
gdb-multiarch --tui benos.elf, the localhost port is 1234.
For the config files, you can get them by https://gist.github.com/carloscn/538d57d36b828e52bf8f88d6362b1528
The text was updated successfully, but these errors were encountered: